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

remove CATKIN_TEST_RESULTS_DIR environment variable #728

Merged
merged 1 commit into from
Apr 13, 2015

Conversation

dirk-thomas
Copy link
Member

This patch removes the CATKIN_TEST_RESULTS_DIR environment variable. That should prevent any kind of "cross talk" between packages build in parallel since the location is only depending on configure-time information.

The user can still override the location by setting the CMake variable via -DCATKIN_TEST_RESULTS_DIR=....

Addresses #719.

@esteve @tfoote @wjwwood Please review.

@tfoote
Copy link
Member

tfoote commented Apr 3, 2015

lgtm

@esteve
Copy link
Member

esteve commented Apr 3, 2015

+1

@bricerebsamen
Copy link

that fixed #719 for me.

It prints a lot of lines about skipping packages such as the one below, but it finally reports the correct number of tests, success, etc.

Skipping "src/driving_public/carviz_plugins_imagery/plugin_description.xml": 'tests'

@wjwwood
Copy link
Member

wjwwood commented Apr 3, 2015

lgtm, however, I am concerned about how we roll this out since it is a pretty serious change to remove an env variable like this at such a low level in the system. I talked with @dirk-thomas about it and we agreed that the right thing to do was to go forward with it, but to be proactive about communicating this to the users and giving them a chance to comment before releasing this change.

@dirk-thomas
Copy link
Member Author

@bricerebsamen The script searches recursively for .xml - by default starting in the current folder. You might want to pass the test results folder to narrow the search and prevent non-unit test results to show. For a non-isolated build with default paths that would be:

catkin_test_results build/test_results

Update: The script can not use an environment variable from the devel space for the exact location since the devel space is commonly not sourced when running tests. Also the naming scheme of the workspace can be custom and the script can not infer the correct location of the build space.

@mikepurvis
Copy link
Member

Change LGTM. None of our tooling relies on setting CATKIN_TEST_RESULTS_DIR.

@aleeper
Copy link

aleeper commented Apr 6, 2015

+1.

@dirk-thomas
Copy link
Member Author

Waiting for feedback after announcement: https://groups.google.com/forum/#!topic/ros-sig-buildsystem/suBvWzoGODU

@floweisshardt
Copy link

+1. None of our tooling uses 'CATKIN_TEST_RESULTS_DIR'.

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

Successfully merging this pull request may close these issues.

8 participants