jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Philippe Mouawad <pmoua...@apache.org>
Subject Re: Build failed in Jenkins: JMeter-trunk #7296
Date Mon, 12 Aug 2019 21:23:06 GMT
AFAIR The test was stable before migration to gradle.

Maybe more parallelism in test lead to such instabilities.

I don’t think it should be disabled

Regards

On Monday, August 12, 2019, sebb <sebbaz@gmail.com> wrote:

> On Mon, 12 Aug 2019 at 21:09, Vladimir Sitnikov
> <sitnikov.vladimir@gmail.com> wrote:
> >
> > TL;DR:
> >
> > org.apache.jmeter.samplers.TestSampleResult > testSubResultsFalsePause
> FAILED
> >     java.lang.AssertionError: TestElapsed: 424 -  ParentElapsed: 401
> > => 23 not in [0,16]; nanotime=false
> >         at org.junit.Assert.fail(Assert.java:88)
> >         at org.apache.jmeter.samplers.TestSampleResult.testSubResults(
> TestSampleResult.java:292)
> >         at org.apache.jmeter.samplers.TestSampleResult.testSubResults(
> TestSampleResult.java:198)
> >         at org.apache.jmeter.samplers.TestSampleResult.
> testSubResultsFalsePause(TestSampleResult.java:181)
> >
> >
> >
> >
> > Should we disable the test?
>
> Only if it cannot be fixed or it serves no purpose.
>
> > Can we write the test in such a way that it does not break half of the
> > times in CI?
>
> Increase the time limit?
>
> > Is the test doing any good for us?
> >
> > It is really annoying to have flaky tests for little reason.
>
> Timing tests are always tricky to get right, but that does not mean
> they are not useful.
>
> Maybe it can be reworked so that it allows for a slower system.
>
> > Vladimir
> >
> > пн, 12 авг. 2019 г. в 23:02, Apache Jenkins Server <
> > jenkins@builds.apache.org>:
> >
> > > See <https://builds.apache.org/job/JMeter-trunk/7296/display/redirect>
> > >
> > >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message