0s autopkgtest [10:27:12]: starting date and time: 2024-12-03 10:27:12+0000 0s autopkgtest [10:27:12]: git checkout: be626eda Fix armhf LXD image generation for plucky 0s autopkgtest [10:27:12]: host juju-7f2275-prod-proposed-migration-environment-20; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.mhrn1pfm/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-s390x --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-20@bos03-s390x-18.secgroup --name adt-plucky-s390x-sundials-20241203-102712-juju-7f2275-prod-proposed-migration-environment-20-4d01689d-45dc-4606-8c75-36a80aaa661d --image adt/ubuntu-plucky-s390x-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-20 --net-id=net_prod-proposed-migration-s390x -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/ 62s autopkgtest [10:28:14]: testbed dpkg architecture: s390x 62s autopkgtest [10:28:14]: testbed apt version: 2.9.14ubuntu1 63s autopkgtest [10:28:15]: @@@@@@@@@@@@@@@@@@@@ test bed setup 63s autopkgtest [10:28:15]: testbed release detected to be: None 64s autopkgtest [10:28:16]: updating testbed package index (apt update) 64s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB] 64s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 64s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 64s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 64s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [14.2 kB] 64s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B] 64s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [65.3 kB] 64s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [771 kB] 65s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main s390x Packages [125 kB] 65s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted s390x Packages [928 B] 65s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe s390x Packages [619 kB] 65s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse s390x Packages [7444 B] 65s Fetched 1687 kB in 1s (1916 kB/s) 65s Reading package lists... 66s Reading package lists... 66s Building dependency tree... 66s Reading state information... 66s Calculating upgrade... 66s The following packages will be upgraded: 66s gcc-14-base libatomic1 libgcc-s1 libstdc++6 66s 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 66s Need to get 994 kB of archives. 66s After this operation, 1024 B of additional disk space will be used. 66s Get:1 http://ftpmaster.internal/ubuntu plucky/main s390x libatomic1 s390x 14.2.0-9ubuntu1 [9424 B] 66s Get:2 http://ftpmaster.internal/ubuntu plucky/main s390x gcc-14-base s390x 14.2.0-9ubuntu1 [51.9 kB] 66s Get:3 http://ftpmaster.internal/ubuntu plucky/main s390x libstdc++6 s390x 14.2.0-9ubuntu1 [897 kB] 67s Get:4 http://ftpmaster.internal/ubuntu plucky/main s390x libgcc-s1 s390x 14.2.0-9ubuntu1 [35.9 kB] 67s Fetched 994 kB in 1s (1849 kB/s) 67s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 55869 files and directories currently installed.) 67s Preparing to unpack .../libatomic1_14.2.0-9ubuntu1_s390x.deb ... 67s Unpacking libatomic1:s390x (14.2.0-9ubuntu1) over (14.2.0-8ubuntu1) ... 67s Preparing to unpack .../gcc-14-base_14.2.0-9ubuntu1_s390x.deb ... 67s Unpacking gcc-14-base:s390x (14.2.0-9ubuntu1) over (14.2.0-8ubuntu1) ... 67s Setting up gcc-14-base:s390x (14.2.0-9ubuntu1) ... 67s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 55869 files and directories currently installed.) 67s Preparing to unpack .../libstdc++6_14.2.0-9ubuntu1_s390x.deb ... 67s Unpacking libstdc++6:s390x (14.2.0-9ubuntu1) over (14.2.0-8ubuntu1) ... 67s Setting up libstdc++6:s390x (14.2.0-9ubuntu1) ... 67s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 55869 files and directories currently installed.) 67s Preparing to unpack .../libgcc-s1_14.2.0-9ubuntu1_s390x.deb ... 67s Unpacking libgcc-s1:s390x (14.2.0-9ubuntu1) over (14.2.0-8ubuntu1) ... 67s Setting up libgcc-s1:s390x (14.2.0-9ubuntu1) ... 67s Setting up libatomic1:s390x (14.2.0-9ubuntu1) ... 67s Processing triggers for libc-bin (2.40-1ubuntu3) ... 67s Reading package lists... 68s Building dependency tree... 68s Reading state information... 68s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 68s autopkgtest [10:28:20]: upgrading testbed (apt dist-upgrade and autopurge) 68s Reading package lists... 68s Building dependency tree... 68s Reading state information... 68s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 68s Starting 2 pkgProblemResolver with broken count: 0 68s Done 68s Entering ResolveByKeep 69s 69s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 69s Reading package lists... 69s Building dependency tree... 69s Reading state information... 69s Starting pkgProblemResolver with broken count: 0 69s Starting 2 pkgProblemResolver with broken count: 0 69s Done 69s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 72s autopkgtest [10:28:24]: testbed running kernel: Linux 6.11.0-8-generic #8-Ubuntu SMP Mon Sep 16 12:49:35 UTC 2024 72s autopkgtest [10:28:24]: @@@@@@@@@@@@@@@@@@@@ apt-source sundials 84s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed/universe sundials 7.1.1+dfsg1-5 (dsc) [3171 B] 84s Get:2 http://ftpmaster.internal/ubuntu plucky-proposed/universe sundials 7.1.1+dfsg1-5 (tar) [18.6 MB] 84s Get:3 http://ftpmaster.internal/ubuntu plucky-proposed/universe sundials 7.1.1+dfsg1-5 (diff) [14.1 kB] 84s gpgv: Signature made Sat Nov 2 12:07:53 2024 UTC 84s gpgv: using RSA key D54C3BFAFFB042DE382DA5D741CE7F0B9F1B8B32 84s gpgv: Can't check signature: No public key 84s dpkg-source: warning: cannot verify inline signature for ./sundials_7.1.1+dfsg1-5.dsc: no acceptable signature found 85s autopkgtest [10:28:37]: testing package sundials version 7.1.1+dfsg1-5 86s autopkgtest [10:28:38]: build not needed 90s autopkgtest [10:28:42]: test arkode: preparing testbed 91s Reading package lists... 91s Building dependency tree... 91s Reading state information... 91s Starting pkgProblemResolver with broken count: 1 91s Starting 2 pkgProblemResolver with broken count: 1 91s Investigating (0) libopenmpi40:s390x < none -> 5.0.6-3 @un puN Ib > 91s Broken libopenmpi40:s390x Breaks on libopenmpi3:s390x < none @un H > (< 5.0.6-3) 91s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 91s Considering libopenmpi3t64:s390x 45 as a solution to libopenmpi40:s390x 3 91s Re-Instated libopenmpi3t64:s390x 91s Broken libopenmpi40:s390x Breaks on libopenmpi3t64:s390x < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 91s Considering libopenmpi3t64:s390x 3 as a solution to libopenmpi40:s390x 3 91s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 91s Done 91s Some packages could not be installed. This may mean that you have 91s requested an impossible situation or if you are using the unstable 91s distribution that some required packages have not yet been created 91s or been moved out of Incoming. 91s The following information may help to resolve the situation: 91s 91s The following packages have unmet dependencies: 91s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 91s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 91s E: Unable to correct problems, you have held broken packages. 91s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed 91s Reading package lists... 91s Building dependency tree... 91s Reading state information... 92s Starting pkgProblemResolver with broken count: 1 92s Starting 2 pkgProblemResolver with broken count: 1 92s Investigating (0) libopenmpi40:s390x < none -> 5.0.6-3 @un puN Ib >autopkgtest [10:28:44]: test cvode: preparing testbed 92s 92s Broken libopenmpi40:s390x Breaks on libopenmpi3:s390x < none @un H > (< 5.0.6-3) 92s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 92s Considering libopenmpi3t64:s390x 30 as a solution to libopenmpi40:s390x 17 92s Re-Instated libopenmpi3t64:s390x 92s Broken libopenmpi40:s390x Breaks on libopenmpi3t64:s390x < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 92s Considering libopenmpi3t64:s390x 17 as a solution to libopenmpi40:s390x 17 92s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 92s Done 92s Some packages could not be installed. This may mean that you have 92s requested an impossible situation or if you are using the unstable 92s distribution that some required packages have not yet been created 92s or been moved out of Incoming. 92s The following information may help to resolve the situation: 92s 92s The following packages have unmet dependencies: 92s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 92s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 92s E: Unable to correct problems, you have held broken packages. 92s arkode FAIL badpkg 92s blame: sundials 92s 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. 92s Reading package lists... 92s Building dependency tree... 92s Reading state information... 92s Starting pkgProblemResolver with broken count: 1 92s Starting 2 pkgProblemResolver with broken count: 1 92s Investigating (0) libopenmpi40:s390x < none -> 5.0.6-3 @un puN Ib > 92s Broken libopenmpi40:s390x Breaks on libopenmpi3:s390x < none @un H > (< 5.0.6-3) 92s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 92s Considering libopenmpi3t64:s390x 30 as a solution to libopenmpi40:s390x 17 92s Re-Instated libopenmpi3t64:s390x 92s Broken libopenmpi40:s390x Breaks on libopenmpi3t64:s390x < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 92s Considering libopenmpi3t64:s390x 17 as a solution to libopenmpi40:s390x 17 92s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 92s Done 92s Some packages could not be installed. This may mean that you have 92s requested an impossible situation or if you are using the unstable 92s distribution that some required packages have not yet been created 92s or been moved out of Incoming. 92s The following information may help to resolve the situation: 92s 92s The following packages have unmet dependencies: 92s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 92s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 92s E: Unable to correct problems, you have held broken packages. 92s cvode FAIL badpkg 92s blame: sundials 92s 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. 92s autopkgtest [10:28:44]: test cvodes: preparing testbed 92s Reading package lists... 93s Building dependency tree... 93s Reading state information... 93s Starting pkgProblemResolver with broken count: 1 93s Starting 2 pkgProblemResolver with broken count: 1 93s Investigating (0) libopenmpi40:s390x < none -> 5.0.6-3 @un puN Ib > 93s Broken libopenmpi40:s390x Breaks on libopenmpi3:s390x < none @un H > (< 5.0.6-3) 93s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 93s Considering libopenmpi3t64:s390x 30 as a solution to libopenmpi40:s390x 17 93s Re-Instated libopenmpi3t64:s390x 93s Broken libopenmpi40:s390x Breaks on libopenmpi3t64:s390x < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 93s Considering libopenmpi3t64:s390x 17 as a solution to libopenmpi40:s390x 17 93s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 93s Done 93s Some packages could not be installed. This may mean that you have 93s requested an impossible situation or if you are using the unstable 93s distribution that some required packages have not yet been created 93s or been moved out of Incoming. 93s The following information may help to resolve the situation: 93s 93s The following packages have unmet dependencies: 93s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 93s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 93s E: Unable to correct problems, you have held broken packages. 93s cvodes FAIL badpkg 93s blame: sundials 93s 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. 93s autopkgtest [10:28:45]: test ida: preparing testbed 93s Reading package lists... 93s Building dependency tree... 93s Reading state information... 93s Starting pkgProblemResolver with broken count: 1 93s Starting 2 pkgProblemResolver with broken count: 1 93s Investigating (0) libopenmpi40:s390x < none -> 5.0.6-3 @un puN Ib > 93s Broken libopenmpi40:s390x Breaks on libopenmpi3:s390x < none @un H > (< 5.0.6-3) 93s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 93s Considering libopenmpi3t64:s390x 30 as a solution to libopenmpi40:s390x 17 93s Re-Instated libopenmpi3t64:s390x 93s Broken libopenmpi40:s390x Breaks on libopenmpi3t64:s390x < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 93s Considering libopenmpi3t64:s390x 17 as a solution to libopenmpi40:s390x 17 93s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 93s Done 93s Some packages could not be installed. This may mean that you have 93s requested an impossible situation or if you are using the unstable 93s distribution that some required packages have not yet been created 93s or been moved out of Incoming. 93s The following information may help to resolve the situation: 93s 93s The following packages have unmet dependencies: 93s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 93s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 93s E: Unable to correct problems, you have held broken packages. 93s ida FAIL badpkg 93s blame: sundials 93s 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. 93s autopkgtest [10:28:45]: test idas: preparing testbed 94s Reading package lists... 94s Building dependency tree... 94s Reading state information... 94s Starting pkgProblemResolver with broken count: 1 94s Starting 2 pkgProblemResolver with broken count: 1 94s Investigating (0) libopenmpi40:s390x < none -> 5.0.6-3 @un puN Ib > 94s Broken libopenmpi40:s390x Breaks on libopenmpi3:s390x < none @un H > (< 5.0.6-3) 94s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 94s Considering libopenmpi3t64:s390x 30 as a solution to libopenmpi40:s390x 17 94s Re-Instated libopenmpi3t64:s390x 94s Broken libopenmpi40:s390x Breaks on libopenmpi3t64:s390x < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 94s Considering libopenmpi3t64:s390x 17 as a solution to libopenmpi40:s390x 17 94s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 94s Done 94s Some packages could not be installed. This may mean that you have 94s requested an impossible situation or if you are using the unstable 94s distribution that some required packages have not yet been created 94s or been moved out of Incoming. 94s The following information may help to resolve the situation: 94s 94s The following packages have unmet dependencies: 94s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 94s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 94s E: Unable to correct problems, you have held broken packages. 94s idas FAIL badpkg 94s blame: sundials 94s 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. 94s autopkgtest [10:28:46]: test kinsol: preparing testbed 94s Reading package lists... 94s Building dependency tree... 94s Reading state information... 95s Starting pkgProblemResolver with broken count: 1 95s Starting 2 pkgProblemResolver with broken count: 1 95s Investigating (0) libopenmpi40:s390x < none -> 5.0.6-3 @un puN Ib > 95s Broken libopenmpi40:s390x Breaks on libopenmpi3:s390x < none @un H > (< 5.0.6-3) 95s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 95s Considering libopenmpi3t64:s390x 30 as a solution to libopenmpi40:s390x 17 95s Re-Instated libopenmpi3t64:s390x 95s Broken libopenmpi40:s390x Breaks on libopenmpi3t64:s390x < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 95s Considering libopenmpi3t64:s390x 17 as a solution to libopenmpi40:s390x 17 95s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 95s Done 95s Some packages could not be installed. This may mean that you have 95s requested an impossible situation or if you are using the unstable 95s distribution that some required packages have not yet been created 95s or been moved out of Incoming. 95s The following information may help to resolve the situation: 95s 95s The following packages have unmet dependencies: 95s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 95s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 95s E: Unable to correct problems, you have held broken packages. 95s kinsol FAIL badpkg 95s blame: sundials 95s 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. 95s autopkgtest [10:28:47]: test sunnonlinsol: preparing testbed 95s Reading package lists... 95s Building dependency tree... 95s Reading state information... 95s Starting pkgProblemResolver with broken count: 1 95s Starting 2 pkgProblemResolver with broken count: 1 95s Investigating (0) libopenmpi40:s390x < none -> 5.0.6-3 @un puN Ib > 95s Broken libopenmpi40:s390x Breaks on libopenmpi3:s390x < none @un H > (< 5.0.6-3) 95s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 95s Considering libopenmpi3t64:s390x 30 as a solution to libopenmpi40:s390x 17 95s Re-Instated libopenmpi3t64:s390x 95s Broken libopenmpi40:s390x Breaks on libopenmpi3t64:s390x < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 95s Considering libopenmpi3t64:s390x 17 as a solution to libopenmpi40:s390x 17 95s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 95s Done 95s Some packages could not be installed. This may mean that you have 95s requested an impossible situation or if you are using the unstable 95s distribution that some required packages have not yet been created 95s or been moved out of Incoming. 95s The following information may help to resolve the situation: 95s 95s The following packages have unmet dependencies: 95s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 95s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 95s E: Unable to correct problems, you have held broken packages. 95s sunnonlinsol FAIL badpkg 95s blame: sundials 95s 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. 95s autopkgtest [10:28:47]: @@@@@@@@@@@@@@@@@@@@ summary 95s arkode FAIL badpkg 95s blame: sundials 95s 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. 95s cvode FAIL badpkg 95s blame: sundials 95s 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. 95s cvodes FAIL badpkg 95s blame: sundials 95s 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. 95s ida FAIL badpkg 95s blame: sundials 95s 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. 95s idas FAIL badpkg 95s blame: sundials 95s 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. 95s kinsol FAIL badpkg 95s blame: sundials 95s 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. 95s sunnonlinsol FAIL badpkg 95s blame: sundials 95s 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. 106s nova [W] Using flock in prodstack6-s390x 106s Creating nova instance adt-plucky-s390x-sundials-20241203-102712-juju-7f2275-prod-proposed-migration-environment-20-4d01689d-45dc-4606-8c75-36a80aaa661d from image adt/ubuntu-plucky-s390x-server-20241203.img (UUID 1a991c1c-46bc-40f7-9cba-4c8bff864ded)...