Hi Romain,
Run the test suite probably few dozen times on Windows and Ubuntu boxes, got it
failing a few times on Ubuntu (but no failures on Windows):
[INFO] RequestHandlerClass from context returned
com.github.tomakehurst.wiremock.http.AdminRequestHandler. Normalized mapped
under returned 'null'
[ERROR] Tests run: 145, Failures: 1, Errors: 0, Skipped: 1, Time elapsed:
90.181 s <<< FAILURE! - in TestSuitealized mapped under returned 'null'
[ERROR]
testAsyncInvocationInterceptorProvider(org.eclipse.microprofile.rest.client.tck.asynctests.AsyncMethodTest)
Time elapsed: 0.103 s <<< FAILURE!
java.lang.AssertionError: expected [80] but found [null]
at
org.eclipse.microprofile.rest.client.tck.asynctests.AsyncMethodTest.testAsyncInvocationInterceptorProvider(AsyncMethodTest.java:235)
[INFO]
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR]
AsyncMethodTest>Arquillian.run:138->testAsyncInvocationInterceptorProvider:235
expected [80] but found [null]
[INFO]
[ERROR] Tests run: 145, Failures: 1, Errors: 0, Skipped: 1
[INFO]
Yes, you are right, the test is non-deterministic. Trying to understand what is
going on, may take some time.
Thanks for noticing it.
Best Regards,
Andriy Redko
RMB> Hi Andriy,
RMB> Result is random but it is
RMB>
org.eclipse.microprofile.rest.client.tck.asynctests.AsyncMethodTest.testAsyncInvocationInterceptorProvider
RMB> Le dim. 2 juin 2019 à 19:12, Andriy Redko <[email protected]> a écrit :
RMB> Hi Romain,
RMB> Yes, the async flows are difficult to test, which test cases for MP rest
client are
RMB> intermittently failing for you? I would be able to take a look. Thanks.
RMB> Best Regards,
RMB> Andriy Redko
RMB>> Hi everyone,
RMB>> I just realize - thanks for failling test on jenkins, that part of the
test
RMB>> suite is not deterministic.
RMB>> It mainly affects async calls. I found some opentracing ones - fixed by
RMB>>
https://github.com/apache/cxf/pull/561/commits/23cbbb9db73a74913fd4294f805032f923ffcf09
RMB>> -
RMB>> and there are some in MP rest client TCK (async interceptor provider).
RMB>> I didn't dig deep into the root cause but I suspect we ack the client
RMB>> before the full chain is processed on the server side.
RMB>> Does it ring any bell to anyone?
RMB>> Romain Manni-Bucau
RMB>> @rmannibucau <https://twitter.com/rmannibucau> | Blog
RMB>> <https://rmannibucau.metawerx.net/> | Old Blog
RMB>> <http://rmannibucau.wordpress.com> | Github
<https://github.com/rmannibucau> |
RMB>> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
RMB>>
<https://www.packtpub.com/application-development/java-ee-8-high-performance>
