[Qa-jenkins-scm] Build failed in Jenkins: dpkg_sid_find_trigger_cycles #378

[jenkins at jenkins.debian.net]

See <https://jenkins.debian.net/job/dpkg_sid_find_trigger_cycles/378/display/redirect>

------------------------------------------
Started by user Holger Levsen
[EnvInject] - Loading node environment variables.
Building on master in workspace <https://jenkins.debian.net/job/dpkg_sid_find_trigger_cycles/ws/>
[workspace] $ /bin/sh -xe /tmp/jenkins702583439294883447.sh
+ /srv/jenkins/bin/find_dpkg_trigger_cycles.sh sid
====================================================================================

Mon 20 Nov 08:40:09 UTC 2017 - running /srv/jenkins/bin/find_dpkg_trigger_cycles.sh (dpkg_sid_find_trigger_cycles) on jenkins now.

To learn to understand this, git clone https://anonscm.debian.org/git/qa/jenkins.debian.net.git
and then have a look at the files README, INSTALL, CONTRIBUTING and maybe TODO.

This invocation of this script, which is located in bin/find_dpkg_trigger_cycles.sh,
has been called using "sid" as arguments.

Please send feedback about jenkins to qa-jenkins-dev at lists.alioth.debian.org,
or as a bug against the 'jenkins.debian.org' pseudo-package,
feedback about specific job results should go to their respective lists and/or the BTS.

====================================================================================
Mon 20 Nov 08:40:09 UTC 2017 - start running "/srv/jenkins/bin/find_dpkg_trigger_cycles.sh" (md5sum 637fdc2f67b8f0e0d071adbd164ff1ba) as "/tmp/jenkins-script-yusERVIm" on jenkins.


WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
W: Unable to read tmp.jenkins_find_dpkg_trigger_cycles_amd64_sid_84LBtgwv3j/tmp.jenkins_find_dpkg_trigger_cycles_amd64_sid_84LBtgwv3j/etc/apt/apt.conf.d/ - DirectoryExists (2: No such file or directory)
W: Unable to read tmp.jenkins_find_dpkg_trigger_cycles_amd64_sid_84LBtgwv3j/tmp.jenkins_find_dpkg_trigger_cycles_amd64_sid_84LBtgwv3j/etc/apt/tmp.jenkins_find_dpkg_trigger_cycles_amd64_sid_84LBtgwv3j/etc/apt/sources.list.d/ - DirectoryExists (2: No such file or directory)
W: Unable to read tmp.jenkins_find_dpkg_trigger_cycles_amd64_sid_84LBtgwv3j/tmp.jenkins_find_dpkg_trigger_cycles_amd64_sid_84LBtgwv3j/etc/apt/tmp.jenkins_find_dpkg_trigger_cycles_amd64_sid_84LBtgwv3j/etc/apt/sources.list - RealFileExists (2: No such file or directory)
E: List directory tmp.jenkins_find_dpkg_trigger_cycles_amd64_sid_84LBtgwv3j/tmp.jenkins_find_dpkg_trigger_cycles_amd64_sid_84LBtgwv3j/var/lib/apt/lists/partial is missing. - Acquire (2: No such file or directory)
E: flAbsPath on tmp.jenkins_find_dpkg_trigger_cycles_amd64_sid_84LBtgwv3j/tmp.jenkins_find_dpkg_trigger_cycles_amd64_sid_84LBtgwv3j/var/lib/apt/tmp.jenkins_find_dpkg_trigger_cycles_amd64_sid_84LBtgwv3j/var/lib/dpkg/status failed - realpath (2: No such file or directory)
E: Could not open file  - open (2: No such file or directory)
E: Problem opening 
E: The package lists or status file could not be parsed or opened.
Mon 20 Nov 08:40:09 UTC 2017 - /srv/jenkins/bin/find_dpkg_trigger_cycles.sh stopped running as /tmp/jenkins-script-yusERVIm, which will now be removed.
Build step 'Execute shell' marked build as failure