-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
test_threaded_bad_options not expected to raise AustinError? #13
Comments
Oh, I think I found something which might repro outside of my system:
This causes (In my Nix package |
Even better repro: running just test_threaded_bad_options in isolation fails:
|
test_threaded_bad_options was only passing in CI because it was running after test_threaded_invalid_binary, which altered the base class to ignore some exceptions. Restructure the tests by using the fact that ThreadedAustin.join will bubble up any exception that happened during startup. This avoids manipulating global state in test_threaded_invalid_binary. Fixes P403n1x87#13.
test_threaded_bad_options was only passing in CI because it was running after test_threaded_invalid_binary, which altered the base class to ignore some exceptions. Restructure the tests by using the fact that ThreadedAustin.join will bubble up any exception that happened during startup. This avoids manipulating global state in test_threaded_invalid_binary. Fixes P403n1x87#13.
test_threaded_bad_options was only passing in CI because it was running after test_threaded_invalid_binary, which altered the base class to ignore some exceptions. Restructure the tests by using the fact that ThreadedAustin.join will bubble up any exception that happened during startup. This avoids manipulating global state in test_threaded_invalid_binary. Fixes #13.
Description
On my system
test_threaded_bad_options
does not pass, instead failing due to anAustinError
. I don't really understand how this test is supposed to work right now, it's by design trying to make austin fail to start, but doesn't assert that an exception was raised.This is unlike
test_simple_bad_options
andtest_async_bad_options
which both have awith raises(AustinError)
.IMO this should also have a
with raises(AustinError)
, but that raises the question of why the test is currently passing in your CI environment and not on my local system... My local setup is slightly weird (I'm working on packaging austin, austin-python and austin-tui for NixOS) but looking at the code I don't understand how this could not fail.Steps to Reproduce
Expected behavior: All tests pass.
Actual behavior:
test_threaded_bad_options
is the only failure, with the following stack trace:Reproduces how often: 100% on my system, but that's not particularly helpful to you :)
Versions
Python 3.10, austin 3.4.1, austin-python 1.4.1.
Additional Information
n/a
The text was updated successfully, but these errors were encountered: