Actions
action #37628
closedFlaky scheduler test: 'Simulation of heavy unstable load' at t/05-scheduler-full.t
Start date:
2018-06-21
Due date:
% Done:
0%
Estimated time:
Description
Sometimes we get that scheduler-full test failing:
ok 38 - Scheduler clock got reset
# Running scheduler step
$VAR1 = [];
ok 39 - timeout in range 1000->3000 (setted tick 2000, real tick occurred at 2002)
ok 40 - Tick is at the expected value (4000) (failures 1) (no_actions 1)
ok 41 - All failed allocation on second step - workers were killed
not ok 42 - Failure count(1) should be >=8, since we took too much time to schedule
# Failed test 'Failure count(1) should be >=8, since we took too much time to schedule'
# at t/05-scheduler-full.t line 261.
ok 43 - Tick is at the expected value
Updated by okurz over 5 years ago
- Status changed from New to Resolved
- Assignee set to okurz
I do not recall seeing this while tracking flaky tests. Not feeling very confident but 577a921a1 with a remove of d-bus or 535f87443 , a bigger restructuring, could have fixed this.
Updated by okurz over 5 years ago
https://github.com/os-autoinst/openQA/pull/2259 to remove "travis_retry" again after test stabilization – and proper testing in the PR
Updated by andriinikitin about 5 years ago
Btw after this fix the test is stable for me so far https://github.com/os-autoinst/openQA/commit/e57598c0767b7fffa3fd8f9cda20ec089e9d25af#diff-6e6080618fd44df22643c71cdaaacc35R148
Actions