0s autopkgtest [10:05:05]: starting date and time: 2024-12-03 10:05:05+0000
  0s autopkgtest [10:05:05]: git checkout: be626eda Fix armhf LXD image generation for plucky
  0s autopkgtest [10:05:05]: host juju-7f2275-prod-proposed-migration-environment-2; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.adba9b8c/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-ppc64el --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-2@bos03-ppc64el-5.secgroup --name adt-plucky-ppc64el-mshr-20241203-093431-juju-7f2275-prod-proposed-migration-environment-2-605d859b-dacc-4774-90be-792af12fdbf6 --image adt/ubuntu-plucky-ppc64el-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-2 --net-id=net_prod-proposed-migration-ppc64el -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/
106s autopkgtest [10:06:51]: testbed dpkg architecture: ppc64el
106s autopkgtest [10:06:51]: testbed apt version: 2.9.14ubuntu1
107s autopkgtest [10:06:52]: @@@@@@@@@@@@@@@@@@@@ test bed setup
107s autopkgtest [10:06:52]: testbed release detected to be: None
108s autopkgtest [10:06:53]: updating testbed package index (apt update)
108s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB]
108s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease
109s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease
109s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease
109s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [781 kB]
109s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B]
109s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [65.3 kB]
109s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [15.1 kB]
109s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main ppc64el Packages [127 kB]
109s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted ppc64el Packages [928 B]
109s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe ppc64el Packages [655 kB]
109s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse ppc64el Packages [11.0 kB]
110s Fetched 1739 kB in 1s (1213 kB/s)
111s Reading package lists...
112s Reading package lists...
112s Building dependency tree...
112s Reading state information...
113s Calculating upgrade...
113s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
113s Reading package lists...
113s Building dependency tree...
113s Reading state information...
114s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
114s autopkgtest [10:06:59]: upgrading testbed (apt dist-upgrade and autopurge)
114s Reading package lists...
114s Building dependency tree...
114s Reading state information...
115s Calculating upgrade...Starting pkgProblemResolver with broken count: 0
115s Starting 2 pkgProblemResolver with broken count: 0
115s Done
115s Entering ResolveByKeep
116s 
116s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
116s Reading package lists...
117s Building dependency tree...
117s Reading state information...
117s Starting pkgProblemResolver with broken count: 0
117s Starting 2 pkgProblemResolver with broken count: 0
117s Done
118s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
120s autopkgtest [10:07:05]: testbed running kernel: Linux 6.11.0-8-generic #8-Ubuntu SMP Mon Sep 16 13:49:23 UTC 2024
120s autopkgtest [10:07:05]: @@@@@@@@@@@@@@@@@@@@ apt-source mshr
127s Get:1 http://ftpmaster.internal/ubuntu plucky/universe mshr 2019.2.0~git20230811.ff54a68+dfsg1-4build1 (dsc) [3114 B]
127s Get:2 http://ftpmaster.internal/ubuntu plucky/universe mshr 2019.2.0~git20230811.ff54a68+dfsg1-4build1 (tar) [122 kB]
127s Get:3 http://ftpmaster.internal/ubuntu plucky/universe mshr 2019.2.0~git20230811.ff54a68+dfsg1-4build1 (diff) [14.3 kB]
127s gpgv: Signature made Sat Nov 16 08:53:30 2024 UTC
127s gpgv:                using RSA key 568BF22A66337CBFC9A6B9B72C83DBC8E9BD0E37
127s gpgv: Can't check signature: No public key
127s dpkg-source: warning: cannot verify inline signature for ./mshr_2019.2.0~git20230811.ff54a68+dfsg1-4build1.dsc: no acceptable signature found
127s autopkgtest [10:07:12]: testing package mshr version 2019.2.0~git20230811.ff54a68+dfsg1-4build1
128s autopkgtest [10:07:13]: build not needed
131s autopkgtest [10:07:16]: test test-mshr-python: preparing testbed
131s Reading package lists...
131s Building dependency tree...
131s Reading state information...
131s Starting pkgProblemResolver with broken count: 1
131s Starting 2 pkgProblemResolver with broken count: 1
131s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib >
131s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3)
131s   Considering libopenmpi3t64:ppc64el 87 as a solution to libopenmpi40:ppc64el 0
131s   Re-Instated libopenmpi3t64:ppc64el
131s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 4.1.6-13.3ubuntu2 @un puN > (< 5.0.6-3)
131s   Conflicts//Breaks against version 5.0.5-6 for libopenmpi3t64 but that is not InstVer, ignoring
131s   Considering libopenmpi3t64:ppc64el 0 as a solution to libopenmpi40:ppc64el 0
131s Done
131s Some packages could not be installed. This may mean that you have
131s requested an impossible situation or if you are using the unstable
131s distribution that some required packages have not yet been created
131s or been moved out of Incoming.
131s The following information may help to resolve the situation:
131s 
131s The following packages have unmet dependencies:
131s  libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3)
131s                 Breaks: libopenmpi3t64 (< 5.0.6-3) but 4.1.6-13.3ubuntu2 is to be installed
131s E: Unable to correct problems, you have held broken packages.
131s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed
132s Reading package lists...
132s Building dependency tree...
132s Reading state information...
132s Starting pkgProblemResolver with broken count: 1
132s Starting 2 pkgProblemResolver with broken count: 1
132s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib >
132s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3)
132s   Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring
132s   Considering libopenmpi3t64:ppc64el 27 as a solution to libopenmpi40:ppc64el 25
132s   Re-Instated libopenmpi3t64:ppc64el
132s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3)
132s   Considering libopenmpi3t64:ppc64el 25 as a solution to libopenmpi40:ppc64el 25
132s   Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring
132s Done
132s Some packages could not be installed. This may mean that you have
132s requested an impossible situation or if you are using the unstable
132s distribution that some required packages have not yet been created
132s or been moved out of Incoming.
132s The following information may help to resolve the situation:
132s 
132s The following packages have unmet dependencies:
133s  libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3)
133s                 Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed
133s E: Unable to correct problems, you have held broken packages.
133s autopkgtest [10:07:18]: test test-mshr64-python: preparing testbed
133s test-mshr-python     FAIL badpkg
133s blame: mshr
133s 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.
133s Reading package lists...
133s Building dependency tree...
133s Reading state information...
134s Starting pkgProblemResolver with broken count: 1
134s Starting 2 pkgProblemResolver with broken count: 1
134s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib >
134s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3)
134s   Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring
134s   Considering libopenmpi3t64:ppc64el 37 as a solution to libopenmpi40:ppc64el 37
134s   Re-Instated libopenmpi3t64:ppc64el
134s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3)
134s   Considering libopenmpi3t64:ppc64el 37 as a solution to libopenmpi40:ppc64el 37
134s   Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring
134s Done
134s Some packages could not be installed. This may mean that you have
134s requested an impossible situation or if you are using the unstable
134s distribution that some required packages have not yet been created
134s or been moved out of Incoming.
134s The following information may help to resolve the situation:
134s 
134s The following packages have unmet dependencies:
135s  libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3)
135s                 Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed
135s E: Unable to correct problems, you have held broken packages.
135s test-mshr64-python   FAIL badpkg
135s blame: mshr
135s 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.
135s autopkgtest [10:07:20]: @@@@@@@@@@@@@@@@@@@@ summary
135s test-mshr-python     FAIL badpkg
135s blame: mshr
135s 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.
135s test-mshr64-python   FAIL badpkg
135s blame: mshr
135s 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.
139s nova [W] Using flock in prodstack6-ppc64el
139s Creating nova instance adt-plucky-ppc64el-mshr-20241203-093431-juju-7f2275-prod-proposed-migration-environment-2-605d859b-dacc-4774-90be-792af12fdbf6 from image adt/ubuntu-plucky-ppc64el-server-20241203.img (UUID 71a10fe7-f168-4d19-8647-b89d09dd4cc0)...