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

Fix Travis CI failures #102

Closed
jack-oquin opened this issue Jan 24, 2018 · 10 comments
Closed

Fix Travis CI failures #102

jack-oquin opened this issue Jan 24, 2018 · 10 comments
Labels

Comments

@jack-oquin
Copy link
Member

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.

@jack-oquin jack-oquin added the bug label Jan 24, 2018
@nickswalker
Copy link
Member

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.

@jack-oquin
Copy link
Member Author

Good to know. Thanks for the pointer, Nick.

@jack-oquin
Copy link
Member Author

jack-oquin commented Jan 30, 2018

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.

@jack-oquin
Copy link
Member Author

Getting closer. Failed in the build step for kinova_demo:

Starting  >>> kinova_demo                                   
_______________________________________________________________________________
Errors     << kinova_demo:cmake /root/catkin_ws/logs/kinova_demo/build.cmake.000.log
CMake Error at /root/catkin_ws/install/share/kinova_driver/cmake/kinova_driverConfig.cmake:148 (message):
  Project 'kinova_demo' tried to find library 'kinova_driver'.  The library
  is neither a target nor built/installed properly.  Did you compile project
  'kinova_driver'? Did you find_package() it before the subdirectory
  containing its code is included?
Call Stack (most recent call first):
  /opt/ros/kinetic/share/catkin/cmake/catkinConfig.cmake:76 (find_package)
  CMakeLists.txt:7 (find_package)

Travis link: https://travis-ci.org/utexas-bwi/bwi_common/jobs/335396370

@jack-oquin
Copy link
Member Author

I guess we need separate Travis configurations for the different branches. There's no point in compiling the kinetic branch on Indigo.

@jack-oquin
Copy link
Member Author

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.

@jack-oquin
Copy link
Member Author

Commit 96cd6c5 uses the ROS-I tools to run master on ROS Indigo, a simpler build than the current Kinetic branch. That may demonstrate whether the problem is in kinova-ros or not.

@jack-oquin
Copy link
Member Author

jack-oquin commented Jan 31, 2018

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.

jack-oquin added a commit that referenced this issue Jan 31, 2018
This attemps to work around a problem with kinova-ros.
@jack-oquin
Copy link
Member Author

I am able to reproduce the kinova_demo build failure by compiling into install space:

 $ catkin config --install
 $ catkin build

That seems to indicate a CMake install() error somewhere in kinova-ros.

@jack-oquin
Copy link
Member Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants