Log files do not contain some failure strings that they used to
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Auto Package Testing |
New
|
Undecided
|
Unassigned |
Bug Description
Recently a version of systemd was uploaded which broke resolved and caused the autopackage tests for systemd to fail. The following messages were logged:
autopkgtest [10:17:56]: rebooting testbed after setup commands that affected boot
autopkgtest [10:18:11]: testbed running kernel: Linux 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022
autopkgtest [10:18:12]: testbed dpkg architecture: amd64
autopkgtest [10:18:14]: @@@@@@@
qemu-system-x86_64: terminating on signal 15 from pid 983677 (/usr/bin/python3)
autopkgtest [10:21:21]: ERROR: testbed failure: rules extract failed with exit code 100 (apt failure)
However, running the test w/ autopkgtest and --shell-fail we see the following:
Err:1 https:/
Temporary failure resolving 'ppa.launchpadc
Err:2 https:/
Temporary failure resolving 'ppa.launchpadc
Err:3 https:/
Temporary failure resolving 'ppa.launchpadc
E: Failed to fetch https:/
E: Failed to fetch https:/
E: Failed to fetch https:/
E: Failed to fetch some archives.
Looking at FAIL_PKG_STRINGS in autopkgtest-
The result.tar file from running the bad version of systemd in the staging autopkgtest environment.