-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Closed as not planned
Labels
kind/failing-testCategorizes issue or PR as related to a consistently or frequently failing test.Categorizes issue or PR as related to a consistently or frequently failing test.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.Denotes an issue or PR has remained open with no activity and has become stale.
Description
Which jobs are failing?
ci-rhel-integration
Which tests are failing?
not ok 19 checkpoint and restore one container into a new pod (drop infra:false)
not ok 253 seccomp notifier with runtime/default
not ok 254 seccomp notifier with runtime/default but not stop
not ok 255 seccomp notifier with custom profile
Since when has it been failing?
Since before the winter break
Testgrid link
Reason for failure (if possible)
the seccomp issues are something to do with the libseccomp version I think (uncomfirmed). I've only just realized there's a checkpoint issue too
Anything else we need to know?
No response
Metadata
Metadata
Assignees
Labels
kind/failing-testCategorizes issue or PR as related to a consistently or frequently failing test.Categorizes issue or PR as related to a consistently or frequently failing test.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.Denotes an issue or PR has remained open with no activity and has become stale.