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
The Makefile provides several convenient sub-targets: test-proxy, test-whonix, test-gpg, test-app, test-base. However, they all fail with:
test-proxy
test-whonix
test-gpg
test-app
test-base
ImportError: No module named 'base'
The text was updated successfully, but these errors were encountered:
As far as I can tell, to fix this, we can either use the discover subcommand throughout, e.g.
discover
python3 -m unittest discover tests/ -v -p test_proxy_vm*
Or we can alter the import logic in the tests themselves. Using discover throughout seems like the simpler fix to me.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
The Makefile provides several convenient sub-targets:
test-proxy
,test-whonix
,test-gpg
,test-app
,test-base
. However, they all fail with:The text was updated successfully, but these errors were encountered: