0s autopkgtest [09:34:16]: starting date and time: 2024-12-03 09:34:16+0000 0s autopkgtest [09:34:16]: git checkout: be626eda Fix armhf LXD image generation for plucky 0s autopkgtest [09:34:16]: host juju-7f2275-prod-proposed-migration-environment-2; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.yne6iiip/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:openmpi,src:superlu-dist --apt-upgrade hypre --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 '--env=ADT_TEST_TRIGGERS=openmpi/5.0.6-3 superlu-dist/8.2.1+dfsg1-5build1' -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-2@bos03-arm64-23.secgroup --name adt-plucky-arm64-hypre-20241203-093416-juju-7f2275-prod-proposed-migration-environment-2-8dd629ac-6d72-4280-8abc-9fe976d6ad63 --image adt/ubuntu-plucky-arm64-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-2 --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/ 149s autopkgtest [09:36:45]: testbed dpkg architecture: arm64 149s autopkgtest [09:36:45]: testbed apt version: 2.9.14ubuntu1 149s autopkgtest [09:36:45]: @@@@@@@@@@@@@@@@@@@@ test bed setup 150s autopkgtest [09:36:46]: testbed release detected to be: None 150s autopkgtest [09:36:46]: updating testbed package index (apt update) 151s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB] 151s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 151s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 151s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 151s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [781 kB] 152s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [15.1 kB] 152s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [65.3 kB] 152s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B] 152s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main arm64 Packages [145 kB] 152s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted arm64 Packages [58.2 kB] 152s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe arm64 Packages [669 kB] 152s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse arm64 Packages [21.3 kB] 152s Fetched 1838 kB in 1s (1560 kB/s) 153s Reading package lists... 154s Reading package lists... 154s Building dependency tree... 154s Reading state information... 155s Calculating upgrade... 156s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 156s Reading package lists... 157s Building dependency tree... 157s Reading state information... 158s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 158s autopkgtest [09:36:54]: upgrading testbed (apt dist-upgrade and autopurge) 159s Reading package lists... 159s Building dependency tree... 159s Reading state information... 159s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 160s Starting 2 pkgProblemResolver with broken count: 0 160s Done 160s Entering ResolveByKeep 161s 161s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 161s Reading package lists... 162s Building dependency tree... 162s Reading state information... 162s Starting pkgProblemResolver with broken count: 0 163s Starting 2 pkgProblemResolver with broken count: 0 163s Done 163s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 166s autopkgtest [09:37:02]: testbed running kernel: Linux 6.11.0-8-generic #8-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 16 14:19:41 UTC 2024 166s autopkgtest [09:37:02]: @@@@@@@@@@@@@@@@@@@@ apt-source hypre 174s Get:1 http://ftpmaster.internal/ubuntu plucky/universe hypre 2.31.0-1exp2 (dsc) [3485 B] 174s Get:2 http://ftpmaster.internal/ubuntu plucky/universe hypre 2.31.0-1exp2 (tar) [7491 kB] 174s Get:3 http://ftpmaster.internal/ubuntu plucky/universe hypre 2.31.0-1exp2 (diff) [20.8 kB] 174s gpgv: Signature made Sun Aug 4 10:09:26 2024 UTC 174s gpgv: using RSA key 23C9A93E585819E9126D0A36573EF1E4BD5A01FA 174s gpgv: Can't check signature: No public key 174s dpkg-source: warning: cannot verify inline signature for ./hypre_2.31.0-1exp2.dsc: no acceptable signature found 175s autopkgtest [09:37:11]: testing package hypre version 2.31.0-1exp2 178s autopkgtest [09:37:14]: build not needed 182s autopkgtest [09:37:18]: test test-hypre: preparing testbed 182s Reading package lists... 183s Building dependency tree... 183s Reading state information... 183s Starting pkgProblemResolver with broken count: 1 183s Starting 2 pkgProblemResolver with broken count: 1 183s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 183s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3) 183s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 183s Considering libopenmpi3t64:arm64 1 as a solution to libopenmpi40:arm64 4 183s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 183s Considering libopenmpi3t64:arm64 1 as a solution to libopenmpi40:arm64 4 183s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 183s Done 183s Some packages could not be installed. This may mean that you have 183s requested an impossible situation or if you are using the unstable 183s distribution that some required packages have not yet been created 183s or been moved out of Incoming. 183s The following information may help to resolve the situation: 183s 183s The following packages have unmet dependencies: 184s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 184s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 184s E: Unable to correct problems, you have held broken packages. 184s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed 184s Reading package lists... 184s Building dependency tree... 184s Reading state information... 185s Starting pkgProblemResolver with broken count: 1 185s Starting 2 pkgProblemResolver with broken count: 1 185s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 185s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3) 185s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 185s Considering libopenmpi3t64:arm64 -1 as a solution to libopenmpi40:arm64 6 185s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 185s Considering libopenmpi3t64:arm64 -1 as a solution to libopenmpi40:arm64 6 185s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 185s Done 185s Some packages could not be installed. This may mean that you have 185s requested an impossible situation or if you are using the unstable 185s distribution that some required packages have not yet been created 185s or been moved out of Incoming. 185s The following information may help to resolve the situation: 185s 185s The following packages have unmet dependencies: 185s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 185s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 185s E: Unable to correct problems, you have held broken packages. 185s autopkgtest [09:37:21]: test test-hypre64: preparing testbed 185s test-hypre FAIL badpkg 185s blame: hypre 185s 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. 401s autopkgtest [09:40:57]: testbed dpkg architecture: arm64 401s autopkgtest [09:40:57]: testbed apt version: 2.9.14ubuntu1 401s autopkgtest [09:40:57]: @@@@@@@@@@@@@@@@@@@@ test bed setup 402s autopkgtest [09:40:58]: testbed release detected to be: plucky 403s autopkgtest [09:40:59]: updating testbed package index (apt update) 403s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB] 403s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 403s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 403s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 403s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [781 kB] 404s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [65.3 kB] 404s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [15.1 kB] 404s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B] 404s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main arm64 Packages [145 kB] 404s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted arm64 Packages [58.2 kB] 404s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe arm64 Packages [669 kB] 404s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse arm64 Packages [21.3 kB] 404s Fetched 1838 kB in 1s (1738 kB/s) 405s Reading package lists... 406s Reading package lists... 406s Building dependency tree... 406s Reading state information... 406s Calculating upgrade... 407s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 407s Reading package lists... 407s Building dependency tree... 407s Reading state information... 408s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 408s autopkgtest [09:41:04]: upgrading testbed (apt dist-upgrade and autopurge) 408s Reading package lists... 408s Building dependency tree... 408s Reading state information... 409s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 409s Starting 2 pkgProblemResolver with broken count: 0 409s Done 410s Entering ResolveByKeep 410s 411s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 411s Reading package lists... 411s Building dependency tree... 411s Reading state information... 412s Starting pkgProblemResolver with broken count: 0 412s Starting 2 pkgProblemResolver with broken count: 0 412s Done 412s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 416s Reading package lists... 416s Building dependency tree... 416s Reading state information... 416s Starting pkgProblemResolver with broken count: 1 416s Starting 2 pkgProblemResolver with broken count: 1 416s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 416s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3) 416s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 416s Considering libopenmpi3t64:arm64 2 as a solution to libopenmpi40:arm64 5 416s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 416s Considering libopenmpi3t64:arm64 2 as a solution to libopenmpi40:arm64 5 416s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 416s Done 417s Some packages could not be installed. This may mean that you have 417s requested an impossible situation or if you are using the unstable 417s distribution that some required packages have not yet been created 417s or been moved out of Incoming. 417s The following information may help to resolve the situation: 417s 417s The following packages have unmet dependencies: 417s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 417s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 417s E: Unable to correct problems, you have held broken packages. 417s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed 417s Reading package lists... 418s Building dependency tree... 418s Reading state information... 418s Starting pkgProblemResolver with broken count: 1 418s Starting 2 pkgProblemResolver with broken count: 1 418s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 418s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3) 418s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 418s Considering libopenmpi3t64:arm64 0 as a solution to libopenmpi40:arm64 7 418s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 418s Considering libopenmpi3t64:arm64 0 as a solution to libopenmpi40:arm64 7 418s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 418s Done 418s Some packages could not be installed. This may mean that you have 418s requested an impossible situation or if you are using the unstable 418s distribution that some required packages have not yet been created 418s or been moved out of Incoming. 418s The following information may help to resolve the situation: 418s 418s The following packages have unmet dependencies: 418s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 418s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 418s E: Unable to correct problems, you have held broken packages. 419s test-hypre64 FAIL badpkg 419s blame: hypre 419s 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. 419s autopkgtest [09:41:15]: test test-hypre64m: preparing testbed 419s Reading package lists... 419s Building dependency tree... 419s Reading state information... 419s Starting pkgProblemResolver with broken count: 1 419s Starting 2 pkgProblemResolver with broken count: 1 419s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 419s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3) 419s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 419s Considering libopenmpi3t64:arm64 0 as a solution to libopenmpi40:arm64 7 419s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 419s Considering libopenmpi3t64:arm64 0 as a solution to libopenmpi40:arm64 7 419s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 419s Done 419s Some packages could not be installed. This may mean that you have 419s requested an impossible situation or if you are using the unstable 419s distribution that some required packages have not yet been created 419s or been moved out of Incoming. 419s The following information may help to resolve the situation: 419s 419s The following packages have unmet dependencies: 420s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 420s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 420s E: Unable to correct problems, you have held broken packages. 420s test-hypre64m FAIL badpkg 420s blame: hypre 420s 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. 420s autopkgtest [09:41:16]: @@@@@@@@@@@@@@@@@@@@ summary 420s test-hypre FAIL badpkg 420s blame: hypre 420s 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. 420s test-hypre64 FAIL badpkg 420s blame: hypre 420s 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. 420s test-hypre64m FAIL badpkg 420s blame: hypre 420s 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. 433s nova [W] Using flock in prodstack6-arm64 433s flock: timeout while waiting to get lock 433s Creating nova instance adt-plucky-arm64-hypre-20241203-093416-juju-7f2275-prod-proposed-migration-environment-2-8dd629ac-6d72-4280-8abc-9fe976d6ad63 from image adt/ubuntu-plucky-arm64-server-20241203.img (UUID b9293590-1195-42ea-ba16-5ab4b1e94eab)... 433s nova [W] Using flock in prodstack6-arm64 433s Creating nova instance adt-plucky-arm64-hypre-20241203-093416-juju-7f2275-prod-proposed-migration-environment-2-8dd629ac-6d72-4280-8abc-9fe976d6ad63 from image adt/ubuntu-plucky-arm64-server-20241203.img (UUID b9293590-1195-42ea-ba16-5ab4b1e94eab)...