0s autopkgtest [09:15:44]: starting date and time: 2024-12-04 09:15:44+0000 0s autopkgtest [09:15:44]: git checkout: be626eda Fix armhf LXD image generation for plucky 0s autopkgtest [09:15:44]: host juju-7f2275-prod-proposed-migration-environment-15; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.8iawdxwp/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:hdf5,src:mpi4py,src:openmpi,src:vtk9 --apt-upgrade vtk9 --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 '--env=ADT_TEST_TRIGGERS=hdf5/1.10.10+repack-5ubuntu1 mpi4py/4.0.1-3ubuntu2 openmpi/5.0.6-3 vtk9/9.3.0+dfsg1-1.1build2' -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-15@bos03-arm64-12.secgroup --name adt-plucky-arm64-vtk9-20241204-091544-juju-7f2275-prod-proposed-migration-environment-15-042ff64b-dbbd-44c7-8d90-d281e7812514 --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/ 96s autopkgtest [09:17:20]: testbed dpkg architecture: arm64 96s autopkgtest [09:17:20]: testbed apt version: 2.9.14ubuntu1 96s autopkgtest [09:17:20]: @@@@@@@@@@@@@@@@@@@@ test bed setup 96s autopkgtest [09:17:20]: testbed release detected to be: None 97s autopkgtest [09:17:21]: updating testbed package index (apt update) 97s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB] 98s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 98s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 98s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 98s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [14.2 kB] 98s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B] 98s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [55.9 kB] 98s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [745 kB] 98s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main arm64 Packages [122 kB] 98s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted arm64 Packages [58.2 kB] 98s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe arm64 Packages [612 kB] 98s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse arm64 Packages [20.8 kB] 98s Fetched 1712 kB in 1s (1909 kB/s) 100s Reading package lists... 100s Reading package lists... 100s Building dependency tree... 100s Reading state information... 101s Calculating upgrade... 101s The following package was automatically installed and is no longer required: 101s libassuan0 101s Use 'sudo apt autoremove' to remove it. 101s The following packages will be upgraded: 101s apt apt-utils binutils binutils-aarch64-linux-gnu binutils-common dirmngr 101s gnupg gnupg-l10n gnupg-utils gpg gpg-agent gpg-wks-client gpgconf gpgsm gpgv 101s keyboxd libapt-pkg6.0t64 libbinutils libcap-ng0 libctf-nobfd0 libctf0 101s libgprofng0 libsframe1 publicsuffix 101s 24 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 101s Need to get 10.4 MB of archives. 101s After this operation, 35.8 kB disk space will be freed. 101s Get:1 http://ftpmaster.internal/ubuntu plucky/main arm64 libapt-pkg6.0t64 arm64 2.9.16 [1017 kB] 102s Get:2 http://ftpmaster.internal/ubuntu plucky/main arm64 apt arm64 2.9.16 [1342 kB] 102s Get:3 http://ftpmaster.internal/ubuntu plucky/main arm64 apt-utils arm64 2.9.16 [207 kB] 102s Get:4 http://ftpmaster.internal/ubuntu plucky/main arm64 gpg-wks-client arm64 2.4.4-2ubuntu20 [70.3 kB] 102s Get:5 http://ftpmaster.internal/ubuntu plucky/main arm64 dirmngr arm64 2.4.4-2ubuntu20 [320 kB] 102s Get:6 http://ftpmaster.internal/ubuntu plucky/main arm64 gpgsm arm64 2.4.4-2ubuntu20 [227 kB] 102s Get:7 http://ftpmaster.internal/ubuntu plucky/main arm64 gnupg-utils arm64 2.4.4-2ubuntu20 [107 kB] 102s Get:8 http://ftpmaster.internal/ubuntu plucky/main arm64 gpg-agent arm64 2.4.4-2ubuntu20 [224 kB] 102s Get:9 http://ftpmaster.internal/ubuntu plucky/main arm64 gpg arm64 2.4.4-2ubuntu20 [554 kB] 102s Get:10 http://ftpmaster.internal/ubuntu plucky/main arm64 gpgconf arm64 2.4.4-2ubuntu20 [103 kB] 102s Get:11 http://ftpmaster.internal/ubuntu plucky/main arm64 gnupg all 2.4.4-2ubuntu20 [359 kB] 102s Get:12 http://ftpmaster.internal/ubuntu plucky/main arm64 keyboxd arm64 2.4.4-2ubuntu20 [76.0 kB] 102s Get:13 http://ftpmaster.internal/ubuntu plucky/main arm64 gpgv arm64 2.4.4-2ubuntu20 [153 kB] 102s Get:14 http://ftpmaster.internal/ubuntu plucky/main arm64 libcap-ng0 arm64 0.8.5-4 [14.9 kB] 102s Get:15 http://ftpmaster.internal/ubuntu plucky/main arm64 publicsuffix all 20241025.1547-0.1 [135 kB] 102s Get:16 http://ftpmaster.internal/ubuntu plucky/main arm64 libgprofng0 arm64 2.43.50.20241126-3ubuntu1 [781 kB] 102s Get:17 http://ftpmaster.internal/ubuntu plucky/main arm64 libctf0 arm64 2.43.50.20241126-3ubuntu1 [99.0 kB] 102s Get:18 http://ftpmaster.internal/ubuntu plucky/main arm64 libctf-nobfd0 arm64 2.43.50.20241126-3ubuntu1 [102 kB] 102s Get:19 http://ftpmaster.internal/ubuntu plucky/main arm64 binutils arm64 2.43.50.20241126-3ubuntu1 [3258 B] 102s Get:20 http://ftpmaster.internal/ubuntu plucky/main arm64 binutils-aarch64-linux-gnu arm64 2.43.50.20241126-3ubuntu1 [3390 kB] 102s Get:21 http://ftpmaster.internal/ubuntu plucky/main arm64 libbinutils arm64 2.43.50.20241126-3ubuntu1 [782 kB] 102s Get:22 http://ftpmaster.internal/ubuntu plucky/main arm64 binutils-common arm64 2.43.50.20241126-3ubuntu1 [244 kB] 102s Get:23 http://ftpmaster.internal/ubuntu plucky/main arm64 libsframe1 arm64 2.43.50.20241126-3ubuntu1 [14.3 kB] 102s Get:24 http://ftpmaster.internal/ubuntu plucky/main arm64 gnupg-l10n all 2.4.4-2ubuntu20 [66.3 kB] 103s Fetched 10.4 MB in 1s (11.1 MB/s) 103s (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 ... 80333 files and directories currently installed.) 103s Preparing to unpack .../libapt-pkg6.0t64_2.9.16_arm64.deb ... 103s Unpacking libapt-pkg6.0t64:arm64 (2.9.16) over (2.9.14ubuntu1) ... 103s Setting up libapt-pkg6.0t64:arm64 (2.9.16) ... 103s (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 ... 80333 files and directories currently installed.) 103s Preparing to unpack .../archives/apt_2.9.16_arm64.deb ... 103s Unpacking apt (2.9.16) over (2.9.14ubuntu1) ... 103s Setting up apt (2.9.16) ... 104s (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 ... 80338 files and directories currently installed.) 104s Preparing to unpack .../00-apt-utils_2.9.16_arm64.deb ... 104s Unpacking apt-utils (2.9.16) over (2.9.14ubuntu1) ... 104s Preparing to unpack .../01-gpg-wks-client_2.4.4-2ubuntu20_arm64.deb ... 104s Unpacking gpg-wks-client (2.4.4-2ubuntu20) over (2.4.4-2ubuntu18) ... 104s Preparing to unpack .../02-dirmngr_2.4.4-2ubuntu20_arm64.deb ... 104s Unpacking dirmngr (2.4.4-2ubuntu20) over (2.4.4-2ubuntu18) ... 104s Preparing to unpack .../03-gpgsm_2.4.4-2ubuntu20_arm64.deb ... 104s Unpacking gpgsm (2.4.4-2ubuntu20) over (2.4.4-2ubuntu18) ... 104s Preparing to unpack .../04-gnupg-utils_2.4.4-2ubuntu20_arm64.deb ... 104s Unpacking gnupg-utils (2.4.4-2ubuntu20) over (2.4.4-2ubuntu18) ... 104s Preparing to unpack .../05-gpg-agent_2.4.4-2ubuntu20_arm64.deb ... 104s Unpacking gpg-agent (2.4.4-2ubuntu20) over (2.4.4-2ubuntu18) ... 104s Preparing to unpack .../06-gpg_2.4.4-2ubuntu20_arm64.deb ... 104s Unpacking gpg (2.4.4-2ubuntu20) over (2.4.4-2ubuntu18) ... 104s Preparing to unpack .../07-gpgconf_2.4.4-2ubuntu20_arm64.deb ... 104s Unpacking gpgconf (2.4.4-2ubuntu20) over (2.4.4-2ubuntu18) ... 104s Preparing to unpack .../08-gnupg_2.4.4-2ubuntu20_all.deb ... 104s Unpacking gnupg (2.4.4-2ubuntu20) over (2.4.4-2ubuntu18) ... 105s Preparing to unpack .../09-keyboxd_2.4.4-2ubuntu20_arm64.deb ... 105s Unpacking keyboxd (2.4.4-2ubuntu20) over (2.4.4-2ubuntu18) ... 105s Preparing to unpack .../10-gpgv_2.4.4-2ubuntu20_arm64.deb ... 105s Unpacking gpgv (2.4.4-2ubuntu20) over (2.4.4-2ubuntu18) ... 105s Setting up gpgv (2.4.4-2ubuntu20) ... 105s (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 ... 80338 files and directories currently installed.) 105s Preparing to unpack .../libcap-ng0_0.8.5-4_arm64.deb ... 105s Unpacking libcap-ng0:arm64 (0.8.5-4) over (0.8.5-3build1) ... 105s Setting up libcap-ng0:arm64 (0.8.5-4) ... 105s (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 ... 80338 files and directories currently installed.) 105s Preparing to unpack .../0-publicsuffix_20241025.1547-0.1_all.deb ... 105s Unpacking publicsuffix (20241025.1547-0.1) over (20231001.0357-0.1) ... 105s Preparing to unpack .../1-libgprofng0_2.43.50.20241126-3ubuntu1_arm64.deb ... 105s Unpacking libgprofng0:arm64 (2.43.50.20241126-3ubuntu1) over (2.43.1-4ubuntu1) ... 105s Preparing to unpack .../2-libctf0_2.43.50.20241126-3ubuntu1_arm64.deb ... 105s Unpacking libctf0:arm64 (2.43.50.20241126-3ubuntu1) over (2.43.1-4ubuntu1) ... 105s Preparing to unpack .../3-libctf-nobfd0_2.43.50.20241126-3ubuntu1_arm64.deb ... 105s Unpacking libctf-nobfd0:arm64 (2.43.50.20241126-3ubuntu1) over (2.43.1-4ubuntu1) ... 105s Preparing to unpack .../4-binutils_2.43.50.20241126-3ubuntu1_arm64.deb ... 105s Unpacking binutils (2.43.50.20241126-3ubuntu1) over (2.43.1-4ubuntu1) ... 105s Preparing to unpack .../5-binutils-aarch64-linux-gnu_2.43.50.20241126-3ubuntu1_arm64.deb ... 105s Unpacking binutils-aarch64-linux-gnu (2.43.50.20241126-3ubuntu1) over (2.43.1-4ubuntu1) ... 105s Preparing to unpack .../6-libbinutils_2.43.50.20241126-3ubuntu1_arm64.deb ... 105s Unpacking libbinutils:arm64 (2.43.50.20241126-3ubuntu1) over (2.43.1-4ubuntu1) ... 105s Preparing to unpack .../7-binutils-common_2.43.50.20241126-3ubuntu1_arm64.deb ... 105s Unpacking binutils-common:arm64 (2.43.50.20241126-3ubuntu1) over (2.43.1-4ubuntu1) ... 105s Preparing to unpack .../8-libsframe1_2.43.50.20241126-3ubuntu1_arm64.deb ... 105s Unpacking libsframe1:arm64 (2.43.50.20241126-3ubuntu1) over (2.43.1-4ubuntu1) ... 105s Preparing to unpack .../9-gnupg-l10n_2.4.4-2ubuntu20_all.deb ... 105s Unpacking gnupg-l10n (2.4.4-2ubuntu20) over (2.4.4-2ubuntu18) ... 106s Setting up apt-utils (2.9.16) ... 106s Setting up binutils-common:arm64 (2.43.50.20241126-3ubuntu1) ... 106s Setting up libctf-nobfd0:arm64 (2.43.50.20241126-3ubuntu1) ... 106s Setting up libsframe1:arm64 (2.43.50.20241126-3ubuntu1) ... 106s Setting up gnupg-l10n (2.4.4-2ubuntu20) ... 106s Setting up gpgconf (2.4.4-2ubuntu20) ... 106s Setting up libbinutils:arm64 (2.43.50.20241126-3ubuntu1) ... 106s Setting up publicsuffix (20241025.1547-0.1) ... 106s Setting up gpg (2.4.4-2ubuntu20) ... 106s Setting up gnupg-utils (2.4.4-2ubuntu20) ... 106s Setting up libctf0:arm64 (2.43.50.20241126-3ubuntu1) ... 106s Setting up gpg-agent (2.4.4-2ubuntu20) ... 106s Setting up gpgsm (2.4.4-2ubuntu20) ... 106s Setting up dirmngr (2.4.4-2ubuntu20) ... 107s Setting up libgprofng0:arm64 (2.43.50.20241126-3ubuntu1) ... 107s Setting up keyboxd (2.4.4-2ubuntu20) ... 107s Setting up gnupg (2.4.4-2ubuntu20) ... 107s Setting up gpg-wks-client (2.4.4-2ubuntu20) ... 107s Setting up binutils-aarch64-linux-gnu (2.43.50.20241126-3ubuntu1) ... 107s Setting up binutils (2.43.50.20241126-3ubuntu1) ... 107s Processing triggers for install-info (7.1.1-1) ... 107s Processing triggers for libc-bin (2.40-1ubuntu3) ... 107s Processing triggers for man-db (2.13.0-1) ... 111s Reading package lists... 111s Building dependency tree... 111s Reading state information... 112s The following packages will be REMOVED: 112s libassuan0* 113s 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 113s After this operation, 156 kB disk space will be freed. 113s (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 ... 80343 files and directories currently installed.) 113s Removing libassuan0:arm64 (2.5.6-1build1) ... 113s Processing triggers for libc-bin (2.40-1ubuntu3) ... 113s autopkgtest [09:17:37]: upgrading testbed (apt dist-upgrade and autopurge) 113s Reading package lists... 113s Building dependency tree... 113s Reading state information... 114s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 114s Starting 2 pkgProblemResolver with broken count: 0 114s Done 115s Entering ResolveByKeep 115s 115s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 116s Reading package lists... 116s Building dependency tree... 116s Reading state information... 117s Starting pkgProblemResolver with broken count: 0 117s Starting 2 pkgProblemResolver with broken count: 0 118s Done 119s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 120s autopkgtest [09:17:44]: rebooting testbed after setup commands that affected boot 124s autopkgtest-virt-ssh: WARNING: ssh connection failed. Retrying in 3 seconds... 146s autopkgtest [09:18:10]: testbed running kernel: Linux 6.11.0-8-generic #8-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 16 14:19:41 UTC 2024 148s autopkgtest [09:18:12]: @@@@@@@@@@@@@@@@@@@@ apt-source vtk9 157s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed/universe vtk9 9.3.0+dfsg1-1.1build2 (dsc) [3746 B] 157s Get:2 http://ftpmaster.internal/ubuntu plucky-proposed/universe vtk9 9.3.0+dfsg1-1.1build2 (tar) [69.8 MB] 157s Get:3 http://ftpmaster.internal/ubuntu plucky-proposed/universe vtk9 9.3.0+dfsg1-1.1build2 (diff) [22.5 kB] 157s gpgv: Signature made Sun Dec 1 20:55:53 2024 UTC 157s gpgv: using RSA key 568BF22A66337CBFC9A6B9B72C83DBC8E9BD0E37 157s gpgv: Can't check signature: No public key 157s dpkg-source: warning: cannot verify inline signature for ./vtk9_9.3.0+dfsg1-1.1build2.dsc: no acceptable signature found 161s autopkgtest [09:18:25]: testing package vtk9 version 9.3.0+dfsg1-1.1build2 162s autopkgtest [09:18:26]: build not needed 171s autopkgtest [09:18:35]: test buildBoolean: preparing testbed 171s Reading package lists... 171s Building dependency tree... 171s Reading state information... 172s Starting pkgProblemResolver with broken count: 2 172s Starting 2 pkgProblemResolver with broken count: 2 172s Investigating (0) libvtk9.3:arm64 < none -> 9.3.0+dfsg1-1build2 @un puN Ib > 172s Broken libvtk9.3:arm64 Depends on libopenmpi3t64:arm64 < none @un pH > (>= 5.0.5) 172s Considering libopenmpi3t64:arm64 0 as a solution to libvtk9.3:arm64 7 172s Investigating (0) python3-vtk9:arm64 < none -> 9.3.0+dfsg1-1build2 @un puN Ib > 172s Broken python3-vtk9:arm64 Depends on libopenmpi3t64:arm64 < none @un pH > (>= 5.0.5) 172s Considering libopenmpi3t64:arm64 0 as a solution to python3-vtk9:arm64 1 172s Done 172s Some packages could not be installed. This may mean that you have 172s requested an impossible situation or if you are using the unstable 172s distribution that some required packages have not yet been created 172s or been moved out of Incoming. 172s The following information may help to resolve the situation: 172s 172s The following packages have unmet dependencies: 173s libvtk9.3 : Depends: libopenmpi3t64 (>= 5.0.5) but it is not installable 173s python3-vtk9 : Depends: libopenmpi3t64 (>= 5.0.5) but it is not installable 173s E: Unable to correct problems, you have held broken packages. 173s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed 173s Reading package lists... 174s Building dependency tree... 174s Reading state information... 175s Starting pkgProblemResolver with broken count: 2 175s Starting 2 pkgProblemResolver with broken count: 2 175s Investigating (0) libvtk9.3:arm64 < none -> 9.3.0+dfsg1-1build2 @un puN Ib > 175s Broken libvtk9.3:arm64 Depends on libopenmpi3t64:arm64 < none @un pH > (>= 5.0.5) 175s Considering libopenmpi3t64:arm64 0 as a solution to libvtk9.3:arm64 7 175s Investigating (0) python3-vtk9:arm64 < none -> 9.3.0+dfsg1-1build2 @un puN Ib > 175s Broken python3-vtk9:arm64 Depends on libopenmpi3t64:arm64 < none @un pH > (>= 5.0.5) 175s Considering libopenmpi3t64:arm64 0 as a solution to python3-vtk9:arm64 1 175s Done 175s Some packages could not be installed. This may mean that you have 175s requested an impossible situation or if you are using the unstable 175s distribution that some required packages have not yet been created 175s or been moved out of Incoming. 175s The following information may help to resolve the situation: 175s 175s The following packages have unmet dependencies: 176s libvtk9.3 : Depends: libopenmpi3t64 (>= 5.0.5) but it is not installable 176s python3-vtk9 : Depends: libopenmpi3t64 (>= 5.0.5) but it is not installable 176s E: Unable to correct problems, you have held broken packages. 176s autopkgtest [09:18:40]: test buildPoint: preparing testbed 176s buildBoolean FAIL badpkg 176s blame: vtk9 176s 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. 176s Reading package lists... 177s Building dependency tree... 177s Reading state information... 177s Starting pkgProblemResolver with broken count: 2 178s Starting 2 pkgProblemResolver with broken count: 2 178s Investigating (0) libvtk9.3:arm64 < none -> 9.3.0+dfsg1-1build2 @un puN Ib > 178s Broken libvtk9.3:arm64 Depends on libopenmpi3t64:arm64 < none @un pH > (>= 5.0.5) 178s Considering libopenmpi3t64:arm64 0 as a solution to libvtk9.3:arm64 7 178s Investigating (0) python3-vtk9:arm64 < none -> 9.3.0+dfsg1-1build2 @un puN Ib > 178s Broken python3-vtk9:arm64 Depends on libopenmpi3t64:arm64 < none @un pH > (>= 5.0.5) 178s Considering libopenmpi3t64:arm64 0 as a solution to python3-vtk9:arm64 1 178s Done 178s Some packages could not be installed. This may mean that you have 178s requested an impossible situation or if you are using the unstable 178s distribution that some required packages have not yet been created 178s or been moved out of Incoming. 178s The following information may help to resolve the situation: 178s 178s The following packages have unmet dependencies: 178s libvtk9.3 : Depends: libopenmpi3t64 (>= 5.0.5) but it is not installable 178s python3-vtk9 : Depends: libopenmpi3t64 (>= 5.0.5) but it is not installable 178s E: Unable to correct problems, you have held broken packages. 178s buildPoint FAIL badpkg 178s blame: vtk9 178s 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. 178s autopkgtest [09:18:42]: test buildVTU: preparing testbed 179s Reading package lists... 179s Building dependency tree... 179s Reading state information... 180s Starting pkgProblemResolver with broken count: 2 181s Starting 2 pkgProblemResolver with broken count: 2 181s Investigating (0) libvtk9.3:arm64 < none -> 9.3.0+dfsg1-1build2 @un puN Ib > 181s Broken libvtk9.3:arm64 Depends on libopenmpi3t64:arm64 < none @un pH > (>= 5.0.5) 181s Considering libopenmpi3t64:arm64 0 as a solution to libvtk9.3:arm64 7 181s Investigating (0) python3-vtk9:arm64 < none -> 9.3.0+dfsg1-1build2 @un puN Ib > 181s Broken python3-vtk9:arm64 Depends on libopenmpi3t64:arm64 < none @un pH > (>= 5.0.5) 181s Considering libopenmpi3t64:arm64 0 as a solution to python3-vtk9:arm64 1 181s Done 181s Some packages could not be installed. This may mean that you have 181s requested an impossible situation or if you are using the unstable 181s distribution that some required packages have not yet been created 181s or been moved out of Incoming. 181s The following information may help to resolve the situation: 181s 181s The following packages have unmet dependencies: 181s libvtk9.3 : Depends: libopenmpi3t64 (>= 5.0.5) but it is not installable 181s python3-vtk9 : Depends: libopenmpi3t64 (>= 5.0.5) but it is not installable 181s E: Unable to correct problems, you have held broken packages. 181s buildVTU FAIL badpkg 181s blame: vtk9 181s 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. 181s autopkgtest [09:18:45]: test buildDistance: preparing testbed 182s Reading package lists... 182s Building dependency tree... 182s Reading state information... 183s Starting pkgProblemResolver with broken count: 2 183s Starting 2 pkgProblemResolver with broken count: 2 183s Investigating (0) libvtk9.3:arm64 < none -> 9.3.0+dfsg1-1build2 @un puN Ib > 183s Broken libvtk9.3:arm64 Depends on libopenmpi3t64:arm64 < none @un pH > (>= 5.0.5) 183s Considering libopenmpi3t64:arm64 0 as a solution to libvtk9.3:arm64 7 183s Investigating (0) python3-vtk9:arm64 < none -> 9.3.0+dfsg1-1build2 @un puN Ib > 183s Broken python3-vtk9:arm64 Depends on libopenmpi3t64:arm64 < none @un pH > (>= 5.0.5) 183s Considering libopenmpi3t64:arm64 0 as a solution to python3-vtk9:arm64 1 183s Done 183s Some packages could not be installed. This may mean that you have 183s requested an impossible situation or if you are using the unstable 183s distribution that some required packages have not yet been created 183s or been moved out of Incoming. 183s The following information may help to resolve the situation: 183s 183s The following packages have unmet dependencies: 184s libvtk9.3 : Depends: libopenmpi3t64 (>= 5.0.5) but it is not installable 184s python3-vtk9 : Depends: libopenmpi3t64 (>= 5.0.5) but it is not installable 184s E: Unable to correct problems, you have held broken packages. 184s buildDistance FAIL badpkg 184s blame: vtk9 184s 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. 184s autopkgtest [09:18:48]: test buildPNG: preparing testbed 184s Reading package lists... 185s Building dependency tree... 185s Reading state information... 185s Starting pkgProblemResolver with broken count: 2 186s Starting 2 pkgProblemResolver with broken count: 2 186s Investigating (0) libvtk9.3:arm64 < none -> 9.3.0+dfsg1-1build2 @un puN Ib > 186s Broken libvtk9.3:arm64 Depends on libopenmpi3t64:arm64 < none @un pH > (>= 5.0.5) 186s Considering libopenmpi3t64:arm64 0 as a solution to libvtk9.3:arm64 7 186s Investigating (0) python3-vtk9:arm64 < none -> 9.3.0+dfsg1-1build2 @un puN Ib > 186s Broken python3-vtk9:arm64 Depends on libopenmpi3t64:arm64 < none @un pH > (>= 5.0.5) 186s Considering libopenmpi3t64:arm64 0 as a solution to python3-vtk9:arm64 1 186s Done 186s Some packages could not be installed. This may mean that you have 186s requested an impossible situation or if you are using the unstable 186s distribution that some required packages have not yet been created 186s or been moved out of Incoming. 186s The following information may help to resolve the situation: 186s 186s The following packages have unmet dependencies: 186s libvtk9.3 : Depends: libopenmpi3t64 (>= 5.0.5) but it is not installable 186s python3-vtk9 : Depends: libopenmpi3t64 (>= 5.0.5) but it is not installable 186s E: Unable to correct problems, you have held broken packages. 186s buildPNG FAIL badpkg 186s blame: vtk9 186s 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. 186s autopkgtest [09:18:50]: test buildVTP: preparing testbed 187s Reading package lists... 187s Building dependency tree... 187s Reading state information... 188s Starting pkgProblemResolver with broken count: 2 188s Starting 2 pkgProblemResolver with broken count: 2 188s Investigating (0) libvtk9.3:arm64 < none -> 9.3.0+dfsg1-1build2 @un puN Ib > 188s Broken libvtk9.3:arm64 Depends on libopenmpi3t64:arm64 < none @un pH > (>= 5.0.5) 188s Considering libopenmpi3t64:arm64 0 as a solution to libvtk9.3:arm64 7 188s Investigating (0) python3-vtk9:arm64 < none -> 9.3.0+dfsg1-1build2 @un puN Ib > 188s Broken python3-vtk9:arm64 Depends on libopenmpi3t64:arm64 < none @un pH > (>= 5.0.5) 188s Considering libopenmpi3t64:arm64 0 as a solution to python3-vtk9:arm64 1 188s Done 188s Some packages could not be installed. This may mean that you have 188s requested an impossible situation or if you are using the unstable 188s distribution that some required packages have not yet been created 188s or been moved out of Incoming. 188s The following information may help to resolve the situation: 188s 188s The following packages have unmet dependencies: 189s libvtk9.3 : Depends: libopenmpi3t64 (>= 5.0.5) but it is not installable 189s python3-vtk9 : Depends: libopenmpi3t64 (>= 5.0.5) but it is not installable 189s E: Unable to correct problems, you have held broken packages. 189s buildVTP FAIL badpkg 189s blame: vtk9 189s 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. 189s autopkgtest [09:18:53]: @@@@@@@@@@@@@@@@@@@@ summary 189s buildBoolean FAIL badpkg 189s blame: vtk9 189s 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. 189s buildPoint FAIL badpkg 189s blame: vtk9 189s 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. 189s buildVTU FAIL badpkg 189s blame: vtk9 189s 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. 189s buildDistance FAIL badpkg 189s blame: vtk9 189s 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. 189s buildPNG FAIL badpkg 189s blame: vtk9 189s 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. 189s buildVTP FAIL badpkg 189s blame: vtk9 189s 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. 221s nova [W] Using flock in prodstack6-arm64 221s Creating nova instance adt-plucky-arm64-vtk9-20241204-091544-juju-7f2275-prod-proposed-migration-environment-15-042ff64b-dbbd-44c7-8d90-d281e7812514 from image adt/ubuntu-plucky-arm64-server-20241203.img (UUID b9293590-1195-42ea-ba16-5ab4b1e94eab)...