-
Notifications
You must be signed in to change notification settings - Fork 32
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
Fix Travis CI failures #102
Comments
I took a whack at using ROS Industrial's setup on this branch of segbot_arm. It is functional (though to pass without kinetic releases, we would have to modify the configuration to pull all BWI code from source). Their approach of loading a ROS docker image should insulate us from issues like those we faced with the July Travis image change. |
Good to know. Thanks for the pointer, Nick. |
I tried using the ROS-I test tool in the kinetic branch, as Nick suggested. I probably don't understand all there is to it yet. |
Getting closer. Failed in the build step for kinova_demo:
Travis link: https://travis-ci.org/utexas-bwi/bwi_common/jobs/335396370 |
I guess we need separate Travis configurations for the different branches. There's no point in compiling the |
It's possible that the kinova driver may not install all its files correctly. We normally build it in devel space. I should try an install-space build to see what happens. |
Commit 96cd6c5 uses the ROS-I tools to run |
Yes! Master does succeed on Indigo: https://travis-ci.org/utexas-bwi/bwi_common/builds/335651370?utm_source=email&utm_medium=notification Now, I need to figure out what the problem is with kinova-ros. |
This attemps to work around a problem with kinova-ros.
I am able to reproduce the kinova_demo build failure by compiling into install space:
That seems to indicate a CMake install() error somewhere in kinova-ros. |
Configuring Travis not to build into install space worked! Since I'm fairly sure the install problem is in kinova-ros and not here, I'm going to close this issue as fixed and open a new one there. |
While we're at it, we need to figure out how to run valid Travis tests on ROS Kinetic. That looks tricky, but I'm sure some people must be doing it.
The text was updated successfully, but these errors were encountered: