1:59 a.m.
Detected one or more Cirrus-CI cron-triggered jobs have failed recently:
Cron build 'main' Failed: https://cirrus-ci.com/build/6025541596741632
Cron build 'v4.0' Failed: https://cirrus-ci.com/build/5231705207341056
# Source: check_cirrus_cron workflow on containers/podman.
This message was generated by an automated system. Replies to the sender will bounce, be
ignored and discarded.
8 p.m.
New subject: Cirrus-CI cron build failures on containers/podman
On 7/14/22 19:59, Do Not Reply wrote:
Detected one or more Cirrus-CI cron-triggered jobs have failed
recently:
Cron build 'main' Failed: https://cirrus-ci.com/build/6025541596741632
Cron build 'v4.0' Failed: https://cirrus-ci.com/build/5231705207341056
The '4.0' one is a flake - ignoring.
Ed,
This the failure in F36 remote sys looks important:
https://cirrus-ci.com/task/6574677626716160?logs=main#L305-L316
Seems likely something else was still "using" the infra container. In
any case, it also seems like a lot of subsequent tests depend on 'podman
rm --force to remove infra container' succeeding.
Maybe related to https://github.com/containers/podman/issues/14929 ?
--
Chris Evich (he/him), RHCA III
Senior Quality Assurance Engineer
My personal robot overlord told me to include this signature line.
433
days inactive
434
days old
podman-monitor@lists.podman.io
1 comments
2 participants
participants (2)
-
Chris Evich -
Do Not Reply