7 p.m.
Detected one or more Cirrus-CI cron-triggered jobs have failed recently:
Cron build 'main' Failed: https://cirrus-ci.com/build/6167703365877760
Cron build '1.21' Failed: https://cirrus-ci.com/build/6293777433231360
# Source: check_cirrus_cron workflow on containers/buildah.
This message was generated by an automated system. Replies to the sender will bounce, be
ignored and discarded.
10:19 a.m.
New subject: Cirrus-CI cron build failures on containers/buildah
On 12/15/21 19:00, 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/6167703365877760
Unit test failure:
[+2687s] === RUN TestGetPermissionErrorNoChroot/ignore=false
[+2687s] copier_linux_test.go:148:
[+2687s] Error Trace: copier_linux_test.go:148
[+2687s] Error: Should be true
[+2687s] Test: TestGetPermissionErrorNoChroot/ignore=false
[+2687s] Messages: expected the error (exit status 1: error
encoding request for copier subprocess: write |1: broken pipe) to be a
permission error
[+2687s] === RUN TestGetPermissionErrorNoChroot/ignore=true
[+2687s] --- FAIL: TestGetPermissionErrorNoChroot (0.54s)
[+2687s] --- FAIL: TestGetPermissionErrorNoChroot/ignore=false (0.24s)
Re-running and will monitor in case it was a flake.
Cron build '1.21' Failed:
https://cirrus-ci.com/build/6293777433231360
This hit similar networking flakes as I saw in podman CI at the time.
Ignoring.
--
Chris Evich (he/him), RHCA III
Senior Quality Assurance Engineer
My personal robot overlord told me to include this signature line.
203
days inactive
203
days old
podman-monitor@lists.podman.io
1 comments
2 participants
participants (2)
-
Chris Evich -
Do Not Reply