-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ros2-testing repository inconsistent references #3
Comments
I can't reproduce the error. I suspect that our mirror replication has failed or you got the unfortunate timing of hitting it during a sync. There were three syncs onging near that time. https://build.ros2.org/job/Grel_sync-packages-to-testing_focal_amd64/lastSuccessfulBuild/ I can't reproduce the error now. And I checked all three mirrors directly.
|
@tfoote Thanks a lot for looking into this. I cannot reproduce this right now either, and all the runs are turning back to succeeding, though this was persistent for at least 7-8 hours in recurring runs on multiple repositories in ros-planning and ros-control organizations. We were probably in an unfortunate timing during multiple syncs. |
If there was an issue for 7-8 hours prior that sounds like the last syncs resolved the inconsistency in the database. As opposed to causing them. The sync outage is basically as fast as we can copy the files into the repository. |
For what it is worth, we did have a problem where the |
Thanks a lot for resolving this, will try to remember to come here instead of writing Tully next time (old habits... :) ). |
A somewhat similar thing happened to Melodic over the weekend; see https://discourse.ros.org/t/testing-repository-empty-amd64/20908 for some more of the details. I'm wondering if it would make sense to have the sync-to-testing jobs run nightly, as a backup in case something failed. That way the time frame of the breakage (if it does occur) would at least be time-limited. |
In the failed melodic log noticed that there's actually a real error that we should not be having
We should make sure that doesn't happen. |
I've refiled a tracking ticket on the upstream repository to track it there. |
Problem description
Report from a user:
Seems like the Packages file for ros2-testing is not up to date:
I.e. ros-foxy-ros-workspace should have version
1.0.1-1focal.20210422.234610 but only 1.0.1-1focal.20210422.235134 is
there:
http://packages.ros.org/ros2-testing/ubuntu/pool/main/r/ros-foxy-ros-workspace/
or in one line ;):
$ wget "http://packages.ros.org/ros2-testing/ubuntu/$(curl "http://packages.ros.org/ros2-testing/ubuntu/dists/focal/main/binary-amd64/Packages" | grep-dctrl -F Package -s Filename ros-foxy-ros-workspace | cut -d" " -f2)"
2021-06-09 16:28:28 ERROR 404: Not Found.
This is currently failing industrial_ci:
https://github.com/vatanaksoytezer/warehouse_ros_mongo/runs/2783974132?check_suite_focus=true
The text was updated successfully, but these errors were encountered: