-
Notifications
You must be signed in to change notification settings - Fork 39
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
Allow specifying make arguments for testing #109
base: master
Are you sure you want to change the base?
Allow specifying make arguments for testing #109
Conversation
866c154
to
86534fd
Compare
Would it be possible to achieve the same thing by setting the environment variable |
Probably, but then you would apply it for all build steps |
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.
No harm in having the option to do that.
Still, parallel testing should be possible!
The issue you reference was about some state machine code, so I guess you experience different errors?
Could you at least show an error message?
If you run multiple gazebo tests in parallel you probably have to ensure individual server URIs for the tests to keep nodes from talking to the wrong server?
To stay with the existing variable naming for tests, I suggest renaming the new parameter to |
Wasn't showing any errors, neither when running on Travis nor locally.
Thanks, I didn't think about this.
Will do, fixed the tests also |
I ran into an issue where several integration tests using Gazebo caused a memory conflict resulting in the test runs being blocked and to fail. By limiting the number of make jobs to 1 (using -j1 inspired by ros-industrial/industrial_ci#446) all tests succeeded. I kept the new variable name generic, since I'm sure there are many more use cases for custom test options.