-
Notifications
You must be signed in to change notification settings - Fork 80
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
KeyError: 'specific_test' when running stem's tests #63
Comments
nmathewson
added a commit
to nmathewson/tor
that referenced
this issue
May 13, 2020
This is a workaround for torproject/stem#63
It's actually d1174a8 that works for me. |
nmathewson
added a commit
to nmathewson/tor
that referenced
this issue
May 14, 2020
This is a workaround for torproject/stem#63
ghost
pushed a commit
to torproject/tor
that referenced
this issue
May 14, 2020
This is a workaround for torproject/stem#63
ghost
pushed a commit
that referenced
this issue
May 15, 2020
Commit 076f89d rewrote how we parse arguments. This broke our --test and --exclude-test arguments because there is no longer a default value in the 'args' dictionary... % ./run_tests.py --unit --test endpoint Traceback (most recent call last): File "./run_tests.py", line 482, in <module> main() File "./run_tests.py", line 197, in main args = test.arguments.Arguments.parse(sys.argv[1:]) File "/home/atagar/Desktop/stem/test/arguments.py", line 109, in parse args['specific_test'].append(crop_module_name(arg)) KeyError: 'specific_test' Reported by teor on... #63
Thanks teor! Fixed... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When running stem's tests on commit 99c3043, we see the following error in tor's CI:
The previous commit d1174a8 does not appear to have this issue.
Edit: specify the correct working commit.
The text was updated successfully, but these errors were encountered: