0s autopkgtest [12:31:23]: starting date and time: 2025-12-01 12:31:23+0000 0s autopkgtest [12:31:23]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [12:31:23]: host juju-7f2275-prod-proposed-migration-environment-15; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.4xeh85fd/out --timeout-copy=6000 -a i386 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:snapd --apt-upgrade livecd-rootfs --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 --env=ADT_TEST_TRIGGERS=snapd/2.73+ubuntu26.04.1 -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest-cpu2-ram4-disk20-amd64 --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-15@sto01-8.secgroup --name adt-resolute-i386-livecd-rootfs-20251201-123123-juju-7f2275-prod-proposed-migration-environment-15-752eeaaa-96e7-4963-9754-e596a5725001 --image adt/ubuntu-resolute-amd64-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-15 --net-id=net_prod-autopkgtest-workers-amd64 -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 4s Creating nova instance adt-resolute-i386-livecd-rootfs-20251201-123123-juju-7f2275-prod-proposed-migration-environment-15-752eeaaa-96e7-4963-9754-e596a5725001 from image adt/ubuntu-resolute-amd64-server-20251201.img (UUID 39d1a540-0dcd-4ef7-85c6-802f9b0efa74)... 49s autopkgtest [12:32:12]: testbed dpkg architecture: amd64 49s autopkgtest [12:32:12]: testbed apt version: 3.1.12 50s autopkgtest [12:32:13]: @@@@@@@@@@@@@@@@@@@@ test bed setup 50s autopkgtest [12:32:13]: testbed release detected to be: None 50s autopkgtest [12:32:13]: 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 [775 kB] 51s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [57.0 kB] 51s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [21.7 kB] 51s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 Packages [58.1 kB] 51s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main i386 Packages [44.6 kB] 51s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 c-n-f Metadata [3260 B] 51s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 c-n-f Metadata [120 B] 51s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/universe i386 Packages [252 kB] 51s Get:13 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 Packages [511 kB] 51s Get:14 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 c-n-f Metadata [16.6 kB] 51s Get:15 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 Packages [8352 B] 51s Get:16 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse i386 Packages [3800 B] 52s Get:17 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 c-n-f Metadata [616 B] 53s Fetched 1876 kB in 1s (2131 kB/s) 54s Reading package lists... 54s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 54s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 54s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 55s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 55s Reading package lists... 55s Reading package lists... 56s Building dependency tree... 56s Reading state information... 56s Calculating upgrade... 56s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 56s autopkgtest [12:32:19]: upgrading testbed (apt dist-upgrade and autopurge) 56s Reading package lists... 56s Building dependency tree... 56s Reading state information... 56s Calculating upgrade... 56s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 57s Reading package lists... 57s Building dependency tree... 57s Reading state information... 57s Solving dependencies... 57s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 59s autopkgtest [12:32:22]: testbed running kernel: Linux 6.17.0-6-generic #6-Ubuntu SMP PREEMPT_DYNAMIC Tue Oct 7 13:34:17 UTC 2025 59s autopkgtest [12:32:22]: @@@@@@@@@@@@@@@@@@@@ apt-source livecd-rootfs 60s Get:1 http://ftpmaster.internal/ubuntu resolute/main livecd-rootfs 26.04.9 (dsc) [1001 B] 60s Get:2 http://ftpmaster.internal/ubuntu resolute/main livecd-rootfs 26.04.9 (tar) [174 kB] 60s gpgv: Signature made Wed Nov 26 07:53:08 2025 UTC 60s gpgv: using DSA key DD00EF8F4D23C30D78EC990998B24A9CE4AC208E 60s gpgv: Can't check signature: No public key 60s dpkg-source: warning: cannot verify inline signature for ./livecd-rootfs_26.04.9.dsc: no acceptable signature found 60s autopkgtest [12:32:23]: testing package livecd-rootfs version 26.04.9 61s autopkgtest [12:32:24]: build not needed 61s autopkgtest [12:32:24]: test default-bootstraps: preparing testbed 61s Reading package lists... 61s Building dependency tree... 61s Reading state information... 61s Solving dependencies... 61s Some packages could not be installed. This may mean that you have 61s requested an impossible situation or if you are using the unstable 61s distribution that some required packages have not yet been created 61s or been moved out of Incoming. 61s The following information may help to resolve the situation: 61s 61s The following packages have unmet dependencies: 62s satisfy:command-line : Depends: livecd-rootfs:i386 62s E: Unable to satisfy dependencies. Reached two conflicting decisions: 62s 1. python3:i386 is selected for install because: 62s 1. satisfy:command-line:amd64=1 is selected for install 62s 2. satisfy:command-line:amd64 Depends livecd-rootfs:i386 62s 3. livecd-rootfs:i386 Depends python3:i386 62s 2. python3:i386 is available in versions 3.13.7-1, 3.13.7-2 62s but none of the choices are installable: 62s - python3:i386=3.13.7-1 is not selected for install because: 62s 1. shim-signed:amd64 is selected for install 62s 2. shim-signed:amd64 Depends grub2-common (>= 2.04-1ubuntu24) 62s 3. grub2-common:amd64 Depends python3 62s 4. python3:amd64 Conflicts python3:i386 62s [selected python3:amd64] 62s - python3:i386=3.13.7-2 is not selected for install 62s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 62s Reading package lists... 62s Building dependency tree... 62s Reading state information... 62s Solving dependencies... 62s Some packages could not be installed. This may mean that you have 62s requested an impossible situation or if you are using the unstable 62s distribution that some required packages have not yet been created 62s or been moved out of Incoming. 62s The following information may help to resolve the situation: 62s 62s The following packages have unmet dependencies: 62s satisfy:command-line : Depends: livecd-rootfs:i386 62s E: Unable to satisfy dependencies. Reached two conflicting decisions: 62s 1. python3:i386 is selected for install because: 62s 1. satisfy:command-line:amd64=1 is selected for install 62s 2. satisfy:command-line:amd64 Depends livecd-rootfs:i386 62s 3. livecd-rootfs:i386 Depends python3:i386 62s 2. python3:i386 is available in versions 3.13.7-2, 3.13.7-1 62s but none of the choices are installable: 62s - python3:i386=3.13.7-2 is not selected for install because: 62s 1. shim-signed:amd64 is selected for install 62s 2. shim-signed:amd64 Depends grub2-common (>= 2.04-1ubuntu24) 62s 3. grub2-common:amd64 Depends python3 62s 4. python3:amd64 Conflicts python3:i386 62s [selected python3:amd64] 62s - python3:i386=3.13.7-1 is not selected for install 62s default-bootstraps FAIL badpkg 62s blame: livecd-rootfs 62s 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. 62s autopkgtest [12:32:25]: test minimized: preparing testbed 63s Reading package lists... 63s Building dependency tree... 63s Reading state information... 63s Solving dependencies... 63s Some packages could not be installed. This may mean that you have 63s requested an impossible situation or if you are using the unstable 63s distribution that some required packages have not yet been created 63s or been moved out of Incoming. 63s The following information may help to resolve the situation: 63s 63s The following packages have unmet dependencies: 63s satisfy:command-line : Depends: livecd-rootfs:i386 63s E: Unable to satisfy dependencies. Reached two conflicting decisions: 63s 1. python3:i386 is selected for install because: 63s 1. satisfy:command-line:amd64=1 is selected for install 63s 2. satisfy:command-line:amd64 Depends livecd-rootfs:i386 63s 3. livecd-rootfs:i386 Depends python3:i386 63s 2. python3:i386 is available in versions 3.13.7-2, 3.13.7-1 63s but none of the choices are installable: 63s - python3:i386=3.13.7-2 is not selected for install because: 63s 1. shim-signed:amd64 is selected for install 63s 2. shim-signed:amd64 Depends grub2-common (>= 2.04-1ubuntu24) 63s 3. grub2-common:amd64 Depends python3 63s 4. python3:amd64 Conflicts python3:i386 63s [selected python3:amd64] 63s - python3:i386=3.13.7-1 is not selected for install 63s minimized FAIL badpkg 63s blame: livecd-rootfs 63s 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. 63s autopkgtest [12:32:26]: @@@@@@@@@@@@@@@@@@@@ summary 63s default-bootstraps FAIL badpkg 63s blame: livecd-rootfs 63s 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. 63s minimized FAIL badpkg 63s blame: livecd-rootfs 63s 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.