Running as unit: rb-build-amd64_33-88300.service; invocation ID: 1051c1fe261a473baceea4b74d2d577b ==================================================================================== Fri Oct 31 15:57:36 UTC 2025 - running /srv/jenkins/bin/reproducible_build.sh (for job reproducible_builder_amd64_33) on jenkins, called using "infom01-amd64 infom02-amd64" as arguments. Fri Oct 31 15:57:36 UTC 2025 - actually running "reproducible_build.sh" (md5sum cc591790ab2c8e13f5e554202b95c89c) as "/tmp/jenkins-script-U3j7cnLy" $ git clone https://salsa.debian.org/qa/jenkins.debian.net.git ; more CONTRIBUTING Fri Oct 31 15:57:36 UTC 2025 - checking /var/lib/jenkins/offline_nodes if infom01-amd64.debian.net is marked as down. Fri Oct 31 15:57:36 UTC 2025 - checking via ssh if infom01-amd64.debian.net is up. removed '/tmp/read-only-fs-test-lAUAkv' Fri Oct 31 15:57:37 UTC 2025 - checking /var/lib/jenkins/offline_nodes if infom02-amd64.debian.net is marked as down. Fri Oct 31 15:57:37 UTC 2025 - checking via ssh if infom02-amd64.debian.net is up. removed '/tmp/read-only-fs-test-bmEJpF' ok, let's check if ruby-rbtrace is building anywhere yet… ok, ruby-rbtrace is not building anywhere… UPDATE 1 ============================================================================= Initialising reproducibly build of ruby-rbtrace in unstable on amd64 on jenkins now. 1st build will be done on infom01-amd64.debian.net. 2nd build will be done on infom02-amd64.debian.net. ============================================================================= Fri Oct 31 15:57:55 UTC 2025 I: starting to build ruby-rbtrace/unstable/amd64 on jenkins on '2025-10-31 15:57' Fri Oct 31 15:57:55 UTC 2025 I: The jenkins build log is/was available at https://jenkins.debian.net/userContent/reproducible/debian/build_service/amd64_33/88300/console.log 1761926275 amd64 unstable ruby-rbtrace Fri Oct 31 15:57:55 UTC 2025 I: Downloading source for unstable/ruby-rbtrace=0.5.2-0.1 E: Can not find version '0.5.2-0.1' of package 'ruby-rbtrace' E: Unable to find a source package for ruby-rbtrace Fri Oct 31 15:57:55 UTC 2025 E: Download of ruby-rbtrace=0.5.2-0.1 sources (for unstable) failed. ls: cannot access 'ruby-rbtrace*': No such file or directory Fri Oct 31 15:57:55 UTC 2025 E: Sleeping 5m before re-trying... Fri Oct 31 16:02:55 UTC 2025 I: Downloading source for unstable/ruby-rbtrace=0.5.2-0.1 E: Can not find version '0.5.2-0.1' of package 'ruby-rbtrace' E: Unable to find a source package for ruby-rbtrace Fri Oct 31 16:02:55 UTC 2025 E: Download of ruby-rbtrace=0.5.2-0.1 sources (for unstable) failed. ls: cannot access 'ruby-rbtrace*': No such file or directory Fri Oct 31 16:02:55 UTC 2025 E: Sleeping 5m before re-trying... Fri Oct 31 16:07:55 UTC 2025 I: Downloading source for unstable/ruby-rbtrace=0.5.2-0.1 E: Can not find version '0.5.2-0.1' of package 'ruby-rbtrace' E: Unable to find a source package for ruby-rbtrace Fri Oct 31 16:07:55 UTC 2025 E: Download of ruby-rbtrace=0.5.2-0.1 sources (for unstable) failed. ls: cannot access 'ruby-rbtrace*': No such file or directory Fri Oct 31 16:07:55 UTC 2025 E: Sleeping 5m before re-trying... Fri Oct 31 16:12:55 UTC 2025 I: Downloading source for unstable/ruby-rbtrace=0.5.2-0.1 E: Can not find version '0.5.2-0.1' of package 'ruby-rbtrace' E: Unable to find a source package for ruby-rbtrace Fri Oct 31 16:12:56 UTC 2025 W: Download of ruby-rbtrace sources from unstable failed. ls: cannot access 'ruby-rbtrace*': No such file or directory Fri Oct 31 16:12:56 UTC 2025 W: Maybe there was a network problem, or ruby-rbtrace is not a source package in unstable, or it was removed or renamed. Please investigate. Sleeping 5m as this should not happen. INSERT 0 1 INSERT 0 1 DELETE 1 [2025-10-31 16:12:56] INFO: Starting at 2025-10-31 16:12:56.545345 [2025-10-31 16:12:56] INFO: Generating the pages of 1 package(s) [2025-10-31 16:12:56] CRITICAL: buildinfo not detected at /var/lib/jenkins/userContent/reproducible/debian/buildinfo/unstable/amd64/ruby-rbtrace_0.5.2-0.1_amd64.buildinfo [2025-10-31 16:12:56] CRITICAL: https://tests.reproducible-builds.org/debian/unstable/amd64/ruby-rbtrace didn't produce a buildlog, even though it has been built. [2025-10-31 16:12:56] ERROR: Either /var/lib/jenkins/userContent/reproducible/debian/logs/unstable/arm64/ruby-rbtrace_0.5.1-1.1.build2.log.gz or /var/lib/jenkins/userContent/reproducible/debian/logdiffs/unstable/arm64/ruby-rbtrace_0.5.1-1.1.diff.gz is missing [2025-10-31 16:12:56] INFO: Finished at 2025-10-31 16:12:56.727199, took: 0:00:00.181857 Fri Oct 31 16:12:56 UTC 2025 - successfully updated the database and updated https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-rbtrace.html Starting cleanup. /var/lib/jenkins/userContent/reproducible/debian/rbuild/unstable/amd64/ruby-rbtrace_0.5.2-0.1.rbuild.log: 71.0% -- replaced with /var/lib/jenkins/userContent/reproducible/debian/rbuild/unstable/amd64/ruby-rbtrace_0.5.2-0.1.rbuild.log.gz [2025-10-31 16:17:57] INFO: Starting at 2025-10-31 16:17:57.032169 [2025-10-31 16:17:57] INFO: Generating the pages of 1 package(s) [2025-10-31 16:17:57] CRITICAL: buildinfo not detected at /var/lib/jenkins/userContent/reproducible/debian/buildinfo/unstable/amd64/ruby-rbtrace_0.5.2-0.1_amd64.buildinfo [2025-10-31 16:17:57] ERROR: Either /var/lib/jenkins/userContent/reproducible/debian/logs/unstable/amd64/ruby-rbtrace_0.5.2-0.1.build2.log.gz or /var/lib/jenkins/userContent/reproducible/debian/logdiffs/unstable/amd64/ruby-rbtrace_0.5.2-0.1.diff.gz is missing [2025-10-31 16:17:57] CRITICAL: buildinfo not detected at /var/lib/jenkins/userContent/reproducible/debian/buildinfo/unstable/arm64/ruby-rbtrace_0.5.2-0.1_arm64.buildinfo [2025-10-31 16:17:57] CRITICAL: https://tests.reproducible-builds.org/debian/unstable/arm64/ruby-rbtrace didn't produce a buildlog, even though it has been built. [2025-10-31 16:17:57] INFO: Finished at 2025-10-31 16:17:57.267052, took: 0:00:00.234886 All cleanup done. Fri Oct 31 16:17:57 UTC 2025 - total duration: 0h 0m 0s. Fri Oct 31 16:17:57 UTC 2025 - reproducible_build.sh stopped running as /tmp/jenkins-script-U3j7cnLy, removing. Finished with result: success Main processes terminated with: code=exited, status=0/SUCCESS Service runtime: 20min 20.669s CPU time consumed: 2.381s Memory peak: 37.8M (swap: 0B)