0s autopkgtest [12:56:31]: starting date and time: 2026-01-29 12:56:31+0000 0s autopkgtest [12:56:31]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [12:56:31]: host juju-7f2275-prod-proposed-migration-environment-2; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.bk9cni3x/out --timeout-copy=6000 --needs-internet=try -a i386 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:pkgconf --apt-upgrade libdockapp --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 --env=ADT_TEST_TRIGGERS=pkgconf/2.5.1-2 -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest-cpu2-ram4-disk20-amd64 --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-2@sto01-15.secgroup --name adt-resolute-i386-libdockapp-20260129-125631-juju-7f2275-prod-proposed-migration-environment-2-ef41c29b-2dad-4503-8947-c0a6d068ba25 --image adt/ubuntu-resolute-amd64-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-2 --net-id=net_prod-autopkgtest-workers-amd64 -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 4s Creating nova instance adt-resolute-i386-libdockapp-20260129-125631-juju-7f2275-prod-proposed-migration-environment-2-ef41c29b-2dad-4503-8947-c0a6d068ba25 from image adt/ubuntu-resolute-amd64-server-20260129.img (UUID c052dd91-e629-41e8-9bf0-bad94c4bd713)... 78s autopkgtest [12:57:49]: testbed dpkg architecture: amd64 78s autopkgtest [12:57:49]: testbed apt version: 3.1.14 79s autopkgtest [12:57:50]: @@@@@@@@@@@@@@@@@@@@ test bed setup 79s autopkgtest [12:57:50]: testbed release detected to be: None 79s autopkgtest [12:57:50]: updating testbed package index (apt update) 80s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 80s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 80s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 80s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 80s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [2820 B] 80s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [1074 kB] 80s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [25.4 kB] 80s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [106 kB] 80s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main i386 Packages [114 kB] 80s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 Packages [132 kB] 80s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 c-n-f Metadata [4360 B] 80s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 Packages [12.3 kB] 80s Get:13 http://ftpmaster.internal/ubuntu resolute-proposed/restricted i386 Packages [3696 B] 80s Get:14 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 c-n-f Metadata [336 B] 80s Get:15 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 Packages [872 kB] 80s Get:16 http://ftpmaster.internal/ubuntu resolute-proposed/universe i386 Packages [357 kB] 80s Get:17 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 c-n-f Metadata [23.0 kB] 80s Get:18 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 Packages [23.2 kB] 80s Get:19 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse i386 Packages [3336 B] 81s Get:20 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 c-n-f Metadata [1036 B] 81s Fetched 2880 kB in 1s (3245 kB/s) 82s Reading package lists... 82s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 82s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 82s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 82s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 83s Reading package lists... 83s Reading package lists... 83s Building dependency tree... 83s Reading state information... 83s Calculating upgrade... 83s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 83s autopkgtest [12:57:54]: upgrading testbed (apt dist-upgrade and autopurge) 83s Reading package lists... 83s Building dependency tree... 83s Reading state information... 83s Calculating upgrade... 83s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 84s Reading package lists... 84s Building dependency tree... 84s Reading state information... 84s Solving dependencies... 84s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 86s autopkgtest [12:57:57]: testbed running kernel: Linux 6.18.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 12 16:49:02 UTC 2026 86s autopkgtest [12:57:57]: @@@@@@@@@@@@@@@@@@@@ apt-source libdockapp 88s Get:1 http://ftpmaster.internal/ubuntu resolute/universe libdockapp 1:0.7.3-3 (dsc) [2306 B] 88s Get:2 http://ftpmaster.internal/ubuntu resolute/universe libdockapp 1:0.7.3-3 (tar) [388 kB] 88s Get:3 http://ftpmaster.internal/ubuntu resolute/universe libdockapp 1:0.7.3-3 (diff) [7536 B] 88s gpgv: Signature made Thu Sep 12 20:21:58 2024 UTC 88s gpgv: using RSA key 6C1DB45363EF4037BD56D5172986AC0ABDF1040D 88s gpgv: issuer "azazel@debian.org" 88s gpgv: Can't check signature: No public key 88s dpkg-source: warning: cannot verify inline signature for ./libdockapp_0.7.3-3.dsc: no acceptable signature found 88s autopkgtest [12:57:59]: testing package libdockapp version 1:0.7.3-3 88s autopkgtest [12:57:59]: build not needed 89s autopkgtest [12:58:00]: test build: preparing testbed 89s Reading package lists... 89s Building dependency tree... 89s Reading state information... 89s Solving dependencies... 89s Some packages could not be installed. This may mean that you have 89s requested an impossible situation or if you are using the unstable 89s distribution that some required packages have not yet been created 89s or been moved out of Incoming. 89s The following information may help to resolve the situation: 89s 89s The following packages have unmet dependencies: 89s satisfy:command-line : Depends: libdockapp-dev:i386 but it is not installable 89s Depends: libxext-dev but it is not going to be installed 89s Depends: pkg-config 89s Depends: build-essential:amd64 89s Depends: crossbuild-essential-i386:amd64 89s Depends: libc-dev:i386 89s Depends: libstdc++-dev:i386 89s E: Unable to satisfy dependencies. Reached two conflicting assignments: 89s 1. satisfy:command-line:amd64=1 is selected for install 89s 2. satisfy:command-line:amd64 Depends libdockapp-dev:i386 89s but none of the choices are installable: 89s [no choices] 89s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 90s Reading package lists... 90s Building dependency tree... 90s Reading state information... 90s Solving dependencies... 90s Some packages could not be installed. This may mean that you have 90s requested an impossible situation or if you are using the unstable 90s distribution that some required packages have not yet been created 90s or been moved out of Incoming. 90s The following information may help to resolve the situation: 90s 90s The following packages have unmet dependencies: 90s satisfy:command-line : Depends: libdockapp-dev:i386 but it is not installable 90s Depends: libxext-dev but it is not going to be installed 90s Depends: pkg-config 90s Depends: build-essential:amd64 90s Depends: crossbuild-essential-i386:amd64 90s Depends: libc-dev:i386 90s Depends: libstdc++-dev:i386 90s E: Unable to satisfy dependencies. Reached two conflicting assignments: 90s 1. satisfy:command-line:amd64=1 is selected for install 90s 2. satisfy:command-line:amd64 Depends libdockapp-dev:i386 90s but none of the choices are installable: 90s [no choices] 90s build FAIL badpkg 90s blame: libdockapp 90s 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. 90s autopkgtest [12:58:01]: @@@@@@@@@@@@@@@@@@@@ summary 90s build FAIL badpkg 90s blame: libdockapp 90s 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.