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

use console_bridge_vendor #63

merged 1 commit into from Jul 5, 2018


None yet
3 participants
Copy link

commented Jul 5, 2018

@mikaelarguedas mikaelarguedas merged commit 2ef0871 into ros2 Jul 5, 2018

@mikaelarguedas mikaelarguedas deleted the console_bridge_vendor branch Jul 5, 2018


This comment has been minimized.

Copy link

commented Jul 6, 2018

I got a failure email that looks related to this:

15:59:26 Traceback (most recent call last):
15:59:26   File "/tmp/ros_buildfarm/scripts/devel/", line 252, in resolve_names
15:59:26     rosdep_key, view, installer, os_name, os_code_name)
15:59:26   File "/usr/lib/python3/dist-packages/rosdep2/", line 87, in resolve_for_os
15:59:26     d = view.lookup(rosdep_key)
15:59:26   File "/usr/lib/python3/dist-packages/rosdep2/", line 197, in lookup
15:59:26     return self.rosdep_defs[rosdep_name]
15:59:26 KeyError: 'console_bridge_vendor'

This comment has been minimized.

Copy link

commented Jul 6, 2018

Yes the new package has not been released in bouncy because just introduced today.

We will settle on Monday for the use of development jobs for the next cycle and the branching strategy.
Until then, packages affected by this set of PR that have devel jobs will fail to resolve the key.


This comment has been minimized.

Copy link

commented Jul 11, 2018

Dev job is now passing on the bouncy branch Build Status

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.