Skip to content
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

catkin_test_results should provide an error code based reporting of errors/failures #392

Closed
wjwwood opened this issue Mar 15, 2013 · 0 comments
Assignees

Comments

@wjwwood
Copy link
Member

wjwwood commented Mar 15, 2013

For build farms which do not manually read in the xunit files, one command which indicates whether or not any tests failed would be nice.

caktin_test_results /path/to/test_results summarizes the tests, but always returns 0, maybe it could have options like --error-code-on-errors and --error-code-on-failures.

For not this works:

python -c "from catkin.test_results import test_results;import sys;sys.exit(sum([v[1] + v[2] for k, v in test_results('build/test_results').iteritems()]))"

@ghost ghost assigned dirk-thomas Mar 16, 2013
cwecht pushed a commit to cwecht/catkin that referenced this issue Mar 20, 2018
This was implicitly set on <= Ubuntu 16.04 when find_package()-ing
GMock in google_enable_testing(). On 17.04, this doesn't happen, and
Catkin builds a shared library by default. cartographer_ros currently
can't be built as a shared library due to a linking problem (which is
a separate issue - ros#392). This makes building on 17.04 consistent with
older versions of Ubuntu.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants