0s autopkgtest [11:57:18]: starting date and time: 2026-01-29 11:57:18+0000 0s autopkgtest [11:57:18]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [11:57:18]: host juju-7f2275-prod-proposed-migration-environment-15; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.t1a0_16a/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 adasockets --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-15@sto01-9.secgroup --name adt-resolute-i386-adasockets-20260129-115718-juju-7f2275-prod-proposed-migration-environment-15-a587e7b0-49c6-41b3-a720-88dd95b9e6b2 --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-adasockets-20260129-115718-juju-7f2275-prod-proposed-migration-environment-15-a587e7b0-49c6-41b3-a720-88dd95b9e6b2 from image adt/ubuntu-resolute-amd64-server-20260129.img (UUID c052dd91-e629-41e8-9bf0-bad94c4bd713)... 79s autopkgtest [11:58:37]: testbed dpkg architecture: amd64 79s autopkgtest [11:58:37]: testbed apt version: 3.1.14 79s autopkgtest [11:58:37]: @@@@@@@@@@@@@@@@@@@@ test bed setup 79s autopkgtest [11:58:37]: testbed release detected to be: None 80s autopkgtest [11:58:38]: 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/main Sources [106 kB] 80s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [25.4 kB] 80s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [2820 B] 80s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [1007 kB] 81s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 Packages [129 kB] 81s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/main i386 Packages [112 kB] 81s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 c-n-f Metadata [4360 B] 81s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 Packages [12.3 kB] 81s Get:13 http://ftpmaster.internal/ubuntu resolute-proposed/restricted i386 Packages [3696 B] 81s Get:14 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 c-n-f Metadata [336 B] 81s Get:15 http://ftpmaster.internal/ubuntu resolute-proposed/universe i386 Packages [312 kB] 81s Get:16 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 Packages [725 kB] 81s Get:17 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 c-n-f Metadata [23.0 kB] 81s Get:18 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 Packages [23.2 kB] 81s 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 2616 kB in 1s (3183 kB/s) 82s Reading package lists... 83s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 83s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 83s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 83s 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... 84s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 84s autopkgtest [11:58:42]: upgrading testbed (apt dist-upgrade and autopurge) 84s Reading package lists... 84s Building dependency tree... 84s Reading state information... 84s Calculating upgrade... 84s 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. 87s autopkgtest [11:58:45]: testbed running kernel: Linux 6.18.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 12 16:49:02 UTC 2026 87s autopkgtest [11:58:45]: @@@@@@@@@@@@@@@@@@@@ apt-source adasockets 88s Get:1 http://ftpmaster.internal/ubuntu resolute/universe adasockets 1.14-3build2 (dsc) [2242 B] 88s Get:2 http://ftpmaster.internal/ubuntu resolute/universe adasockets 1.14-3build2 (tar) [70.3 kB] 88s Get:3 http://ftpmaster.internal/ubuntu resolute/universe adasockets 1.14-3build2 (diff) [9572 B] 89s gpgv: Signature made Sun Sep 21 05:46:35 2025 UTC 89s gpgv: using RSA key 568BF22A66337CBFC9A6B9B72C83DBC8E9BD0E37 89s gpgv: Can't check signature: No public key 89s dpkg-source: warning: cannot verify inline signature for ./adasockets_1.14-3build2.dsc: no acceptable signature found 89s autopkgtest [11:58:47]: testing package adasockets version 1.14-3build2 89s autopkgtest [11:58:47]: build not needed 89s autopkgtest [11:58:47]: test link-with-shared: preparing testbed 89s Reading package lists... 89s Building dependency tree... 89s 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: gprbuild but it is not going to be installed 90s Depends: libadasockets-dev:i386 but it is not installable 90s Depends: libadasockets-doc but it is not going to be installed 90s Depends: pkg-config 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 libadasockets-dev:i386 90s but none of the choices are installable: 90s [no choices] 90s 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: gprbuild but it is not going to be installed 90s Depends: libadasockets-dev:i386 but it is not installable 90s Depends: libadasockets-doc but it is not going to be installed 90s Depends: pkg-config 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 libadasockets-dev:i386 90s but none of the choices are installable: 90s [no choices] 90s autopkgtest [11:58:48]: @@@@@@@@@@@@@@@@@@@@ summary 90s link-with-shared FAIL badpkg 90s blame: adasockets 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 link-with-shared FAIL badpkg 90s blame: adasockets 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.