Running as unit: rb-build-amd64_8-77228.service
====================================================================================
Thu Oct 30 22:59:27 UTC 2025 - running /srv/jenkins/bin/reproducible_build.sh (for job reproducible_builder_amd64_8) on jenkins, called using "ionos15-amd64 ionos11-amd64" as arguments.
Thu Oct 30 22:59:27 UTC 2025 - actually running "reproducible_build.sh" (md5sum cc591790ab2c8e13f5e554202b95c89c) as "/tmp/jenkins-script-C11HcS0o"

$ git clone https://salsa.debian.org/qa/jenkins.debian.net.git ; more CONTRIBUTING

Thu Oct 30 22:59:27 UTC 2025 - checking /var/lib/jenkins/offline_nodes if ionos15-amd64.debian.net is marked as down.
Thu Oct 30 22:59:27 UTC 2025 - checking via ssh if ionos15-amd64.debian.net is up.
removed '/tmp/read-only-fs-test-eiN54f'
Thu Oct 30 22:59:27 UTC 2025 - checking /var/lib/jenkins/offline_nodes if ionos11-amd64.debian.net is marked as down.
Thu Oct 30 22:59:27 UTC 2025 - checking via ssh if ionos11-amd64.debian.net is up.
removed '/tmp/read-only-fs-test-HeEHHq'
ok, let's check if rust-xz2 is building anywhere yet…
hm, seems rust-xz2 is building somewhere… schedule table now listed it as building somewhere else.
Thu Oct 30 22:59:37 UTC 2025  W: Package rust-xz2 (id=3714636) in unstable on amd64 is probably already building at amd64_24/78788, while this is https://jenkins.debian.net/userContent/reproducible/debian/build_service/amd64_8/77228/.

Thu Oct 30 22:59:37 UTC 2025  W: Terminating this build quickly and nicely...
Starting cleanup.
/srv/reproducible-results/rbuild-debian/r-b-build.Rq5QZpea/rbuildlog.ORbaYvR:	 29.6% -- replaced with /srv/reproducible-results/rbuild-debian/r-b-build.Rq5QZpea/rbuildlog.ORbaYvR.gz
[2025-10-30 22:59:37] INFO: Starting at 2025-10-30 22:59:37.682072
[2025-10-30 22:59:37] INFO: Generating the pages of 1 package(s)
[2025-10-30 22:59:37] INFO: Finished at 2025-10-30 22:59:37.899432, took: 0:00:00.217363
All cleanup done.
Thu Oct 30 22:59:37 UTC 2025 - reproducible_build.sh stopped running as /tmp/jenkins-script-C11HcS0o, removing.
Finished with result: success
Main processes terminated with: code=exited, status=0/SUCCESS
Service runtime: 10.315s
CPU time consumed: 865ms
Memory peak: 34.6M (swap: 0B)