On Wed, Sep 22, 2021 at 09:52:18AM -0400, Chris Evich wrote:
On 9/21/21 8:00 PM, Do Not Reply wrote:
> Detected one or more Cirrus-CI cron-triggered jobs have failed recently:
> Cron build '1.21' Failed: https://cirrus-ci.com/build/4991832632328192
This flake seems to pop up every other week or so in our cron-jobs.
Yesterday we got a BOGO, same error on F33 and 34. Such a deal! Wow! :D
I found this same error message in both cases, on the idmapping test:
...level=error msg="A layer is mounted: layer is in use by a container"
Eventually followed by:
[+1073s] # #/vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
[+1073s] # #| FAIL: gid_map
[+1073s] # #| expected: '0 231072
[+1073s] # 296608 65536'
[+1073s] # #| actual: '0 231072 65536'
[+1073s] # #| > '65536 296608 65536'
[+1073s] # #\^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Could that layer-in-use error be the cause?
Maybe is this not worth worrying about (it's been a flake for a long while
now)? If so, may I expand the string-match to something like '0
That isn't my code. My name appears on it simply because I did
some refactoring, as did Hironori Shiina before me, but ultimately
the code is Nalin's, from 2b18391 on 2018-05-24. My refactoring
was purely of the dumb-monkey type, in which I eliminated copy-paste
code with no actual understanding of the test itself. IOW I can't
have an opinion on how to resolve this.
FWIW we see this flake in CI also, six times since August 29:
Ed Santiago [he/him] Toolsmith santiago(a)redhat.com