-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
TEST-82-SOFTREBOOT is flaky in Github Actions #32834
Comments
yuwata
added a commit
to yuwata/systemd
that referenced
this issue
May 17, 2024
Otherwise, at the time systemd-soft-reboot.service succeeds, services which has Conflicts= and Before=soft-reboot.target may not be stopped yet, and may be SIGKILLed. Especially, systemd-journald.service has the dependencies, thus journal may be corrupted. See systemd#32223. Follow-up for 13ffc60. Fixes systemd#32834
yuwata
added a commit
to yuwata/systemd
that referenced
this issue
May 17, 2024
Otherwise, at the time systemd-soft-reboot.service succeeds, services which has Conflicts= and Before=soft-reboot.target may not be stopped yet, and may be SIGKILLed. Especially, systemd-journald.service has the dependencies, thus journal may be corrupted. See systemd#32223. Follow-up for 13ffc60. Fixes systemd#32834.
Still failed.
|
yuwata
added a commit
to yuwata/systemd
that referenced
this issue
May 18, 2024
Workaround for systemd#32834.
yuwata
added a commit
to yuwata/systemd
that referenced
this issue
May 18, 2024
Workaround for systemd#32834 and systemd#32890.
After #32975, the test fails again:
|
That seems a race between journald and journalctl, and not an issue in soft-reboot:
|
yuwata
added a commit
to yuwata/systemd
that referenced
this issue
May 24, 2024
This was referenced May 24, 2024
mwilck
pushed a commit
to mwilck/systemd
that referenced
this issue
May 28, 2024
Workaround for systemd#32834 and systemd#32890. (cherry picked from commit a610ba0)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
systemd version the issue has been seen with
main
Used distribution
No response
Linux kernel version used
No response
CPU architectures issue was seen on
None
Component
No response
Expected behaviour you didn't see
No response
Unexpected behaviour you saw
https://github.com/systemd/systemd/actions/runs/9091034899/job/24984872166?pr=32833
Steps to reproduce the problem
No response
Additional program output to the terminal or log subsystem illustrating the issue
The text was updated successfully, but these errors were encountered: