<div dir="ltr">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. <br>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jul 8, 2013 at 7:44 PM, Michael Ferguson <span dir="ltr"><<a href="mailto:mfergs7@gmail.com" target="_blank">mfergs7@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Dirk,<div><br></div><div>Is expected that doc jobs will be occasionally failing due to unmet dependencies or inability to get the dpkg lock?</div>
<div><br></div><div>I just looked at the groovy doc job for pocketsphinx, and there are a number of failed builds (<a href="http://jenkins.willowgarage.com:8080/view/Gdoc/job/doc-groovy-pocketsphinx/" target="_blank">http://jenkins.willowgarage.com:8080/view/Gdoc/job/doc-groovy-pocketsphinx/</a>). Most end with:</div>
<div><br></div><div><pre style="font-size:11px;white-space:pre-wrap;margin-bottom:0px;margin-top:0px;word-wrap:break-word">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</pre></div><div><br></div><div>Is this something I'm doing wrong?</div></div></blockquote><div><br></div><div>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: <a href="https://github.com/ros-infrastructure/buildfarm/issues/128">https://github.com/ros-infrastructure/buildfarm/issues/128</a></div>
<div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><br></div><div>Also, the most recent job failed with:</div>
<div><br></div><div><pre style="font-size:11px;white-space:pre-wrap;margin-bottom:0px;margin-top:0px;word-wrap:break-word">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?</pre></div></div></blockquote><div><br></div><div>There's a ticket here that I just put together a pull request to resolve this issue. <a href="https://github.com/ros-infrastructure/buildfarm/issues/126">https://github.com/ros-infrastructure/buildfarm/issues/126</a></div>
<div><br></div><div>Tully</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">
<div><br></div><div>Thanks for any feedback,</div><div>-Fergs</div></div><div class=""><div class="h5"><div class="gmail_extra">
<br><br><div class="gmail_quote">On Mon, Jul 8, 2013 at 6:31 PM, Dirk Thomas <span dir="ltr"><<a href="mailto:dthomas@osrfoundation.org" target="_blank">dthomas@osrfoundation.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
As of today the ROS buildfarm will send notification emails for non-stable doc jobs.<br>
Doc jobs currently run every third day (randomized over all doc jobs).<br>
Jenkins will send an email for every failing and unstable build (as well as one more when a job turns stable again).<br>
<br>
The notification emails are sent to all maintainers of packages within the repo being documented.<br>
For dry stacks the email addresses of the authors are used (if available).<br>
<br>
Currently 62 doc jobs for Groovy are failing which are 15 % (same percentage for Hydro).<br>
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.<br>
<br>
Thank you,<br>
- Dirk<br>
<br>
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...<br>
______________________________<u></u>_________________<br>
Ros-release mailing list<br>
<a href="mailto:Ros-release@code.ros.org" target="_blank">Ros-release@code.ros.org</a><br>
<a href="https://code.ros.org/mailman/listinfo/ros-release" target="_blank">https://code.ros.org/mailman/<u></u>listinfo/ros-release</a><br>
</blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Ros-release mailing list<br>
<a href="mailto:Ros-release@code.ros.org">Ros-release@code.ros.org</a><br>
<a href="https://code.ros.org/mailman/listinfo/ros-release" target="_blank">https://code.ros.org/mailman/listinfo/ros-release</a><br>
<br></blockquote></div><br></div></div>