6:59 p.m.
Detected one or more Cirrus-CI cron-triggered jobs have failed recently:
Cron build 'v3.3.1-rhel' Failed: https://cirrus-ci.com/build/6048749137952768
Cron build 'v3.2.3-rhel' Failed: https://cirrus-ci.com/build/6494423331635200
Cron build 'main' Failed: https://cirrus-ci.com/build/5200739822731264
# 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.
11:28 a.m.
New subject: Cirrus-CI cron build failures on containers/podman
On 6/9/22 19:59, Do Not Reply wrote:
Cron build 'v3.3.1-rhel' Failed:
https://cirrus-ci.com/build/6048749137952768
Looks like a Cirrus internal flake. Re-ran.
Cron build 'main' Failed:
https://cirrus-ci.com/build/5200739822731264
Fix: https://github.com/containers/podman/pull/14521
Cron build 'v3.2.3-rhel' Failed:
https://cirrus-ci.com/build/6494423331635200
Appears like some kind of execution flake. Ignoring it (first time I've
seen it) because it's a negative test:
[+0862s] not ok 182 podman corrupt images - system reset
...cut...
time="2022-06-09T19:48:52Z" level=error msg="failed to kill 53967"
--
Chris Evich (he/him), RHCA III
Senior Quality Assurance Engineer
My personal robot overlord told me to include this signature line.
240
days inactive
241
days old
podman-monitor@lists.podman.io
1 comments
2 participants
participants (2)
-
Chris Evich -
Do Not Reply