action #12110
closedgnome_control_center: short timeout on details caused test to fail
0%
Description
observation¶
gnome_control_center fails as there is no details displayed as expected, e.g. see https://openqa.suse.de/tests/396384
problem¶
It seems like in staging we see issue with short timeout set to 3 so the the needle does not match to the expected results.
suggestions¶
perhaps increase the timeout however that is a bad solution.
should we monitor system resources to get the better picture instead of just increasing timeouts?
Updated by okurz over 8 years ago
- Subject changed from gnome_control_center: short timeout on details caued test to fail to gnome_control_center: short timeout on details caused test to fail
- Description updated (diff)
- sounds like a very good idea to me.
git grep 'assert_screen.*, [0-9];' yields still a whole lot of locations where we use assert_screen with a pretty low timeout, e.g. in x11 regression tests. We could set them all back to the default of 30 but I prefer to keep them and rather handle these failures accordingly. Interlinked to #12064
Updated by okurz over 8 years ago
- Related to action #12064: Improved logging for debugging performance related issues added
Updated by okurz over 8 years ago
- Status changed from New to In Progress
Updated by okurz over 8 years ago
- Status changed from In Progress to Resolved
fixed with https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/1574
The idea in https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/1437 was deemed to be too complicated. The common understanding is: openQA is not really suitable for checking performance regressions by relying on hard timeouts. A better approach might be to read out the match times from the log files or add this data to some result files from which nice graphs could be rendered and such. For the issue at hand: Solved.