Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

Release process of buildfarm

asked 2018-07-24 03:46:58 -0500

agutenkunst
90 ●10 ●17 ●16

Hi,

currently I have a failing build (xenial, x64) in Travis due to a missing package on the shadow-fixed repository.

The package is "ros-kinetic-moveit-planners-ompl", yet I don't want to solve this special issue, but gain more understanding of the overall process.

In the build farm I see that everythink works: http://build.ros.org/view/Kbin_uX64/j...

On the status page of repositories.ros.org I can see that there is currently no green light on (testing aka shadow-fixed) image description

Also on http://packages.ros.org/ros-shadow-fi... there is no debian package for the respective architecture.

image description

How could I gain more insight what is happening here and why?

edit retag flag offensive close merge delete

add a comment

1 Answer

Sort by » oldest newest most voted

answered 2018-07-24 10:39:23 -0500

nuclearsandwich
906 ●24 ●10

When a new package is built and added to the buildfarm repository, packages which depend on it are removed from the repo before being rebuilt with the newly built dependency in order to prevent syncing packages with an inconsistent and possibly incompatible state to the testing and eventually main repositories.

Syncs to the testing repo wait for the last in-progress build to finish before running automatically. If a package fails and doesn't get rescheduled before a sync runs and there are enough packages built successfully, the sync will occur and remove those packages from the testing repository. Later, when the build is retriggered, the missing packages should sync once all packages in the distro finish.

The buildfarm is designed to be somewhat eventually consistent with failures do to operational glitches being resolved automatically by later syncs.

edit flag offensive delete link

add a comment

Question Tools

2 followers

Stats

Asked: 2018-07-24 03:46:58 -0500

Seen: 182 times

Last updated: Jul 24 '18

Release process of buildfarm edit

1 Answer

Question Tools

Stats

Related questions

Release process of buildfarm