Running as unit: rb-build-amd64_15-53368.service ==================================================================================== Wed Apr 23 13:25:46 UTC 2025 - running /srv/jenkins/bin/reproducible_build.sh (for job reproducible_builder_amd64_15) on jenkins, called using "ionos11-amd64 ionos15-amd64" as arguments. Wed Apr 23 13:25:46 UTC 2025 - actually running "reproducible_build.sh" (md5sum 68e686e434c9ab7bc3ec047d8b309cbc) as "/tmp/jenkins-script-HVYWwnKt" $ git clone https://salsa.debian.org/qa/jenkins.debian.net.git ; more CONTRIBUTING Wed Apr 23 13:25:46 UTC 2025 - checking /var/lib/jenkins/offline_nodes if ionos11-amd64.debian.net is marked as down. Wed Apr 23 13:25:46 UTC 2025 - checking via ssh if ionos11-amd64.debian.net is up. removed '/tmp/read-only-fs-test-mXtP8E' Wed Apr 23 13:25:46 UTC 2025 - checking /var/lib/jenkins/offline_nodes if ionos15-amd64.debian.net is marked as down. Wed Apr 23 13:25:46 UTC 2025 - checking via ssh if ionos15-amd64.debian.net is up. removed '/tmp/read-only-fs-test-L3UO2a' ok, let's check if r-cran-deal is building anywhere yet… hm, seems r-cran-deal is building somewhere… schedule table now listed it as building somewhere else. Wed Apr 23 13:26:00 UTC 2025 W: Package r-cran-deal (id=16982) in unstable on amd64 is probably already building at amd64_9/35341, while this is https://jenkins.debian.net/userContent/reproducible/debian/build_service/amd64_15/53368/. Wed Apr 23 13:26:00 UTC 2025 W: Terminating this build quickly and nicely... Starting cleanup. /srv/reproducible-results/rbuild-debian/r-b-build.hMx1Lhx7/rbuildlog.WNmDgnv: 30.2% -- replaced with /srv/reproducible-results/rbuild-debian/r-b-build.hMx1Lhx7/rbuildlog.WNmDgnv.gz [2025-04-23 13:26:00] INFO: Starting at 2025-04-23 13:26:00.701684 [2025-04-23 13:26:00] INFO: Generating the pages of 1 package(s) [2025-04-23 13:26:01] INFO: Finished at 2025-04-23 13:26:01.145111, took: 0:00:00.443431 All cleanup done. Wed Apr 23 13:26:01 UTC 2025 - reproducible_build.sh stopped running as /tmp/jenkins-script-HVYWwnKt, removing. Finished with result: success Main processes terminated with: code=exited/status=0 Service runtime: 15.078s CPU time consumed: 1.773s