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?
Added by okurz over 5 years ago.
Updated over 5 years ago.
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 23
Description
Observation¶
openQA test in scenario sle-15-SP1-Installer-DVD-ppc64le-allpatterns@ppc64le fails in
force_scheduled_tasks
Reproducible¶
Fails since (at least) Build 22.7
Expected result¶
Last good: Build 143.1
Further details¶
Always latest result in this scenario: latest
- Status changed from Workable to In Progress
- Assignee set to okurz
- Status changed from In Progress to Workable
- Assignee deleted (
okurz)
- Priority changed from High to Normal
- 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
- Status changed from Workable to In Progress
- Assignee set to jorauch
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
- Status changed from In Progress to Feedback
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.
- 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
- Related to action #46835: [functional][u] test fails in force_scheduled_tasks: timeout added
Also available in: Atom
PDF