Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ci-rhel-integration failing #6522

Closed
haircommander opened this issue Jan 11, 2023 · 2 comments
Closed

ci-rhel-integration failing #6522

haircommander opened this issue Jan 11, 2023 · 2 comments
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@haircommander
Copy link
Member

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

https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/cri-o_cri-o/6514/pull-ci-cri-o-cri-o-main-ci-rhel-integration/1613166564008267776

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
@haircommander haircommander added the kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. label Jan 11, 2023
@haircommander haircommander mentioned this issue Jan 11, 2023
Merged
@jlojosnegros jlojosnegros mentioned this issue Jan 30, 2023
Merged
@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 11, 2023
@github-actions
Copy link

Closing this issue since it had no activity in the past 90 days.

@github-actions github-actions bot added the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label May 13, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@haircommander