6:14 p.m.
Detected one or more Cirrus-CI cron-triggered jobs have failed recently:
Cron build 'v3.0' Failed: https://cirrus-ci.com/build/5836083164348416
# 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.
9:49 a.m.
New subject: Cirrus-CI cron build failures on containers/podman
On 3/7/21 7:14 PM, Do Not Reply wrote:
Detected one or more Cirrus-CI cron-triggered jobs have failed
recently:
Cron build 'v3.0' Failed: https://cirrus-ci.com/build/5836083164348416
restarted test:
https://cirrus-ci.com/task/5203160210866176?command=main#L1068
Another 'bind: address already in use' flake on 'test_start_containers'.
This one seems to be flaking quite a bit. Anyone know how to make
this test try a different port and/or find/kill whatever is bound to 8889???
--
Chris Evich (he/him), RHCA III
Senior Quality Assurance Engineer
If it ain't broke, yain't tryin' hard 'nough.
932
days inactive
932
days old
podman-monitor@lists.podman.io
1 comments
2 participants
participants (2)
-
Chris Evich -
Do Not Reply