denylist: bump snooze for kdump.crash and drop extensions.module #2284
Conversation
kola-denylist.yaml
Outdated
| @@ -46,7 +46,7 @@ | |||
| snooze: 2023-03-10 | |||
| - pattern: ext.config.extensions.module | |||
| tracker: https://github.com/coreos/fedora-coreos-tracker/issues/1420 | |||
| snooze: 2023-03-08 | |||
| snooze: 2023-03-22 | |||
There was a problem hiding this comment.
did ext.config.extensions.module fail?
There was a problem hiding this comment.
No, it did not yet. I bumped the snooze seeing the issue is still open.
There was a problem hiding this comment.
The issue just needs an update. The snooze is the mechanism by which it gets updated. If the test is passing now then the issue can be updated and closed and this snooze dropped.
| @@ -58,7 +58,7 @@ | |||
| - next | |||
| - pattern: ext.config.kdump.crash | |||
| tracker: https://github.com/coreos/fedora-coreos-tracker/issues/1430 | |||
| snooze: 2023-03-08 | |||
| snooze: 2023-03-22 | |||
There was a problem hiding this comment.
did ext.config.kdump.crash fail?
did it fail on more than one stream?
If it failed on next-devel let's add next to the list of streams below since we'll be releasing f38 content on next soon.
There was a problem hiding this comment.
Yes, it failed on next-devel, so will add next to it.
gursewak1997
changed the title
|
Usually what I would do here is update coreos/fedora-coreos-tracker#1420 with the new information, then add a commit here dropping the snooze and linking to that and ultimately closing the issue when it merges. Bumping the snooze for the separate test would be in a different (2nd) commit (with a different rationale in the commit message). |
We are still waiting on updates for #1430 so bumping the snooze for
kdump.crash for now. Also droppingext.config.extensions.module` from denylist as the test passes in rawhide now.Closes: coreos/fedora-coreos-tracker#1420