-
Notifications
You must be signed in to change notification settings - Fork 196
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
Switch to sqlite db breaks some tests #2435
Comments
This reverts commit 51cd493. It seems like it breaks some rpm-ostree pkglayering tests, which means it might be subtly changing layering semantics. Let's revert for now while we investigate to make sure it doesn't somehow get into a release. See: coreos/rpm-ostree#2435
OK I've narrowed this down a bit, here's some debugging I have:
The problem seems to be the
Yet this test case used Ah and here's another interesting fact, it is visible in
|
Worth noting that coreos/fedora-coreos-config#677 would have (potentially) caused this to fail in the FCOS PR. |
Narrowing it down more via
Then e.g. |
Oh yeah...
Testing a patch to use (I mean ordinarily what rsync is doing is sane, it's really ostree's mtime canonicalization that's defeating it) |
Apparently small rpmdb changes can cause the size to stay the same due to preallocation, and rsync defaults to skipping files based on (name, size, mtime). It's really ostree's mtime canonicalization that's unfortunate here. Anyways, we obviously don't care about performance here so use `-I` to disable that rsync check. (Also remove the `mkdir -p` since it's not necessary since a long time) Closes: coreos#2435
PR in #2436 |
Apparently small rpmdb changes can cause the size to stay the same due to preallocation, and rsync defaults to skipping files based on (name, size, mtime). It's really ostree's mtime canonicalization that's unfortunate here. Anyways, we obviously don't care about performance here so use `-I` to disable that rsync check. (Also remove the `mkdir -p` since it's not necessary since a long time) Closes: #2435
e.g.
Haven't debugged why this is yet.
The text was updated successfully, but these errors were encountered: