action #30700
closed
[sle][functional][sporadic][medium][sle12 sp4] test fails in memtest
Added by zluo over 6 years ago.
Updated over 6 years ago.
Category:
Bugs in existing tests
- Subject changed from [sle][functional][sle12 sp4] test fails in memtest to [sle][functional][sporadic][sle12 sp4] test fails in memtest
- Description updated (diff)
- Due date set to 2018-02-27
- Status changed from New to Blocked
- Assignee set to okurz
- Target version set to Milestone 14
All failed tests I could find where happening on openqaworker10 which has some issues currently, see #30388 . That worker has been taken offline so should not pose a problem for now. The failed tests looked like "nearly done" and then went into timeout. I assume it's worker related so waiting for the resolution in #30388 first.
- Blocked by action #30388: [qam] openqaworker10:4 - worker fail all tests - qemu instances are left behind added
- Status changed from Blocked to In Progress
- Blocked by deleted (action #30388: [qam] openqaworker10:4 - worker fail all tests - qemu instances are left behind)
- Related to action #30388: [qam] openqaworker10:4 - worker fail all tests - qemu instances are left behind added
16/20 passed, 4 incompleted because of other reasons -> #30388
- Status changed from In Progress to Resolved
We have all-green memtest unless for worker problems, e.g. to be tracked in #30388, done here.
- Subject changed from [sle][functional][sporadic][sle12 sp4] test fails in memtest to [sle][functional][sporadic][medium][sle12 sp4] test fails in memtest
Also available in: Atom
PDF