Running as unit: rb-build-amd64_30-58816.service
====================================================================================
Tue Sep 16 09:27:43 UTC 2025 - running /srv/jenkins/bin/reproducible_build.sh (for job reproducible_builder_amd64_30) on jenkins, called using "ionos15-amd64 ionos1-amd64" as arguments.
Tue Sep 16 09:27:43 UTC 2025 - actually running "reproducible_build.sh" (md5sum cc591790ab2c8e13f5e554202b95c89c) as "/tmp/jenkins-script-XOOWpRKW"

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

Tue Sep 16 09:27:44 UTC 2025 - checking /var/lib/jenkins/offline_nodes if ionos15-amd64.debian.net is marked as down.
Tue Sep 16 09:27:44 UTC 2025 - checking via ssh if ionos15-amd64.debian.net is up.
removed '/tmp/read-only-fs-test-I0Lo0K'
Tue Sep 16 09:27:44 UTC 2025 - checking /var/lib/jenkins/offline_nodes if ionos1-amd64.debian.net is marked as down.
Tue Sep 16 09:27:44 UTC 2025 - checking via ssh if ionos1-amd64.debian.net is up.
removed '/tmp/read-only-fs-test-u5p5dU'
ok, let's check if kronosnet is building anywhere yet…
hm, seems kronosnet is building somewhere… schedule table now listed it as building somewhere else.
Tue Sep 16 09:27:59 UTC 2025  W: Package kronosnet (id=369486) in unstable on amd64 is probably already building at amd64_31/57644, while this is https://jenkins.debian.net/userContent/reproducible/debian/build_service/amd64_30/58816/.

Tue Sep 16 09:27:59 UTC 2025  W: Terminating this build quickly and nicely...
Starting cleanup.
/srv/reproducible-results/rbuild-debian/r-b-build.dEwpmi2k/rbuildlog.AMYaWZ7:	 30.5% -- replaced with /srv/reproducible-results/rbuild-debian/r-b-build.dEwpmi2k/rbuildlog.AMYaWZ7.gz
[2025-09-16 09:27:59] INFO: Starting at 2025-09-16 09:27:59.984980
[2025-09-16 09:28:00] INFO: Generating the pages of 1 package(s)
[2025-09-16 09:28:00] INFO: Finished at 2025-09-16 09:28:00.268790, took: 0:00:00.283817
All cleanup done.
Tue Sep 16 09:28:00 UTC 2025 - reproducible_build.sh stopped running as /tmp/jenkins-script-XOOWpRKW, removing.
Finished with result: success
Main processes terminated with: code=exited, status=0/SUCCESS
Service runtime: 16.671s
CPU time consumed: 1.006s
Memory peak: 37.7M (swap: 0B)