7:01 p.m.
Detected one or more Cirrus-CI cron-triggered jobs have failed recently:
Cron build 'main' Failed: https://cirrus-ci.com/build/4957429298364416
# 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:52 a.m.
New subject: Cirrus-CI cron build failures on containers/buildah
On 7/8/21 8:01 PM, 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/4957429298364416
Ed,
This may be an interesting buikdah:main failure:
https://cirrus-ci.com/task/6174615916511232?logs=integration_test#L960-L955
"Interesting" in that I have no idea how that could have made it past
PR-level CI and get merged. Is this possibly some kind of flake you're
aware of?
--
Chris Evich (he/him), RHCA III
Senior Quality Assurance Engineer
If it ain't broke, yain't tryin' hard 'nough.
12:10 p.m.
New subject: Cirrus-CI cron build failures on containers/buildah
On Tue, Jul 13, 2021 at 11:52:45AM -0400, Chris Evich wrote:
On 7/8/21 8:01 PM, 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/4957429298364416
Ed,
This may be an interesting buikdah:main failure:
https://cirrus-ci.com/task/6174615916511232?logs=integration_test#L960-L955
"Interesting" in that I have no idea how that could have made it past
PR-level CI and get merged. Is this possibly some kind of flake you're
aware of?
It's a flake: https://github.com/containers/crun/issues/660
That flake was claimed to have been closed in crun back in May.
Does this CI system have a crun later than May 10?
Ed
--
Ed Santiago [he/him] Toolsmith santiago(a)redhat.com
12:14 p.m.
New subject: Cirrus-CI cron build failures on containers/buildah
On Tue, Jul 13, 2021 at 11:10:41AM -0600, Ed Santiago wrote:
On Tue, Jul 13, 2021 at 11:52:45AM -0400, Chris Evich wrote:
> On 7/8/21 8:01 PM, 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/4957429298364416
>
> Ed,
>
> This may be an interesting buikdah:main failure:
> https://cirrus-ci.com/task/6174615916511232?logs=integration_test#L960-L955
>
> "Interesting" in that I have no idea how that could have made it past
> PR-level CI and get merged. Is this possibly some kind of flake you're
> aware of?
It's a flake: https://github.com/containers/crun/issues/660
That flake was claimed to have been closed in crun back in May.
Does this CI system have a crun later than May 10?
Sorry for replying to self: answer is, no, CI system has ancient crun:
https://cirrus-ci.com/task/6174615916511232?logs=package_versions#L6
crun-0.19.1-3.fc33-x86_64
crun-0.19.1 is from April:
https://github.com/containers/crun/tags
Solution: upgrade crun on CI systems.
--
Ed Santiago [he/him] Toolsmith santiago(a)redhat.com
8:33 a.m.
New subject: Cirrus-CI cron build failures on containers/buildah
On 7/13/21 1:14 PM, Ed Santiago wrote:
crun-0.19.1 is from April:
https://github.com/containers/crun/tags
Solution: upgrade crun on CI systems.
Ed,
Oh goodie, that's something I know how to do. Though I _just_ had
freshly built images merged in the other day. Checking a more recent CI
run...unf. it's still crun-0.19.1 :(
Lokesh, et al.,
Can you (or anyone else) roll up a new version of crun (preferably so
they match between F33 and 34)?
--
Chris Evich (he/him), RHCA III
Senior Quality Assurance Engineer
If it ain't broke, yain't tryin' hard 'nough.
8:21 a.m.
New subject: Cirrus-CI cron build failures on containers/buildah
On 7/13/21 1:10 PM, Ed Santiago wrote:
It's a flake: https://github.com/containers/crun/issues/660
That flake was claimed to have been closed in crun back in May.
Does this CI system have a crun later than May 10?
Ed,
Oh good, I'm glad I asked. Ugh, that looks like a race condition that
really shouldn't be exposed to mortals.
That system (Note: F33) had crun-0.19.1-3.fc33-x86_64 at the time:
https://cirrus-ci.com/task/6174615916511232?logs=package_versions#L6
Conveniently I have that package installed on my laptop, an rpm -qi shows:
Build Date : Mon 17 May 2021 10:18:30 AM EDT
Ooof! I don't fully understand where the race is from the issue, and it
doesn't seem clear (to my ignorant eyes) how the fix works. Could it be
a related/unconsidered failure-path maybe? Should we re-open the issue
and rope in the experts?
--
Chris Evich (he/him), RHCA III
Senior Quality Assurance Engineer
If it ain't broke, yain't tryin' hard 'nough.
564
days inactive
569
days old
podman-monitor@lists.podman.io
5 comments
3 participants
participants (3)
-
Chris Evich -
Do Not Reply -
Ed Santiago