Ask Your Question
0

[noetic] Build failed in Jenkins: debian/buster could not resolve rosdep key

asked 2020-12-03 02:25:02 -0600

Felix Messmer gravatar image

updated 2020-12-08 15:42:39 -0600

gvdhoorn gravatar image

I'm getting daily mails about jenkins failing for one of the repositories that I maintain and that I released to noetic: https://github.com/ipa320/cob_command...

The mail points me to failed builds: e.g. for
http://build.ros.org/job/Nsrc_dB__cob...

One of the packages (cob_monitoring) specifies a dependency that is not available for debian/buster (python3-mechanize). I specify this dependency with a condition on ROS_PYTHON_VERSION:
https://github.com/ipa320/cob_command...

Because python-mechanize is not available for focal and python3-mechanize is not availabe for xenial/bionic.

During the bloom-release step, this was mentioned and I confirmed to skip that generator:
see https://github.com/ipa320/cob_command...

How can I prevent the buildfarm from still trying to build for debian/buster? Or can I modify the dependency condition so debian/buster also uses python-mechanize instead of python3-mechanize?

Thanks


Edit: thanks for the PR for cob_monitoring - I'm no longer receiving the failure reports for that package anymore

still, I receive failure reports for the other packges included in cob_command_tools repository:

I can't relate any missing debian/buster dependency to these failures - in contrary to cob_monitoring Any idea why these packages do not pass?

I see fatal: Remote branch debian/ros-noetic-cob-command-gui_0.6.19-1_buster not found in upstream origin in the logs.
Does that mean I have to re-do a bloom-release?
Should the missing remote branch not disable the buildfarm for this job?

edit retag flag offensive close merge delete

Comments

All of those should be blacklisted too. Just like the above if you skipped the step in bloom. Unless they are blacklisted the buildfarm considers it an error and will tell you that you've asked for them to be built(by putting it in the rosdistro and not blacklisting it) but it's missing resources and it tells you the missing resources.

tfoote gravatar image tfoote  ( 2020-12-08 19:57:05 -0600 )edit

the respective PR is waiting for review/comments: https://github.com/ros-infrastructure...

Felix Messmer gravatar image Felix Messmer  ( 2021-01-04 07:39:50 -0600 )edit

1 Answer

Sort by ยป oldest newest most voted
1

answered 2020-12-03 12:57:54 -0600

tfoote gravatar image

You can blacklist packages for a specific platform in the ros_buildfarm_config. Here's an example of doing it for builds on buster: https://github.com/ros-infrastructure...

PS: Switching the dependency conditionally won't make a difference because the python version will still be python3 which means that it won't find the python-mechanizepython 2 libraries anyway.

edit flag offensive delete link more

Comments

Opened a PR to blacklist cob_monitoring on Buster in Noetic: https://github.com/ros-infrastructure...

sloretz gravatar image sloretz  ( 2020-12-03 14:19:37 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

2 followers

Stats

Asked: 2020-12-03 02:25:02 -0600

Seen: 119 times

Last updated: Dec 08 '20