0s autopkgtest [04:31:56]: starting date and time: 2026-01-24 04:31:56+0000 0s autopkgtest [04:31:56]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [04:31:56]: host juju-7f2275-prod-proposed-migration-environment-2; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.tfokbfzv/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:python3-defaults --apt-upgrade vtk9 --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 --env=ADT_TEST_TRIGGERS=python3-defaults/3.14.2-1 -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest-cpu2-ram4-disk20-s390x --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-2@sto01-s390x-1.secgroup --name adt-resolute-s390x-vtk9-20260124-043156-juju-7f2275-prod-proposed-migration-environment-2-e35b351f-97fd-4323-b778-7fb5dbc3b393 --image adt/ubuntu-resolute-s390x-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-2 --net-id=net_prod-autopkgtest-workers-s390x -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 4s Creating nova instance adt-resolute-s390x-vtk9-20260124-043156-juju-7f2275-prod-proposed-migration-environment-2-e35b351f-97fd-4323-b778-7fb5dbc3b393 from image adt/ubuntu-resolute-s390x-server-20260124.img (UUID cb5f7561-b2f6-4cdf-8333-83c53514cd6a)... 64s autopkgtest [04:33:00]: testbed dpkg architecture: s390x 65s autopkgtest [04:33:01]: testbed apt version: 3.1.13 65s autopkgtest [04:33:01]: @@@@@@@@@@@@@@@@@@@@ test bed setup 65s autopkgtest [04:33:01]: testbed release detected to be: None 66s autopkgtest [04:33:02]: updating testbed package index (apt update) 67s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 67s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 67s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 67s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 67s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [2820 B] 67s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [1058 kB] 67s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [24.3 kB] 67s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [94.5 kB] 67s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main s390x Packages [102 kB] 67s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/universe s390x Packages [859 kB] 67s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse s390x Packages [9916 B] 67s Fetched 2274 kB in 1s (2347 kB/s) 70s Reading package lists... 72s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 72s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 72s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 72s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 75s Reading package lists... 75s Reading package lists... 76s Building dependency tree... 76s Reading state information... 76s Calculating upgrade... 77s The following packages were automatically installed and are no longer required: 77s python3.13 python3.13-minimal 77s Use 'sudo apt autoremove' to remove them. 77s The following NEW packages will be installed: 77s libpython3.14-minimal libpython3.14-stdlib python3.14 python3.14-minimal 77s The following packages will be upgraded: 77s cloud-initramfs-copymods cloud-initramfs-dyn-netconf libgpg-error-l10n 77s libgpg-error0 liblzo2-2 libpython3-stdlib python3 python3-gdbm 77s python3-minimal 77s 9 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. 77s Need to get 6860 kB of archives. 77s After this operation, 24.3 MB of additional disk space will be used. 77s Get:1 http://ftpmaster.internal/ubuntu resolute/main s390x libpython3.14-minimal s390x 3.14.2-1 [917 kB] 77s Get:2 http://ftpmaster.internal/ubuntu resolute/main s390x python3.14-minimal s390x 3.14.2-1 [2510 kB] 77s Get:3 http://ftpmaster.internal/ubuntu resolute-proposed/main s390x python3-minimal s390x 3.14.2-1 [28.2 kB] 77s Get:4 http://ftpmaster.internal/ubuntu resolute-proposed/main s390x python3 s390x 3.14.2-1 [22.9 kB] 77s Get:5 http://ftpmaster.internal/ubuntu resolute/main s390x libpython3.14-stdlib s390x 3.14.2-1 [2373 kB] 78s Get:6 http://ftpmaster.internal/ubuntu resolute/main s390x python3.14 s390x 3.14.2-1 [816 kB] 78s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/main s390x libpython3-stdlib s390x 3.14.2-1 [10.9 kB] 78s Get:8 http://ftpmaster.internal/ubuntu resolute/main s390x libgpg-error-l10n all 1.58-1build1 [9192 B] 78s Get:9 http://ftpmaster.internal/ubuntu resolute/main s390x libgpg-error0 s390x 1.58-1build1 [88.1 kB] 78s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/main s390x python3-gdbm s390x 3.14.2-1 [11.1 kB] 78s Get:11 http://ftpmaster.internal/ubuntu resolute/main s390x liblzo2-2 s390x 2.10-3build2 [62.8 kB] 78s Get:12 http://ftpmaster.internal/ubuntu resolute/main s390x cloud-initramfs-copymods all 0.50 [4528 B] 78s Get:13 http://ftpmaster.internal/ubuntu resolute/main s390x cloud-initramfs-dyn-netconf all 0.50 [6514 B] 79s dpkg-preconfigure: unable to re-open stdin: No such file or directory 79s Fetched 6860 kB in 0s (20.0 MB/s) 79s Selecting previously unselected package libpython3.14-minimal:s390x. 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 ... 87682 files and directories currently installed.) 81s Preparing to unpack .../libpython3.14-minimal_3.14.2-1_s390x.deb ... 81s Unpacking libpython3.14-minimal:s390x (3.14.2-1) ... 81s Selecting previously unselected package python3.14-minimal. 81s Preparing to unpack .../python3.14-minimal_3.14.2-1_s390x.deb ... 81s Unpacking python3.14-minimal (3.14.2-1) ... 82s Setting up libpython3.14-minimal:s390x (3.14.2-1) ... 82s Setting up python3.14-minimal (3.14.2-1) ... 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 ... 88024 files and directories currently installed.) 86s Preparing to unpack .../python3-minimal_3.14.2-1_s390x.deb ... 86s Unpacking python3-minimal (3.14.2-1) over (3.13.9-3) ... 86s Setting up python3-minimal (3.14.2-1) ... 87s (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 ... 88024 files and directories currently installed.) 87s Preparing to unpack .../0-python3_3.14.2-1_s390x.deb ... 87s running python pre-rtupdate hooks for python3.14... 87s Unpacking python3 (3.14.2-1) over (3.13.9-3) ... 88s Selecting previously unselected package libpython3.14-stdlib:s390x. 88s Preparing to unpack .../1-libpython3.14-stdlib_3.14.2-1_s390x.deb ... 88s Unpacking libpython3.14-stdlib:s390x (3.14.2-1) ... 88s Selecting previously unselected package python3.14. 88s Preparing to unpack .../2-python3.14_3.14.2-1_s390x.deb ... 88s Unpacking python3.14 (3.14.2-1) ... 88s Preparing to unpack .../3-libpython3-stdlib_3.14.2-1_s390x.deb ... 88s Unpacking libpython3-stdlib:s390x (3.14.2-1) over (3.13.9-3) ... 88s Preparing to unpack .../4-libgpg-error-l10n_1.58-1build1_all.deb ... 88s Unpacking libgpg-error-l10n (1.58-1build1) over (1.58-1) ... 88s Preparing to unpack .../5-libgpg-error0_1.58-1build1_s390x.deb ... 88s Unpacking libgpg-error0:s390x (1.58-1build1) over (1.58-1) ... 88s Preparing to unpack .../6-python3-gdbm_3.14.2-1_s390x.deb ... 88s Unpacking python3-gdbm (3.14.2-1) over (3.13.9-3) ... 88s Preparing to unpack .../7-liblzo2-2_2.10-3build2_s390x.deb ... 88s Unpacking liblzo2-2:s390x (2.10-3build2) over (2.10-3build1) ... 88s Preparing to unpack .../8-cloud-initramfs-copymods_0.50_all.deb ... 88s Unpacking cloud-initramfs-copymods (0.50) over (0.49build1) ... 88s Preparing to unpack .../9-cloud-initramfs-dyn-netconf_0.50_all.deb ... 88s Unpacking cloud-initramfs-dyn-netconf (0.50) over (0.49build1) ... 88s Setting up libgpg-error0:s390x (1.58-1build1) ... 88s Setting up libpython3.14-stdlib:s390x (3.14.2-1) ... 88s Setting up liblzo2-2:s390x (2.10-3build2) ... 88s Setting up cloud-initramfs-copymods (0.50) ... 88s Setting up cloud-initramfs-dyn-netconf (0.50) ... 88s Setting up python3.14 (3.14.2-1) ... 92s Setting up libgpg-error-l10n (1.58-1build1) ... 92s Setting up libpython3-stdlib:s390x (3.14.2-1) ... 92s Setting up python3-gdbm (3.14.2-1) ... 93s Setting up python3 (3.14.2-1) ... 93s running python rtupdate hooks for python3.14... 93s running python post-rtupdate hooks for python3.14... 93s Processing triggers for man-db (2.13.1-1) ... 98s Processing triggers for initramfs-tools (0.150ubuntu7) ... 98s update-initramfs: Generating /boot/initrd.img-6.18.0-9-generic 114s Using config file '/etc/zipl.conf' 114s Building bootmap in '/boot' 114s Adding IPL section 'ubuntu' (default) 114s Preparing boot device: vda. 114s Done. 114s Processing triggers for libc-bin (2.42-2ubuntu4) ... 114s Processing triggers for systemd (259-1ubuntu2) ... 116s autopkgtest [04:33:52]: upgrading testbed (apt dist-upgrade and autopurge) 116s Reading package lists... 117s Building dependency tree... 117s Reading state information... 117s Calculating upgrade... 117s The following packages were automatically installed and are no longer required: 117s python3.13 python3.13-minimal 117s Use 'sudo apt autoremove' to remove them. 117s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 117s Reading package lists... 118s Building dependency tree... 118s Reading state information... 119s Solving dependencies... 120s The following packages will be REMOVED: 120s python3.13* python3.13-minimal* 121s 0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded. 121s After this operation, 8012 kB disk space will be freed. 121s (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 ... 88458 files and directories currently installed.) 121s Removing python3.13 (3.13.11-1) ... 121s Removing python3.13-minimal (3.13.11-1) ... 124s Processing triggers for man-db (2.13.1-1) ... 126s Processing triggers for systemd (259-1ubuntu2) ... 126s (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 ... 88431 files and directories currently installed.) 126s Purging configuration files for python3.13-minimal (3.13.11-1) ... 127s autopkgtest [04:34:03]: rebooting testbed after setup commands that affected boot 171s autopkgtest [04:34:47]: testbed running kernel: Linux 6.18.0-9-generic #9-Ubuntu SMP Mon Jan 12 15:39:23 UTC 2026 174s autopkgtest [04:34:50]: @@@@@@@@@@@@@@@@@@@@ apt-source vtk9 183s Get:1 http://ftpmaster.internal/ubuntu resolute/universe vtk9 9.5.2+dfsg2-4ubuntu1 (dsc) [3764 B] 183s Get:2 http://ftpmaster.internal/ubuntu resolute/universe vtk9 9.5.2+dfsg2-4ubuntu1 (tar) [25.0 MB] 183s Get:3 http://ftpmaster.internal/ubuntu resolute/universe vtk9 9.5.2+dfsg2-4ubuntu1 (diff) [22.4 kB] 184s gpgv: Signature made Sun Dec 14 11:14:16 2025 UTC 184s gpgv: using RSA key B8340990283D8D9BC1949AC74799A35146D12B35 184s gpgv: issuer "sudipm.mukherjee@gmail.com" 184s gpgv: Can't check signature: No public key 184s dpkg-source: warning: cannot verify inline signature for ./vtk9_9.5.2+dfsg2-4ubuntu1.dsc: no acceptable signature found 190s autopkgtest [04:35:06]: testing package vtk9 version 9.5.2+dfsg2-4ubuntu1 191s autopkgtest [04:35:07]: build not needed 202s autopkgtest [04:35:18]: test buildBoolean: preparing testbed 202s Reading package lists... 203s Building dependency tree... 203s Reading state information... 203s Solving dependencies... 203s Some packages could not be installed. This may mean that you have 203s requested an impossible situation or if you are using the unstable 203s distribution that some required packages have not yet been created 203s or been moved out of Incoming. 203s The following information may help to resolve the situation: 203s 203s The following packages have unmet dependencies: 203s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 203s Depends: libvtk9-qt-dev but it is not going to be installed 203s Depends: build-essential but it is not going to be installed 203s Depends: cmake but it is not going to be installed 203s E: Unable to satisfy dependencies. Reached two conflicting assignments: 203s 1. python3:s390x=3.13.9-3 is not selected for install 203s 2. python3:s390x=3.13.9-3 is selected as a downgrade because: 203s 1. satisfy:command-line:s390x=1 is selected for install 203s 2. satisfy:command-line:s390x Depends libvtk9-dev 203s 3. libvtk9-dev:s390x Depends python3-vtk9 (= 9.5.2+dfsg2-4ubuntu1) 203s 4. python3-vtk9:s390x Depends python3 (< 3.14) 203s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 204s Reading package lists... 205s Building dependency tree... 205s Reading state information... 205s Solving dependencies... 205s Some packages could not be installed. This may mean that you have 205s requested an impossible situation or if you are using the unstable 205s distribution that some required packages have not yet been created 205s or been moved out of Incoming. 205s The following information may help to resolve the situation: 205s 205s The following packages have unmet dependencies: 206s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 206s Depends: libvtk9-qt-dev but it is not going to be installed 206s Depends: build-essential but it is not going to be installed 206s Depends: cmake but it is not going to be installed 206s E: Unable to satisfy dependencies. Reached two conflicting assignments: 206s 1. python3:s390x=3.13.9-3 is not selected for install 206s 2. python3:s390x=3.13.9-3 is selected as a downgrade because: 206s 1. satisfy:command-line:s390x=1 is selected for install 206s 2. satisfy:command-line:s390x Depends libvtk9-dev 206s 3. libvtk9-dev:s390x Depends python3-vtk9 (= 9.5.2+dfsg2-4ubuntu1) 206s 4. python3-vtk9:s390x Depends python3 (< 3.14) 206s autopkgtest [04:35:22]: test buildPoint: preparing testbed 206s buildBoolean FAIL badpkg 206s blame: vtk9 206s 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. 206s Reading package lists... 206s Building dependency tree... 206s Reading state information... 206s Solving dependencies... 206s Some packages could not be installed. This may mean that you have 206s requested an impossible situation or if you are using the unstable 206s distribution that some required packages have not yet been created 206s or been moved out of Incoming. 206s The following information may help to resolve the situation: 206s 206s The following packages have unmet dependencies: 206s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 206s Depends: libvtk9-qt-dev but it is not going to be installed 206s Depends: build-essential but it is not going to be installed 206s Depends: cmake but it is not going to be installed 206s E: Unable to satisfy dependencies. Reached two conflicting assignments: 206s 1. python3:s390x=3.13.9-3 is not selected for install 206s 2. python3:s390x=3.13.9-3 is selected as a downgrade because: 206s 1. satisfy:command-line:s390x=1 is selected for install 206s 2. satisfy:command-line:s390x Depends libvtk9-dev 206s 3. libvtk9-dev:s390x Depends python3-vtk9 (= 9.5.2+dfsg2-4ubuntu1) 206s 4. python3-vtk9:s390x Depends python3 (< 3.14) 206s buildPoint FAIL badpkg 206s blame: vtk9 206s 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. 206s autopkgtest [04:35:22]: test buildVTU: preparing testbed 206s Reading package lists... 207s Building dependency tree... 207s Reading state information... 207s Solving dependencies... 207s Some packages could not be installed. This may mean that you have 207s requested an impossible situation or if you are using the unstable 207s distribution that some required packages have not yet been created 207s or been moved out of Incoming. 207s The following information may help to resolve the situation: 207s 207s The following packages have unmet dependencies: 207s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 207s Depends: libvtk9-qt-dev but it is not going to be installed 207s Depends: build-essential but it is not going to be installed 207s Depends: cmake but it is not going to be installed 207s E: Unable to satisfy dependencies. Reached two conflicting assignments: 207s 1. python3:s390x=3.13.9-3 is not selected for install 207s 2. python3:s390x=3.13.9-3 is selected as a downgrade because: 207s 1. satisfy:command-line:s390x=1 is selected for install 207s 2. satisfy:command-line:s390x Depends libvtk9-dev 207s 3. libvtk9-dev:s390x Depends python3-vtk9 (= 9.5.2+dfsg2-4ubuntu1) 207s 4. python3-vtk9:s390x Depends python3 (< 3.14) 207s buildVTU FAIL badpkg 207s blame: vtk9 207s 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. 207s autopkgtest [04:35:23]: test buildDistance: preparing testbed 207s Reading package lists... 207s Building dependency tree... 207s Reading state information... 207s Solving dependencies... 207s Some packages could not be installed. This may mean that you have 207s requested an impossible situation or if you are using the unstable 207s distribution that some required packages have not yet been created 207s or been moved out of Incoming. 207s The following information may help to resolve the situation: 207s 207s The following packages have unmet dependencies: 208s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 208s Depends: libvtk9-qt-dev but it is not going to be installed 208s Depends: build-essential but it is not going to be installed 208s Depends: cmake but it is not going to be installed 208s E: Unable to satisfy dependencies. Reached two conflicting assignments: 208s 1. python3:s390x=3.13.9-3 is not selected for install 208s 2. python3:s390x=3.13.9-3 is selected as a downgrade because: 208s 1. satisfy:command-line:s390x=1 is selected for install 208s 2. satisfy:command-line:s390x Depends libvtk9-dev 208s 3. libvtk9-dev:s390x Depends python3-vtk9 (= 9.5.2+dfsg2-4ubuntu1) 208s 4. python3-vtk9:s390x Depends python3 (< 3.14) 208s autopkgtest [04:35:24]: test buildPNG: preparing testbed 208s buildDistance FAIL badpkg 208s blame: vtk9 208s 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. 208s Reading package lists... 209s Building dependency tree... 209s Reading state information... 209s Solving dependencies... 209s Some packages could not be installed. This may mean that you have 209s requested an impossible situation or if you are using the unstable 209s distribution that some required packages have not yet been created 209s or been moved out of Incoming. 209s The following information may help to resolve the situation: 209s 209s The following packages have unmet dependencies: 209s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 209s Depends: libvtk9-qt-dev but it is not going to be installed 209s Depends: build-essential but it is not going to be installed 209s Depends: cmake but it is not going to be installed 209s E: Unable to satisfy dependencies. Reached two conflicting assignments: 209s 1. python3:s390x=3.13.9-3 is not selected for install 209s 2. python3:s390x=3.13.9-3 is selected as a downgrade because: 209s 1. satisfy:command-line:s390x=1 is selected for install 209s 2. satisfy:command-line:s390x Depends libvtk9-dev 209s 3. libvtk9-dev:s390x Depends python3-vtk9 (= 9.5.2+dfsg2-4ubuntu1) 209s 4. python3-vtk9:s390x Depends python3 (< 3.14) 209s buildPNG FAIL badpkg 209s blame: vtk9 209s 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. 209s autopkgtest [04:35:25]: test buildVTP: preparing testbed 209s Reading package lists... 210s Building dependency tree... 210s Reading state information... 210s Solving dependencies... 210s Some packages could not be installed. This may mean that you have 210s requested an impossible situation or if you are using the unstable 210s distribution that some required packages have not yet been created 210s or been moved out of Incoming. 210s The following information may help to resolve the situation: 210s 210s The following packages have unmet dependencies: 210s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 210s Depends: libvtk9-qt-dev but it is not going to be installed 210s Depends: build-essential but it is not going to be installed 210s Depends: cmake but it is not going to be installed 210s E: Unable to satisfy dependencies. Reached two conflicting assignments: 210s 1. python3:s390x=3.13.9-3 is not selected for install 210s 2. python3:s390x=3.13.9-3 is selected as a downgrade because: 210s 1. satisfy:command-line:s390x=1 is selected for install 210s 2. satisfy:command-line:s390x Depends libvtk9-dev 210s 3. libvtk9-dev:s390x Depends python3-vtk9 (= 9.5.2+dfsg2-4ubuntu1) 210s 4. python3-vtk9:s390x Depends python3 (< 3.14) 210s buildVTP FAIL badpkg 210s blame: vtk9 210s 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. 210s autopkgtest [04:35:26]: @@@@@@@@@@@@@@@@@@@@ summary 210s buildBoolean FAIL badpkg 210s blame: vtk9 210s 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. 210s buildPoint FAIL badpkg 210s blame: vtk9 210s 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. 210s buildVTU FAIL badpkg 210s blame: vtk9 210s 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. 210s buildDistance FAIL badpkg 210s blame: vtk9 210s 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. 210s buildPNG FAIL badpkg 210s blame: vtk9 210s 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. 210s buildVTP FAIL badpkg 210s blame: vtk9 210s 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. 212s retry: sh returned 1, backing off for 15 seconds and trying again... 228s retry: sh returned 1, backing off for 15 seconds and trying again... 244s retry: sh returned 1, backing off for 15 seconds and trying again... 260s retry: sh returned 1, backing off for 15 seconds and trying again... 275s nova [E] Failed to issue delete command for server dce9c546-f929-47e2-83fb-9ca7b0f7adfd