7: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/6213790913003520
# 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.
12:05 p.m.
New subject: Cirrus-CI cron build failures on containers/podman
On 3/15/21 8: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/6213790913003520
# Source: check_cirrus_cron workflow on containers/podman.
Jhon,
Would you mind back-porting your APIv2 extra-thrrough-cleanup fix to the
v3.0 branch?
--
Chris Evich (he/him), RHCA III
Senior Quality Assurance Engineer
If it ain't broke, yain't tryin' hard 'nough.
3:30 p.m.
See https://github.com/containers/podman/pull/9741
On Tue, Mar 16, 2021 at 10:05 AM Chris Evich <cevich(a)redhat.com> wrote:
On 3/15/21 8: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/6213790913003520
>
> # Source: check_cirrus_cron workflow on containers/podman.
Jhon,
Would you mind back-porting your APIv2 extra-thrrough-cleanup fix to the
v3.0 branch?
--
Chris Evich (he/him), RHCA III
Senior Quality Assurance Engineer
If it ain't broke, yain't tryin' hard 'nough.
--
Jhon Honce
Pr Software Engineer
jhonce(a)redhat.com T: 650.254.4379 M: 602.705.3953 IM: jhonce
740
days inactive
741
days old
podman-monitor@lists.podman.io
2 comments
3 participants
participants (3)
-
Chris Evich -
Do Not Reply -
Jhon Honce