Project

General

Profile

Actions
Copy link

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 about 5 years ago. Updated about 5 years ago.

Status:
Resolved
Priority:
High
Assignee:
jorauch
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 23
Start date:
2019-01-18
Due date:
% Done:

0%

Estimated time:
Difficulty:

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

Related issues 1 (0 open — 1 closed)

Related to openQA Tests - action #46835: [functional][u] test fails in force_scheduled_tasks: timeoutResolvedokurz2019-01-292019-02-18

Actions
Actions
Copy link
 #1

Updated by okurz about 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

Actions
Copy link
 #2

Updated by okurz about 5 years ago

  • Status changed from In Progress to Workable
  • Assignee deleted (okurz)
  • Priority changed from High to Normal
Actions
Copy link
 #3

Updated by okurz about 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
Actions
Copy link
 #4

Updated by jorauch about 5 years ago

  • Status changed from Workable to In Progress
  • Assignee set to jorauch

Taking a look

Actions
Copy link
 #5

Updated by jorauch about 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

Actions
Copy link
 #6

Updated by jorauch about 5 years ago

  • Status changed from In Progress to Feedback
Actions
Copy link
 #7

Updated by okurz about 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.

Actions
Copy link
 #8

Updated by okurz about 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

Actions
Copy link
 #9

Updated by okurz about 5 years ago

  • Related to action #46835: [functional][u] test fails in force_scheduled_tasks: timeout added
Actions
Copy link

Also available in: Atom PDF