Hi Ryan
The ReactiveClientTest has been failing intermittently for some time
now. It only happens with HTTP/2 transport and it mostly happens with
Travis CI. Travis CI has been very effective in reproducing all sorts
of synchronization issues and race conditions in the past.
Given this is relatively new code and there are no other failing
integration tests I tend to suspect this is due to a race condition in
the Reactive Streams message handlers.
Would you have time to take a look?
Cheers
Oleg
[ERROR]
testLongRunningRequest[FORCE_HTTP_2](org.apache.hc.core5.testing.reactive.ReactiveClientTest)
Time elapsed: 30.032 s <<< ERROR!
java.lang.RuntimeException: org.apache.hc.core5.http2.H2StreamResetException:
Timeout due to inactivity (30 SECONDS)
at
org.apache.hc.core5.testing.reactive.ReactiveClientTest.testLongRunningRequest(ReactiveClientTest.java:302)
Caused by: org.apache.hc.core5.http2.H2StreamResetException: Timeout due to
inactivity (30 SECONDS)
https://travis-ci.org/apache/httpcomponents-core/jobs/440564812#L3351
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
