search

coincar-sim / lanelet_rviz_plugin_ros

BSD 3-Clause "New" or "Revised" License
32 stars 11 forks source link

Build failed #15

Closed m-naumann closed 3 years ago

m-naumann commented 3 years ago

Hi @orzechow

I got notified that the build failed, maybe you want to watch this repo from now on 😅

https://github.com/coincar-sim/lanelet_rviz_plugin_ros/runs/2679110720

orzechow commented 3 years ago

Package roslib was not found looks like fun to debug…

Do you have a good workflow to debug travis CI builds locally, besides manually setting up a similar docker and running all those commands there?

orzechow commented 3 years ago

It seems that you can ask Travis to enable debugging for public repos (with SSH access to the container): https://gist.github.com/francois-blanchard/1564cd9b4220e29b7fb55595cff54f68#gistcomment-2857884

orzechow commented 3 years ago

After figuring out that you use a minimal ros installation and let rosdep also install common ROS packages like rosbash, roslib etc. I found the "problem" – rather call it solution :grimacing:

It turns out that ROS Kinetic has reached end of life and thus rosdep simply skips kinetic in the rosdep update step. Somewhat doesn't make sense if we're on a kinetic system, but anyhow, the result is that we're having an empty ROS install within the container:

> tree -d 2 /opt/ros/kinetic/
2 [error opening dir]
/opt/ros/kinetic/
├── bin
├── etc
│   └── catkin
│       └── profile.d
├── lib
│   ├── pkgconfig
│   └── python2.7
│       └── dist-packages
│           ├── catkin
│           └── catkin-0.7.29.egg-info
└── share
    ├── catkin
    │   ├── catkin_env_hook
    │   └── cmake
    │       ├── em
    │       ├── env-hooks
    │       ├── platform
    │       ├── symlink_install
    │       ├── templates
    │       ├── test
    │       └── tools
    └── ros_environment
        ├── catkin_env_hook
        └── cmake

You can't build any meaningful ROS code with that :wink:

I'd suggest to drop kinetic support with its EOL now.

orzechow commented 3 years ago

See also http://wiki.ros.org/Distributions

orzechow commented 3 years ago

Btw. even though you specify some bionic stuff in .travis.yml both builds were done in xenial (that's why both fail). See #16 for Travis using bionic now.

m-naumann commented 3 years ago

Btw. even though you specify some bionic stuff in .travis.yml both builds were done in xenial (that's why both fail). See #16 for Travis using bionic now.

Can you double check that? The way it should work is that either a xenial or a bionic docker is used inside the xenial travis machine.

orzechow commented 3 years ago

Ah, I was already wondering why this env flag had no effect. But you're right, a docker container is run within the TravisCI container, one with xenial 16.04 and one with bionic 18.04.