0s autopkgtest [10:27:13]: starting date and time: 2024-12-03 10:27:13+0000 0s autopkgtest [10:27:13]: git checkout: be626eda Fix armhf LXD image generation for plucky 0s autopkgtest [10:27:13]: host juju-7f2275-prod-proposed-migration-environment-20; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.ufl_tbmb/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:openmpi,src:petsc,src:sundials --apt-upgrade sundials --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 '--env=ADT_TEST_TRIGGERS=openmpi/5.0.6-3 petsc/3.22.1+dfsg1-2ubuntu1 sundials/7.1.1+dfsg1-5' -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest-ppc64el --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-20@bos03-ppc64el-10.secgroup --name adt-plucky-ppc64el-sundials-20241203-102713-juju-7f2275-prod-proposed-migration-environment-20-32e3c703-a2dd-447d-9a35-dc604f6f8d50 --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/ 111s autopkgtest [10:29:04]: testbed dpkg architecture: ppc64el 111s autopkgtest [10:29:04]: testbed apt version: 2.9.14ubuntu1 111s autopkgtest [10:29:04]: @@@@@@@@@@@@@@@@@@@@ test bed setup 112s autopkgtest [10:29:05]: testbed release detected to be: None 113s autopkgtest [10:29:06]: updating testbed package index (apt update) 113s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB] 113s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 113s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 113s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 113s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B] 113s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [771 kB] 114s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [14.2 kB] 114s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [65.3 kB] 114s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main ppc64el Packages [127 kB] 114s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted ppc64el Packages [928 B] 114s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe ppc64el Packages [648 kB] 114s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse ppc64el Packages [10.4 kB] 114s Fetched 1721 kB in 1s (1500 kB/s) 115s Reading package lists... 116s Reading package lists... 116s Building dependency tree... 116s Reading state information... 117s Calculating upgrade... 117s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 117s Reading package lists... 117s Building dependency tree... 117s Reading state information... 118s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 118s autopkgtest [10:29:11]: upgrading testbed (apt dist-upgrade and autopurge) 118s Reading package lists... 118s Building dependency tree... 118s Reading state information... 119s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 119s Starting 2 pkgProblemResolver with broken count: 0 119s Done 120s Entering ResolveByKeep 120s 121s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 121s Reading package lists... 121s Building dependency tree... 121s Reading state information... 122s Starting pkgProblemResolver with broken count: 0 122s Starting 2 pkgProblemResolver with broken count: 0 122s Done 123s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 125s autopkgtest [10:29:18]: testbed running kernel: Linux 6.11.0-8-generic #8-Ubuntu SMP Mon Sep 16 13:49:23 UTC 2024 126s autopkgtest [10:29:19]: @@@@@@@@@@@@@@@@@@@@ apt-source sundials 144s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed/universe sundials 7.1.1+dfsg1-5 (dsc) [3171 B] 144s Get:2 http://ftpmaster.internal/ubuntu plucky-proposed/universe sundials 7.1.1+dfsg1-5 (tar) [18.6 MB] 144s Get:3 http://ftpmaster.internal/ubuntu plucky-proposed/universe sundials 7.1.1+dfsg1-5 (diff) [14.1 kB] 145s gpgv: Signature made Sat Nov 2 12:07:53 2024 UTC 145s gpgv: using RSA key D54C3BFAFFB042DE382DA5D741CE7F0B9F1B8B32 145s gpgv: Can't check signature: No public key 145s dpkg-source: warning: cannot verify inline signature for ./sundials_7.1.1+dfsg1-5.dsc: no acceptable signature found 146s autopkgtest [10:29:39]: testing package sundials version 7.1.1+dfsg1-5 147s autopkgtest [10:29:40]: build not needed 151s autopkgtest [10:29:44]: test arkode: preparing testbed 151s Reading package lists... 152s Building dependency tree... 152s Reading state information... 152s Starting pkgProblemResolver with broken count: 1 152s Starting 2 pkgProblemResolver with broken count: 1 152s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib > 152s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3) 152s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 152s Considering libopenmpi3t64:ppc64el 45 as a solution to libopenmpi40:ppc64el 3 152s Re-Instated libopenmpi3t64:ppc64el 152s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 152s Considering libopenmpi3t64:ppc64el 3 as a solution to libopenmpi40:ppc64el 3 152s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 152s Done 152s Some packages could not be installed. This may mean that you have 152s requested an impossible situation or if you are using the unstable 152s distribution that some required packages have not yet been created 152s or been moved out of Incoming. 152s The following information may help to resolve the situation: 152s 152s The following packages have unmet dependencies: 152s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 152s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 152s E: Unable to correct problems, you have held broken packages. 152s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed 153s Reading package lists... 153s Building dependency tree... 153s Reading state information... 154s Starting pkgProblemResolver with broken count: 1 154s Starting 2 pkgProblemResolver with broken count: 1 154s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib > 154s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3) 154s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 154s Considering libopenmpi3t64:ppc64el 29 as a solution to libopenmpi40:ppc64el 19 154s Re-Instated libopenmpi3t64:ppc64el 154s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 154s Considering libopenmpi3t64:ppc64el 19 as a solution to libopenmpi40:ppc64el 19 154s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 154s Done 154s Some packages could not be installed. This may mean that you have 154s requested an impossible situation or if you are using the unstable 154s distribution that some required packages have not yet been created 154s or been moved out of Incoming. 154s The following information may help to resolve the situation: 154s 154s The following packages have unmet dependencies: 154s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 154s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 154s E: Unable to correct problems, you have held broken packages. 154s autopkgtest [10:29:47]: test cvode: preparing testbed 154s arkode FAIL badpkg 154s blame: sundials 154s 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. 154s Reading package lists... 154s Building dependency tree... 154s Reading state information... 155s Starting pkgProblemResolver with broken count: 1 155s Starting 2 pkgProblemResolver with broken count: 1 155s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib > 155s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3) 155s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 155s Considering libopenmpi3t64:ppc64el 29 as a solution to libopenmpi40:ppc64el 19 155s Re-Instated libopenmpi3t64:ppc64el 155s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 155s Considering libopenmpi3t64:ppc64el 19 as a solution to libopenmpi40:ppc64el 19 155s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 155s Done 155s Some packages could not be installed. This may mean that you have 155s requested an impossible situation or if you are using the unstable 155s distribution that some required packages have not yet been created 155s or been moved out of Incoming. 155s The following information may help to resolve the situation: 155s 155s The following packages have unmet dependencies: 155s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 155s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 155s E: Unable to correct problems, you have held broken packages. 155s cvode FAIL badpkg 155s blame: sundials 155s 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. 155s autopkgtest [10:29:48]: test cvodes: preparing testbed 155s Reading package lists... 155s Building dependency tree... 155s Reading state information... 156s Starting pkgProblemResolver with broken count: 1 156s Starting 2 pkgProblemResolver with broken count: 1 156s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib > 156s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3) 156s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 156s Considering libopenmpi3t64:ppc64el 29 as a solution to libopenmpi40:ppc64el 19 156s Re-Instated libopenmpi3t64:ppc64el 156s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 156s Considering libopenmpi3t64:ppc64el 19 as a solution to libopenmpi40:ppc64el 19 156s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 156s Done 156s Some packages could not be installed. This may mean that you have 156s requested an impossible situation or if you are using the unstable 156s distribution that some required packages have not yet been created 156s or been moved out of Incoming. 156s The following information may help to resolve the situation: 156s 156s The following packages have unmet dependencies: 156s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 156s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 156s E: Unable to correct problems, you have held broken packages. 156s autopkgtest [10:29:49]: test ida: preparing testbed 156s cvodes FAIL badpkg 156s blame: sundials 156s 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 Reading package lists... 157s Building dependency tree... 157s Reading state information... 157s Starting pkgProblemResolver with broken count: 1 157s Starting 2 pkgProblemResolver with broken count: 1 157s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib > 157s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3) 157s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 157s Considering libopenmpi3t64:ppc64el 29 as a solution to libopenmpi40:ppc64el 19 157s Re-Instated libopenmpi3t64:ppc64el 157s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 157s Considering libopenmpi3t64:ppc64el 19 as a solution to libopenmpi40:ppc64el 19 157s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 157s Done 157s Some packages could not be installed. This may mean that you have 157s requested an impossible situation or if you are using the unstable 157s distribution that some required packages have not yet been created 157s or been moved out of Incoming. 157s The following information may help to resolve the situation: 157s 157s The following packages have unmet dependencies: 157s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 157s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 157s E: Unable to correct problems, you have held broken packages. 157s ida FAIL badpkg 157s blame: sundials 157s 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. 157s autopkgtest [10:29:50]: test idas: preparing testbed 157s Reading package lists... 158s Building dependency tree... 158s Reading state information... 158s Starting pkgProblemResolver with broken count: 1 158s Starting 2 pkgProblemResolver with broken count: 1 158s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib > 158s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3) 158s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 158s Considering libopenmpi3t64:ppc64el 29 as a solution to libopenmpi40:ppc64el 19 158s Re-Instated libopenmpi3t64:ppc64el 158s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 158s Considering libopenmpi3t64:ppc64el 19 as a solution to libopenmpi40:ppc64el 19 158s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 158s Done 158s Some packages could not be installed. This may mean that you have 158s requested an impossible situation or if you are using the unstable 158s distribution that some required packages have not yet been created 158s or been moved out of Incoming. 158s The following information may help to resolve the situation: 158s 158s The following packages have unmet dependencies: 158s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 158s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 158s E: Unable to correct problems, you have held broken packages. 158s autopkgtest [10:29:51]: test kinsol: preparing testbed 158s idas FAIL badpkg 158s blame: sundials 158s 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. 158s Reading package lists... 159s Building dependency tree... 159s Reading state information... 159s Starting pkgProblemResolver with broken count: 1 159s Starting 2 pkgProblemResolver with broken count: 1 159s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib > 159s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3) 159s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 159s Considering libopenmpi3t64:ppc64el 29 as a solution to libopenmpi40:ppc64el 19 159s Re-Instated libopenmpi3t64:ppc64el 159s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 159s Considering libopenmpi3t64:ppc64el 19 as a solution to libopenmpi40:ppc64el 19 159s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 159s Done 159s Some packages could not be installed. This may mean that you have 159s requested an impossible situation or if you are using the unstable 159s distribution that some required packages have not yet been created 159s or been moved out of Incoming. 159s The following information may help to resolve the situation: 159s 159s The following packages have unmet dependencies: 159s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 159s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 159s E: Unable to correct problems, you have held broken packages. 159s autopkgtest [10:29:52]: test sunnonlinsol: preparing testbed 159s kinsol FAIL badpkg 159s blame: sundials 159s 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. 160s Reading package lists... 160s Building dependency tree... 160s Reading state information... 160s Starting pkgProblemResolver with broken count: 1 160s Starting 2 pkgProblemResolver with broken count: 1 160s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib > 160s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3) 160s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 160s Considering libopenmpi3t64:ppc64el 29 as a solution to libopenmpi40:ppc64el 19 160s Re-Instated libopenmpi3t64:ppc64el 160s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 160s Considering libopenmpi3t64:ppc64el 19 as a solution to libopenmpi40:ppc64el 19 160s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 160s Done 160s Some packages could not be installed. This may mean that you have 160s requested an impossible situation or if you are using the unstable 160s distribution that some required packages have not yet been created 160s or been moved out of Incoming. 160s The following information may help to resolve the situation: 160s 160s The following packages have unmet dependencies: 160s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 160s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 160s E: Unable to correct problems, you have held broken packages. 160s autopkgtest [10:29:53]: @@@@@@@@@@@@@@@@@@@@ summary 160s arkode FAIL badpkg 160s blame: sundials 160s 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. 160s cvode FAIL badpkg 160s blame: sundials 160s 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. 160s cvodes FAIL badpkg 160s blame: sundials 160s 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. 160s ida FAIL badpkg 160s blame: sundials 160s 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. 160s idas FAIL badpkg 160s blame: sundials 160s 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. 160s kinsol FAIL badpkg 160s blame: sundials 160s 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. 160s sunnonlinsol FAIL badpkg 160s blame: sundials 160s 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. 160s sunnonlinsol FAIL badpkg 160s blame: sundials 160s 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. 165s nova [W] Using flock in prodstack6-ppc64el 165s Creating nova instance adt-plucky-ppc64el-sundials-20241203-102713-juju-7f2275-prod-proposed-migration-environment-20-32e3c703-a2dd-447d-9a35-dc604f6f8d50 from image adt/ubuntu-plucky-ppc64el-server-20241203.img (UUID 71a10fe7-f168-4d19-8647-b89d09dd4cc0)...