There were errors in two separate attempts to complete the release process for gz-sim 10.2.0, corresponding to the following gz-sim10-source jobs:
Each of those -source jobs generated tarball artifacts of size 339.79 MiB (with different sha256 checksums), but in the console output of the repository_uploader_packages jobs, files of smaller size were uploaded to s3, and downstream debbuilder jobs failed to match the sha256 checksum after downloading from s3.
upload: '/home/jenkins/workspace/repository_uploader_packages/pkgs/gz-sim-10.2.0.tar.bz2' -> 's3://osrf-distributions/gz-sim/releases/gz-sim-10.2.0.tar.bz2' [part 1 of 21, 15MB] [1 of 1]
...
upload: '/home/jenkins/workspace/repository_uploader_packages/pkgs/gz-sim-10.2.0.tar.bz2' -> 's3://osrf-distributions/gz-sim/releases/gz-sim-10.2.0.tar.bz2' [part 20 of 21, 15MB] [1 of 1]
...
upload: '/home/jenkins/workspace/repository_uploader_packages/pkgs/gz-sim-10.2.0.tar.bz2' -> 's3://osrf-distributions/gz-sim/releases/gz-sim-10.2.0.tar.bz2' [part 21 of 21, 4MB] [1 of 1]
upload: '/home/jenkins/workspace/repository_uploader_packages/pkgs/gz-sim-10.2.0.tar.bz2' -> 's3://osrf-distributions/gz-sim/releases/gz-sim-10.2.0.tar.bz2' [part 1 of 13, 15MB] [1 of 1]
...
upload: '/home/jenkins/workspace/repository_uploader_packages/pkgs/gz-sim-10.2.0.tar.bz2' -> 's3://osrf-distributions/gz-sim/releases/gz-sim-10.2.0.tar.bz2' [part 12 of 13, 15MB] [1 of 1]
...
upload: '/home/jenkins/workspace/repository_uploader_packages/pkgs/gz-sim-10.2.0.tar.bz2' -> 's3://osrf-distributions/gz-sim/releases/gz-sim-10.2.0.tar.bz2' [part 13 of 13, 11MB] [1 of 1]
In this case, we downloaded a tarball artifact from the -source job and manually uploaded it to s3 to proceed with this release, but we did not identify the underlying cause of the incomplete tarball.
There were errors in two separate attempts to complete the release process for gz-sim 10.2.0, corresponding to the following gz-sim10-source jobs:
Each of those
-sourcejobs generated tarball artifacts of size 339.79 MiB (with different sha256 checksums), but in the console output of the repository_uploader_packages jobs, files of smaller size were uploaded to s3, and downstream debbuilder jobs failed to match the sha256 checksum after downloading from s3.In this case, we downloaded a tarball artifact from the
-sourcejob and manually uploaded it to s3 to proceed with this release, but we did not identify the underlying cause of the incomplete tarball.