Definitely let us know if you see spurrious failures. Without the email notifications we haven't been catching a lot of them. Please report them so we can track them and know how frequently they are happening. On Mon, Jul 8, 2013 at 7:44 PM, Michael Ferguson wrote: > 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 > 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? > This just means that there was a regression and shadow-fixed had fewer packages. We're working on improving our continuous integration but sometimes we get regressions. I create an issue here: https://github.com/ros-infrastructure/buildfarm/issues/128 > 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? > > There's a ticket here that I just put together a pull request to resolve this issue. https://github.com/ros-infrastructure/buildfarm/issues/126 Tully > > Thanks for any feedback, > -Fergs > > > On Mon, Jul 8, 2013 at 6:31 PM, Dirk Thomas 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@code.ros.org >> https://code.ros.org/mailman/**listinfo/ros-release >> > > > _______________________________________________ > Ros-release mailing list > Ros-release@code.ros.org > https://code.ros.org/mailman/listinfo/ros-release > >