action #97832
closed
[security][qem][maint][journald_fss] test fails in journald_fss - flaky failures in QEM aggregate tests
Added by vsvecova over 3 years ago.
Updated almost 3 years ago.
Category:
Bugs in existing tests
- Has duplicate action #98508: [security][qem] journald corruption on s390x - journald_fss test fails often on s390x added
- Subject changed from [qem][maint][journald_fss] test fails in journald_fss - flaky failures in QEM aggregate tests to [security][qem][maint][journald_fss] test fails in journald_fss - flaky failures in QEM aggregate tests
journald_fss.pm module mentions it being developed by QE Security, being FIPS/forward secure sealing related.
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: mau-extratests2
https://openqa.suse.de/tests/7546447
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
I just wonder will QEM team take this poo and fix it?
- Assignee set to bchou
- Estimated time set to 12.00 h
- Status changed from New to In Progress
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
- Estimated time changed from 12.00 h to 8.00 h
Also available in: Atom
PDF