Performing the verification on Noble.
First, we check to see if we can reproduce the problem.
$ apt policy autopkgtest
autopkgtest:
Installed: 5.34ubuntu2
Candidate: 5.34ubuntu2
Version table:
5.38ubuntu1~24.04.1 100
100 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages
*** 5.34ubuntu2 500
500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages
100 /var/lib/dpkg/status
After creating a Noble image we run the reproducer:
$ autopkgtest -U -ddd hello*.dsc -- qemu ../autopkgtest-noble-amd64.img
autopkgtest: DBG: autopkgtest options: Namespace(override_control=None,
only_tests=[], skip_tests=None, built_binaries=True, architecture=None,
packages=['hello_2.10-3build2.dsc'], output_dir=None)
autopkgtest: DBG: virt-runner arguments: ['qemu',
'../autopkgtest-noble-amd64.img']
autopkgtest: DBG: actions: [('source', 'hello_2.10-3build2.dsc', True)]
autopkgtest: DBG: build binaries: True
autopkgtest: DBG: testbed init
autopkgtest [12:09:07]: starting date and time: 2024-10-21 12:09:07-0700
autopkgtest [12:09:07]: version 5.34ubuntu2
autopkgtest [12:09:07]: host clean-noble-amd64; command line:
/usr/bin/autopkgtest -U -ddd hello_2.10-3build2.dsc -- qemu
../autopkgtest-noble-amd64.img
(truncated for brevity)
autopkgtest: DBG: sending command to testbed: copydown hello_2.10.orig.tar.gz
/tmp/autopkgtest.gHgSJl/hello_2.10.orig.tar.gz
autopkgtest: DBG: got reply from testbed: timeout
autopkgtest: DBG: sending command to testbed: auxverb_debug_fail
autopkgtest: DBG: got reply from testbed: ok
autopkgtest: DBG: TestbedFailure sent `auxverb_debug_fail', got `timeout',
expected `ok...'
autopkgtest: DBG: testbed stop
autopkgtest: DBG: testbed close, scratch=/tmp/autopkgtest.gHgSJl
autopkgtest: DBG: sending command to testbed: close
qemu-system-x86_64: terminating on signal 15 from pid 7523 (/usr/bin/python3)
autopkgtest: DBG: got reply from testbed: ok
autopkgtest: DBG: sending command to testbed: quit
autopkgtest [12:14:36]: ERROR: testbed failure: sent `auxverb_debug_fail', got
`timeout', expected `ok...'
The testbed hung until timeout during copydown, so the bug is replicated.
Now we verify the fix.
$ apt policy autopkgtest
autopkgtest:
Installed: 5.38ubuntu1~24.04.1
Candidate: 5.38ubuntu1~24.04.1
Version table:
*** 5.38ubuntu1~24.04.1 100
100 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages
100 /var/lib/dpkg/status
5.34ubuntu2 500
500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages
We create a fresh Noble image and rerun the reproducer:
$ autopkgtest -U hello*.dsc -- qemu ../autopkgtest-noble-amd64.img
autopkgtest [12:35:03]: starting date and time: 2024-10-21 12:35:03-0700
autopkgtest [12:35:03]: version 5.38ubuntu1~24.04.1
autopkgtest [12:35:03]: host clean-noble-amd64; command line:
/usr/bin/autopkgtest -U hello_2.10-3build2.dsc -- qemu
../autopkgtest-noble-amd64.img
autopkgtest [12:35:19]: testbed dpkg architecture: amd64
autopkgtest [12:35:20]: testbed apt version: 2.7.14build2
autopkgtest [12:35:20]: @@@@@@@@@@@@@@@@@@@@ test bed setup
(truncated for brevity)
autopkgtest [12:37:04]: test upstream-tests: [-----------------------
Testing greeting-1 ...
Testing hello-1 ...
Testing last-1 ...
Testing traditional-1 ...
autopkgtest [12:37:05]: test upstream-tests: -----------------------]
autopkgtest [12:37:06]: test upstream-tests: - - - - - - - - - - results - - -
- - - - - - -
upstream-tests PASS
autopkgtest [12:37:06]: @@@@@@@@@@@@@@@@@@@@ summary
command1 PASS
upstream-tests PASS
So the test was completed without a timeout.
This concludes the verification for Noble.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056461
Title:
autopkgtest-virt-qemu on noble images sometimes hangs doing copydown
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2056461/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
