0s autopkgtest [09:15:45]: starting date and time: 2024-12-04 09:15:45+0000 0s autopkgtest [09:15:45]: git checkout: be626eda Fix armhf LXD image generation for plucky 0s autopkgtest [09:15:45]: host juju-7f2275-prod-proposed-migration-environment-20; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.2siquye9/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-ppc64el --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-20@bos03-ppc64el-7.secgroup --name adt-plucky-ppc64el-vtk9-20241204-091545-juju-7f2275-prod-proposed-migration-environment-20-e7f6e279-f0c1-4d35-8233-7b90dcc37aac --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/ 74s autopkgtest [09:16:59]: testbed dpkg architecture: ppc64el 74s autopkgtest [09:16:59]: testbed apt version: 2.9.14ubuntu1 74s autopkgtest [09:16:59]: @@@@@@@@@@@@@@@@@@@@ test bed setup 75s autopkgtest [09:17:00]: testbed release detected to be: None 75s autopkgtest [09:17:00]: updating testbed package index (apt update) 76s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB] 76s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 76s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 76s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 76s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [745 kB] 76s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [55.9 kB] 76s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B] 76s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [14.2 kB] 76s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main ppc64el Packages [105 kB] 76s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted ppc64el Packages [928 B] 76s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe ppc64el Packages [597 kB] 76s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse ppc64el Packages [10.4 kB] 77s Fetched 1612 kB in 1s (1628 kB/s) 77s Reading package lists... 78s Reading package lists... 78s Building dependency tree... 78s Reading state information... 78s Calculating upgrade... 78s The following package was automatically installed and is no longer required: 78s libassuan0 78s Use 'sudo apt autoremove' to remove it. 78s The following packages will be upgraded: 78s apt apt-utils binutils binutils-common binutils-powerpc64le-linux-gnu 78s dirmngr gnupg gnupg-l10n gnupg-utils gpg gpg-agent gpg-wks-client gpgconf 78s gpgsm gpgv keyboxd libapt-pkg6.0t64 libbinutils libcap-ng0 libctf-nobfd0 78s libctf0 libsframe1 publicsuffix 79s 23 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 79s Need to get 9352 kB of archives. 79s After this operation, 508 kB of additional disk space will be used. 79s Get:1 http://ftpmaster.internal/ubuntu plucky/main ppc64el libapt-pkg6.0t64 ppc64el 2.9.16 [1140 kB] 79s Get:2 http://ftpmaster.internal/ubuntu plucky/main ppc64el apt ppc64el 2.9.16 [1400 kB] 79s Get:3 http://ftpmaster.internal/ubuntu plucky/main ppc64el apt-utils ppc64el 2.9.16 [229 kB] 79s Get:4 http://ftpmaster.internal/ubuntu plucky/main ppc64el gpg-wks-client ppc64el 2.4.4-2ubuntu20 [84.3 kB] 79s Get:5 http://ftpmaster.internal/ubuntu plucky/main ppc64el dirmngr ppc64el 2.4.4-2ubuntu20 [390 kB] 79s Get:6 http://ftpmaster.internal/ubuntu plucky/main ppc64el gpgsm ppc64el 2.4.4-2ubuntu20 [292 kB] 79s Get:7 http://ftpmaster.internal/ubuntu plucky/main ppc64el gnupg-utils ppc64el 2.4.4-2ubuntu20 [123 kB] 79s Get:8 http://ftpmaster.internal/ubuntu plucky/main ppc64el gpg-agent ppc64el 2.4.4-2ubuntu20 [275 kB] 79s Get:9 http://ftpmaster.internal/ubuntu plucky/main ppc64el gpg ppc64el 2.4.4-2ubuntu20 [707 kB] 79s Get:10 http://ftpmaster.internal/ubuntu plucky/main ppc64el gpgconf ppc64el 2.4.4-2ubuntu20 [115 kB] 79s Get:11 http://ftpmaster.internal/ubuntu plucky/main ppc64el gnupg all 2.4.4-2ubuntu20 [359 kB] 79s Get:12 http://ftpmaster.internal/ubuntu plucky/main ppc64el keyboxd ppc64el 2.4.4-2ubuntu20 [93.3 kB] 79s Get:13 http://ftpmaster.internal/ubuntu plucky/main ppc64el gpgv ppc64el 2.4.4-2ubuntu20 [197 kB] 79s Get:14 http://ftpmaster.internal/ubuntu plucky/main ppc64el libcap-ng0 ppc64el 0.8.5-4 [16.2 kB] 79s Get:15 http://ftpmaster.internal/ubuntu plucky/main ppc64el publicsuffix all 20241025.1547-0.1 [135 kB] 79s Get:16 http://ftpmaster.internal/ubuntu plucky/main ppc64el libctf0 ppc64el 2.43.50.20241126-3ubuntu1 [114 kB] 79s Get:17 http://ftpmaster.internal/ubuntu plucky/main ppc64el libctf-nobfd0 ppc64el 2.43.50.20241126-3ubuntu1 [117 kB] 79s Get:18 http://ftpmaster.internal/ubuntu plucky/main ppc64el binutils ppc64el 2.43.50.20241126-3ubuntu1 [3096 B] 79s Get:19 http://ftpmaster.internal/ubuntu plucky/main ppc64el binutils-powerpc64le-linux-gnu ppc64el 2.43.50.20241126-3ubuntu1 [2547 kB] 79s Get:20 http://ftpmaster.internal/ubuntu plucky/main ppc64el libbinutils ppc64el 2.43.50.20241126-3ubuntu1 [711 kB] 79s Get:21 http://ftpmaster.internal/ubuntu plucky/main ppc64el binutils-common ppc64el 2.43.50.20241126-3ubuntu1 [222 kB] 79s Get:22 http://ftpmaster.internal/ubuntu plucky/main ppc64el libsframe1 ppc64el 2.43.50.20241126-3ubuntu1 [16.0 kB] 79s Get:23 http://ftpmaster.internal/ubuntu plucky/main ppc64el gnupg-l10n all 2.4.4-2ubuntu20 [66.3 kB] 80s Fetched 9352 kB in 1s (9358 kB/s) 80s (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 ... 74178 files and directories currently installed.) 80s Preparing to unpack .../libapt-pkg6.0t64_2.9.16_ppc64el.deb ... 80s Unpacking libapt-pkg6.0t64:ppc64el (2.9.16) over (2.9.14ubuntu1) ... 80s Setting up libapt-pkg6.0t64:ppc64el (2.9.16) ... 80s (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 ... 74178 files and directories currently installed.) 80s Preparing to unpack .../apt_2.9.16_ppc64el.deb ... 80s Unpacking apt (2.9.16) over (2.9.14ubuntu1) ... 80s Setting up apt (2.9.16) ... 81s (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 ... 74183 files and directories currently installed.) 81s Preparing to unpack .../00-apt-utils_2.9.16_ppc64el.deb ... 81s Unpacking apt-utils (2.9.16) over (2.9.14ubuntu1) ... 81s Preparing to unpack .../01-gpg-wks-client_2.4.4-2ubuntu20_ppc64el.deb ... 81s Unpacking gpg-wks-client (2.4.4-2ubuntu20) over (2.4.4-2ubuntu18) ... 81s Preparing to unpack .../02-dirmngr_2.4.4-2ubuntu20_ppc64el.deb ... 81s Unpacking dirmngr (2.4.4-2ubuntu20) over (2.4.4-2ubuntu18) ... 81s Preparing to unpack .../03-gpgsm_2.4.4-2ubuntu20_ppc64el.deb ... 81s Unpacking gpgsm (2.4.4-2ubuntu20) over (2.4.4-2ubuntu18) ... 81s Preparing to unpack .../04-gnupg-utils_2.4.4-2ubuntu20_ppc64el.deb ... 81s Unpacking gnupg-utils (2.4.4-2ubuntu20) over (2.4.4-2ubuntu18) ... 81s Preparing to unpack .../05-gpg-agent_2.4.4-2ubuntu20_ppc64el.deb ... 81s Unpacking gpg-agent (2.4.4-2ubuntu20) over (2.4.4-2ubuntu18) ... 81s Preparing to unpack .../06-gpg_2.4.4-2ubuntu20_ppc64el.deb ... 81s Unpacking gpg (2.4.4-2ubuntu20) over (2.4.4-2ubuntu18) ... 81s Preparing to unpack .../07-gpgconf_2.4.4-2ubuntu20_ppc64el.deb ... 81s Unpacking gpgconf (2.4.4-2ubuntu20) over (2.4.4-2ubuntu18) ... 81s Preparing to unpack .../08-gnupg_2.4.4-2ubuntu20_all.deb ... 81s Unpacking gnupg (2.4.4-2ubuntu20) over (2.4.4-2ubuntu18) ... 81s Preparing to unpack .../09-keyboxd_2.4.4-2ubuntu20_ppc64el.deb ... 81s Unpacking keyboxd (2.4.4-2ubuntu20) over (2.4.4-2ubuntu18) ... 81s Preparing to unpack .../10-gpgv_2.4.4-2ubuntu20_ppc64el.deb ... 81s Unpacking gpgv (2.4.4-2ubuntu20) over (2.4.4-2ubuntu18) ... 81s Setting up gpgv (2.4.4-2ubuntu20) ... 81s (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 ... 74183 files and directories currently installed.) 81s Preparing to unpack .../libcap-ng0_0.8.5-4_ppc64el.deb ... 81s Unpacking libcap-ng0:ppc64el (0.8.5-4) over (0.8.5-3build1) ... 81s Setting up libcap-ng0:ppc64el (0.8.5-4) ... 81s (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 ... 74183 files and directories currently installed.) 81s Preparing to unpack .../0-publicsuffix_20241025.1547-0.1_all.deb ... 81s Unpacking publicsuffix (20241025.1547-0.1) over (20231001.0357-0.1) ... 81s Preparing to unpack .../1-libctf0_2.43.50.20241126-3ubuntu1_ppc64el.deb ... 81s Unpacking libctf0:ppc64el (2.43.50.20241126-3ubuntu1) over (2.43.1-4ubuntu1) ... 81s Preparing to unpack .../2-libctf-nobfd0_2.43.50.20241126-3ubuntu1_ppc64el.deb ... 81s Unpacking libctf-nobfd0:ppc64el (2.43.50.20241126-3ubuntu1) over (2.43.1-4ubuntu1) ... 81s Preparing to unpack .../3-binutils_2.43.50.20241126-3ubuntu1_ppc64el.deb ... 81s Unpacking binutils (2.43.50.20241126-3ubuntu1) over (2.43.1-4ubuntu1) ... 81s Preparing to unpack .../4-binutils-powerpc64le-linux-gnu_2.43.50.20241126-3ubuntu1_ppc64el.deb ... 81s Unpacking binutils-powerpc64le-linux-gnu (2.43.50.20241126-3ubuntu1) over (2.43.1-4ubuntu1) ... 82s Preparing to unpack .../5-libbinutils_2.43.50.20241126-3ubuntu1_ppc64el.deb ... 82s Unpacking libbinutils:ppc64el (2.43.50.20241126-3ubuntu1) over (2.43.1-4ubuntu1) ... 82s Preparing to unpack .../6-binutils-common_2.43.50.20241126-3ubuntu1_ppc64el.deb ... 82s Unpacking binutils-common:ppc64el (2.43.50.20241126-3ubuntu1) over (2.43.1-4ubuntu1) ... 82s Preparing to unpack .../7-libsframe1_2.43.50.20241126-3ubuntu1_ppc64el.deb ... 82s Unpacking libsframe1:ppc64el (2.43.50.20241126-3ubuntu1) over (2.43.1-4ubuntu1) ... 82s Preparing to unpack .../8-gnupg-l10n_2.4.4-2ubuntu20_all.deb ... 82s Unpacking gnupg-l10n (2.4.4-2ubuntu20) over (2.4.4-2ubuntu18) ... 82s Setting up apt-utils (2.9.16) ... 82s Setting up binutils-common:ppc64el (2.43.50.20241126-3ubuntu1) ... 82s Setting up libctf-nobfd0:ppc64el (2.43.50.20241126-3ubuntu1) ... 82s Setting up libsframe1:ppc64el (2.43.50.20241126-3ubuntu1) ... 82s Setting up gnupg-l10n (2.4.4-2ubuntu20) ... 82s Setting up gpgconf (2.4.4-2ubuntu20) ... 82s Setting up libbinutils:ppc64el (2.43.50.20241126-3ubuntu1) ... 82s Setting up publicsuffix (20241025.1547-0.1) ... 82s Setting up gpg (2.4.4-2ubuntu20) ... 82s Setting up gnupg-utils (2.4.4-2ubuntu20) ... 82s Setting up libctf0:ppc64el (2.43.50.20241126-3ubuntu1) ... 82s Setting up gpg-agent (2.4.4-2ubuntu20) ... 82s Setting up gpgsm (2.4.4-2ubuntu20) ... 82s Setting up dirmngr (2.4.4-2ubuntu20) ... 82s Setting up keyboxd (2.4.4-2ubuntu20) ... 83s Setting up gnupg (2.4.4-2ubuntu20) ... 83s Setting up binutils-powerpc64le-linux-gnu (2.43.50.20241126-3ubuntu1) ... 83s Setting up gpg-wks-client (2.4.4-2ubuntu20) ... 83s Setting up binutils (2.43.50.20241126-3ubuntu1) ... 83s Processing triggers for install-info (7.1.1-1) ... 83s Processing triggers for libc-bin (2.40-1ubuntu3) ... 83s Processing triggers for man-db (2.13.0-1) ... 85s Reading package lists... 86s Building dependency tree... 86s Reading state information... 86s The following packages will be REMOVED: 86s libassuan0* 86s 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 86s After this operation, 156 kB disk space will be freed. 86s (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 ... 74183 files and directories currently installed.) 86s Removing libassuan0:ppc64el (2.5.6-1build1) ... 86s Processing triggers for libc-bin (2.40-1ubuntu3) ... 86s autopkgtest [09:17:11]: upgrading testbed (apt dist-upgrade and autopurge) 86s Reading package lists... 87s Building dependency tree... 87s Reading state information... 87s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 87s Starting 2 pkgProblemResolver with broken count: 0 87s Done 87s Entering ResolveByKeep 87s 87s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 88s Reading package lists... 88s Building dependency tree... 88s Reading state information... 88s Starting pkgProblemResolver with broken count: 0 88s Starting 2 pkgProblemResolver with broken count: 0 88s Done 88s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 88s autopkgtest [09:17:13]: rebooting testbed after setup commands that affected boot 92s autopkgtest-virt-ssh: WARNING: ssh connection failed. Retrying in 3 seconds... 117s autopkgtest [09:17:42]: testbed running kernel: Linux 6.11.0-8-generic #8-Ubuntu SMP Mon Sep 16 13:49:23 UTC 2024 119s autopkgtest [09:17:44]: @@@@@@@@@@@@@@@@@@@@ apt-source vtk9 126s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed/universe vtk9 9.3.0+dfsg1-1.1build2 (dsc) [3746 B] 126s Get:2 http://ftpmaster.internal/ubuntu plucky-proposed/universe vtk9 9.3.0+dfsg1-1.1build2 (tar) [69.8 MB] 126s Get:3 http://ftpmaster.internal/ubuntu plucky-proposed/universe vtk9 9.3.0+dfsg1-1.1build2 (diff) [22.5 kB] 127s gpgv: Signature made Sun Dec 1 20:55:53 2024 UTC 127s gpgv: using RSA key 568BF22A66337CBFC9A6B9B72C83DBC8E9BD0E37 127s gpgv: Can't check signature: No public key 127s dpkg-source: warning: cannot verify inline signature for ./vtk9_9.3.0+dfsg1-1.1build2.dsc: no acceptable signature found 131s autopkgtest [09:17:56]: testing package vtk9 version 9.3.0+dfsg1-1.1build2 132s autopkgtest [09:17:57]: build not needed 142s autopkgtest [09:18:07]: test buildBoolean: preparing testbed 142s Reading package lists... 142s Building dependency tree... 142s Reading state information... 142s Starting pkgProblemResolver with broken count: 2 142s Starting 2 pkgProblemResolver with broken count: 2 142s Investigating (0) libvtk9.3:ppc64el < none -> 9.3.0+dfsg1-1build2 @un puN Ib > 142s Broken libvtk9.3:ppc64el Depends on libopenmpi3t64:ppc64el < none @un pH > (>= 5.0.5) 142s Considering libopenmpi3t64:ppc64el 0 as a solution to libvtk9.3:ppc64el 7 142s Investigating (0) python3-vtk9:ppc64el < none -> 9.3.0+dfsg1-1build2 @un puN Ib > 142s Broken python3-vtk9:ppc64el Depends on libopenmpi3t64:ppc64el < none @un pH > (>= 5.0.5) 142s Considering libopenmpi3t64:ppc64el 0 as a solution to python3-vtk9:ppc64el 1 142s Done 142s Some packages could not be installed. This may mean that you have 142s requested an impossible situation or if you are using the unstable 142s distribution that some required packages have not yet been created 142s or been moved out of Incoming. 142s The following information may help to resolve the situation: 142s 142s The following packages have unmet dependencies: 142s libvtk9.3 : Depends: libopenmpi3t64 (>= 5.0.5) but it is not installable 142s python3-vtk9 : Depends: libopenmpi3t64 (>= 5.0.5) but it is not installable 142s E: Unable to correct problems, you have held broken packages. 142s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed 143s Reading package lists... 143s Building dependency tree... 143s Reading state information... 144s Starting pkgProblemResolver with broken count: 2 144s Starting 2 pkgProblemResolver with broken count: 2 144s Investigating (0) libvtk9.3:ppc64el < none -> 9.3.0+dfsg1-1build2 @un puN Ib > 144s Broken libvtk9.3:ppc64el Depends on libopenmpi3t64:ppc64el < none @un pH > (>= 5.0.5) 144s Considering libopenmpi3t64:ppc64el 0 as a solution to libvtk9.3:ppc64el 7 144s Investigating (0) python3-vtk9:ppc64el < none -> 9.3.0+dfsg1-1build2 @un puN Ib > 144s Broken python3-vtk9:ppc64el Depends on libopenmpi3t64:ppc64el < none @un pH > (>= 5.0.5) 144s Considering libopenmpi3t64:ppc64el 0 as a solution to python3-vtk9:ppc64el 1 144s Done 144s Some packages could not be installed. This may mean that you have 144s requested an impossible situation or if you are using the unstable 144s distribution that some required packages have not yet been created 144s or been moved out of Incoming. 144s The following information may help to resolve the situation: 144s 144s The following packages have unmet dependencies: 144s libvtk9.3 : Depends: libopenmpi3t64 (>= 5.0.5) but it is not installable 144s python3-vtk9 : Depends: libopenmpi3t64 (>= 5.0.5) but it is not installable 144s E: Unable to correct problems, you have held broken packages. 144s buildBoolean FAIL badpkg 144s blame: vtk9 144s badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. 144s autopkgtest [09:18:09]: test buildPoint: preparing testbed 144s Reading package lists... 144s Building dependency tree... 144s Reading state information... 144s Starting pkgProblemResolver with broken count: 2 144s Starting 2 pkgProblemResolver with broken count: 2 144s Investigating (0) libvtk9.3:ppc64el < none -> 9.3.0+dfsg1-1build2 @un puN Ib > 144s Broken libvtk9.3:ppc64el Depends on libopenmpi3t64:ppc64el < none @un pH > (>= 5.0.5) 144s Considering libopenmpi3t64:ppc64el 0 as a solution to libvtk9.3:ppc64el 7 144s Investigating (0) python3-vtk9:ppc64el < none -> 9.3.0+dfsg1-1build2 @un puN Ib > 144s Broken python3-vtk9:ppc64el Depends on libopenmpi3t64:ppc64el < none @un pH > (>= 5.0.5) 144s Considering libopenmpi3t64:ppc64el 0 as a solution to python3-vtk9:ppc64el 1 144s Done 144s Some packages could not be installed. This may mean that you have 144s requested an impossible situation or if you are using the unstable 144s distribution that some required packages have not yet been created 144s or been moved out of Incoming. 144s The following information may help to resolve the situation: 144s 144s The following packages have unmet dependencies: 145s libvtk9.3 : Depends: libopenmpi3t64 (>= 5.0.5) but it is not installable 145s python3-vtk9 : Depends: libopenmpi3t64 (>= 5.0.5) but it is not installable 145s E: Unable to correct problems, you have held broken packages. 145s autopkgtest [09:18:10]: test buildVTU: preparing testbed 145s buildPoint FAIL badpkg 145s blame: vtk9 145s badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. 145s Reading package lists... 145s Building dependency tree... 145s Reading state information... 145s Starting pkgProblemResolver with broken count: 2 145s Starting 2 pkgProblemResolver with broken count: 2 145s Investigating (0) libvtk9.3:ppc64el < none -> 9.3.0+dfsg1-1build2 @un puN Ib > 145s Broken libvtk9.3:ppc64el Depends on libopenmpi3t64:ppc64el < none @un pH > (>= 5.0.5) 145s Considering libopenmpi3t64:ppc64el 0 as a solution to libvtk9.3:ppc64el 7 145s Investigating (0) python3-vtk9:ppc64el < none -> 9.3.0+dfsg1-1build2 @un puN Ib > 145s Broken python3-vtk9:ppc64el Depends on libopenmpi3t64:ppc64el < none @un pH > (>= 5.0.5) 145s Considering libopenmpi3t64:ppc64el 0 as a solution to python3-vtk9:ppc64el 1 145s Done 145s Some packages could not be installed. This may mean that you have 145s requested an impossible situation or if you are using the unstable 145s distribution that some required packages have not yet been created 145s or been moved out of Incoming. 145s The following information may help to resolve the situation: 145s 145s The following packages have unmet dependencies: 145s libvtk9.3 : Depends: libopenmpi3t64 (>= 5.0.5) but it is not installable 145s python3-vtk9 : Depends: libopenmpi3t64 (>= 5.0.5) but it is not installable 145s E: Unable to correct problems, you have held broken packages. 145s autopkgtest [09:18:10]: test buildDistance: preparing testbed 145s buildVTU FAIL badpkg 145s blame: vtk9 145s badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. 145s Reading package lists... 146s Building dependency tree... 146s Reading state information... 146s Starting pkgProblemResolver with broken count: 2 146s Starting 2 pkgProblemResolver with broken count: 2 146s Investigating (0) libvtk9.3:ppc64el < none -> 9.3.0+dfsg1-1build2 @un puN Ib > 146s Broken libvtk9.3:ppc64el Depends on libopenmpi3t64:ppc64el < none @un pH > (>= 5.0.5) 146s Considering libopenmpi3t64:ppc64el 0 as a solution to libvtk9.3:ppc64el 7 146s Investigating (0) python3-vtk9:ppc64el < none -> 9.3.0+dfsg1-1build2 @un puN Ib > 146s Broken python3-vtk9:ppc64el Depends on libopenmpi3t64:ppc64el < none @un pH > (>= 5.0.5) 146s Considering libopenmpi3t64:ppc64el 0 as a solution to python3-vtk9:ppc64el 1 146s Done 146s Some packages could not be installed. This may mean that you have 146s requested an impossible situation or if you are using the unstable 146s distribution that some required packages have not yet been created 146s or been moved out of Incoming. 146s The following information may help to resolve the situation: 146s 146s The following packages have unmet dependencies: 146s libvtk9.3 : Depends: libopenmpi3t64 (>= 5.0.5) but it is not installable 146s python3-vtk9 : Depends: libopenmpi3t64 (>= 5.0.5) but it is not installable 146s E: Unable to correct problems, you have held broken packages. 146s autopkgtest [09:18:11]: test buildPNG: preparing testbed 146s buildDistance FAIL badpkg 146s blame: vtk9 146s 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. 146s Reading package lists... 146s Building dependency tree... 146s Reading state information... 146s Starting pkgProblemResolver with broken count: 2 146s Starting 2 pkgProblemResolver with broken count: 2 146s Investigating (0) libvtk9.3:ppc64el < none -> 9.3.0+dfsg1-1build2 @un puN Ib > 146s Broken libvtk9.3:ppc64el Depends on libopenmpi3t64:ppc64el < none @un pH > (>= 5.0.5) 146s Considering libopenmpi3t64:ppc64el 0 as a solution to libvtk9.3:ppc64el 7 146s Investigating (0) python3-vtk9:ppc64el < none -> 9.3.0+dfsg1-1build2 @un puN Ib > 146s Broken python3-vtk9:ppc64el Depends on libopenmpi3t64:ppc64el < none @un pH > (>= 5.0.5) 146s Considering libopenmpi3t64:ppc64el 0 as a solution to python3-vtk9:ppc64el 1 146s Done 146s Some packages could not be installed. This may mean that you have 146s requested an impossible situation or if you are using the unstable 146s distribution that some required packages have not yet been created 146s or been moved out of Incoming. 146s The following information may help to resolve the situation: 146s 146s The following packages have unmet dependencies: 146s libvtk9.3 : Depends: libopenmpi3t64 (>= 5.0.5) but it is not installable 146s python3-vtk9 : Depends: libopenmpi3t64 (>= 5.0.5) but it is not installable 146s E: Unable to correct problems, you have held broken packages. 146s buildPNG FAIL badpkg 146s blame: vtk9 146s 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. 146s autopkgtest [09:18:11]: test buildVTP: preparing testbed 147s Reading package lists... 147s Building dependency tree... 147s Reading state information... 147s Starting pkgProblemResolver with broken count: 2 147s Starting 2 pkgProblemResolver with broken count: 2 147s Investigating (0) libvtk9.3:ppc64el < none -> 9.3.0+dfsg1-1build2 @un puN Ib > 147s Broken libvtk9.3:ppc64el Depends on libopenmpi3t64:ppc64el < none @un pH > (>= 5.0.5) 147s Considering libopenmpi3t64:ppc64el 0 as a solution to libvtk9.3:ppc64el 7 147s Investigating (0) python3-vtk9:ppc64el < none -> 9.3.0+dfsg1-1build2 @un puN Ib > 147s Broken python3-vtk9:ppc64el Depends on libopenmpi3t64:ppc64el < none @un pH > (>= 5.0.5) 147s Considering libopenmpi3t64:ppc64el 0 as a solution to python3-vtk9:ppc64el 1 147s Done 147s Some packages could not be installed. This may mean that you have 147s requested an impossible situation or if you are using the unstable 147s distribution that some required packages have not yet been created 147s or been moved out of Incoming. 147s The following information may help to resolve the situation: 147s 147s The following packages have unmet dependencies: 147s libvtk9.3 : Depends: libopenmpi3t64 (>= 5.0.5) but it is not installable 147s python3-vtk9 : Depends: libopenmpi3t64 (>= 5.0.5) but it is not installable 147s E: Unable to correct problems, you have held broken packages. 147s buildVTP FAIL badpkg 147s blame: vtk9 147s 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. 147s autopkgtest [09:18:12]: @@@@@@@@@@@@@@@@@@@@ summary 147s buildBoolean FAIL badpkg 147s blame: vtk9 147s 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. 147s buildPoint FAIL badpkg 147s blame: vtk9 147s 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. 147s buildVTU FAIL badpkg 147s blame: vtk9 147s 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. 147s buildDistance FAIL badpkg 147s blame: vtk9 147s 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. 147s buildPNG FAIL badpkg 147s blame: vtk9 147s 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. 147s buildVTP FAIL badpkg 147s blame: vtk9 147s 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. 152s nova [W] Using flock in prodstack6-ppc64el 152s Creating nova instance adt-plucky-ppc64el-vtk9-20241204-091545-juju-7f2275-prod-proposed-migration-environment-20-e7f6e279-f0c1-4d35-8233-7b90dcc37aac from image adt/ubuntu-plucky-ppc64el-server-20241203.img (UUID 71a10fe7-f168-4d19-8647-b89d09dd4cc0)...