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.

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

Handle spurious "connection refused" when sending a uevent #254

Merged

Conversation

bobhenz-jabil
Copy link
Contributor

This error was already being handled on the connect call right above these changes, but wasn't being handled on the call to sendmsg. Depending on the timing it was possible for the connect call to succeed while the sendmsg call failed with an ECONNREFUSED error leading to the test crashing from the abort call.

This error was already being handled on the `connect` call right above
these changes, but wasn't being handled on the call to `sendmsg`.
Depending on the timing it was possible for the `connect` call to
succeed while the `sendmsg` call failed with an ECONNREFUSED error
leading to the test crashing from the abort call.
@bobhenz-jabil
Copy link
Contributor Author

@martinpitt: I'm back with another PR. Let me know if you have questions or want changes.

Copy link
Owner

@martinpitt martinpitt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @bobhenz-jabil ! The duplication is a bit annoying, but C just sucks at error handling.. 😅

I retried the (hopefully spurious) CentOS 10 failure. I don't see how python3-dnf would really disappear, this just sounds like a package mirror hiccup.

@martinpitt martinpitt merged commit 6b45ca7 into martinpitt:main Sep 15, 2024
27 checks passed
@bobhenz-jabil bobhenz-jabil deleted the fix-spurious-conn-refused-crash branch September 20, 2024 18:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants