-
Notifications
You must be signed in to change notification settings - Fork 697
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
Fix focal testinfra test failures #5839
Conversation
Still getting some unexpected failures on my install-and-restore rc1 mac mini (other than sources.list) which is expected. Can anyone reproduce this?
|
I did not get those errors on a clean Focal install on NUC7+NUC10. I only saw the expected failures due to the Focal staging passed, no errors. Xenial staging somehow had testinfra, Xenial staging
|
Turns out Xenial has always had |
Judging by the diff, the python version output that @emkll should still be happening. Test against prod VMs via Tails VM now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested on Focal prod VMs, output looks good.
Status
Ready for review
Description of Changes
Fixes #5825 .
host.check_output('hostname -s')
instead of ansible backend to get hostname, as ansible backend not used in prod verify.Testing
set up a prod Focal system on latest 1.8.0 RC (or 1.8.0 if released).
On the Admin Workstation, switch to this branch.
In a terminal, run
USE_FOCAL=True ./securedrop-admin verify
test_fpf_apt_repo
if the apt-test repo was used for the install)on a dev workstation, set up a staging environment and run tests with
make build-debs-notest && make staging && make testinfra
on a dev workstation, set up a focal staging environment and run tests with
make build-debs-focal-notest && make staging-focal && USE_FOCAL=True make testinfra
Deployment
test-only.
Checklist
If you made non-trivial code changes: