0s autopkgtest [10:27:08]: starting date and time: 2024-12-03 10:27:08+0000 0s autopkgtest [10:27:08]: git checkout: be626eda Fix armhf LXD image generation for plucky 0s autopkgtest [10:27:08]: host juju-7f2275-prod-proposed-migration-environment-15; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.2a7uldrq/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:openmpi,src:petsc,src:petsc4py,src:slepc,src:slepc4py --apt-upgrade slepc4py --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 '--env=ADT_TEST_TRIGGERS=openmpi/5.0.6-3 petsc/3.22.1+dfsg1-2ubuntu1 petsc4py/3.22.1-2ubuntu1 slepc/3.22.1+dfsg1-2 slepc4py/3.21.2-1ubuntu2' -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-15@bos03-arm64-2.secgroup --name adt-plucky-arm64-slepc4py-20241203-102708-juju-7f2275-prod-proposed-migration-environment-15-d63b7ce6-fe2b-4ee3-b85a-721219100936 --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/ 80s autopkgtest [10:28:28]: testbed dpkg architecture: arm64 80s autopkgtest [10:28:28]: testbed apt version: 2.9.14ubuntu1 80s autopkgtest [10:28:28]: @@@@@@@@@@@@@@@@@@@@ test bed setup 80s autopkgtest [10:28:28]: testbed release detected to be: None 81s autopkgtest [10:28:29]: updating testbed package index (apt update) 81s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB] 82s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 82s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 82s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 82s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [771 kB] 82s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [65.3 kB] 82s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B] 82s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [14.2 kB] 82s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main arm64 Packages [145 kB] 82s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted arm64 Packages [58.2 kB] 82s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe arm64 Packages [661 kB] 82s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse arm64 Packages [20.8 kB] 82s Fetched 1820 kB in 1s (1967 kB/s) 83s Reading package lists... 84s Reading package lists... 84s Building dependency tree... 84s Reading state information... 84s Calculating upgrade... 85s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 85s Reading package lists... 85s Building dependency tree... 85s Reading state information... 86s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 86s autopkgtest [10:28:34]: upgrading testbed (apt dist-upgrade and autopurge) 86s Reading package lists... 86s Building dependency tree... 86s Reading state information... 87s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 87s Starting 2 pkgProblemResolver with broken count: 0 87s Done 88s Entering ResolveByKeep 88s 88s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 89s Reading package lists... 89s Building dependency tree... 89s Reading state information... 89s Starting pkgProblemResolver with broken count: 0 89s Starting 2 pkgProblemResolver with broken count: 0 89s Done 90s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 92s autopkgtest [10:28:40]: testbed running kernel: Linux 6.11.0-8-generic #8-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 16 14:19:41 UTC 2024 93s autopkgtest [10:28:41]: @@@@@@@@@@@@@@@@@@@@ apt-source slepc4py 100s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed/universe slepc4py 3.21.2-1ubuntu2 (dsc) [3554 B] 100s Get:2 http://ftpmaster.internal/ubuntu plucky-proposed/universe slepc4py 3.21.2-1ubuntu2 (tar) [136 kB] 100s Get:3 http://ftpmaster.internal/ubuntu plucky-proposed/universe slepc4py 3.21.2-1ubuntu2 (diff) [9768 B] 100s gpgv: Signature made Fri Nov 15 13:41:39 2024 UTC 100s gpgv: using RSA key 568BF22A66337CBFC9A6B9B72C83DBC8E9BD0E37 100s gpgv: Can't check signature: No public key 100s dpkg-source: warning: cannot verify inline signature for ./slepc4py_3.21.2-1ubuntu2.dsc: no acceptable signature found 100s autopkgtest [10:28:48]: testing package slepc4py version 3.21.2-1ubuntu2 101s autopkgtest [10:28:49]: build not needed 101s autopkgtest [10:28:49]: test run-tests: preparing testbed 101s Reading package lists... 102s Building dependency tree... 102s Reading state information... 102s Starting pkgProblemResolver with broken count: 1 102s Starting 2 pkgProblemResolver with broken count: 1 102s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 102s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3) 102s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 102s Considering libopenmpi3t64:arm64 96 as a solution to libopenmpi40:arm64 6 102s Re-Instated libopenmpi3t64:arm64 102s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 102s Considering libopenmpi3t64:arm64 6 as a solution to libopenmpi40:arm64 6 102s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 102s Done 102s Some packages could not be installed. This may mean that you have 102s requested an impossible situation or if you are using the unstable 102s distribution that some required packages have not yet been created 102s or been moved out of Incoming. 102s The following information may help to resolve the situation: 102s 102s The following packages have unmet dependencies: 102s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 102s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 102s E: Unable to correct problems, you have held broken packages. 102s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed 103s Reading package lists... 103s Building dependency tree... 103s Reading state information... 104s Starting pkgProblemResolver with broken count: 1 104s Starting 2 pkgProblemResolver with broken count: 1 104s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 104s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3) 104s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 104s Considering libopenmpi3t64:arm64 60 as a solution to libopenmpi40:arm64 40 104s Re-Instated libopenmpi3t64:arm64 104s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 104s Considering libopenmpi3t64:arm64 40 as a solution to libopenmpi40:arm64 40 104s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 104s Done 104s Some packages could not be installed. This may mean that you have 104s requested an impossible situation or if you are using the unstable 104s distribution that some required packages have not yet been created 104s or been moved out of Incoming. 104s The following information may help to resolve the situation: 104s 104s The following packages have unmet dependencies: 104s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 104s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 104s E: Unable to correct problems, you have held broken packages. 104s autopkgtest [10:28:52]: test run-demos: preparing testbed 104s run-tests FAIL badpkg 104s blame: slepc4py 104s 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. 104s Reading package lists... 104s Building dependency tree... 104s Reading state information... 105s Starting pkgProblemResolver with broken count: 1 105s Starting 2 pkgProblemResolver with broken count: 1 105s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 105s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3) 105s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 105s Considering libopenmpi3t64:arm64 60 as a solution to libopenmpi40:arm64 40 105s Re-Instated libopenmpi3t64:arm64 105s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 105s Considering libopenmpi3t64:arm64 40 as a solution to libopenmpi40:arm64 40 105s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 105s Done 105s Some packages could not be installed. This may mean that you have 105s requested an impossible situation or if you are using the unstable 105s distribution that some required packages have not yet been created 105s or been moved out of Incoming. 105s The following information may help to resolve the situation: 105s 105s The following packages have unmet dependencies: 105s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 105s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 105s E: Unable to correct problems, you have held broken packages. 105s autopkgtest [10:28:53]: test run-tests-64: preparing testbed 105s run-demos FAIL badpkg 105s blame: slepc4py 105s 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. 105s Reading package lists... 106s Building dependency tree... 106s Reading state information... 106s Starting pkgProblemResolver with broken count: 1 106s Starting 2 pkgProblemResolver with broken count: 1 106s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 106s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3) 106s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 106s Considering libopenmpi3t64:arm64 60 as a solution to libopenmpi40:arm64 40 106s Re-Instated libopenmpi3t64:arm64 106s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 106s Considering libopenmpi3t64:arm64 40 as a solution to libopenmpi40:arm64 40 106s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 106s Done 106s Some packages could not be installed. This may mean that you have 106s requested an impossible situation or if you are using the unstable 106s distribution that some required packages have not yet been created 106s or been moved out of Incoming. 106s The following information may help to resolve the situation: 106s 106s The following packages have unmet dependencies: 107s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 107s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 107s E: Unable to correct problems, you have held broken packages. 107s run-tests-64 FAIL badpkg 107s blame: slepc4py 107s 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. 107s autopkgtest [10:28:55]: test run-demos-64: preparing testbed 107s Reading package lists... 107s Building dependency tree... 107s Reading state information... 107s Starting pkgProblemResolver with broken count: 1 107s Starting 2 pkgProblemResolver with broken count: 1 107s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 107s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3) 107s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 107s Considering libopenmpi3t64:arm64 60 as a solution to libopenmpi40:arm64 40 107s Re-Instated libopenmpi3t64:arm64 107s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 107s Considering libopenmpi3t64:arm64 40 as a solution to libopenmpi40:arm64 40 107s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 107s Done 107s Some packages could not be installed. This may mean that you have 107s requested an impossible situation or if you are using the unstable 107s distribution that some required packages have not yet been created 107s or been moved out of Incoming. 107s The following information may help to resolve the situation: 107s 107s The following packages have unmet dependencies: 108s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 108s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 108s E: Unable to correct problems, you have held broken packages. 108s autopkgtest [10:28:56]: @@@@@@@@@@@@@@@@@@@@ summary 108s run-tests FAIL badpkg 108s blame: slepc4py 108s 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. 108s run-demos FAIL badpkg 108s blame: slepc4py 108s 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. 108s run-tests-64 FAIL badpkg 108s blame: slepc4py 108s 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. 108s run-demos-64 FAIL badpkg 108s blame: slepc4py 108s 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. 108s run-demos-64 FAIL badpkg 108s blame: slepc4py 108s 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. 132s nova [W] Using flock in prodstack6-arm64 132s Creating nova instance adt-plucky-arm64-slepc4py-20241203-102708-juju-7f2275-prod-proposed-migration-environment-15-d63b7ce6-fe2b-4ee3-b85a-721219100936 from image adt/ubuntu-plucky-arm64-server-20241203.img (UUID b9293590-1195-42ea-ba16-5ab4b1e94eab)...