0s autopkgtest [19:16:32]: starting date and time: 2026-01-24 19:16:32+0000 0s autopkgtest [19:16:32]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [19:16:32]: host juju-7f2275-prod-proposed-migration-environment-15; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.nxyp3ina/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:tcl8.6 --apt-upgrade vtk9 --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 --env=ADT_TEST_TRIGGERS=tcl8.6/8.6.17+dfsg-1build1 -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest-cpu2-ram4-disk20-ppc64el --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-15@sto01-ppc64el-17.secgroup --name adt-resolute-ppc64el-vtk9-20260124-191632-juju-7f2275-prod-proposed-migration-environment-15-c9770deb-9e44-430b-bbf2-56bdfade8d01 --image adt/ubuntu-resolute-ppc64el-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-15 --net-id=net_prod-autopkgtest-workers-ppc64el -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 4s Creating nova instance adt-resolute-ppc64el-vtk9-20260124-191632-juju-7f2275-prod-proposed-migration-environment-15-c9770deb-9e44-430b-bbf2-56bdfade8d01 from image adt/ubuntu-resolute-ppc64el-server-20260124.img (UUID a269ca64-3301-4299-8bab-2247218fc911)... 49s autopkgtest [19:17:21]: testbed dpkg architecture: ppc64el 49s autopkgtest [19:17:21]: testbed apt version: 3.1.13 50s autopkgtest [19:17:22]: @@@@@@@@@@@@@@@@@@@@ test bed setup 50s autopkgtest [19:17:22]: testbed release detected to be: None 51s autopkgtest [19:17:23]: updating testbed package index (apt update) 51s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 51s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 51s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 51s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 51s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [976 kB] 51s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [2820 B] 51s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [95.5 kB] 51s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [24.3 kB] 51s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el Packages [107 kB] 51s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/universe ppc64el Packages [806 kB] 51s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse ppc64el Packages [9920 B] 51s Fetched 2145 kB in 1s (3654 kB/s) 52s Reading package lists... 53s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 53s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 53s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 53s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 54s Reading package lists... 54s Reading package lists... 54s Building dependency tree... 54s Reading state information... 54s Calculating upgrade... 54s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 54s autopkgtest [19:17:26]: upgrading testbed (apt dist-upgrade and autopurge) 54s Reading package lists... 54s Building dependency tree... 54s Reading state information... 54s Calculating upgrade... 54s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 55s Reading package lists... 55s Building dependency tree... 55s Reading state information... 55s Solving dependencies... 55s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 57s autopkgtest [19:17:29]: testbed running kernel: Linux 6.18.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 12 16:45:54 UTC 2026 57s autopkgtest [19:17:29]: @@@@@@@@@@@@@@@@@@@@ apt-source vtk9 63s Get:1 http://ftpmaster.internal/ubuntu resolute/universe vtk9 9.5.2+dfsg2-4ubuntu1 (dsc) [3764 B] 63s Get:2 http://ftpmaster.internal/ubuntu resolute/universe vtk9 9.5.2+dfsg2-4ubuntu1 (tar) [25.0 MB] 63s Get:3 http://ftpmaster.internal/ubuntu resolute/universe vtk9 9.5.2+dfsg2-4ubuntu1 (diff) [22.4 kB] 63s gpgv: Signature made Sun Dec 14 11:14:16 2025 UTC 63s gpgv: using RSA key B8340990283D8D9BC1949AC74799A35146D12B35 63s gpgv: issuer "sudipm.mukherjee@gmail.com" 63s gpgv: Can't check signature: No public key 63s dpkg-source: warning: cannot verify inline signature for ./vtk9_9.5.2+dfsg2-4ubuntu1.dsc: no acceptable signature found 66s autopkgtest [19:17:38]: testing package vtk9 version 9.5.2+dfsg2-4ubuntu1 66s autopkgtest [19:17:38]: build not needed 73s autopkgtest [19:17:45]: test buildBoolean: preparing testbed 73s Reading package lists... 73s Building dependency tree... 73s Reading state information... 73s Solving dependencies... 73s Some packages could not be installed. This may mean that you have 73s requested an impossible situation or if you are using the unstable 73s distribution that some required packages have not yet been created 73s or been moved out of Incoming. 73s The following information may help to resolve the situation: 73s 73s The following packages have unmet dependencies: 73s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 73s Depends: libvtk9-qt-dev but it is not going to be installed 73s Depends: build-essential but it is not going to be installed 73s Depends: cmake but it is not going to be installed 73s E: Unable to satisfy dependencies. Reached two conflicting assignments: 73s 1. libvtk9-dev:ppc64el is selected for install because: 73s 1. satisfy:command-line:ppc64el=1 is selected for install 73s 2. satisfy:command-line:ppc64el Depends libvtk9-dev 73s 2. libvtk9-dev:ppc64el Depends libexpat-dev 73s but none of the choices are installable: 73s - libexpat1-dev:ppc64el=2.7.3-1 is not selected for install 73s - libexpat1-dev:ppc64el=2.7.3-2 is not selected for install 73s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 74s Reading package lists... 74s Building dependency tree... 74s Reading state information... 74s Solving dependencies... 74s Some packages could not be installed. This may mean that you have 74s requested an impossible situation or if you are using the unstable 74s distribution that some required packages have not yet been created 74s or been moved out of Incoming. 74s The following information may help to resolve the situation: 74s 74s The following packages have unmet dependencies: 74s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 74s Depends: libvtk9-qt-dev but it is not going to be installed 74s Depends: build-essential but it is not going to be installed 74s Depends: cmake but it is not going to be installed 74s E: Unable to satisfy dependencies. Reached two conflicting assignments: 74s 1. zlib1g-dev:ppc64el is selected for install because: 74s 1. satisfy:command-line:ppc64el=1 is selected for install 74s 2. satisfy:command-line:ppc64el Depends libvtk9-dev 74s 3. libvtk9-dev:ppc64el Depends zlib1g-dev 74s 2. zlib1g-dev:ppc64el is available in versions 1:1.3.dfsg+really1.3.1-1ubuntu3, 1:1.3.dfsg+really1.3.1-1ubuntu2 74s but none of the choices are installable: 74s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu3 is not selected for install 74s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu2 is not selected for install 74s autopkgtest [19:17:46]: test buildPoint: preparing testbed 74s buildBoolean FAIL badpkg 74s blame: vtk9 74s 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. 74s Reading package lists... 74s Building dependency tree... 74s Reading state information... 74s Solving dependencies... 74s Some packages could not be installed. This may mean that you have 74s requested an impossible situation or if you are using the unstable 74s distribution that some required packages have not yet been created 74s or been moved out of Incoming. 74s The following information may help to resolve the situation: 74s 74s The following packages have unmet dependencies: 74s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 74s Depends: libvtk9-qt-dev but it is not going to be installed 74s Depends: build-essential but it is not going to be installed 74s Depends: cmake but it is not going to be installed 74s E: Unable to satisfy dependencies. Reached two conflicting assignments: 74s 1. zlib1g-dev:ppc64el is selected for install because: 74s 1. satisfy:command-line:ppc64el=1 is selected for install 74s 2. satisfy:command-line:ppc64el Depends libvtk9-dev 74s 3. libvtk9-dev:ppc64el Depends zlib1g-dev 74s 2. zlib1g-dev:ppc64el is available in versions 1:1.3.dfsg+really1.3.1-1ubuntu3, 1:1.3.dfsg+really1.3.1-1ubuntu2 74s but none of the choices are installable: 74s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu3 is not selected for install 74s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu2 is not selected for install 74s autopkgtest [19:17:46]: test buildVTU: preparing testbed 74s buildPoint FAIL badpkg 74s blame: vtk9 74s 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. 75s Reading package lists... 75s Building dependency tree... 75s Reading state information... 75s Solving dependencies... 75s Some packages could not be installed. This may mean that you have 75s requested an impossible situation or if you are using the unstable 75s distribution that some required packages have not yet been created 75s or been moved out of Incoming. 75s The following information may help to resolve the situation: 75s 75s The following packages have unmet dependencies: 75s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 75s Depends: libvtk9-qt-dev but it is not going to be installed 75s Depends: build-essential but it is not going to be installed 75s Depends: cmake but it is not going to be installed 75s E: Unable to satisfy dependencies. Reached two conflicting assignments: 75s 1. zlib1g-dev:ppc64el is selected for install because: 75s 1. satisfy:command-line:ppc64el=1 is selected for install 75s 2. satisfy:command-line:ppc64el Depends libvtk9-dev 75s 3. libvtk9-dev:ppc64el Depends zlib1g-dev 75s 2. zlib1g-dev:ppc64el is available in versions 1:1.3.dfsg+really1.3.1-1ubuntu3, 1:1.3.dfsg+really1.3.1-1ubuntu2 75s but none of the choices are installable: 75s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu3 is not selected for install 75s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu2 is not selected for install 75s autopkgtest [19:17:47]: test buildDistance: preparing testbed 75s buildVTU FAIL badpkg 75s blame: vtk9 75s 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. 75s Reading package lists... 75s Building dependency tree... 75s Reading state information... 75s Solving dependencies... 75s Some packages could not be installed. This may mean that you have 75s requested an impossible situation or if you are using the unstable 75s distribution that some required packages have not yet been created 75s or been moved out of Incoming. 75s The following information may help to resolve the situation: 75s 75s The following packages have unmet dependencies: 75s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 75s Depends: libvtk9-qt-dev but it is not going to be installed 75s Depends: build-essential but it is not going to be installed 75s Depends: cmake but it is not going to be installed 75s E: Unable to satisfy dependencies. Reached two conflicting assignments: 75s 1. zlib1g-dev:ppc64el is selected for install because: 75s 1. satisfy:command-line:ppc64el=1 is selected for install 75s 2. satisfy:command-line:ppc64el Depends libvtk9-dev 75s 3. libvtk9-dev:ppc64el Depends zlib1g-dev 75s 2. zlib1g-dev:ppc64el is available in versions 1:1.3.dfsg+really1.3.1-1ubuntu3, 1:1.3.dfsg+really1.3.1-1ubuntu2 75s but none of the choices are installable: 75s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu3 is not selected for install 75s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu2 is not selected for install 75s buildDistance FAIL badpkg 75s blame: vtk9 75s 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. 75s autopkgtest [19:17:47]: test buildPNG: preparing testbed 76s Reading package lists... 76s Building dependency tree... 76s Reading state information... 76s Solving dependencies... 76s Some packages could not be installed. This may mean that you have 76s requested an impossible situation or if you are using the unstable 76s distribution that some required packages have not yet been created 76s or been moved out of Incoming. 76s The following information may help to resolve the situation: 76s 76s The following packages have unmet dependencies: 76s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 76s Depends: libvtk9-qt-dev but it is not going to be installed 76s Depends: build-essential but it is not going to be installed 76s Depends: cmake but it is not going to be installed 76s E: Unable to satisfy dependencies. Reached two conflicting assignments: 76s 1. zlib1g-dev:ppc64el is selected for install because: 76s 1. satisfy:command-line:ppc64el=1 is selected for install 76s 2. satisfy:command-line:ppc64el Depends libvtk9-dev 76s 3. libvtk9-dev:ppc64el Depends zlib1g-dev 76s 2. zlib1g-dev:ppc64el is available in versions 1:1.3.dfsg+really1.3.1-1ubuntu3, 1:1.3.dfsg+really1.3.1-1ubuntu2 76s but none of the choices are installable: 76s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu3 is not selected for install 76s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu2 is not selected for install 76s buildPNG FAIL badpkg 76s blame: vtk9 76s 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. 76s autopkgtest [19:17:48]: test buildVTP: preparing testbed 76s Reading package lists... 76s Building dependency tree... 76s Reading state information... 76s Solving dependencies... 76s Some packages could not be installed. This may mean that you have 76s requested an impossible situation or if you are using the unstable 76s distribution that some required packages have not yet been created 76s or been moved out of Incoming. 76s The following information may help to resolve the situation: 76s 76s The following packages have unmet dependencies: 76s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 76s Depends: libvtk9-qt-dev but it is not going to be installed 76s Depends: build-essential but it is not going to be installed 76s Depends: cmake but it is not going to be installed 76s E: Unable to satisfy dependencies. Reached two conflicting assignments: 76s 1. zlib1g-dev:ppc64el is selected for install because: 76s 1. satisfy:command-line:ppc64el=1 is selected for install 76s 2. satisfy:command-line:ppc64el Depends libvtk9-dev 76s 3. libvtk9-dev:ppc64el Depends zlib1g-dev 76s 2. zlib1g-dev:ppc64el is available in versions 1:1.3.dfsg+really1.3.1-1ubuntu3, 1:1.3.dfsg+really1.3.1-1ubuntu2 76s but none of the choices are installable: 76s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu3 is not selected for install 76s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu2 is not selected for install 76s buildVTP FAIL badpkg 76s blame: vtk9 76s 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. 76s autopkgtest [19:17:48]: @@@@@@@@@@@@@@@@@@@@ summary 76s buildBoolean FAIL badpkg 76s blame: vtk9 76s 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. 76s buildPoint FAIL badpkg 76s blame: vtk9 76s 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. 76s buildVTU FAIL badpkg 76s blame: vtk9 76s 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. 76s buildDistance FAIL badpkg 76s blame: vtk9 76s 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. 76s buildPNG FAIL badpkg 76s blame: vtk9 76s 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. 76s buildVTP FAIL badpkg 76s blame: vtk9 76s 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.