[functional][bsc#1063638][u] soft fail in force_cron_run is too strict
openQA test in scenario sle-15-Leanos-DVD-Staging:G-x86_64-gnome@64bit-staging fails in
but the mentioned bug in the soft fail should be already fixed.
Probably the check is too strict.
[25 Sep 2017 09:59:15] <okurz> coolo: https://openqa.opensuse.org/tests/491791#step/force_cron_run/6 looks to me as if it won't get any better [25 Sep 2017 10:22:17] <coolo> okurz: one way could be settling load *before* the crons? [25 Sep 2017 10:22:31] <coolo> but havig a load of 0.3 for unused X sounds like a bug - a different one though :) [25 Sep 2017 10:27:19] <okurz> hm, settle load before crons, execute them, check again, that could work. I wonder though if you have a good test scenario in mind which one could trigger 500 times to check if the bug is really solved or another one stopping us now
Always latest result in this scenario: latest
#10 Updated by okurz over 2 years ago
- Subject changed from [functional]soft fail in force_cron_run is too strict to [functional][bsc#1063638]soft fail in force_cron_run is too strict
- Due date changed from 2018-02-13 to 2018-05-15
- Status changed from New to Blocked
- Target version changed from Milestone 13 to Milestone 15
Now test tracks bsc#1063638, will set ticket to blocked and review progress on bug later.
#12 Updated by StefanBruens over 2 years ago
Currently settle_load reports any time above 30 seconds as a softfailure, which is too short IMHO:
- load average (first value) is a 1 minute sliding window average. Even for a completely idle system this value can be arbitrarily large for any time < 1 minute.
- force_cron_run is executed immediately after boot, some large values (>>= 1) in the window are to be expected
- starting top will likely contribute to the load (once), as processes waiting for disk I/O contribute to the load value.
A timeout of 70 seconds (60 seconds window plus startup) is likely more appropriate.
#16 Updated by okurz about 2 years ago
- Subject changed from [functional][bsc#1063638][u]soft fail in force_cron_run is too strict to [functional][bsc#1063638][u] soft fail in force_cron_run is too strict
- Status changed from Blocked to Workable
- Assignee deleted (
- Target version changed from Milestone 15 to Milestone 16
#24 Updated by zluo about 2 years ago
#27 Updated by zluo about 2 years ago
- Status changed from Feedback to Resolved
test results on osd: