Re: Failing tracing systests on master

Hey Colm, Have hard time reproducing these failures. Nothing shows up on Jenkins https://builds.apache.org/job/CXF-Trunk-JDK18/3629/, passing for me locally as well. Do you see them failing all the time, or more like intermittent failures? Thanks! Best Regards, Andriy Redko COh> Hi all,

Re: What about adding WebClient#patch ?

It is good question actually, the JAXRS 2.1 API (SyncInvoker) does not have patch() either, I think we could add one to WebClient, won't harm. Not sure about USE_ASYNC though, we may have to keep it for backward compatiblity, no? Best Regards, Andriy Redko On Mon, Aug 13, 2018, 10:08 AM Fra

Re: Failing tracing systests on master

Hey Colm, Yes, I will take a look tonight, thanks! Best Regards, Andriy Redko On Tue, Aug 14, 2018, 7:01 AM Colm O hEigeartaigh wrote: > Hi all, > > Following some of the recent upgrades the tracing systests are failing on > master for me: > > [ERROR] Failures: > [ERROR] > > BraveTracingTe

Failing tracing systests on master

Hi all, Following some of the recent upgrades the tracing systests are failing on master for me: [ERROR] Failures: [ERROR] BraveTracingTest.testThatNewSpanIsCreatedWhenNotProvidedUsingAsyncClient:236->Assert.assertThat:923->Assert.assertThat:956 Expected: <3> but: was <5> Can someone take

[GitHub] coheigea closed pull request #434: NPE when annotations bundle found but not active

coheigea closed pull request #434: NPE when annotations bundle found but not active URL: https://github.com/apache/cxf/pull/434 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign

[GitHub] coheigea commented on issue #434: NPE when annotations bundle found but not active

coheigea commented on issue #434: NPE when annotations bundle found but not active URL: https://github.com/apache/cxf/pull/434#issuecomment-412828625 Looks good thanks This is an automated message from the Apache Git Service.