-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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.
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
CI flake: run --preserve-fds: attach / unixpacket / bad file descriptor #6987
Labels
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
stale-issue
Comments
@QiWang19 PTAL |
edsantiago
changed the title
CI flake: attach / unixpacket / bad file descriptor
CI flake: run --preserve-fds: attach / unixpacket / bad file descriptor
Jul 15, 2020
Seeing it on f32 now. Three failures, so it caused a CI flake. @QiWang19 PTAL.
|
QiWang19
added a commit
to QiWang19/podman
that referenced
this issue
Jul 30, 2020
Test flakes mentioned in containers#6987 might be caused by uncorrect closing of file descriptor. Fix the code to close file descriptors for podman run since it may close those used by other processes. Signed-off-by: Qi Wang <[email protected]>
A friendly reminder that this issue had no activity for 30 days. |
This flake should be fixed by #7120 |
github-actions
bot
added
the
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
label
Sep 22, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
stale-issue
Flake seen three times on CI for #6958. Passed on re-run:
Log: https://api.cirrus-ci.com/v1/task/6481256420474880/logs/integration_test.log#t--podman-run---preserve-fds
This was in "test fedora-31". cirrus-flake-xref finds no other instances of this in the last three weeks.
The error looks suspiciously close to #5769 (fixed last month), but that was
exec
; this isrun
. Possibly because of #6625The text was updated successfully, but these errors were encountered: