-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI: podman run - idmapped mounts flake #25572
Comments
@giuseppe PTAL |
Said so, don't see how it could affect this test though, since we perform a EDIT: no, wrong analysis, that should not happen even with :O |
It failed 6 times now on #25506 (https://cirrus-ci.com/task/6193661458776064), I do have a c/common update there but if you look at the diff this is only my DiskUsage() bug fix. I cannot see how this diff would influences that flake and its only a single task all the others passed already and of course it passes locally fine as well. And I think I have seen it on other PRs as well.
I agree that parts confuses me as well.
Wait I think you are right no test that does That doesn't explain the containerenv error message but I don't think it safe for parallel testing. |
we refcount how many times the image was mounted:
|
one small improvement that I've noticed while staring at this code for too long: #25575 |
Ok, so this is still failing in all my runs on the PR. I have no idea what the hell is going on there as code wise. I have used hack/get_ci_vm to get the same VM. When I run the test individually I am not able to reproduce either. When I ran the full 030-run.bats file it did not reproduce either, even with the parallel tag set. However when I ran everything with Anything I can/should add to the test in order to debug? |
Ok it doesn't seem to be flake although it still totally unclear how to reproduce properly. The only thing I narrowed down so for that if I remove the image prune from the test it seems to work: 8cefffe Running the new test and the idmapped only doesn't seem to trigger the issue either. This make no sense to me... |
I have seen this a few times already so reporting this, AFAICT it always fails on the
run/.containerenv
path, not idea why this would be flaky.Log:
https://api.cirrus-ci.com/v1/artifact/task/4599002940833792/html/sys-podman-fedora-41-root-host-boltdb.log.html
The text was updated successfully, but these errors were encountered: