-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
rawhide: brq / blkio / loopbackfs / something broken #19471
Comments
Ref: #19471 Signed-off-by: Chris Evich <[email protected]>
@cevich found a related hit on f38. I spun up a 1mt VM, confirmed same kernel as this failure (6.4.6-200.fc38), presumably the same This is 100% reproducible on rawhide. It does not make sense that it could be a flake on f38. |
Bug does not reproduce on 6.5.0-0.rc6.20230818git0e8860d2125f.47.fc40.x86_64 but I'm not going to close this nor remove the test skips yet, not until we understand the problem and where else it may manifest. |
A friendly reminder that this issue had no activity for 30 days. |
- containers#15074 ("subtree_control" flake). The flake is NOT FIXED, I saw it six months ago on my (non-aarch64) laptop. However, it looks like the frequent-flake-on-aarch64 bug is resolved. I've been testing in containers#17831 and have not seen it. So, tentatively remove the skip and see what happens. - Closes: containers#19407 (broken tar, "duplicates of file paths") All Fedoras now have a fixed tar. Debian DOES NOT, but we're handling that in our build-ci-vm code. I.e., the Debian VM we're using has a working tar even though there's currently a broken tar out in the wild. Added distro-integration tag so we can catch future problems like this in OpenQA. - Closes: containers#19471 (brq / blkio / loopbackfs in rawhide) Bug appears to be fixed in rawhide, at least in the VMs we're using now. Added distro-integration tag because this test obviously relies on other system stuff. Signed-off-by: Ed Santiago <[email protected]>
No clue what. loopbackfs tests are broken on rawhide. bz2226558. This is just a tracking issue for benefit of tracking skipped tests.
The text was updated successfully, but these errors were encountered: