Closed tfoote closed 8 years ago
The ROS build farm is already designed in a way that it gracefully handles those kind of inconsistencies of the apt repository state. Until know we haven't seen this specific apt error yet: Unable to locate package
. It will be trivial to add it as a know error case to the apt-get wrapper script and retry the installation step: #204.
When the testing repo sync happens it can break doc jobs, and probably devel jobs too. This is an inherent race condition due to apt-get not supporting atomic operations. I'm not sure there's much we can do besides make the uploads more atomic. And to do that we'd probably need to change to a new repository hosting software.
We can probably close this as won't fix. @dirk-thomas thoughts?
The sync was at the same time: http://build.ros.org/job/Irel_sync-packages-to-testing_trusty_amd64/50/
Example failure: http://build.ros.org/job/Idoc__staubli_experimental__ubuntu_trusty_amd64/7/console
http://build.ros.org/job/Idoc__jsk_visualization__ubuntu_trusty_amd64/11/console
Similar errors: http://build.ros.org/job/Idoc__patrolling_sim__ubuntu_trusty_amd64/12/console http://build.ros.org/job/Idoc__moveit_commander__ubuntu_trusty_amd64/7/console http://build.ros.org/job/Idoc__flir_ptu__ubuntu_trusty_amd64/7/console