0s autopkgtest [09:34:31]: starting date and time: 2024-12-03 09:34:31+0000
  0s autopkgtest [09:34:31]: git checkout: be626eda Fix armhf LXD image generation for plucky
  0s autopkgtest [09:34:31]: host juju-7f2275-prod-proposed-migration-environment-15; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.r3sbjpok/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:boost1.83 --apt-upgrade mshr --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 --env=ADT_TEST_TRIGGERS=boost1.83/1.83.0-3.2ubuntu4 -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-15@bos03-arm64-6.secgroup --name adt-plucky-arm64-mshr-20241203-093431-juju-7f2275-prod-proposed-migration-environment-15-af1df67c-dde0-46dd-94a0-dc3a3edc78b2 --image adt/ubuntu-plucky-arm64-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-15 --net-id=net_prod-proposed-migration -e TERM=linux -e ''"'"'http_proxy=http://squid.internal:3128'"'"'' -e ''"'"'https_proxy=http://squid.internal:3128'"'"'' -e ''"'"'no_proxy=127.0.0.1,127.0.1.1,login.ubuntu.com,localhost,localdomain,novalocal,internal,archive.ubuntu.com,ports.ubuntu.com,security.ubuntu.com,ddebs.ubuntu.com,changelogs.ubuntu.com,keyserver.ubuntu.com,launchpadlibrarian.net,launchpadcontent.net,launchpad.net,10.24.0.0/24,keystone.ps5.canonical.com,objectstorage.prodstack5.canonical.com'"'"'' --mirror=http://ftpmaster.internal/ubuntu/
134s autopkgtest [09:36:45]: testbed dpkg architecture: arm64
134s autopkgtest [09:36:45]: testbed apt version: 2.9.14ubuntu1
134s autopkgtest [09:36:45]: @@@@@@@@@@@@@@@@@@@@ test bed setup
135s autopkgtest [09:36:46]: testbed release detected to be: None
135s autopkgtest [09:36:46]: updating testbed package index (apt update)
136s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB]
136s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease
136s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease
136s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease
136s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [781 kB]
137s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B]
137s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [65.3 kB]
137s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [15.1 kB]
137s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main arm64 Packages [145 kB]
137s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted arm64 Packages [58.2 kB]
137s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe arm64 Packages [669 kB]
137s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse arm64 Packages [21.3 kB]
137s Fetched 1838 kB in 1s (1571 kB/s)
138s Reading package lists...
139s Reading package lists...
139s Building dependency tree...
139s Reading state information...
141s Calculating upgrade...
141s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
142s Reading package lists...
142s Building dependency tree...
142s Reading state information...
143s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
143s autopkgtest [09:36:54]: upgrading testbed (apt dist-upgrade and autopurge)
144s Reading package lists...
144s Building dependency tree...
144s Reading state information...
145s Calculating upgrade...Starting pkgProblemResolver with broken count: 0
146s Starting 2 pkgProblemResolver with broken count: 0
146s Done
147s Entering ResolveByKeep
147s 
148s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
148s Reading package lists...
148s Building dependency tree...
148s Reading state information...
149s Starting pkgProblemResolver with broken count: 0
149s Starting 2 pkgProblemResolver with broken count: 0
149s Done
151s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
154s autopkgtest [09:37:05]: testbed running kernel: Linux 6.11.0-8-generic #8-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 16 14:19:41 UTC 2024
154s autopkgtest [09:37:05]: @@@@@@@@@@@@@@@@@@@@ apt-source mshr
160s Get:1 http://ftpmaster.internal/ubuntu plucky/universe mshr 2019.2.0~git20230811.ff54a68+dfsg1-4build1 (dsc) [3114 B]
160s Get:2 http://ftpmaster.internal/ubuntu plucky/universe mshr 2019.2.0~git20230811.ff54a68+dfsg1-4build1 (tar) [122 kB]
160s Get:3 http://ftpmaster.internal/ubuntu plucky/universe mshr 2019.2.0~git20230811.ff54a68+dfsg1-4build1 (diff) [14.3 kB]
160s gpgv: Signature made Sat Nov 16 08:53:30 2024 UTC
160s gpgv:                using RSA key 568BF22A66337CBFC9A6B9B72C83DBC8E9BD0E37
160s gpgv: Can't check signature: No public key
160s dpkg-source: warning: cannot verify inline signature for ./mshr_2019.2.0~git20230811.ff54a68+dfsg1-4build1.dsc: no acceptable signature found
161s autopkgtest [09:37:12]: testing package mshr version 2019.2.0~git20230811.ff54a68+dfsg1-4build1
162s autopkgtest [09:37:13]: build not needed
163s autopkgtest [09:37:14]: test test-mshr-python: preparing testbed
163s Reading package lists...
163s Building dependency tree...
163s Reading state information...
164s Starting pkgProblemResolver with broken count: 1
164s Starting 2 pkgProblemResolver with broken count: 1
164s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib >
164s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3)
164s   Considering libopenmpi3t64:arm64 87 as a solution to libopenmpi40:arm64 0
164s   Re-Instated libopenmpi3t64:arm64
164s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 4.1.6-13.3ubuntu2 @un puN > (< 5.0.6-3)
164s   Conflicts//Breaks against version 5.0.5-6 for libopenmpi3t64 but that is not InstVer, ignoring
164s   Considering libopenmpi3t64:arm64 0 as a solution to libopenmpi40:arm64 0
164s Done
164s Some packages could not be installed. This may mean that you have
164s requested an impossible situation or if you are using the unstable
164s distribution that some required packages have not yet been created
164s or been moved out of Incoming.
164s The following information may help to resolve the situation:
164s 
164s The following packages have unmet dependencies:
164s  libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3)
164s                 Breaks: libopenmpi3t64 (< 5.0.6-3) but 4.1.6-13.3ubuntu2 is to be installed
164s E: Unable to correct problems, you have held broken packages.
164s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed
165s Reading package lists...
165s Building dependency tree...
165s Reading state information...
166s Starting pkgProblemResolver with broken count: 1
166s Starting 2 pkgProblemResolver with broken count: 1
166s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib >
166s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3)
166s   Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring
166s   Considering libopenmpi3t64:arm64 28 as a solution to libopenmpi40:arm64 23
166s   Re-Instated libopenmpi3t64:arm64
166s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3)
166s   Considering libopenmpi3t64:arm64 23 as a solution to libopenmpi40:arm64 23
166s   Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring
166s Done
166s Some packages could not be installed. This may mean that you have
166s requested an impossible situation or if you are using the unstable
166s distribution that some required packages have not yet been created
166s or been moved out of Incoming.
166s The following information may help to resolve the situation:
166s 
166s The following packages have unmet dependencies:
167s  libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3)
167s                 Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed
167s E: Unable to correct problems, you have held broken packages.
167s test-mshr-python     FAIL badpkg
167s blame: mshr
167s badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.
167s autopkgtest [09:37:18]: test test-mshr64-python: preparing testbed
167s Reading package lists...
168s Building dependency tree...
168s Reading state information...
169s Starting pkgProblemResolver with broken count: 1
169s Starting 2 pkgProblemResolver with broken count: 1
169s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib >
169s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3)
169s   Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring
169s   Considering libopenmpi3t64:arm64 39 as a solution to libopenmpi40:arm64 33
169s   Re-Instated libopenmpi3t64:arm64
169s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3)
169s   Considering libopenmpi3t64:arm64 33 as a solution to libopenmpi40:arm64 33
169s   Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring
169s Done
169s Some packages could not be installed. This may mean that you have
169s requested an impossible situation or if you are using the unstable
169s distribution that some required packages have not yet been created
169s or been moved out of Incoming.
169s The following information may help to resolve the situation:
169s 
169s The following packages have unmet dependencies:
170s  libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3)
170s                 Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed
170s E: Unable to correct problems, you have held broken packages.
170s autopkgtest [09:37:21]: @@@@@@@@@@@@@@@@@@@@ summary
170s test-mshr-python     FAIL badpkg
170s blame: mshr
170s badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.
170s test-mshr64-python   FAIL badpkg
170s blame: mshr
170s badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.
170s test-mshr64-python   FAIL badpkg
170s blame: mshr
170s badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.
189s nova [W] Using flock in prodstack6-arm64
189s flock: timeout while waiting to get lock
189s Creating nova instance adt-plucky-arm64-mshr-20241203-093431-juju-7f2275-prod-proposed-migration-environment-15-af1df67c-dde0-46dd-94a0-dc3a3edc78b2 from image adt/ubuntu-plucky-arm64-server-20241203.img (UUID b9293590-1195-42ea-ba16-5ab4b1e94eab)...