How long has Travis CI been behaving this way? Has the problem gotten worse
recently?

On Wed, Sep 23, 2020 at 11:38 AM Oleg Kalnichevski <[email protected]> wrote:

> Folks
>
> Travis CI jobs have been failing en masse with the same error.
>
> Has anyone ever seen this kind of test failure locally?
>
> Please help me out.
>
> Oleg
>
>
> On Sat, 2020-09-19 at 13:16 +0200, Oleg Kalnichevski wrote:
> > Folks
> >
> > There is an extremely annoying bug in HTTP/1.1 Reactive test cases
> > that
> > causes intermittent test failures in Travis CI.
> >
> > No matter what I do I am unable to reproduce this failure locally or
> > on
> > ASF Jenkins.
> >
> > Did anyone see this kind of test failure in their local environment?
> > It
> > _might_ be platform / OS related.
> >
> > I am running Ubuntu 20.04.1 LTS.
> >
> > Oleg
> >
> > ---
> > [ERROR] testSequentialHeadRequests[HTTP/1.1
> > http](org.apache.hc.client5.testing.async.TestHttp1Reactive)  Time
> > elapsed: 0.013 s  <<< ERROR!
> > java.lang.RuntimeException: java.io.InterruptedIOException
> > Caused by: java.io.InterruptedIOException
> > [INFO] Running
> > org.apache.hc.client5.testing.async.TestHttpAsyncMinimal
> > [INFO] Tests run: 28, Failures: 0, Errors: 0, Skipped: 0, Time
> > elapsed: 5.927 s - in
> > org.apache.hc.client5.testing.async.TestHttpAsyncMinimal
> > [INFO]
> > [INFO] Results:
> > [INFO]
> > [ERROR] Errors:
> > [ERROR]   TestHttp1Reactive>AbstractHttpReactiveFundamentalsTest.test
> > SequentialHeadRequests:114-
> > >AbstractHttpReactiveFundamentalsTest.publisherToString:267-
> > >AbstractHttpReactiveFundamentalsTest.publisherToByteArray:279 ยป
> > Runtime
> > [INFO]
> > [ERROR] Tests run: 366, Failures: 0, Errors: 1, Skipped: 1
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to