-
Notifications
You must be signed in to change notification settings - Fork 117
[bugfix] Fix crash in failure report when test is killed due to timeout #680
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
Conversation
* Calling the `communicate` method returns a tuple of `_io.TextIOWrapper` objects if the subprocess has timed out. Therefore, using the `__str__` method of the `SpawnedProcessTimeout` exception raises a `TypeError`. * The `read` method shoud be used to retrieve the string of the `_io.TextIOWrapper` objects.
|
Hello @teojgo, Thank you for updating! Cheers! There are no PEP8 issues in this Pull Request!Do see the ReFrame Coding Style Guide Comment last updated on February 18, 2019 at 15:00 Hours UTC |
|
@jenkins-cscs retry daint |
Codecov Report
@@ Coverage Diff @@
## master #680 +/- ##
==========================================
- Coverage 91.87% 91.85% -0.03%
==========================================
Files 77 77
Lines 9444 9445 +1
==========================================
- Hits 8677 8676 -1
- Misses 767 769 +2
Continue to review full report at Codecov.
|
This fix boils down to fixing the string conversion of
SpawnedProcessTimeout:Calling the
communicatemethod returns a tuple of_io.TextIOWrapperobjects if the subprocess has timed out.Therefore, using the
__str__method of theSpawnedProcessTimeoutexception raises a
TypeError.The
readmethod shoud be used to retrieve the string of the_io.TextIOWrapperobjects.Fixes #658