0s autopkgtest [19:16:52]: starting date and time: 2026-01-24 19:16:52+0000 0s autopkgtest [19:16:52]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [19:16:52]: host juju-7f2275-prod-proposed-migration-environment-2; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.pay4ccj4/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:zlib --apt-upgrade f3d --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-2@sto01-ppc64el-12.secgroup --name adt-resolute-ppc64el-f3d-20260124-191652-juju-7f2275-prod-proposed-migration-environment-2-9e3241aa-07e3-4b79-8e8b-b82d40fe8b9c --image adt/ubuntu-resolute-ppc64el-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-2 --net-id=net_prod-autopkgtest-workers-ppc64el -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 5s Creating nova instance adt-resolute-ppc64el-f3d-20260124-191652-juju-7f2275-prod-proposed-migration-environment-2-9e3241aa-07e3-4b79-8e8b-b82d40fe8b9c from image adt/ubuntu-resolute-ppc64el-server-20260124.img (UUID a269ca64-3301-4299-8bab-2247218fc911)... 56s autopkgtest [19:17:48]: testbed dpkg architecture: ppc64el 56s autopkgtest [19:17:48]: testbed apt version: 3.1.13 56s autopkgtest [19:17:48]: @@@@@@@@@@@@@@@@@@@@ test bed setup 56s autopkgtest [19:17:48]: testbed release detected to be: None 57s autopkgtest [19:17:49]: updating testbed package index (apt update) 57s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 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 57s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [95.5 kB] 57s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [24.3 kB] 57s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [976 kB] 57s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [2820 B] 57s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el Packages [107 kB] 58s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/universe ppc64el Packages [806 kB] 58s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse ppc64el Packages [9920 B] 58s Fetched 2145 kB in 1s (4220 kB/s) 58s Reading package lists... 59s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 59s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 59s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 59s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 60s Reading package lists... 60s Reading package lists... 60s Building dependency tree... 60s Reading state information... 60s Calculating upgrade... 60s The following packages will be upgraded: 60s zlib1g 60s 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 60s Need to get 74.6 kB of archives. 60s After this operation, 0 B of additional disk space will be used. 60s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el zlib1g ppc64el 1:1.3.dfsg+really1.3.1-1ubuntu3 [74.6 kB] 61s dpkg-preconfigure: unable to re-open stdin: No such file or directory 61s Fetched 74.6 kB in 0s (3419 kB/s) 61s (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.) 61s Preparing to unpack .../zlib1g_1%3a1.3.dfsg+really1.3.1-1ubuntu3_ppc64el.deb ... 61s Unpacking zlib1g:ppc64el (1:1.3.dfsg+really1.3.1-1ubuntu3) over (1:1.3.dfsg+really1.3.1-1ubuntu2) ... 61s Setting up zlib1g:ppc64el (1:1.3.dfsg+really1.3.1-1ubuntu3) ... 61s Processing triggers for libc-bin (2.42-2ubuntu4) ... 61s autopkgtest [19:17:53]: upgrading testbed (apt dist-upgrade and autopurge) 61s Reading package lists... 62s Building dependency tree... 62s Reading state information... 62s Calculating upgrade... 62s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 62s Reading package lists... 62s Building dependency tree... 62s Reading state information... 62s Solving dependencies... 62s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 65s autopkgtest [19:17:57]: testbed running kernel: Linux 6.18.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 12 16:45:54 UTC 2026 65s autopkgtest [19:17:57]: @@@@@@@@@@@@@@@@@@@@ apt-source f3d 67s Get:1 http://ftpmaster.internal/ubuntu resolute/universe f3d 3.2.0+dfsg-3 (dsc) [2248 B] 67s Get:2 http://ftpmaster.internal/ubuntu resolute/universe f3d 3.2.0+dfsg-3 (tar) [15.0 MB] 67s Get:3 http://ftpmaster.internal/ubuntu resolute/universe f3d 3.2.0+dfsg-3 (diff) [102 kB] 67s gpgv: Signature made Sun Oct 12 09:24:33 2025 UTC 67s gpgv: using RSA key 8F6DE104377F3B11E741748731F3144544A1741A 67s gpgv: issuer "tchet@debian.org" 67s gpgv: Can't check signature: No public key 67s dpkg-source: warning: cannot verify inline signature for ./f3d_3.2.0+dfsg-3.dsc: no acceptable signature found 68s autopkgtest [19:18:00]: testing package f3d version 3.2.0+dfsg-3 69s autopkgtest [19:18:01]: build not needed 70s autopkgtest [19:18:02]: test command1: preparing testbed 71s Reading package lists... 71s Building dependency tree... 71s Reading state information... 71s Solving dependencies... 71s Some packages could not be installed. This may mean that you have 71s requested an impossible situation or if you are using the unstable 71s distribution that some required packages have not yet been created 71s or been moved out of Incoming. 71s The following information may help to resolve the situation: 71s 71s The following packages have unmet dependencies: 71s satisfy:command-line : Depends: f3d but it is not going to be installed 71s E: Unable to satisfy dependencies. Reached two conflicting assignments: 71s 1. libamdhip64-6:ppc64el is selected for install because: 71s 1. satisfy:command-line:ppc64el=1 is selected for install 71s 2. satisfy:command-line:ppc64el Depends f3d 71s 3. f3d:ppc64el Depends libvtk9.5 (>= 9.5.2+dfsg2) 71s 4. libvtk9.5:ppc64el Depends libopenmpi40 (>= 5.0.8) 71s 5. libopenmpi40:ppc64el Depends libucx0 71s 6. libucx0:ppc64el Depends libamdhip64-6 (>= 6.1.5) 71s 2. libamdhip64-6:ppc64el Depends libamd-comgr3 71s but none of the choices are installable: 71s [no choices] 71s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 71s Reading package lists... 71s Building dependency tree... 71s Reading state information... 72s Solving dependencies... 72s Some packages could not be installed. This may mean that you have 72s requested an impossible situation or if you are using the unstable 72s distribution that some required packages have not yet been created 72s or been moved out of Incoming. 72s The following information may help to resolve the situation: 72s 72s The following packages have unmet dependencies: 72s satisfy:command-line : Depends: f3d but it is not going to be installed 72s E: Unable to satisfy dependencies. Reached two conflicting assignments: 72s 1. libamdhip64-6:ppc64el is selected for install because: 72s 1. satisfy:command-line:ppc64el=1 is selected for install 72s 2. satisfy:command-line:ppc64el Depends f3d 72s 3. f3d:ppc64el Depends libvtk9.5 (>= 9.5.2+dfsg2) 72s 4. libvtk9.5:ppc64el Depends libopenmpi40 (>= 5.0.8) 72s 5. libopenmpi40:ppc64el Depends libucx0 72s 6. libucx0:ppc64el Depends libamdhip64-6 (>= 6.1.5) 72s 2. libamdhip64-6:ppc64el Depends libamd-comgr3 72s but none of the choices are installable: 72s [no choices] 72s autopkgtest [19:18:04]: test command2: preparing testbed 72s command1 FAIL badpkg 72s blame: f3d 72s 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. 72s Reading package lists... 72s Building dependency tree... 72s Reading state information... 72s Solving dependencies... 72s Some packages could not be installed. This may mean that you have 72s requested an impossible situation or if you are using the unstable 72s distribution that some required packages have not yet been created 72s or been moved out of Incoming. 72s The following information may help to resolve the situation: 72s 72s The following packages have unmet dependencies: 72s satisfy:command-line : Depends: f3d but it is not going to be installed 72s E: Unable to satisfy dependencies. Reached two conflicting assignments: 72s 1. libamdhip64-6:ppc64el is selected for install because: 72s 1. satisfy:command-line:ppc64el=1 is selected for install 72s 2. satisfy:command-line:ppc64el Depends f3d 72s 3. f3d:ppc64el Depends libvtk9.5 (>= 9.5.2+dfsg2) 72s 4. libvtk9.5:ppc64el Depends libopenmpi40 (>= 5.0.8) 72s 5. libopenmpi40:ppc64el Depends libucx0 72s 6. libucx0:ppc64el Depends libamdhip64-6 (>= 6.1.5) 72s 2. libamdhip64-6:ppc64el Depends libamd-comgr3 72s but none of the choices are installable: 72s [no choices] 72s command2 FAIL badpkg 72s blame: f3d 72s 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. 72s autopkgtest [19:18:04]: test check-cube-vtp: preparing testbed 72s Reading package lists... 72s Building dependency tree... 72s Reading state information... 72s Solving dependencies... 72s Some packages could not be installed. This may mean that you have 72s requested an impossible situation or if you are using the unstable 72s distribution that some required packages have not yet been created 72s or been moved out of Incoming. 72s The following information may help to resolve the situation: 72s 72s The following packages have unmet dependencies: 73s satisfy:command-line : Depends: f3d but it is not going to be installed 73s Depends: xvfb but it is not going to be installed 73s Depends: openimageio-tools but it is not going to be installed 73s E: Unable to satisfy dependencies. Reached two conflicting assignments: 73s 1. libamdhip64-6:ppc64el is selected for install because: 73s 1. satisfy:command-line:ppc64el=1 is selected for install 73s 2. satisfy:command-line:ppc64el Depends f3d 73s 3. f3d:ppc64el Depends libvtk9.5 (>= 9.5.2+dfsg2) 73s 4. libvtk9.5:ppc64el Depends libopenmpi40 (>= 5.0.8) 73s 5. libopenmpi40:ppc64el Depends libucx0 73s 6. libucx0:ppc64el Depends libamdhip64-6 (>= 6.1.5) 73s 2. libamdhip64-6:ppc64el Depends libamd-comgr3 73s but none of the choices are installable: 73s [no choices] 73s autopkgtest [19:18:05]: test check-cube-step: preparing testbed 73s check-cube-vtp FAIL badpkg 73s blame: f3d 73s 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. 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: f3d but it is not going to be installed 73s Depends: xvfb but it is not going to be installed 73s Depends: openimageio-tools but it is not going to be installed 73s E: Unable to satisfy dependencies. Reached two conflicting assignments: 73s 1. libamdhip64-6:ppc64el is selected for install because: 73s 1. satisfy:command-line:ppc64el=1 is selected for install 73s 2. satisfy:command-line:ppc64el Depends f3d 73s 3. f3d:ppc64el Depends libvtk9.5 (>= 9.5.2+dfsg2) 73s 4. libvtk9.5:ppc64el Depends libopenmpi40 (>= 5.0.8) 73s 5. libopenmpi40:ppc64el Depends libucx0 73s 6. libucx0:ppc64el Depends libamdhip64-6 (>= 6.1.5) 73s 2. libamdhip64-6:ppc64el Depends libamd-comgr3 73s but none of the choices are installable: 73s [no choices] 73s autopkgtest [19:18:05]: test check-cube-dae: preparing testbed 73s check-cube-step FAIL badpkg 73s blame: f3d 73s 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. 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: f3d but it is not going to be installed 73s Depends: xvfb but it is not going to be installed 73s Depends: openimageio-tools but it is not going to be installed 73s E: Unable to satisfy dependencies. Reached two conflicting assignments: 73s 1. libamdhip64-6:ppc64el is selected for install because: 73s 1. satisfy:command-line:ppc64el=1 is selected for install 73s 2. satisfy:command-line:ppc64el Depends f3d 73s 3. f3d:ppc64el Depends libvtk9.5 (>= 9.5.2+dfsg2) 73s 4. libvtk9.5:ppc64el Depends libopenmpi40 (>= 5.0.8) 73s 5. libopenmpi40:ppc64el Depends libucx0 73s 6. libucx0:ppc64el Depends libamdhip64-6 (>= 6.1.5) 73s 2. libamdhip64-6:ppc64el Depends libamd-comgr3 73s but none of the choices are installable: 73s [no choices] 73s check-cube-dae FAIL badpkg 73s blame: f3d 73s 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. 73s autopkgtest [19:18:05]: @@@@@@@@@@@@@@@@@@@@ summary 73s command1 FAIL badpkg 73s blame: f3d 73s 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. 73s command2 FAIL badpkg 73s blame: f3d 73s 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. 73s check-cube-vtp FAIL badpkg 73s blame: f3d 73s 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. 73s check-cube-step FAIL badpkg 73s blame: f3d 73s 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. 73s check-cube-dae FAIL badpkg 73s blame: f3d 73s 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.