Running as unit: rb-build-amd64_1-54624.service; invocation ID: 05809f190cc145099abb8043d24af9c8
====================================================================================
Wed Sep 17 09:53:23 UTC 2025 - running /srv/jenkins/bin/reproducible_build.sh (for job reproducible_builder_amd64_1) on jenkins, called using "ionos1-amd64 ionos5-amd64" as arguments.
Wed Sep 17 09:53:23 UTC 2025 - actually running "reproducible_build.sh" (md5sum cc591790ab2c8e13f5e554202b95c89c) as "/tmp/jenkins-script-r1lyrqct"

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

Wed Sep 17 09:53:23 UTC 2025 - checking /var/lib/jenkins/offline_nodes if ionos1-amd64.debian.net is marked as down.
Wed Sep 17 09:53:23 UTC 2025 - checking via ssh if ionos1-amd64.debian.net is up.
removed '/tmp/read-only-fs-test-ol6ODs'
Wed Sep 17 09:53:23 UTC 2025 - checking /var/lib/jenkins/offline_nodes if ionos5-amd64.debian.net is marked as down.
Wed Sep 17 09:53:23 UTC 2025 - checking via ssh if ionos5-amd64.debian.net is up.
removed '/tmp/read-only-fs-test-yQdzzD'
ok, let's check if ruby-spoon is building anywhere yet…
hm, seems ruby-spoon is building somewhere… schedule table now listed it as building somewhere else.
Wed Sep 17 09:53:28 UTC 2025  W: Package ruby-spoon (id=6383093) in forky on amd64 is probably already building at amd64_6/57898, while this is https://jenkins.debian.net/userContent/reproducible/debian/build_service/amd64_1/54624/.

Wed Sep 17 09:53:28 UTC 2025  W: Terminating this build quickly and nicely...
Starting cleanup.
/srv/reproducible-results/rbuild-debian/r-b-build.H1xvWnzp/rbuildlog.W1boC1H:	 29.5% -- replaced with /srv/reproducible-results/rbuild-debian/r-b-build.H1xvWnzp/rbuildlog.W1boC1H.gz
[2025-09-17 09:53:28] INFO: Starting at 2025-09-17 09:53:28.738086
[2025-09-17 09:53:28] INFO: Generating the pages of 1 package(s)
[2025-09-17 09:53:29] INFO: Finished at 2025-09-17 09:53:29.011444, took: 0:00:00.273363
All cleanup done.
Wed Sep 17 09:53:29 UTC 2025 - reproducible_build.sh stopped running as /tmp/jenkins-script-r1lyrqct, removing.
Finished with result: success
Main processes terminated with: code=exited, status=0/SUCCESS
Service runtime: 6.041s
CPU time consumed: 948ms
Memory peak: 37.8M (swap: 0B)