-
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
Base client hidden exceptions processing #688
Labels
Milestone
Comments
RomanBelozerov
added
enhancement
New feature or request
Infrastructure
The framework reworking and extensions
labels
Sep 27, 2024
One more similar case: tempesta-test/helpers/stateful.py Line 63 in f53c85a
If an exception is caught, it is being hidden (all information is provided, but the situation is not considered as an error) Example (there is an exception but test is considered as successfull):
|
Fails on a teardown or a cleanup should be considered as fail. One more example:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Current implementation of the
framework.client.Client
has a hidden error(perhaps this is architecture feature). But it is not easy to debug with such realization.Let's look at a situation: we have a test that work with a client, for my case it is
ratecheck
(t_frang.test_connection_rate_burst.FrangTcpVsBoth.test_burst
).Now, I already knew, that the client did not exist on my machine (was not installed).
But when I run the test with low details first times I received something like:
The real problem is hidden.
I can set more detailed logs and I may see an error, but the error displayed in the middle of log output and I have to search for it, and it is just a message (it is colored now, but we added logs processing recently).
Real problem here:
tempesta-test/framework/client.py
Line 8 in fc5e2e3
run_cmd
raises an exception if an error was caught, but here it become hidden.We need to explicit (re)raise an exception in such cases to provide an user correct information.
I have not updated the code right away, because the client works with
multiprocessing
and we need to think about the best way how to implement it, otherwise side effects may occur.The text was updated successfully, but these errors were encountered: