-
Notifications
You must be signed in to change notification settings - Fork 126
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
Catch JSONDecodeError and printout some debug info #291
Catch JSONDecodeError and printout some debug info #291
Conversation
Signed-off-by: Stephen Brawner <brawner@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One suggestion, but looks good other than that.
'Failure parsing performance results file at: %s' % args.result_file_in, | ||
file=sys.stderr) | ||
print(e) | ||
res.returncode = 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
res.returncode = 1 | |
if res.returncode == 0: | |
res.returncode = 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
Signed-off-by: Stephen Brawner <brawner@gmail.com>
It would be nice to test at least one package with performance tests enabled just to ensure that this didn't regress normal builds. |
The cmake warning in these last tests is just cmake complaining about packages not making use of AMENT_RUN_PERFORMANCE_TESTS=ON. In this case that should be expected. |
Attempting to debug a simple programming error led me to want some more information in the test results log file. Because the results file was incomplete after the test threw an exception, the json loads fails and throws an Python exception. By the nature of Python's helpful exception output, it makes it look like the error is the results file being the problem, but really it's just the test itself that failed to complete. I'm totally open to adjusting how this information looks though.
This is the new output if my test throws an exception:
Example of old output:
Signed-off-by: Stephen Brawner brawner@gmail.com