sdnotify doesn't work on aarch64 #15277
Labels
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
|
Link to sample log (weeks old) |
|
A friendly reminder that this issue had no activity for 30 days. |
edsantiago
added a commit
to edsantiago/libpod
that referenced
this issue
Sep 21, 2022
Background: in order to add aarch64 tests, we had to add emergency skips to a lot of failing tests. No attempt was ever made to understand why they were failing. Fast forward to today, I filed containers#15888 just to see if tests are still failing. Looks like a number of them are fixed. (Yes, magically). Remove those skips. See: containers#15074, containers#15277 Signed-off-by: Ed Santiago <[email protected]>
|
The Code Fairy came and fixed this while we were distracted. |
github-actions
bot
added
the
locked - please file new issue/PR
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Looks like
socatnever picks up anything on the socket, so sdnotify tests fail. Seeing this right now in @vrothberg's #15248, and we saw it in #14801 (the PR that enabled aarch64 testing) but just did a blanketskipbecause there was so much stuff that was broken. Amid the confusion, I neglected to file an issue for this.Someone will need to
get_ci_vmto figure out details, but basically, the gist seems to be thatsdnotifycontainerdoes not work.The text was updated successfully, but these errors were encountered: