8:03 p.m.
Detected one or more Cirrus-CI cron-triggered jobs have failed recently:
Cron build 'v3.0.1-rhel' Failed: https://cirrus-ci.com/build/4801467342127104
# 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:26 a.m.
New subject: Cirrus-CI cron build failures on containers/podman
On 8/11/21 8:03 PM, Do Not Reply wrote:
Detected one or more Cirrus-CI cron-triggered jobs have failed
recently:
Cron build 'v3.0.1-rhel' Failed: https://cirrus-ci.com/build/4801467342127104
Jhon,
This seems to be a frequent flake recently (example)
https://cirrus-ci.com/task/5054373471453184?logs=main#L1067-L1077
Is there a fix for this on master that could be back-ported to the
v3.0.1-rhel branch?
--
Chris Evich (he/him), RHCA III
Senior Quality Assurance Engineer
My personal robot overlord told me to include this signature line.
2:57 p.m.
Maybe...?
I backtracked that error, and that is coming from code before the tests
were all broken into separate files by area of concern. I could try a PR of
the current test code against that branch. It may help, or make matters
worse...
/jwh
On Thu, Aug 12, 2021 at 8:26 AM Chris Evich <cevich(a)redhat.com> wrote:
On 8/11/21 8:03 PM, Do Not Reply wrote:
> Detected one or more Cirrus-CI cron-triggered jobs have failed recently:
>
> Cron build 'v3.0.1-rhel' Failed:
https://cirrus-ci.com/build/4801467342127104
Jhon,
This seems to be a frequent flake recently (example)
https://cirrus-ci.com/task/5054373471453184?logs=main#L1067-L1077
Is there a fix for this on master that could be back-ported to the
v3.0.1-rhel branch?
--
Chris Evich (he/him), RHCA III
Senior Quality Assurance Engineer
My personal robot overlord told me to include this signature line.
--
Jhon Honce
Pr Software Engineer
jhonce(a)redhat.com T: 650.254.4379 M: 602.705.3953 IM: jhonce
3:02 p.m.
New subject: Cirrus-CI cron build failures on containers/podman
On 8/30/21 2:57 PM, Jhon Honce wrote:
Maybe...?
I backtracked that error, and that is coming from code before the tests
were all broken into separate files by area of concern. I could try a PR
of the current test code against that branch. It may help, or make
matters worse...
Yep, that's often the worry :( It's wasting maybe about 2-5 minutes a
week for me. So if it's a 15-minute fix and goes smoothly, great. If
not, please give up immediately. I'll simply suffer for the remaining
weeks/months we need to test this branch.
--
Chris Evich (he/him), RHCA III
Senior Quality Assurance Engineer
My personal robot overlord told me to include this signature line.
755
days inactive
774
days old
podman-monitor@lists.podman.io
3 comments
3 participants
participants (3)
-
Chris Evich -
Do Not Reply -
Jhon Honce