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-20; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.wmv_09mg/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-ppc64el --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-20@bos03-ppc64el-3.secgroup --name adt-plucky-ppc64el-slepc4py-20241203-102708-juju-7f2275-prod-proposed-migration-environment-20-c19796e6-a2a3-4431-a1be-decf7957f1af --image adt/ubuntu-plucky-ppc64el-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-20 --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/ 114s autopkgtest [10:29:02]: testbed dpkg architecture: ppc64el 114s autopkgtest [10:29:02]: testbed apt version: 2.9.14ubuntu1 114s autopkgtest [10:29:02]: @@@@@@@@@@@@@@@@@@@@ test bed setup 115s autopkgtest [10:29:03]: testbed release detected to be: None 115s autopkgtest [10:29:03]: updating testbed package index (apt update) 116s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB] 116s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 116s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 116s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 116s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [65.3 kB] 116s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [14.2 kB] 116s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B] 116s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [771 kB] 116s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main ppc64el Packages [127 kB] 116s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted ppc64el Packages [928 B] 116s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe ppc64el Packages [648 kB] 117s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse ppc64el Packages [10.4 kB] 117s Fetched 1721 kB in 1s (1481 kB/s) 118s Reading package lists... 119s Reading package lists... 119s Building dependency tree... 119s Reading state information... 120s Calculating upgrade... 120s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 120s Reading package lists... 121s Building dependency tree... 121s Reading state information... 121s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 121s autopkgtest [10:29:09]: upgrading testbed (apt dist-upgrade and autopurge) 121s Reading package lists... 122s Building dependency tree... 122s Reading state information... 122s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 122s Starting 2 pkgProblemResolver with broken count: 0 122s Done 123s Entering ResolveByKeep 124s 124s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 124s Reading package lists... 125s Building dependency tree... 125s Reading state information... 125s Starting pkgProblemResolver with broken count: 0 125s Starting 2 pkgProblemResolver with broken count: 0 125s Done 126s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 128s autopkgtest [10:29:16]: testbed running kernel: Linux 6.11.0-8-generic #8-Ubuntu SMP Mon Sep 16 13:49:23 UTC 2024 128s autopkgtest [10:29:16]: @@@@@@@@@@@@@@@@@@@@ apt-source slepc4py 138s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed/universe slepc4py 3.21.2-1ubuntu2 (dsc) [3554 B] 138s Get:2 http://ftpmaster.internal/ubuntu plucky-proposed/universe slepc4py 3.21.2-1ubuntu2 (tar) [136 kB] 138s Get:3 http://ftpmaster.internal/ubuntu plucky-proposed/universe slepc4py 3.21.2-1ubuntu2 (diff) [9768 B] 138s gpgv: Signature made Fri Nov 15 13:41:39 2024 UTC 138s gpgv: using RSA key 568BF22A66337CBFC9A6B9B72C83DBC8E9BD0E37 138s gpgv: Can't check signature: No public key 138s dpkg-source: warning: cannot verify inline signature for ./slepc4py_3.21.2-1ubuntu2.dsc: no acceptable signature found 138s autopkgtest [10:29:26]: testing package slepc4py version 3.21.2-1ubuntu2 139s autopkgtest [10:29:27]: build not needed 139s autopkgtest [10:29:27]: test run-tests: preparing testbed 139s Reading package lists... 140s Building dependency tree... 140s Reading state information... 140s Starting pkgProblemResolver with broken count: 1 140s Starting 2 pkgProblemResolver with broken count: 1 140s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib > 140s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3) 140s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 140s Considering libopenmpi3t64:ppc64el 96 as a solution to libopenmpi40:ppc64el 6 140s Re-Instated libopenmpi3t64:ppc64el 140s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 140s Considering libopenmpi3t64:ppc64el 6 as a solution to libopenmpi40:ppc64el 6 140s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 140s Done 140s Some packages could not be installed. This may mean that you have 140s requested an impossible situation or if you are using the unstable 140s distribution that some required packages have not yet been created 140s or been moved out of Incoming. 140s The following information may help to resolve the situation: 140s 140s The following packages have unmet dependencies: 140s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 140s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 140s E: Unable to correct problems, you have held broken packages. 140s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed 140s Reading package lists... 141s Building dependency tree... 141s Reading state information... 141s Starting pkgProblemResolver with broken count: 1 141s Starting 2 pkgProblemResolver with broken count: 1 141s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib > 141s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3) 141s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 141s Considering libopenmpi3t64:ppc64el 58 as a solution to libopenmpi40:ppc64el 44 141s Re-Instated libopenmpi3t64:ppc64el 141s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 141s Considering libopenmpi3t64:ppc64el 44 as a solution to libopenmpi40:ppc64el 44 141s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 141s Done 141s Some packages could not be installed. This may mean that you have 141s requested an impossible situation or if you are using the unstable 141s distribution that some required packages have not yet been created 141s or been moved out of Incoming. 141s The following information may help to resolve the situation: 141s 141s The following packages have unmet dependencies: 141s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 141s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 141s E: Unable to correct problems, you have held broken packages. 141s run-tests FAIL badpkg 141s blame: slepc4py 141s 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. 141s autopkgtest [10:29:29]: test run-demos: preparing testbed 142s Reading package lists... 142s Building dependency tree... 142s Reading state information... 142s Starting pkgProblemResolver with broken count: 1 142s Starting 2 pkgProblemResolver with broken count: 1 142s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib > 142s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3) 142s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 142s Considering libopenmpi3t64:ppc64el 58 as a solution to libopenmpi40:ppc64el 44 142s Re-Instated libopenmpi3t64:ppc64el 142s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 142s Considering libopenmpi3t64:ppc64el 44 as a solution to libopenmpi40:ppc64el 44 142s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 142s Done 142s Some packages could not be installed. This may mean that you have 142s requested an impossible situation or if you are using the unstable 142s distribution that some required packages have not yet been created 142s or been moved out of Incoming. 142s The following information may help to resolve the situation: 142s 142s The following packages have unmet dependencies: 142s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 142s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 142s E: Unable to correct problems, you have held broken packages. 142s autopkgtest [10:29:30]: test run-tests-64: preparing testbed 142s run-demos FAIL badpkg 142s blame: slepc4py 142s 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. 143s Reading package lists... 143s Building dependency tree... 143s Reading state information... 143s Starting pkgProblemResolver with broken count: 1 143s Starting 2 pkgProblemResolver with broken count: 1 143s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib > 143s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3) 143s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 143s Considering libopenmpi3t64:ppc64el 58 as a solution to libopenmpi40:ppc64el 44 143s Re-Instated libopenmpi3t64:ppc64el 143s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 143s Considering libopenmpi3t64:ppc64el 44 as a solution to libopenmpi40:ppc64el 44 143s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 143s Done 143s Some packages could not be installed. This may mean that you have 143s requested an impossible situation or if you are using the unstable 143s distribution that some required packages have not yet been created 143s or been moved out of Incoming. 143s The following information may help to resolve the situation: 143s 143s The following packages have unmet dependencies: 144s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 144s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 144s E: Unable to correct problems, you have held broken packages. 144s run-tests-64 FAIL badpkg 144s blame: slepc4py 144s 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. 144s autopkgtest [10:29:32]: test run-demos-64: preparing testbed 144s Reading package lists... 144s Building dependency tree... 144s Reading state information... 144s Starting pkgProblemResolver with broken count: 1 145s Starting 2 pkgProblemResolver with broken count: 1 145s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib > 145s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3) 145s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 145s Considering libopenmpi3t64:ppc64el 58 as a solution to libopenmpi40:ppc64el 44 145s Re-Instated libopenmpi3t64:ppc64el 145s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 145s Considering libopenmpi3t64:ppc64el 44 as a solution to libopenmpi40:ppc64el 44 145s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 145s Done 145s Some packages could not be installed. This may mean that you have 145s requested an impossible situation or if you are using the unstable 145s distribution that some required packages have not yet been created 145s or been moved out of Incoming. 145s The following information may help to resolve the situation: 145s 145s The following packages have unmet dependencies: 145s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 145s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 145s E: Unable to correct problems, you have held broken packages. 145s run-demos-64 FAIL badpkg 145s blame: slepc4py 145s 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. 145s autopkgtest [10:29:33]: @@@@@@@@@@@@@@@@@@@@ summary 145s run-tests FAIL badpkg 145s blame: slepc4py 145s 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. 145s run-demos FAIL badpkg 145s blame: slepc4py 145s 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. 145s run-tests-64 FAIL badpkg 145s blame: slepc4py 145s 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. 145s run-demos-64 FAIL badpkg 145s blame: slepc4py 145s 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. 156s nova [W] Using flock in prodstack6-ppc64el 156s Creating nova instance adt-plucky-ppc64el-slepc4py-20241203-102708-juju-7f2275-prod-proposed-migration-environment-20-c19796e6-a2a3-4431-a1be-decf7957f1af from image adt/ubuntu-plucky-ppc64el-server-20241203.img (UUID 71a10fe7-f168-4d19-8647-b89d09dd4cc0)...