Add an explicit run of the cron jobs #2577
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Validation run https://tortuga.suse.de/tests/1841#step/force_cron_run/3 |
okurz
reviewed
Mar 22, 2017
| @@ -620,6 +620,7 @@ sub load_consoletests() { | |||
| loadtest "console/xorg_vt"; | |||
| } | |||
| loadtest "console/zypper_lr"; | |||
| loadtest "console/force_cron_run"; | |||
There was a problem hiding this comment.
could you extract more common code?
There was a problem hiding this comment.
between the main.pms? Possibly a future me
Our data shows pretty clear that the tests type much more unreliable around the time the first cron.weekly is called (*/15) - and it's believed that the btrfs maintenance is killing responsiveness as described in boo#1017461 (and others). So better run these cron jobs at a given time to avoid random tests becoming unreproducible
dzedro
approved these changes
Mar 22, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Our data shows pretty clear that the tests type much more unreliable
around the time the first cron.weekly is called (*/15) - and it's
believed that the btrfs maintenance is killing responsiveness
as described in boo#1017461 (and others). So better run these
cron jobs at a given time to avoid random tests becoming unreproducible