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/5214931904626688
Cron build 'v3.2.3-rhel' Failed: https://cirrus-ci.com/build/6628372087308288
Cron build 'multiarch' Failed: https://cirrus-ci.com/build/5036542451253248
Cron build 'main' Failed: https://cirrus-ci.com/build/5160065173815296
# 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.
2:53 p.m.
New subject: Cirrus-CI cron build failures on containers/podman
On 6/13/22 19:59, Do Not Reply wrote:
Cron build 'v3.3.1-rhel' Failed:
https://cirrus-ci.com/build/5214931904626688
Ewww, haven't seen this before. Re-ran and will monitor for success.
Cron build 'v3.2.3-rhel' Failed:
https://cirrus-ci.com/build/6628372087308288
Odd 'not ok 204 podman networking: port on localhost' failure, possible
flake. Re-ran and will monitor for success.
Cron build 'multiarch' Failed:
https://cirrus-ci.com/build/5036542451253248
A "hello" image flake (I think it's a buildah problem). Re-ran the job.
Cron build 'main' Failed:
https://cirrus-ci.com/build/5160065173815296
Fixed by https://github.com/containers/podman/pull/14592
--
Chris Evich (he/him), RHCA III
Senior Quality Assurance Engineer
My personal robot overlord told me to include this signature line.
114
days inactive
115
days old
podman-monitor@lists.podman.io
1 comments
2 participants
participants (2)
-
Chris Evich -
Do Not Reply