jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Felix Schumacher <felix.schumac...@internetallee.de>
Subject Re: Jenkins build became unstable: JMeter-trunk #7180
Date Sat, 18 May 2019 10:39:05 GMT

Am 18.05.19 um 11:38 schrieb Philippe Mouawad:
> Hello Felix,
> Ok by me.

Changed.

 Felix

>
> Regards
>
> On Saturday, May 18, 2019, Felix Schumacher <
> felix.schumacher@internetallee.de> wrote:
>
>> Am 17.05.19 um 20:15 schrieb Apache Jenkins Server:
>>> See <https://builds.apache.org/job/JMeter-trunk/7180/display/
>> redirect?page=changes>
>>
>> The tests failed on TestSampleResult:
>>
>>
>>         Error
>>
>> ParentElapsed: 408 - sum(samples): 400 = 8 not in [0,3]; nanotime=true
>>
>>
>>         Stacktrace
>>
>> junit.framework.AssertionFailedError: ParentElapsed: 408 - sum(samples):
>> 400 = 8 not in [0,3]; nanotime=true
>> at
>> org.apache.jmeter.samplers.TestSampleResult.testSubResults(
>> TestSampleResult.java:283)
>> at
>> org.apache.jmeter.samplers.TestSampleResult.testSubResults(
>> TestSampleResult.java:198)
>> at
>> org.apache.jmeter.samplers.TestSampleResult.testSubResultsTruePause(
>> TestSampleResult.java:171)
>>
>> This looks like the test machine was a bit too slow for the test. Should
>> we give the test a bit more leeway?
>>
>> I am thinking of changing the values from (3, 16) to (10, 16).
>>
>> Felix
>>
>

Mime
View raw message