Running as unit: rb-build-amd64_29-54997.service ==================================================================================== Wed Sep 17 11:32:03 UTC 2025 - running /srv/jenkins/bin/reproducible_build.sh (for job reproducible_builder_amd64_29) on jenkins, called using "ionos1-amd64 ionos15-amd64" as arguments. Wed Sep 17 11:32:04 UTC 2025 - actually running "reproducible_build.sh" (md5sum cc591790ab2c8e13f5e554202b95c89c) as "/tmp/jenkins-script-CTJUqy6v" $ git clone https://salsa.debian.org/qa/jenkins.debian.net.git ; more CONTRIBUTING Wed Sep 17 11:32:04 UTC 2025 - checking /var/lib/jenkins/offline_nodes if ionos1-amd64.debian.net is marked as down. Wed Sep 17 11:32:04 UTC 2025 - checking via ssh if ionos1-amd64.debian.net is up. removed '/tmp/read-only-fs-test-mS48cs' Wed Sep 17 11:32:04 UTC 2025 - checking /var/lib/jenkins/offline_nodes if ionos15-amd64.debian.net is marked as down. Wed Sep 17 11:32:04 UTC 2025 - checking via ssh if ionos15-amd64.debian.net is up. removed '/tmp/read-only-fs-test-0MPMR6' ok, let's check if rust-ntp-udp is building anywhere yet… hm, seems rust-ntp-udp is building somewhere… schedule table now listed it as building somewhere else. Wed Sep 17 11:32:11 UTC 2025 W: Package rust-ntp-udp (id=6434695) in forky on amd64 is probably already building at amd64_7/72596, while this is https://jenkins.debian.net/userContent/reproducible/debian/build_service/amd64_29/54997/. Wed Sep 17 11:32:11 UTC 2025 W: Terminating this build quickly and nicely... Starting cleanup. /srv/reproducible-results/rbuild-debian/r-b-build.DqBNM0JI/rbuildlog.teO61M9: 29.8% -- replaced with /srv/reproducible-results/rbuild-debian/r-b-build.DqBNM0JI/rbuildlog.teO61M9.gz [2025-09-17 11:32:11] INFO: Starting at 2025-09-17 11:32:11.939630 [2025-09-17 11:32:12] INFO: Generating the pages of 1 package(s) [2025-09-17 11:32:12] INFO: Finished at 2025-09-17 11:32:12.127234, took: 0:00:00.187607 All cleanup done. Wed Sep 17 11:32:12 UTC 2025 - reproducible_build.sh stopped running as /tmp/jenkins-script-CTJUqy6v, removing. Finished with result: success Main processes terminated with: code=exited, status=0/SUCCESS Service runtime: 8.279s CPU time consumed: 853ms Memory peak: 34.3M (swap: 0B)