0s autopkgtest [10:27:15]: starting date and time: 2024-12-03 10:27:15+0000 0s autopkgtest [10:27:15]: git checkout: be626eda Fix armhf LXD image generation for plucky 0s autopkgtest [10:27:15]: host juju-7f2275-prod-proposed-migration-environment-20; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work._vtxijad/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 --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-20@bos03-arm64-40.secgroup --name adt-plucky-arm64-sundials-20241203-102715-juju-7f2275-prod-proposed-migration-environment-20-1d7c7257-4b3f-4cbd-9cda-cec6539db8e8 --image adt/ubuntu-plucky-arm64-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-20 --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/ 111s autopkgtest [10:29:06]: testbed dpkg architecture: arm64 112s autopkgtest [10:29:07]: testbed apt version: 2.9.14ubuntu1 112s autopkgtest [10:29:07]: @@@@@@@@@@@@@@@@@@@@ test bed setup 112s autopkgtest [10:29:07]: testbed release detected to be: None 113s autopkgtest [10:29:08]: updating testbed package index (apt update) 114s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB] 114s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 114s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 114s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 114s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [14.2 kB] 114s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [771 kB] 114s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [65.3 kB] 114s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B] 114s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main arm64 Packages [145 kB] 114s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted arm64 Packages [58.2 kB] 114s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe arm64 Packages [661 kB] 114s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse arm64 Packages [20.8 kB] 114s Fetched 1820 kB in 1s (1959 kB/s) 116s Reading package lists... 116s Reading package lists... 117s Building dependency tree... 117s Reading state information... 118s Calculating upgrade... 118s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 118s Reading package lists... 119s Building dependency tree... 119s Reading state information... 120s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 120s autopkgtest [10:29:15]: upgrading testbed (apt dist-upgrade and autopurge) 120s Reading package lists... 121s Building dependency tree... 121s 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 125s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 125s Reading package lists... 126s Building dependency tree... 126s Reading state information... 127s Starting pkgProblemResolver with broken count: 0 127s Starting 2 pkgProblemResolver with broken count: 0 127s Done 129s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 131s autopkgtest [10:29:26]: testbed running kernel: Linux 6.11.0-8-generic #8-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 16 14:19:41 UTC 2024 131s autopkgtest [10:29:26]: @@@@@@@@@@@@@@@@@@@@ apt-source sundials 147s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed/universe sundials 7.1.1+dfsg1-5 (dsc) [3171 B] 147s Get:2 http://ftpmaster.internal/ubuntu plucky-proposed/universe sundials 7.1.1+dfsg1-5 (tar) [18.6 MB] 147s Get:3 http://ftpmaster.internal/ubuntu plucky-proposed/universe sundials 7.1.1+dfsg1-5 (diff) [14.1 kB] 147s gpgv: Signature made Sat Nov 2 12:07:53 2024 UTC 147s gpgv: using RSA key D54C3BFAFFB042DE382DA5D741CE7F0B9F1B8B32 147s gpgv: Can't check signature: No public key 147s dpkg-source: warning: cannot verify inline signature for ./sundials_7.1.1+dfsg1-5.dsc: no acceptable signature found 148s autopkgtest [10:29:43]: testing package sundials version 7.1.1+dfsg1-5 149s autopkgtest [10:29:44]: build not needed 153s autopkgtest [10:29:48]: test arkode: preparing testbed 153s Reading package lists... 154s Building dependency tree... 154s Reading state information... 154s Starting pkgProblemResolver with broken count: 1 154s Starting 2 pkgProblemResolver with broken count: 1 154s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 154s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < 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:arm64 45 as a solution to libopenmpi40:arm64 3 154s Re-Instated libopenmpi3t64:arm64 154s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 154s Considering libopenmpi3t64:arm64 3 as a solution to libopenmpi40:arm64 3 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. 155s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed 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:arm64 < none -> 5.0.6-3 @un puN Ib > 156s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < 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:arm64 30 as a solution to libopenmpi40:arm64 17 156s Re-Instated libopenmpi3t64:arm64 156s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 156s Considering libopenmpi3t64:arm64 17 as a solution to libopenmpi40:arm64 17 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:51]: test cvode: preparing testbed 156s arkode 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... 156s Building dependency tree... 156s Reading state information... 157s Starting pkgProblemResolver with broken count: 1 157s Starting 2 pkgProblemResolver with broken count: 1 157s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 157s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < 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:arm64 30 as a solution to libopenmpi40:arm64 17 157s Re-Instated libopenmpi3t64:arm64 157s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 157s Considering libopenmpi3t64:arm64 17 as a solution to libopenmpi40:arm64 17 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 autopkgtest [10:29:52]: test cvodes: preparing testbed 157s cvode 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. 158s 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:arm64 < none -> 5.0.6-3 @un puN Ib > 158s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < 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:arm64 30 as a solution to libopenmpi40:arm64 17 158s Re-Instated libopenmpi3t64:arm64 158s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 158s Considering libopenmpi3t64:arm64 17 as a solution to libopenmpi40:arm64 17 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: 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:54]: test ida: preparing testbed 159s cvodes 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. 159s Reading package lists... 159s Building dependency tree... 159s Reading state information... 159s Starting pkgProblemResolver with broken count: 1 160s Starting 2 pkgProblemResolver with broken count: 1 160s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 160s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < 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:arm64 30 as a solution to libopenmpi40:arm64 17 160s Re-Instated libopenmpi3t64:arm64 160s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 160s Considering libopenmpi3t64:arm64 17 as a solution to libopenmpi40:arm64 17 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:55]: test idas: preparing testbed 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 Reading package lists... 160s Building dependency tree... 160s Reading state information... 161s Starting pkgProblemResolver with broken count: 1 161s Starting 2 pkgProblemResolver with broken count: 1 161s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 161s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3) 161s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 161s Considering libopenmpi3t64:arm64 30 as a solution to libopenmpi40:arm64 17 161s Re-Instated libopenmpi3t64:arm64 161s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 161s Considering libopenmpi3t64:arm64 17 as a solution to libopenmpi40:arm64 17 161s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 161s Done 161s Some packages could not be installed. This may mean that you have 161s requested an impossible situation or if you are using the unstable 161s distribution that some required packages have not yet been created 161s or been moved out of Incoming. 161s The following information may help to resolve the situation: 161s 161s The following packages have unmet dependencies: 161s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 161s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 161s E: Unable to correct problems, you have held broken packages. 161s idas FAIL badpkg 161s blame: sundials 161s 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. 161s autopkgtest [10:29:56]: test kinsol: preparing testbed 162s Reading package lists... 162s Building dependency tree... 162s Reading state information... 162s Starting pkgProblemResolver with broken count: 1 162s Starting 2 pkgProblemResolver with broken count: 1 162s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 162s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3) 162s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 162s Considering libopenmpi3t64:arm64 30 as a solution to libopenmpi40:arm64 17 162s Re-Instated libopenmpi3t64:arm64 162s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 162s Considering libopenmpi3t64:arm64 17 as a solution to libopenmpi40:arm64 17 162s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 162s Done 162s Some packages could not be installed. This may mean that you have 162s requested an impossible situation or if you are using the unstable 162s distribution that some required packages have not yet been created 162s or been moved out of Incoming. 162s The following information may help to resolve the situation: 162s 162s The following packages have unmet dependencies: 163s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 163s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 163s E: Unable to correct problems, you have held broken packages. 163s kinsol FAIL badpkg 163s blame: sundials 163s 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. 163s autopkgtest [10:29:58]: test sunnonlinsol: preparing testbed 163s Reading package lists... 163s Building dependency tree... 163s Reading state information... 163s Starting pkgProblemResolver with broken count: 1 164s Starting 2 pkgProblemResolver with broken count: 1 164s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 164s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3) 164s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 164s Considering libopenmpi3t64:arm64 30 as a solution to libopenmpi40:arm64 17 164s Re-Instated libopenmpi3t64:arm64 164s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 164s Considering libopenmpi3t64:arm64 17 as a solution to libopenmpi40:arm64 17 164s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 164s Done 164s Some packages could not be installed. This may mean that you have 164s requested an impossible situation or if you are using the unstable 164s distribution that some required packages have not yet been created 164s or been moved out of Incoming. 164s The following information may help to resolve the situation: 164s 164s The following packages have unmet dependencies: 164s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 164s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 164s E: Unable to correct problems, you have held broken packages. 164s sunnonlinsol FAIL badpkg 164s blame: sundials 164s 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. 164s autopkgtest [10:29:59]: @@@@@@@@@@@@@@@@@@@@ summary 164s arkode FAIL badpkg 164s blame: sundials 164s 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. 164s cvode FAIL badpkg 164s blame: sundials 164s 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. 164s cvodes FAIL badpkg 164s blame: sundials 164s 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. 164s ida FAIL badpkg 164s blame: sundials 164s 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. 164s idas FAIL badpkg 164s blame: sundials 164s 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. 164s kinsol FAIL badpkg 164s blame: sundials 164s 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. 164s sunnonlinsol FAIL badpkg 164s blame: sundials 164s 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. 175s nova [W] Using flock in prodstack6-arm64 175s Creating nova instance adt-plucky-arm64-sundials-20241203-102715-juju-7f2275-prod-proposed-migration-environment-20-1d7c7257-4b3f-4cbd-9cda-cec6539db8e8 from image adt/ubuntu-plucky-arm64-server-20241203.img (UUID b9293590-1195-42ea-ba16-5ab4b1e94eab)...