Failure of upstream project does not trigger status change

[piyushk]

gazebo_ros succesfully built a few days ago: See build 20 in Jenkins.

gazebo_plugins has subsequently stopped building due to a known migration issue (Jenkins. However, this does not reset the status of gazebo_ros. Consequently, all packages depending on gazebo_ros (but not gazebo_plugins) continue to attempt builds that will never succeed. For instance, segbot_gazebo_plugins.

Is this a Jenkins bug?

[dirk-thomas]

Chronology:

• http://jenkins.willowgarage.com:8080/job/ros-hydro-gazebo-ros_binarydeb_quantal_amd64/20/ built successfully
• http://jenkins.willowgarage.com:8080/view/HbinQ32/job/ros-hydro-segbot-gazebo-plugins_binarydeb_quantal_i386/14/ fails to build due to missing include (so far so good - all (indirect) upstream dependencies are available)
• http://jenkins.willowgarage.com:8080/view/HbinQ32/job/ros-hydro-segbot-gazebo-plugins_binarydeb_quantal_i386/15/ fails to build due to missin http://jenkins.willowgarage.com:8080/view/HbinQ32/job/ros-hydro-segbot-gazebo-plugins_binarydeb_quantal_i386/ failed to build because of ros-hydro-gazebo-plugins which is a virtual package

At some point between the two last bullets an upstream job invalidated the Debian package of _gazeboplugins. But it did no invalidated all recursive downstream dependencies which made the last build fail since from its perspective all direct upstream jobs are green.

[dirk-thomas]

Will be addressed in the ticket just opened by @tfoote.