We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
While running libostree's "as-installed" tests, via ginsttest-runner and Debian's autopkgtest framework:
189s Executing: libostree/test-admin-deploy-var.sh.test 189s ++ _have_user_xattrs= 189s ++ _have_systemd_and_libmount= 189s ++ _have_strace_fault_injection= 189s ++ libtest_exit_cmds+=(libtest_cleanup_gpg) 189s ++ ED25519PUBLIC= 189s ++ ED25519SEED= 189s ++ ED25519SECRET= 189s /usr/libexec/installed-tests/libostree/test-admin-deploy-var.sh: line 24: OSTREE_FEATURES: unbound variable
Probably tests that are meant to work "as-installed" should use ostree --version | grep initial-var instead?
ostree --version | grep initial-var
The text was updated successfully, but these errors were encountered:
test-admin-deploy-var: Don't rely on OSTREE_FEATURES
1998ebb
This is set during build-time testing, but unset during "as-installed" tests. Resolves: ostreedev#3183 Signed-off-by: Simon McVittie <smcv@debian.org>
24ea77e
f6f378f
035b2c1
Successfully merging a pull request may close this issue.
While running libostree's "as-installed" tests, via ginsttest-runner and Debian's autopkgtest framework:
Probably tests that are meant to work "as-installed" should use
ostree --version | grep initial-var
instead?The text was updated successfully, but these errors were encountered: