[Ros-release] Notification for doc jobs

[Michael Ferguson]

Dirk,

Is expected that doc jobs will be occasionally failing due to unmet
dependencies or inability to get the dpkg lock?

I just looked at the groovy doc job for pocketsphinx, and there are a
number of failed builds (
http://jenkins.willowgarage.com:8080/view/Gdoc/job/doc-groovy-pocketsphinx/).
Most end with:

Executing command 'apt-get install ros-groovy-ros ros-groovy-genmsg --yes'
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 ros-groovy-ros:i386 : Depends: ros-groovy-catkin:i386 but it is not
going to be installed
                       Depends: ros-groovy-rosbash:i386 but it is not
going to be installed
                       Depends: ros-groovy-rosbuild:i386 but it is not
going to be installed
                       Depends: ros-groovy-rosclean:i386 but it is not
going to be installed
                       Depends: ros-groovy-roscreate:i386 but it is
not going to be installed
                       Depends: ros-groovy-roslang:i386 but it is not
going to be installed
                       Depends: ros-groovy-roslib:i386 but it is not
going to be installed
                       Depends: ros-groovy-rosmake:i386 but it is not
going to be installed
                       Depends: ros-groovy-rosunit:i386 but it is not
going to be installed
E: Unable to correct problems, you have held broken packages.
/!\  Failed to execute command '['apt-get', 'install',
'ros-groovy-ros', 'ros-groovy-genmsg', '--yes']' with return code 100
Traceback (most recent call last):
  File "/home/rosbuild/hudson/workspace/doc-groovy-pocketsphinx/jenkins_scripts/doc",
line 184, in <module>
    main()
  File "/home/rosbuild/hudson/workspace/doc-groovy-pocketsphinx/jenkins_scripts/doc",
line 99, in main
    doit(ros_distro, stack, workspace, docspace)
  File "/home/rosbuild/hudson/workspace/doc-groovy-pocketsphinx/jenkins_scripts/doc",
line 121, in doit
    call("apt-get install ros-%s-ros ros-%s-genmsg --yes" %
(install_distro, install_distro))
  File "/home/rosbuild/hudson/workspace/doc-groovy-pocketsphinx/jenkins_scripts/common.py",
line 137, in call
    return call_with_list(command.split(' '), envir, verbose)
  File "/home/rosbuild/hudson/workspace/doc-groovy-pocketsphinx/jenkins_scripts/common.py",
line 131, in call_with_list
    raise BuildException(msg)
common.BuildException


Is this something I'm doing wrong?

Also, the most recent job failed with:

E: Could not get lock /var/lib/dpkg/lock - open (11: Resource
temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is
another process using it?


Thanks for any feedback,
-Fergs


On Mon, Jul 8, 2013 at 6:31 PM, Dirk Thomas <dthomas at osrfoundation.org>wrote:

> As of today the ROS buildfarm will send notification emails for non-stable
> doc jobs.
> Doc jobs currently run every third day (randomized over all doc jobs).
> Jenkins will send an email for every failing and unstable build (as well
> as one more when a job turns stable again).
>
> The notification emails are sent to all maintainers of packages within the
> repo being documented.
> For dry stacks the email addresses of the authors are used (if available).
>
> Currently 62 doc jobs for Groovy are failing which are 15 % (same
> percentage for Hydro).
> So if you receive a notification email for a doc job in the next days
> please make sure to get the issues fixed so that all doc jobs become stable.
>
> Thank you,
> - Dirk
>
> PS: Some time in the near future we might remove all jobs from the ROS
> buildfarm which continuously fail to reduce the overhead and have more
> resources for the maintained packages...
> ______________________________**_________________
> Ros-release mailing list
> Ros-release at code.ros.org
> https://code.ros.org/mailman/**listinfo/ros-release<https://code.ros.org/mailman/listinfo/ros-release>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ros.org/pipermail/ros-release/attachments/20130708/cacab2ac/attachment-0009.html>