Actions
action #10368
closedimprove use of timeout in "assert_screen"
Start date:
2016-01-22
Due date:
% Done:
0%
Estimated time:
Description
from
https://progress.opensuse.org/issues/10138#note-9
- no match could mean it exited early from the loop because the screen did not change at all --> check in source code and try to improve log message
- no match 2 and then fail could mean an "off-by-one" incorrectness, return from the loop in the second-to-last run not the last run --> crosscheck and potentially improve
Updated by okurz about 8 years ago
@coolo, RBrownSUSE: which of the two have been done?
Updated by coolo about 8 years ago
- Status changed from New to Resolved
Since 38cfc5edcbcc56efd35997e5c457a1af1aadbf7c the output is predictable - every other jump you see is a CPU stall
Actions