The linked doc jobs has a failing unit test and is therefore marked as
"unstable".
The failing unit test says:

    Failed to generate messages by calling cmake for ['catkin_workspace for
repository'].
    Look in the console for cmake failures, search for "CMake Error"

Basically CMake is invoked to trigger message generation but it fails to
configure.
Going through the console output gets you to the following error:

    CMake Error at
/opt/ros/hydro/share/camera1394/cmake/camera1394Config.cmake:141 (message):
      Project 'segbot_sensors' tried to find library
      'src/nodes/camera1394_nodelet'.  The library is neither a target nor
      built/installed properly.  Did you compile project 'camera1394'? Did
you
      find_package() it before the subdirectory containing its code is
included?
    Call Stack (most recent call first):
      /opt/ros/hydro/share/catkin_basic/cmake/catkin_basicConfig.cmake:12
(find_package)
      /opt/ros/hydro/share/catkin_basic/cmake/catkin_basicConfig.cmake:88
(select_catkin_dependencies)
      segbot/segbot_sensors/CMakeLists.txt:3 (catkin_basic)

"catkin_basic" is used to configure the packages (actually replacing your
packages CMakeLists.txt files).
It tries to automatically export all dependencies of your package and "
segbot_sensors" run depends on "camera1394".
When that happens the CMake config file of "camera1394" generates the above
quoted CMake error.

"camera1394" seems to export a library incorrectly:
https://github.com/ros-drivers/camera1394/blob/master/CMakeLists.txt#L45
That line is definitely wrong - you might want to fill a bug report against
it since the package is basically not find_package()-able.

The general problem is that using "catkin_basic" and replacing your
CMakeLists.txt file in order to message generation without compiling your
package is a bad idea in the first place.
But that is not likely to change in the near future until we take the time
to revamp the buildfarm.

Cheers,
- Dirk


On Fri, Apr 25, 2014 at 7:52 AM, Jack O'Quin <jack.oquin@gmail.com> wrote:

> We have been getting repeated failures on the doc jobs for the segbot
> repository. I have perused the console output several times, but have no
> clue what that job is attempting or what is going wrong. I can tell it has
> something to do with message generation.
>
>  http://jenkins.ros.org/job/doc-hydro-segbot/100/
>
> Any help or suggestions would be welcome!
> --
>  joq
>
> _______________________________________________
> ros-release mailing list
> ros-release@code.ros.org
> http://lists.ros.org/mailman/listinfo/ros-release
>
>