Running as unit: rb-build-amd64_37-38714.service ==================================================================================== Tue Nov 26 04:06:03 UTC 2024 - running /srv/jenkins/bin/reproducible_build.sh (for job reproducible_builder_amd64_37) on jenkins, called using "infom01-amd64 infom02-amd64" as arguments. Tue Nov 26 04:06:03 UTC 2024 - actually running "reproducible_build.sh" (md5sum 68e686e434c9ab7bc3ec047d8b309cbc) as "/tmp/jenkins-script-T9XykBfG" $ git clone https://salsa.debian.org/qa/jenkins.debian.net.git ; more CONTRIBUTING Tue Nov 26 04:06:03 UTC 2024 - checking /var/lib/jenkins/offline_nodes if infom01-amd64.debian.net is marked as down. Tue Nov 26 04:06:03 UTC 2024 - checking via ssh if infom01-amd64.debian.net is up. removed '/tmp/read-only-fs-test-FEx50t' Tue Nov 26 04:06:04 UTC 2024 - checking /var/lib/jenkins/offline_nodes if infom02-amd64.debian.net is marked as down. Tue Nov 26 04:06:04 UTC 2024 - checking via ssh if infom02-amd64.debian.net is up. removed '/tmp/read-only-fs-test-dcqfrK' ok, let's check if pyjunitxml is building anywhere yet… hm, seems pyjunitxml is building somewhere… schedule table now listed it as building somewhere else. Tue Nov 26 04:06:15 UTC 2024 W: Package pyjunitxml (id=15831) in unstable on amd64 is probably already building at amd64_13/25097, while this is https://jenkins.debian.net/userContent/reproducible/debian/build_service/amd64_37/38714/. Tue Nov 26 04:06:15 UTC 2024 W: Terminating this build quickly and nicely... Starting cleanup. /srv/reproducible-results/rbuild-debian/r-b-build.KdL9Q5dg/rbuildlog.FZHKuzG: 30.2% -- replaced with /srv/reproducible-results/rbuild-debian/r-b-build.KdL9Q5dg/rbuildlog.FZHKuzG.gz [2024-11-26 04:06:15] INFO: Starting at 2024-11-26 04:06:15.823537 [2024-11-26 04:06:15] INFO: Generating the pages of 1 package(s) [2024-11-26 04:06:16] INFO: Finished at 2024-11-26 04:06:16.421786, took: 0:00:00.598258 All cleanup done. Tue Nov 26 04:06:16 UTC 2024 - reproducible_build.sh stopped running as /tmp/jenkins-script-T9XykBfG, removing. Finished with result: success Main processes terminated with: code=exited/status=0 Service runtime: 13.238s CPU time consumed: 2.301s