-
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
Yet another missing-logs-and-events flake: journald? #24220
Comments
A friendly reminder that this issue had no activity for 30 days. |
Two on Thursday, but not remote, so I don't know if they're the same bug or something new. The total so far:
|
This one is blowing up, and I'm tentatively blaming it on the recent VM update. Issue title changed accordingly.
|
cirrus-vm-get-versions, trimmed to remove packages that can't possibly (?) be causing this. New:
...and old (
(I can't use the script's Interesting observation: when we see this fail in system tests, it's often in the serial tests (the first pass). That points against it being a high-system-load issue. So far, no luck reproducing on 1mt. |
Get new systemd on rawhide, see what happens with containers#24220 Built in : containers/automation_images#394 Signed-off-by: Ed Santiago <[email protected]>
Get new systemd-257~rc1 on rawhide, see what happens with containers#24220 Built in : containers/automation_images#394 Signed-off-by: Ed Santiago <[email protected]>
I guess this isn't too shocking, but flake is now showing up in APIv2 tests:
|
Get new systemd on rawhide, see what happens with containers#24220 Built in : containers/automation_images#394 Signed-off-by: Ed Santiago <[email protected]>
I've lost track of how many bugs I've opened for something-or-other like this. I'm going to lump together here the category of flakes seen in late 2024 where
podman-remote logs
is supposed to see something but doesn't.Likely fix: change the tests so instead of
podman wait; podman logs
they dofor 5 retries { podman logs; grep for what we want; retry if not there
.The text was updated successfully, but these errors were encountered: