Running as unit: rb-build-amd64_37-82847.service
====================================================================================
Tue Sep 16 14:19:02 UTC 2025 - running /srv/jenkins/bin/reproducible_build.sh (for job reproducible_builder_amd64_37) on jenkins, called using "infom01-amd64 infom02-amd64" as arguments.
Tue Sep 16 14:19:02 UTC 2025 - actually running "reproducible_build.sh" (md5sum cc591790ab2c8e13f5e554202b95c89c) as "/tmp/jenkins-script-ovkJNvwV"

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

Tue Sep 16 14:19:02 UTC 2025 - checking /var/lib/jenkins/offline_nodes if infom01-amd64.debian.net is marked as down.
Tue Sep 16 14:19:02 UTC 2025 - checking via ssh if infom01-amd64.debian.net is up.
removed '/tmp/read-only-fs-test-9tQuNC'
Tue Sep 16 14:19:03 UTC 2025 - checking /var/lib/jenkins/offline_nodes if infom02-amd64.debian.net is marked as down.
Tue Sep 16 14:19:03 UTC 2025 - checking via ssh if infom02-amd64.debian.net is up.
removed '/tmp/read-only-fs-test-xSfYta'
ok, let's check if redshift is building anywhere yet…
hm, seems redshift is building somewhere… schedule table now listed it as building somewhere else.
Tue Sep 16 14:19:24 UTC 2025  W: Package redshift (id=6317406) in forky on amd64 is probably already building at amd64_24/73890, while this is https://jenkins.debian.net/userContent/reproducible/debian/build_service/amd64_37/82847/.

Tue Sep 16 14:19:24 UTC 2025  W: Terminating this build quickly and nicely...
Starting cleanup.
/srv/reproducible-results/rbuild-debian/r-b-build.7A54yqHZ/rbuildlog.yiu3HMi:	 29.8% -- replaced with /srv/reproducible-results/rbuild-debian/r-b-build.7A54yqHZ/rbuildlog.yiu3HMi.gz
[2025-09-16 14:19:25] INFO: Starting at 2025-09-16 14:19:25.200077
[2025-09-16 14:19:25] INFO: Generating the pages of 1 package(s)
[2025-09-16 14:19:25] INFO: Finished at 2025-09-16 14:19:25.480902, took: 0:00:00.280830
All cleanup done.
Tue Sep 16 14:19:25 UTC 2025 - reproducible_build.sh stopped running as /tmp/jenkins-script-ovkJNvwV, removing.
Finished with result: success
Main processes terminated with: code=exited, status=0/SUCCESS
Service runtime: 23.196s
CPU time consumed: 941ms
Memory peak: 38.2M (swap: 0B)