action #46397
closed[functional][u] test fails in force_scheduled_tasks because the btrfs maintenance tasks already triggered before *we* triggered them, just wait longer in the script call?
0%
Description
Updated by okurz over 5 years ago
- Status changed from Workable to In Progress
- Assignee set to okurz
Retriggered as https://openqa.suse.de/tests/2387371 failed reproducibly in the same step. I labeled with bsc#1063638
Updated by okurz over 5 years ago
- Status changed from In Progress to Workable
- Assignee deleted (
okurz) - Priority changed from High to Normal
Updated by okurz over 5 years ago
- Subject changed from [functional][u][ppc64le] test fails in force_scheduled_tasks because the btrfs maintenance tasks already triggered before *we* triggered them, just wait longer in the script call? to [functional][u] test fails in force_scheduled_tasks because the btrfs maintenance tasks already triggered before *we* triggered them, just wait longer in the script call?
- Priority changed from Normal to High
Looks like the same on openSUSE x86_64: https://openqa.opensuse.org/tests/835195#step/force_scheduled_tasks/8
Updated by jorauch over 5 years ago
- Status changed from Workable to In Progress
- Assignee set to jorauch
Taking a look
Updated by jorauch over 5 years ago
Foursixnine proposed a timeout of 2 Minutes.
Also the ticket is in a terrible state for a high priority, it has no AC, one suggestion in the header and no real description whats going on
Updated by jorauch over 5 years ago
- Status changed from In Progress to Feedback
PR with increased timeout:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6657
Updated by okurz over 5 years ago
jorauch wrote:
Also the ticket is in a terrible state for a high priority, it has no AC, one suggestion in the header and no real description whats going on
Do you really need more information in the ticket to start on the suggestion from the subject line? Anyway, it's good to realize this and make the ticket properly workable first then. If needed bring it up with the team, e.g. in the daily.
Updated by okurz over 5 years ago
- Status changed from Feedback to Resolved
Merged. Hard to verify if this is really enough. Let's just assume it is ok and call it resolved. We can reopen in case this would not be effective in all cases
Updated by okurz about 5 years ago
- Related to action #46835: [functional][u] test fails in force_scheduled_tasks: timeout added