-
Notifications
You must be signed in to change notification settings - Fork 305
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
2021.1 failing tests #2313
Comments
I have just updated the data to also include an example of a failed |
It was added for the collections bits, but we made that stable. It's now just cruft and we're very unlikely to reuse the infrastructure again. Motivated by a unit test failure when running from a tarball: ostreedev#2313
It was added for the collections bits, but we made that stable. It's now just cruft and we're very unlikely to reuse the infrastructure again. Motivated by a unit test failure when running from a tarball: ostreedev#2313
It was added for the collections bits, but we made that stable. It's now just cruft and we're very unlikely to reuse the infrastructure again. Motivated by a unit test failure when running from a tarball: ostreedev#2313
It was added for the collections bits, but we made that stable. It's now just cruft and we're very unlikely to reuse the infrastructure again. Motivated by a unit test failure when running from a tarball: ostreedev#2313
With 2021.2 I still have test-suite.log |
It would probably be easier to deal with each test failure as a separate issue. I'm seeing a similar failure mode for You might find it useful to apply #2350 and re-test - that might make the failure a bit more obvious (it did for Another thing that might help, which I'm trying in Debian, is to run the tests under |
Several tests generate summaries and then expect to use the generated summary immediately. However, this can cause intermittent test failures when they inadvertantly get a cached summary file. This typically happens when the test is run on a filesystem that doesn't support user extended attributes. In that case, the caching code can only use the last modified time, which only has 1 second granularity. If tests don't carefully manage the summary modification times or the repo cache then they are likely subject to races in some test environments. This introduces an environment variable `OSTREE_SKIP_CACHE` that prevents the repo from using a cache directory. This is enabled by default in tests and disabled for tests that are a explicitly trying to test the caching behavior. Fixes: ostreedev#2313 Fixes: ostreedev#2351
I wasn't aware of |
Hi! When packaging 2021.1 for Arch Linux I attempted to run the test session against the build.
Unfortunately 4 test runs (
tests/test-symbols.sh
,tests/test-signed-pull-summary.sh
and sometimes alsotests/test-remote-gpg-import.sh
) still fail and it is unclear to me why.This is the build log:
ostree-2021.1-build.log
Here are the log outputs of the tests:
tests/test-symbols.sh
tests/test-signed-pull-summary.sh
tests/test-remote-gpg-import.sh
The text was updated successfully, but these errors were encountered: