0s autopkgtest [13:57:46]: starting date and time: 2026-01-24 13:57:46+0000 0s autopkgtest [13:57:46]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [13:57:46]: host juju-7f2275-prod-proposed-migration-environment-20; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.z8ij2c9p/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:expat --apt-upgrade vtk9 --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 --env=ADT_TEST_TRIGGERS=expat/2.7.3-2 -- 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-2.secgroup --name adt-resolute-ppc64el-vtk9-20260124-135746-juju-7f2275-prod-proposed-migration-environment-20-7280c801-265f-426b-9d0a-8173cbadb92f --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-135746-juju-7f2275-prod-proposed-migration-environment-20-7280c801-265f-426b-9d0a-8173cbadb92f from image adt/ubuntu-resolute-ppc64el-server-20260124.img (UUID a269ca64-3301-4299-8bab-2247218fc911)... 48s autopkgtest [13:58:34]: testbed dpkg architecture: ppc64el 48s autopkgtest [13:58:34]: testbed apt version: 3.1.13 49s autopkgtest [13:58:35]: @@@@@@@@@@@@@@@@@@@@ test bed setup 49s autopkgtest [13:58:35]: testbed release detected to be: None 50s autopkgtest [13:58:36]: updating testbed package index (apt update) 50s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 50s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 50s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 50s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 50s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [2820 B] 50s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [998 kB] 50s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [92.3 kB] 50s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [24.3 kB] 50s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el Packages [108 kB] 50s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/universe ppc64el Packages [835 kB] 51s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse ppc64el Packages [9920 B] 51s Fetched 2194 kB in 1s (3093 kB/s) 51s Reading package lists... 52s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 52s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 52s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 52s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 53s Reading package lists... 53s Reading package lists... 53s Building dependency tree... 53s Reading state information... 53s Calculating upgrade... 53s The following packages will be upgraded: 53s libexpat1 53s 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 53s Need to get 104 kB of archives. 53s After this operation, 0 B of additional disk space will be used. 53s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el libexpat1 ppc64el 2.7.3-2 [104 kB] 54s dpkg-preconfigure: unable to re-open stdin: No such file or directory 54s Fetched 104 kB in 0s (2116 kB/s) 54s (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.) 54s Preparing to unpack .../libexpat1_2.7.3-2_ppc64el.deb ... 54s Unpacking libexpat1:ppc64el (2.7.3-2) over (2.7.3-1) ... 54s Setting up libexpat1:ppc64el (2.7.3-2) ... 54s Processing triggers for libc-bin (2.42-2ubuntu4) ... 54s autopkgtest [13:58:40]: upgrading testbed (apt dist-upgrade and autopurge) 54s Reading package lists... 55s Building dependency tree... 55s Reading state information... 55s Calculating upgrade... 55s 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. 58s autopkgtest [13:58:44]: testbed running kernel: Linux 6.18.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 12 16:45:54 UTC 2026 58s autopkgtest [13:58:44]: @@@@@@@@@@@@@@@@@@@@ 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] 64s gpgv: Signature made Sun Dec 14 11:14:16 2025 UTC 64s gpgv: using RSA key B8340990283D8D9BC1949AC74799A35146D12B35 64s gpgv: issuer "sudipm.mukherjee@gmail.com" 64s gpgv: Can't check signature: No public key 64s dpkg-source: warning: cannot verify inline signature for ./vtk9_9.5.2+dfsg2-4ubuntu1.dsc: no acceptable signature found 67s autopkgtest [13:58:53]: testing package vtk9 version 9.5.2+dfsg2-4ubuntu1 67s autopkgtest [13:58:53]: build not needed 76s autopkgtest [13:59:02]: test buildBoolean: 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. openjdk-21-jre: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 default-jdk 76s 4. default-jdk:ppc64el Depends default-jre (= 2:1.21-76build1) 76s 5. default-jre:ppc64el Depends openjdk-21-jre 76s 2. openjdk-21-jre:ppc64el Depends libasound2t64 (>= 1.0.16) 76s but none of the choices are installable: 76s - libasound2t64:ppc64el=1.2.15.1-1 is not selected for install 76s - libasound2t64:ppc64el=1.2.15.3-1 is not selected for install 76s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 77s Reading package lists... 77s Building dependency tree... 77s Reading state information... 77s Solving dependencies... 77s Some packages could not be installed. This may mean that you have 77s requested an impossible situation or if you are using the unstable 77s distribution that some required packages have not yet been created 77s or been moved out of Incoming. 77s The following information may help to resolve the situation: 77s 77s The following packages have unmet dependencies: 77s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 77s Depends: libvtk9-qt-dev but it is not going to be installed 77s Depends: build-essential but it is not going to be installed 77s Depends: cmake but it is not going to be installed 77s E: Unable to satisfy dependencies. Reached two conflicting assignments: 77s 1. zlib1g-dev:ppc64el is selected for install because: 77s 1. satisfy:command-line:ppc64el=1 is selected for install 77s 2. satisfy:command-line:ppc64el Depends libvtk9-dev 77s 3. libvtk9-dev:ppc64el Depends zlib1g-dev 77s 2. zlib1g-dev:ppc64el is available in versions 1:1.3.dfsg+really1.3.1-1ubuntu3, 1:1.3.dfsg+really1.3.1-1ubuntu2 77s but none of the choices are installable: 77s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu3 is not selected for install 77s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu2 is not selected for install 77s buildBoolean FAIL badpkg 77s blame: vtk9 77s 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. 77s autopkgtest [13:59:03]: test buildPoint: preparing testbed 77s Reading package lists... 77s Building dependency tree... 77s Reading state information... 77s Solving dependencies... 77s Some packages could not be installed. This may mean that you have 77s requested an impossible situation or if you are using the unstable 77s distribution that some required packages have not yet been created 77s or been moved out of Incoming. 77s The following information may help to resolve the situation: 77s 77s The following packages have unmet dependencies: 77s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 77s Depends: libvtk9-qt-dev but it is not going to be installed 77s Depends: build-essential but it is not going to be installed 77s Depends: cmake but it is not going to be installed 77s E: Unable to satisfy dependencies. Reached two conflicting assignments: 77s 1. zlib1g-dev:ppc64el is selected for install because: 77s 1. satisfy:command-line:ppc64el=1 is selected for install 77s 2. satisfy:command-line:ppc64el Depends libvtk9-dev 77s 3. libvtk9-dev:ppc64el Depends zlib1g-dev 77s 2. zlib1g-dev:ppc64el is available in versions 1:1.3.dfsg+really1.3.1-1ubuntu3, 1:1.3.dfsg+really1.3.1-1ubuntu2 77s but none of the choices are installable: 77s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu3 is not selected for install 77s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu2 is not selected for install 77s autopkgtest [13:59:03]: test buildVTU: preparing testbed 77s buildPoint FAIL badpkg 77s blame: vtk9 77s 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. 77s Reading package lists... 78s Building dependency tree... 78s Reading state information... 78s Solving dependencies... 78s Some packages could not be installed. This may mean that you have 78s requested an impossible situation or if you are using the unstable 78s distribution that some required packages have not yet been created 78s or been moved out of Incoming. 78s The following information may help to resolve the situation: 78s 78s The following packages have unmet dependencies: 78s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 78s Depends: libvtk9-qt-dev but it is not going to be installed 78s Depends: build-essential but it is not going to be installed 78s Depends: cmake but it is not going to be installed 78s E: Unable to satisfy dependencies. Reached two conflicting assignments: 78s 1. zlib1g-dev:ppc64el is selected for install because: 78s 1. satisfy:command-line:ppc64el=1 is selected for install 78s 2. satisfy:command-line:ppc64el Depends libvtk9-dev 78s 3. libvtk9-dev:ppc64el Depends zlib1g-dev 78s 2. zlib1g-dev:ppc64el is available in versions 1:1.3.dfsg+really1.3.1-1ubuntu3, 1:1.3.dfsg+really1.3.1-1ubuntu2 78s but none of the choices are installable: 78s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu3 is not selected for install 78s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu2 is not selected for install 78s autopkgtest [13:59:04]: test buildDistance: preparing testbed 78s buildVTU FAIL badpkg 78s blame: vtk9 78s 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. 78s Reading package lists... 78s Building dependency tree... 78s Reading state information... 78s Solving dependencies... 78s Some packages could not be installed. This may mean that you have 78s requested an impossible situation or if you are using the unstable 78s distribution that some required packages have not yet been created 78s or been moved out of Incoming. 78s The following information may help to resolve the situation: 78s 78s The following packages have unmet dependencies: 78s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 78s Depends: libvtk9-qt-dev but it is not going to be installed 78s Depends: build-essential but it is not going to be installed 78s Depends: cmake but it is not going to be installed 78s E: Unable to satisfy dependencies. Reached two conflicting assignments: 78s 1. zlib1g-dev:ppc64el is selected for install because: 78s 1. satisfy:command-line:ppc64el=1 is selected for install 78s 2. satisfy:command-line:ppc64el Depends libvtk9-dev 78s 3. libvtk9-dev:ppc64el Depends zlib1g-dev 78s 2. zlib1g-dev:ppc64el is available in versions 1:1.3.dfsg+really1.3.1-1ubuntu3, 1:1.3.dfsg+really1.3.1-1ubuntu2 78s but none of the choices are installable: 78s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu3 is not selected for install 78s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu2 is not selected for install 78s buildDistance FAIL badpkg 78s blame: vtk9 78s 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. 78s autopkgtest [13:59:04]: test buildPNG: preparing testbed 78s 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. zlib1g-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 3. libvtk9-dev:ppc64el Depends zlib1g-dev 79s 2. zlib1g-dev:ppc64el is available in versions 1:1.3.dfsg+really1.3.1-1ubuntu3, 1:1.3.dfsg+really1.3.1-1ubuntu2 79s but none of the choices are installable: 79s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu3 is not selected for install 79s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu2 is not selected for install 79s buildPNG FAIL badpkg 79s blame: vtk9 79s 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. 79s autopkgtest [13:59:05]: test buildVTP: 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. zlib1g-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 3. libvtk9-dev:ppc64el Depends zlib1g-dev 79s 2. zlib1g-dev:ppc64el is available in versions 1:1.3.dfsg+really1.3.1-1ubuntu3, 1:1.3.dfsg+really1.3.1-1ubuntu2 79s but none of the choices are installable: 79s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu3 is not selected for install 79s - zlib1g-dev:ppc64el=1:1.3.dfsg+really1.3.1-1ubuntu2 is not selected for install 79s buildVTP FAIL badpkg 79s blame: vtk9 79s 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. 79s autopkgtest [13:59:05]: @@@@@@@@@@@@@@@@@@@@ summary 79s buildBoolean FAIL badpkg 79s blame: vtk9 79s 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. 79s buildPoint FAIL badpkg 79s blame: vtk9 79s 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. 79s buildVTU FAIL badpkg 79s blame: vtk9 79s 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. 79s buildDistance FAIL badpkg 79s blame: vtk9 79s 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. 79s buildPNG FAIL badpkg 79s blame: vtk9 79s 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. 79s buildVTP FAIL badpkg 79s blame: vtk9 79s 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.