[Qa-jenkins-scm] Build failed in Jenkins: reproducible_debian_rebuilder_prototype #1951

[jenkins at jenkins.debian.net]

See <https://jenkins.debian.net/job/reproducible_debian_rebuilder_prototype/1951/display/redirect>

Changes:


------------------------------------------
Started by timer
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on ionos7-amd64.debian.net (ionos7 amd64) in workspace <https://jenkins.debian.net/job/reproducible_debian_rebuilder_prototype/ws/>
[reproducible_debian_rebuilder_prototype] $ /bin/sh -xe /tmp/jenkins10910057349735524298.sh
+ /srv/jenkins/bin/jenkins_master_wrapper.sh

###########################################################################################
###											###
### This prototype is meant to achieve several goals:					###
###											###
### One goal is to polish /usr/bin/debrebuild from src:devscripts to enable anyone to   ###
### independently verify that a distributed Debian binary package comes from the source ###
### package it's said to be coming from.						###
###											###
### Once this goal has been achieved we can document these steps. currently the answer	###
### to the question "how can I verify installed package X is reproducible?" is: "it's   ###
### really complicated" (and sometimes impossible or requires not yet written code).    ###
###											###
### Another goal is to create json export to integrate in tracker.d.o and/or		###
### packages.d.o as well as to provide statistics and graphs.				###
###											###
### The aim is to develop a 'real world' view about the reproducibility of all the      ###
### packages distributed via ftp.d.o. - so far tests.r-b.o/debian only shows the 	###
### 'theoretical' reproducibility of Debian packages.                                   ###
###											###
### We'll leave out the problem of 'trust' here quite entirely. that's why it's called	###
### a Debian rebuilder 'thing', to explore technical feasibility, duck taping our way	###
### ahead, keeping our motto 'to allow anyone to independently verify...' in mind.	###
###											###
###########################################################################################

====================================================================================
Sat 02 Jan 2021 07:24:56 AM UTC - running /srv/jenkins/bin/reproducible_debian_rebuilder_prototype.sh (for job reproducible_debian_rebuilder_prototype) on ionos7-amd64, called using "" as arguments.
Sat 02 Jan 2021 07:24:56 AM UTC - actually running "reproducible_debian_rebuilder_prototype.sh" (md5sum 4ca5ed0fd17053c2128919b3791405b1) as "/tmp/jenkins-script-nAjVE31r"

Please send feedback to qa-jenkins-dev at lists.alioth.debian.org or even better, provide https://salsa.debian.org/qa/jenkins.debian.net/merge_requests !

To dig deeper: git clone https://salsa.debian.org/qa/jenkins.debian.net.git && less README INSTALL CONTRIBUTING TODO

====================================================================================

###########################################################################################
###											###
### This prototype is meant to achieve several goals:					###
###											###
### One goal is to polish /usr/bin/debrebuild from src:devscripts to enable anyone to   ###
### independently verify that a distributed Debian binary package comes from the source ###
### package it's said to be coming from.						###
###											###
### Once this goal has been achieved we can document these steps. currently the answer	###
### to the question "how can I verify installed package X is reproducible?" is: "it's   ###
### really complicated" (and sometimes impossible or requires not yet written code).    ###
###											###
### Another goal is to create json export to integrate in tracker.d.o and/or		###
### packages.d.o as well as to provide statistics and graphs.				###
###											###
### The aim is to develop a 'real world' view about the reproducibility of all the      ###
### packages distributed via ftp.d.o. - so far tests.r-b.o/debian only shows the 	###
### 'theoretical' reproducibility of Debian packages.                                   ###
###											###
### We'll leave out the problem of 'trust' here quite entirely. that's why it's called	###
### a Debian rebuilder 'thing', to explore technical feasibility, duck taping our way	###
### ahead, keeping our motto 'to allow anyone to independently verify...' in mind.	###
###											###
###########################################################################################

ls: cannot access '/srv/reproducible-results/chdist/bullseye-amd64/var/lib/apt/lists/*_dists_bullseye_main_binary-amd64_Packages': No such file or directory
Sat 02 Jan 2021 07:24:57 AM UTC - reproducible_debian_rebuilder_prototype.sh stopped running as /tmp/jenkins-script-nAjVE31r, which will now be removed.

SSH EXIT CODE: 2
Build step 'Execute shell' marked build as failure