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-15; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.z6q0z3ni/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-s390x --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-15@bos03-s390x-11.secgroup --name adt-plucky-s390x-vtk9-20241204-091545-juju-7f2275-prod-proposed-migration-environment-15-3f4bf7d0-34e2-495e-9134-a6532b328ef4 --image adt/ubuntu-plucky-s390x-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-15 --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/ 56s autopkgtest [09:16:41]: testbed dpkg architecture: s390x 56s autopkgtest [09:16:41]: testbed apt version: 2.9.16 57s autopkgtest [09:16:42]: @@@@@@@@@@@@@@@@@@@@ test bed setup 57s autopkgtest [09:16:42]: testbed release detected to be: None 58s autopkgtest [09:16:43]: updating testbed package index (apt update) 58s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB] 58s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 58s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 58s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 58s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [14.2 kB] 58s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [745 kB] 58s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B] 58s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [55.9 kB] 58s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main s390x Packages [103 kB] 58s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted s390x Packages [928 B] 58s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe s390x Packages [573 kB] 59s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse s390x Packages [7444 B] 59s Fetched 1584 kB in 1s (1817 kB/s) 59s Reading package lists... 60s Reading package lists... 60s Building dependency tree... 60s Reading state information... 60s Calculating upgrade... 60s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 60s Reading package lists... 60s Building dependency tree... 60s Reading state information... 60s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 60s autopkgtest [09:16:45]: upgrading testbed (apt dist-upgrade and autopurge) 61s Reading package lists... 61s Building dependency tree... 61s Reading state information... 61s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 61s Starting 2 pkgProblemResolver with broken count: 0 61s Done 61s Entering ResolveByKeep 61s 61s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 61s Reading package lists... 61s Building dependency tree... 61s Reading state information... 62s Starting pkgProblemResolver with broken count: 0 62s Starting 2 pkgProblemResolver with broken count: 0 62s Done 62s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 64s autopkgtest [09:16:49]: testbed running kernel: Linux 6.11.0-8-generic #8-Ubuntu SMP Mon Sep 16 12:49:35 UTC 2024 64s autopkgtest [09:16:49]: @@@@@@@@@@@@@@@@@@@@ apt-source vtk9 72s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed/universe vtk9 9.3.0+dfsg1-1.1build2 (dsc) [3746 B] 72s Get:2 http://ftpmaster.internal/ubuntu plucky-proposed/universe vtk9 9.3.0+dfsg1-1.1build2 (tar) [69.8 MB] 72s Get:3 http://ftpmaster.internal/ubuntu plucky-proposed/universe vtk9 9.3.0+dfsg1-1.1build2 (diff) [22.5 kB] 72s gpgv: Signature made Sun Dec 1 20:55:53 2024 UTC 72s gpgv: using RSA key 568BF22A66337CBFC9A6B9B72C83DBC8E9BD0E37 72s gpgv: Can't check signature: No public key 72s dpkg-source: warning: cannot verify inline signature for ./vtk9_9.3.0+dfsg1-1.1build2.dsc: no acceptable signature found 75s autopkgtest [09:17:00]: testing package vtk9 version 9.3.0+dfsg1-1.1build2 76s autopkgtest [09:17:01]: build not needed 85s autopkgtest [09:17:10]: test buildBoolean: preparing testbed 85s Reading package lists... 85s Building dependency tree... 85s Reading state information... 85s Starting pkgProblemResolver with broken count: 2 85s Starting 2 pkgProblemResolver with broken count: 2 85s Investigating (0) libvtk9.3:s390x < none -> 9.3.0+dfsg1-1build1 @un puN Ib > 85s Broken libvtk9.3:s390x Depends on libopenmpi3t64:s390x < none @un pH > (>= 4.1.6) 85s Considering libopenmpi3t64:s390x 0 as a solution to libvtk9.3:s390x 7 85s Considering libopenmpi3t64:s390x 0 as a solution to libvtk9.3:s390x 7 85s Investigating (0) python3-vtk9:s390x < none -> 9.3.0+dfsg1-1build1 @un puN Ib > 85s Broken python3-vtk9:s390x Depends on libopenmpi3t64:s390x < none @un pH > (>= 4.1.6) 85s Considering libopenmpi3t64:s390x 0 as a solution to python3-vtk9:s390x 1 85s Considering libopenmpi3t64:s390x 0 as a solution to python3-vtk9:s390x 1 85s Done 85s Some packages could not be installed. This may mean that you have 85s requested an impossible situation or if you are using the unstable 85s distribution that some required packages have not yet been created 85s or been moved out of Incoming. 85s The following information may help to resolve the situation: 85s 85s The following packages have unmet dependencies: 85s libvtk9.3 : Depends: libopenmpi3t64 (>= 4.1.6) but it is not installable 85s python3-vtk9 : Depends: libopenmpi3t64 (>= 4.1.6) but it is not installable 85s E: Unable to correct problems, you have held broken packages. 85s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed 86s Reading package lists... 86s Building dependency tree... 86s Reading state information... 86s Starting pkgProblemResolver with broken count: 2 86s Starting 2 pkgProblemResolver with broken count: 2 86s Investigating (0) libvtk9.3:s390x < none -> 9.3.0+dfsg1-1build1 @un puN Ib > 86s Broken libvtk9.3:s390x Depends on libopenmpi3t64:s390x < none @un pH > (>= 4.1.6) 86s Considering libopenmpi3t64:s390x 0 as a solution to libvtk9.3:s390x 7 86s Considering libopenmpi3t64:s390x 0 as a solution to libvtk9.3:s390x 7 86s Investigating (0) python3-vtk9:s390x < none -> 9.3.0+dfsg1-1build1 @un puN Ib > 86s Broken python3-vtk9:s390x Depends on libopenmpi3t64:s390x < none @un pH > (>= 4.1.6) 86s Considering libopenmpi3t64:s390x 0 as a solution to python3-vtk9:s390x 1 86s Considering libopenmpi3t64:s390x 0 as a solution to python3-vtk9:s390x 1 86s Done 86s Some packages could not be installed. This may mean that you have 86s requested an impossible situation or if you are using the unstable 86s distribution that some required packages have not yet been created 86s or been moved out of Incoming. 86s The following information may help to resolve the situation: 86s 86s The following packages have unmet dependencies: 86s libvtk9.3 : Depends: libopenmpi3t64 (>= 4.1.6) but it is not installable 86s python3-vtk9 : Depends: libopenmpi3t64 (>= 4.1.6) but it is not installable 86s E: Unable to correct problems, you have held broken packages. 86s buildBoolean FAIL badpkg 86s blame: vtk9 86s 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. 86s autopkgtest [09:17:11]: test buildPoint: preparing testbed 86s Reading package lists... 86s Building dependency tree... 86s Reading state information... 86s Starting pkgProblemResolver with broken count: 2 86s Starting 2 pkgProblemResolver with broken count: 2 86s Investigating (0) libvtk9.3:s390x < none -> 9.3.0+dfsg1-1build1 @un puN Ib > 86s Broken libvtk9.3:s390x Depends on libopenmpi3t64:s390x < none @un pH > (>= 4.1.6) 86s Considering libopenmpi3t64:s390x 0 as a solution to libvtk9.3:s390x 7 86s Considering libopenmpi3t64:s390x 0 as a solution to libvtk9.3:s390x 7 86s Investigating (0) python3-vtk9:s390x < none -> 9.3.0+dfsg1-1build1 @un puN Ib > 86s Broken python3-vtk9:s390x Depends on libopenmpi3t64:s390x < none @un pH > (>= 4.1.6) 86s Considering libopenmpi3t64:s390x 0 as a solution to python3-vtk9:s390x 1 86s Considering libopenmpi3t64:s390x 0 as a solution to python3-vtk9:s390x 1 86s Done 86s Some packages could not be installed. This may mean that you have 86s requested an impossible situation or if you are using the unstable 86s distribution that some required packages have not yet been created 86s or been moved out of Incoming. 86s The following information may help to resolve the situation: 86s 86s The following packages have unmet dependencies: 87s libvtk9.3 : Depends: libopenmpi3t64 (>= 4.1.6) but it is not installable 87s python3-vtk9 : Depends: libopenmpi3t64 (>= 4.1.6) but it is not installable 87s E: Unable to correct problems, you have held broken packages. 87s buildPoint FAIL badpkg 87s blame: vtk9 87s 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. 87s autopkgtest [09:17:12]: test buildVTU: preparing testbed 87s Reading package lists... 87s Building dependency tree... 87s Reading state information... 87s Starting pkgProblemResolver with broken count: 2 87s Starting 2 pkgProblemResolver with broken count: 2 87s Investigating (0) libvtk9.3:s390x < none -> 9.3.0+dfsg1-1build1 @un puN Ib > 87s Broken libvtk9.3:s390x Depends on libopenmpi3t64:s390x < none @un pH > (>= 4.1.6) 87s Considering libopenmpi3t64:s390x 0 as a solution to libvtk9.3:s390x 7 87s Considering libopenmpi3t64:s390x 0 as a solution to libvtk9.3:s390x 7 87s Investigating (0) python3-vtk9:s390x < none -> 9.3.0+dfsg1-1build1 @un puN Ib > 87s Broken python3-vtk9:s390x Depends on libopenmpi3t64:s390x < none @un pH > (>= 4.1.6) 87s Considering libopenmpi3t64:s390x 0 as a solution to python3-vtk9:s390x 1 87s Considering libopenmpi3t64:s390x 0 as a solution to python3-vtk9:s390x 1 87s Done 87s Some packages could not be installed. This may mean that you have 87s requested an impossible situation or if you are using the unstable 87s distribution that some required packages have not yet been created 87s or been moved out of Incoming. 87s The following information may help to resolve the situation: 87s 87s The following packages have unmet dependencies: 87s libvtk9.3 : Depends: libopenmpi3t64 (>= 4.1.6) but it is not installable 87s python3-vtk9 : Depends: libopenmpi3t64 (>= 4.1.6) but it is not installable 87s E: Unable to correct problems, you have held broken packages. 87s buildVTU FAIL badpkg 87s blame: vtk9 87s 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. 87s autopkgtest [09:17:12]: test buildDistance: preparing testbed 87s Reading package lists... 87s Building dependency tree... 87s Reading state information... 88s Starting pkgProblemResolver with broken count: 2 88s Starting 2 pkgProblemResolver with broken count: 2 88s Investigating (0) libvtk9.3:s390x < none -> 9.3.0+dfsg1-1build1 @un puN Ib > 88s Broken libvtk9.3:s390x Depends on libopenmpi3t64:s390x < none @un pH > (>= 4.1.6) 88s Considering libopenmpi3t64:s390x 0 as a solution to libvtk9.3:s390x 7 88s Considering libopenmpi3t64:s390x 0 as a solution to libvtk9.3:s390x 7 88s Investigating (0) python3-vtk9:s390x < none -> 9.3.0+dfsg1-1build1 @un puN Ib > 88s Broken python3-vtk9:s390x Depends on libopenmpi3t64:s390x < none @un pH > (>= 4.1.6) 88s Considering libopenmpi3t64:s390x 0 as a solution to python3-vtk9:s390x 1 88s Considering libopenmpi3t64:s390x 0 as a solution to python3-vtk9:s390x 1 88s Done 88s Some packages could not be installed. This may mean that you have 88s requested an impossible situation or if you are using the unstable 88s distribution that some required packages have not yet been created 88s or been moved out of Incoming. 88s The following information may help to resolve the situation: 88s 88s The following packages have unmet dependencies: 88s libvtk9.3 : Depends: libopenmpi3t64 (>= 4.1.6) but it is not installable 88s python3-vtk9 : Depends: libopenmpi3t64 (>= 4.1.6) but it is not installable 88s E: Unable to correct problems, you have held broken packages. 88s buildDistance FAIL badpkg 88s blame: vtk9 88s 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. 88s autopkgtest [09:17:13]: test buildPNG: preparing testbed 88s Reading package lists... 88s Building dependency tree... 88s Reading state information... 88s Starting pkgProblemResolver with broken count: 2 88s Starting 2 pkgProblemResolver with broken count: 2 88s Investigating (0) libvtk9.3:s390x < none -> 9.3.0+dfsg1-1build1 @un puN Ib > 88s Broken libvtk9.3:s390x Depends on libopenmpi3t64:s390x < none @un pH > (>= 4.1.6) 88s Considering libopenmpi3t64:s390x 0 as a solution to libvtk9.3:s390x 7 88s Considering libopenmpi3t64:s390x 0 as a solution to libvtk9.3:s390x 7 88s Investigating (0) python3-vtk9:s390x < none -> 9.3.0+dfsg1-1build1 @un puN Ib > 88s Broken python3-vtk9:s390x Depends on libopenmpi3t64:s390x < none @un pH > (>= 4.1.6) 88s Considering libopenmpi3t64:s390x 0 as a solution to python3-vtk9:s390x 1 88s Considering libopenmpi3t64:s390x 0 as a solution to python3-vtk9:s390x 1 88s Done 88s Some packages could not be installed. This may mean that you have 88s requested an impossible situation or if you are using the unstable 88s distribution that some required packages have not yet been created 88s or been moved out of Incoming. 88s The following information may help to resolve the situation: 88s 88s The following packages have unmet dependencies: 88s libvtk9.3 : Depends: libopenmpi3t64 (>= 4.1.6) but it is not installable 88s python3-vtk9 : Depends: libopenmpi3t64 (>= 4.1.6) but it is not installable 88s E: Unable to correct problems, you have held broken packages. 88s buildPNG FAIL badpkg 88s blame: vtk9 88s 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. 88s autopkgtest [09:17:13]: test buildVTP: preparing testbed 89s Reading package lists... 89s Building dependency tree... 89s Reading state information... 89s Starting pkgProblemResolver with broken count: 2 89s Starting 2 pkgProblemResolver with broken count: 2 89s Investigating (0) libvtk9.3:s390x < none -> 9.3.0+dfsg1-1build1 @un puN Ib > 89s Broken libvtk9.3:s390x Depends on libopenmpi3t64:s390x < none @un pH > (>= 4.1.6) 89s Considering libopenmpi3t64:s390x 0 as a solution to libvtk9.3:s390x 7 89s Considering libopenmpi3t64:s390x 0 as a solution to libvtk9.3:s390x 7 89s Investigating (0) python3-vtk9:s390x < none -> 9.3.0+dfsg1-1build1 @un puN Ib > 89s Broken python3-vtk9:s390x Depends on libopenmpi3t64:s390x < none @un pH > (>= 4.1.6) 89s Considering libopenmpi3t64:s390x 0 as a solution to python3-vtk9:s390x 1 89s Considering libopenmpi3t64:s390x 0 as a solution to python3-vtk9:s390x 1 89s Done 89s Some packages could not be installed. This may mean that you have 89s requested an impossible situation or if you are using the unstable 89s distribution that some required packages have not yet been created 89s or been moved out of Incoming. 89s The following information may help to resolve the situation: 89s 89s The following packages have unmet dependencies: 89s libvtk9.3 : Depends: libopenmpi3t64 (>= 4.1.6) but it is not installable 89s python3-vtk9 : Depends: libopenmpi3t64 (>= 4.1.6) but it is not installable 89s E: Unable to correct problems, you have held broken packages. 89s buildVTP FAIL badpkg 89s blame: vtk9 89s 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. 89s autopkgtest [09:17:14]: @@@@@@@@@@@@@@@@@@@@ summary 89s buildBoolean FAIL badpkg 89s blame: vtk9 89s 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. 89s buildPoint FAIL badpkg 89s blame: vtk9 89s 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. 89s buildVTU FAIL badpkg 89s blame: vtk9 89s 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. 89s buildDistance FAIL badpkg 89s blame: vtk9 89s 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. 89s buildPNG FAIL badpkg 89s blame: vtk9 89s 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. 89s buildVTP FAIL badpkg 89s blame: vtk9 89s 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. 100s nova [W] Using flock in prodstack6-s390x 100s Creating nova instance adt-plucky-s390x-vtk9-20241204-091545-juju-7f2275-prod-proposed-migration-environment-15-3f4bf7d0-34e2-495e-9134-a6532b328ef4 from image adt/ubuntu-plucky-s390x-server-20241204.img (UUID 89b4900b-e439-4dd9-be41-eb47bd412513)...