0s autopkgtest [19:17:05]: starting date and time: 2026-01-24 19:17:05+0000 0s autopkgtest [19:17:05]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [19:17:05]: host juju-7f2275-prod-proposed-migration-environment-20; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.nut0_0qk/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:zlib --apt-upgrade vtk9 --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 --env=ADT_TEST_TRIGGERS=zlib/1:1.3.dfsg+really1.3.1-1ubuntu3 -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest-cpu2-ram4-disk20-ppc64el --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-20@sto01-ppc64el-11.secgroup --name adt-resolute-ppc64el-vtk9-20260124-191705-juju-7f2275-prod-proposed-migration-environment-20-1d97ad4a-279e-4c42-9e70-871035f3d9af --image adt/ubuntu-resolute-ppc64el-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-20 --net-id=net_prod-autopkgtest-workers-ppc64el -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 3s Creating nova instance adt-resolute-ppc64el-vtk9-20260124-191705-juju-7f2275-prod-proposed-migration-environment-20-1d97ad4a-279e-4c42-9e70-871035f3d9af from image adt/ubuntu-resolute-ppc64el-server-20260124.img (UUID a269ca64-3301-4299-8bab-2247218fc911)... 53s autopkgtest [19:17:58]: testbed dpkg architecture: ppc64el 53s autopkgtest [19:17:58]: testbed apt version: 3.1.13 54s autopkgtest [19:17:59]: @@@@@@@@@@@@@@@@@@@@ test bed setup 54s autopkgtest [19:17:59]: testbed release detected to be: None 55s autopkgtest [19:18:00]: updating testbed package index (apt update) 55s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 55s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 55s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 55s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 55s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [95.5 kB] 55s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [2820 B] 55s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [976 kB] 55s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [24.3 kB] 55s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el Packages [107 kB] 55s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/universe ppc64el Packages [806 kB] 55s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse ppc64el Packages [9920 B] 55s Fetched 2145 kB in 1s (4099 kB/s) 56s Reading package lists... 57s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 57s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 57s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 57s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 58s Reading package lists... 58s Reading package lists... 58s Building dependency tree... 58s Reading state information... 58s Calculating upgrade... 58s The following packages will be upgraded: 58s zlib1g 58s 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 58s Need to get 74.6 kB of archives. 58s After this operation, 0 B of additional disk space will be used. 58s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el zlib1g ppc64el 1:1.3.dfsg+really1.3.1-1ubuntu3 [74.6 kB] 59s dpkg-preconfigure: unable to re-open stdin: No such file or directory 59s Fetched 74.6 kB in 0s (4128 kB/s) 59s (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 ... 120851 files and directories currently installed.) 59s Preparing to unpack .../zlib1g_1%3a1.3.dfsg+really1.3.1-1ubuntu3_ppc64el.deb ... 59s Unpacking zlib1g:ppc64el (1:1.3.dfsg+really1.3.1-1ubuntu3) over (1:1.3.dfsg+really1.3.1-1ubuntu2) ... 59s Setting up zlib1g:ppc64el (1:1.3.dfsg+really1.3.1-1ubuntu3) ... 59s Processing triggers for libc-bin (2.42-2ubuntu4) ... 60s autopkgtest [19:18:05]: upgrading testbed (apt dist-upgrade and autopurge) 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 Solving dependencies... 60s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 63s autopkgtest [19:18:08]: testbed running kernel: Linux 6.18.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 12 16:45:54 UTC 2026 63s autopkgtest [19:18:08]: @@@@@@@@@@@@@@@@@@@@ apt-source vtk9 68s Get:1 http://ftpmaster.internal/ubuntu resolute/universe vtk9 9.5.2+dfsg2-4ubuntu1 (dsc) [3764 B] 68s Get:2 http://ftpmaster.internal/ubuntu resolute/universe vtk9 9.5.2+dfsg2-4ubuntu1 (tar) [25.0 MB] 68s Get:3 http://ftpmaster.internal/ubuntu resolute/universe vtk9 9.5.2+dfsg2-4ubuntu1 (diff) [22.4 kB] 69s gpgv: Signature made Sun Dec 14 11:14:16 2025 UTC 69s gpgv: using RSA key B8340990283D8D9BC1949AC74799A35146D12B35 69s gpgv: issuer "sudipm.mukherjee@gmail.com" 69s gpgv: Can't check signature: No public key 69s dpkg-source: warning: cannot verify inline signature for ./vtk9_9.5.2+dfsg2-4ubuntu1.dsc: no acceptable signature found 72s autopkgtest [19:18:17]: testing package vtk9 version 9.5.2+dfsg2-4ubuntu1 72s autopkgtest [19:18:17]: build not needed 79s autopkgtest [19:18:24]: test buildBoolean: preparing testbed 79s Reading package lists... 79s Building dependency tree... 79s Reading state information... 79s Solving dependencies... 79s Some packages could not be installed. This may mean that you have 79s requested an impossible situation or if you are using the unstable 79s distribution that some required packages have not yet been created 79s or been moved out of Incoming. 79s The following information may help to resolve the situation: 79s 79s The following packages have unmet dependencies: 79s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 79s Depends: libvtk9-qt-dev but it is not going to be installed 79s Depends: build-essential but it is not going to be installed 79s Depends: cmake but it is not going to be installed 79s E: Unable to satisfy dependencies. Reached two conflicting assignments: 79s 1. libvtk9-dev:ppc64el is selected for install because: 79s 1. satisfy:command-line:ppc64el=1 is selected for install 79s 2. satisfy:command-line:ppc64el Depends libvtk9-dev 79s 2. libvtk9-dev:ppc64el Depends libexpat-dev 79s but none of the choices are installable: 79s - libexpat1-dev:ppc64el=2.7.3-1 is not selected for install 79s - libexpat1-dev:ppc64el=2.7.3-2 is not selected for install 79s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 79s Reading package lists... 80s Building dependency tree... 80s Reading state information... 80s Solving dependencies... 80s Some packages could not be installed. This may mean that you have 80s requested an impossible situation or if you are using the unstable 80s distribution that some required packages have not yet been created 80s or been moved out of Incoming. 80s The following information may help to resolve the situation: 80s 80s The following packages have unmet dependencies: 80s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 80s Depends: libvtk9-qt-dev but it is not going to be installed 80s Depends: build-essential but it is not going to be installed 80s Depends: cmake but it is not going to be installed 80s E: Unable to satisfy dependencies. Reached two conflicting assignments: 80s 1. zlib1g-dev:ppc64el is selected for install because: 80s 1. satisfy:command-line:ppc64el=1 is selected for install 80s 2. satisfy:command-line:ppc64el Depends libvtk9-dev 80s 3. libvtk9-dev:ppc64el Depends zlib1g-dev 80s 2. zlib1g-dev:ppc64el is available in versions 1:1.3.dfsg+really1.3.1-1ubuntu3, 1:1.3.dfsg+really1.3.1-1ubuntu2 80s but none of the choices are installable: 80s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu3 is not selected for install 80s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu2 is not selected for install 80s buildBoolean FAIL badpkg 80s blame: vtk9 80s 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. 80s autopkgtest [19:18:25]: test buildPoint: preparing testbed 80s Reading package lists... 80s Building dependency tree... 80s Reading state information... 80s Solving dependencies... 80s Some packages could not be installed. This may mean that you have 80s requested an impossible situation or if you are using the unstable 80s distribution that some required packages have not yet been created 80s or been moved out of Incoming. 80s The following information may help to resolve the situation: 80s 80s The following packages have unmet dependencies: 80s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 80s Depends: libvtk9-qt-dev but it is not going to be installed 80s Depends: build-essential but it is not going to be installed 80s Depends: cmake but it is not going to be installed 80s E: Unable to satisfy dependencies. Reached two conflicting assignments: 80s 1. zlib1g-dev:ppc64el is selected for install because: 80s 1. satisfy:command-line:ppc64el=1 is selected for install 80s 2. satisfy:command-line:ppc64el Depends libvtk9-dev 80s 3. libvtk9-dev:ppc64el Depends zlib1g-dev 80s 2. zlib1g-dev:ppc64el is available in versions 1:1.3.dfsg+really1.3.1-1ubuntu3, 1:1.3.dfsg+really1.3.1-1ubuntu2 80s but none of the choices are installable: 80s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu3 is not selected for install 80s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu2 is not selected for install 80s buildPoint FAIL badpkg 80s blame: vtk9 80s 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. 80s autopkgtest [19:18:25]: test buildVTU: preparing testbed 80s Reading package lists... 81s Building dependency tree... 81s Reading state information... 81s Solving dependencies... 81s Some packages could not be installed. This may mean that you have 81s requested an impossible situation or if you are using the unstable 81s distribution that some required packages have not yet been created 81s or been moved out of Incoming. 81s The following information may help to resolve the situation: 81s 81s The following packages have unmet dependencies: 81s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 81s Depends: libvtk9-qt-dev but it is not going to be installed 81s Depends: build-essential but it is not going to be installed 81s Depends: cmake but it is not going to be installed 81s E: Unable to satisfy dependencies. Reached two conflicting assignments: 81s 1. zlib1g-dev:ppc64el is selected for install because: 81s 1. satisfy:command-line:ppc64el=1 is selected for install 81s 2. satisfy:command-line:ppc64el Depends libvtk9-dev 81s 3. libvtk9-dev:ppc64el Depends zlib1g-dev 81s 2. zlib1g-dev:ppc64el is available in versions 1:1.3.dfsg+really1.3.1-1ubuntu3, 1:1.3.dfsg+really1.3.1-1ubuntu2 81s but none of the choices are installable: 81s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu3 is not selected for install 81s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu2 is not selected for install 81s buildVTU FAIL badpkg 81s blame: vtk9 81s 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. 81s autopkgtest [19:18:26]: test buildDistance: preparing testbed 81s Reading package lists... 81s Building dependency tree... 81s Reading state information... 81s Solving dependencies... 81s Some packages could not be installed. This may mean that you have 81s requested an impossible situation or if you are using the unstable 81s distribution that some required packages have not yet been created 81s or been moved out of Incoming. 81s The following information may help to resolve the situation: 81s 81s The following packages have unmet dependencies: 81s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 81s Depends: libvtk9-qt-dev but it is not going to be installed 81s Depends: build-essential but it is not going to be installed 81s Depends: cmake but it is not going to be installed 81s E: Unable to satisfy dependencies. Reached two conflicting assignments: 81s 1. zlib1g-dev:ppc64el is selected for install because: 81s 1. satisfy:command-line:ppc64el=1 is selected for install 81s 2. satisfy:command-line:ppc64el Depends libvtk9-dev 81s 3. libvtk9-dev:ppc64el Depends zlib1g-dev 81s 2. zlib1g-dev:ppc64el is available in versions 1:1.3.dfsg+really1.3.1-1ubuntu3, 1:1.3.dfsg+really1.3.1-1ubuntu2 81s but none of the choices are installable: 81s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu3 is not selected for install 81s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu2 is not selected for install 81s buildDistance FAIL badpkg 81s blame: vtk9 81s 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. 81s autopkgtest [19:18:26]: test buildPNG: preparing testbed 81s Reading package lists... 82s Building dependency tree... 82s Reading state information... 82s Solving dependencies... 82s Some packages could not be installed. This may mean that you have 82s requested an impossible situation or if you are using the unstable 82s distribution that some required packages have not yet been created 82s or been moved out of Incoming. 82s The following information may help to resolve the situation: 82s 82s The following packages have unmet dependencies: 82s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 82s Depends: libvtk9-qt-dev but it is not going to be installed 82s Depends: build-essential but it is not going to be installed 82s Depends: cmake but it is not going to be installed 82s E: Unable to satisfy dependencies. Reached two conflicting assignments: 82s 1. zlib1g-dev:ppc64el is selected for install because: 82s 1. satisfy:command-line:ppc64el=1 is selected for install 82s 2. satisfy:command-line:ppc64el Depends libvtk9-dev 82s 3. libvtk9-dev:ppc64el Depends zlib1g-dev 82s 2. zlib1g-dev:ppc64el is available in versions 1:1.3.dfsg+really1.3.1-1ubuntu3, 1:1.3.dfsg+really1.3.1-1ubuntu2 82s but none of the choices are installable: 82s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu3 is not selected for install 82s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu2 is not selected for install 82s buildPNG FAIL badpkg 82s blame: vtk9 82s 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. 82s autopkgtest [19:18:27]: test buildVTP: preparing testbed 82s Reading package lists... 82s Building dependency tree... 82s Reading state information... 82s Solving dependencies... 82s Some packages could not be installed. This may mean that you have 82s requested an impossible situation or if you are using the unstable 82s distribution that some required packages have not yet been created 82s or been moved out of Incoming. 82s The following information may help to resolve the situation: 82s 82s The following packages have unmet dependencies: 82s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 82s Depends: libvtk9-qt-dev but it is not going to be installed 82s Depends: build-essential but it is not going to be installed 82s Depends: cmake but it is not going to be installed 82s E: Unable to satisfy dependencies. Reached two conflicting assignments: 82s 1. zlib1g-dev:ppc64el is selected for install because: 82s 1. satisfy:command-line:ppc64el=1 is selected for install 82s 2. satisfy:command-line:ppc64el Depends libvtk9-dev 82s 3. libvtk9-dev:ppc64el Depends zlib1g-dev 82s 2. zlib1g-dev:ppc64el is available in versions 1:1.3.dfsg+really1.3.1-1ubuntu3, 1:1.3.dfsg+really1.3.1-1ubuntu2 82s but none of the choices are installable: 82s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu3 is not selected for install 82s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu2 is not selected for install 82s buildVTP FAIL badpkg 82s blame: vtk9 82s 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. 82s autopkgtest [19:18:27]: @@@@@@@@@@@@@@@@@@@@ summary 82s buildBoolean FAIL badpkg 82s blame: vtk9 82s 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. 82s buildPoint FAIL badpkg 82s blame: vtk9 82s 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. 82s buildVTU FAIL badpkg 82s blame: vtk9 82s 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. 82s buildDistance FAIL badpkg 82s blame: vtk9 82s 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. 82s buildPNG FAIL badpkg 82s blame: vtk9 82s 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. 82s buildVTP FAIL badpkg 82s blame: vtk9 82s 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.