Testing repository 'empty' (amd64)?

Packaging and Release Management Melodic
1

Getting a bit confused now where I should post this (here, osrf/infrastructure, #buildfarm ?) but according to repositories.ros.org/status_page/melodic_default the testing repository is “empty”?

Almost all ros-melodic-* packages are missing in the amd64 column.

CIs are failing due to not being able to install ros-melodic-catkin.

From CI logs, this started yesterday (ie: 2021-06-12).

2

So the packages get uploaded to the testing repository when the current crop of package builds finishes. As it stands, that is the only time it happens. If that fails (as it did in Mrel_sync-packages-to-testing_bionic_amd64 #644 [Jenkins]), then the packages may be deleted and not uploaded. That’s what happened in this case.

The next time a package is rebuilt, that will get kicked again, and that seems to be what happened this morning: Mrel_sync-packages-to-testing_bionic_amd64 #645 [Jenkins]

So things should now be back to normal, but it does suggest that we may want to re-run that job periodically just in case of a failure. I’ll talk to the infrastructure team about this and see what they have to say.

3

thanks for the clarification.

It’s an open-loop process then?

Things seem to be back to normal indeed again.

4

In the future this would be good for osrf/infrastructure if it’s hosted content that’s problematic that’s a good place for us to track it and we can redistributed/refile it and close it out if necessary.

We could then trace down if it’s a configuration issue or a software issues and fix it in the ros_buildfarm software or in the deployment mechanism or in our specific deployment.

That deployment is programmatically open loop as historically the sync has been very reliable and has not had any documented failure modes that need recovery. We should resolve this one and then it won’t need. However it does send an email report to the distro’s release manager as well as reporting error status on the main dashboard which is periodically checked as well.

5

FYI, there was already a similar issue opened about Foxy from last week: ros2-testing repository inconsistent references · Issue #3 · osrf/infrastructure · GitHub . I just added another comment to it.

1 Like