0s autopkgtest [13:04:34]: starting date and time: 2026-01-29 13:04:34+0000 0s autopkgtest [13:04:34]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [13:04:34]: host juju-7f2275-prod-proposed-migration-environment-2; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work._9asbrzi/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 libhangul --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-10.secgroup --name adt-resolute-i386-libhangul-20260129-130434-juju-7f2275-prod-proposed-migration-environment-2-d7289908-ed8c-43f9-92b3-4f63a4dc0603 --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-libhangul-20260129-130434-juju-7f2275-prod-proposed-migration-environment-2-d7289908-ed8c-43f9-92b3-4f63a4dc0603 from image adt/ubuntu-resolute-amd64-server-20260129.img (UUID c052dd91-e629-41e8-9bf0-bad94c4bd713)... 81s autopkgtest [13:05:55]: testbed dpkg architecture: amd64 81s autopkgtest [13:05:55]: testbed apt version: 3.1.14 81s autopkgtest [13:05:55]: @@@@@@@@@@@@@@@@@@@@ test bed setup 81s autopkgtest [13:05:55]: testbed release detected to be: None 82s autopkgtest [13:05:56]: updating testbed package index (apt update) 82s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 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 82s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [2820 B] 82s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [25.4 kB] 82s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [106 kB] 82s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [1074 kB] 83s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 Packages [132 kB] 83s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/main i386 Packages [114 kB] 83s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 c-n-f Metadata [4360 B] 83s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 Packages [12.3 kB] 83s Get:13 http://ftpmaster.internal/ubuntu resolute-proposed/restricted i386 Packages [3696 B] 83s Get:14 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 c-n-f Metadata [336 B] 83s Get:15 http://ftpmaster.internal/ubuntu resolute-proposed/universe i386 Packages [357 kB] 83s Get:16 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 Packages [872 kB] 83s Get:17 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 c-n-f Metadata [23.0 kB] 83s Get:18 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse i386 Packages [3336 B] 83s Get:19 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 Packages [23.2 kB] 83s Get:20 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 c-n-f Metadata [1036 B] 83s Fetched 2880 kB in 1s (2992 kB/s) 84s Reading package lists... 85s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 85s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 85s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 85s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 85s Reading package lists... 85s Reading package lists... 85s Building dependency tree... 85s Reading state information... 85s Calculating upgrade... 86s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 86s autopkgtest [13:06:00]: upgrading testbed (apt dist-upgrade and autopurge) 86s Reading package lists... 86s Building dependency tree... 86s Reading state information... 86s Calculating upgrade... 86s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 86s Reading package lists... 86s Building dependency tree... 86s Reading state information... 86s Solving dependencies... 87s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 89s autopkgtest [13:06:03]: testbed running kernel: Linux 6.18.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 12 16:49:02 UTC 2026 89s autopkgtest [13:06:03]: @@@@@@@@@@@@@@@@@@@@ apt-source libhangul 92s Get:1 http://ftpmaster.internal/ubuntu resolute/main libhangul 0.2.0-1 (dsc) [2174 B] 92s Get:2 http://ftpmaster.internal/ubuntu resolute/main libhangul 0.2.0-1 (tar) [4019 kB] 92s Get:3 http://ftpmaster.internal/ubuntu resolute/main libhangul 0.2.0-1 (diff) [36.7 kB] 92s gpgv: Signature made Sun May 11 13:05:18 2025 UTC 92s gpgv: using RSA key A27CBEBA35256865380E0CC9EC1879D076D8AB48 92s gpgv: Can't check signature: No public key 92s dpkg-source: warning: cannot verify inline signature for ./libhangul_0.2.0-1.dsc: no acceptable signature found 92s autopkgtest [13:06:06]: testing package libhangul version 0.2.0-1 93s autopkgtest [13:06:07]: build not needed 95s autopkgtest [13:06:09]: test run-test: preparing testbed 95s Reading package lists... 95s Building dependency tree... 95s Reading state information... 95s Solving dependencies... 95s Some packages could not be installed. This may mean that you have 95s requested an impossible situation or if you are using the unstable 95s distribution that some required packages have not yet been created 95s or been moved out of Incoming. 95s The following information may help to resolve the situation: 95s 95s The following packages have unmet dependencies: 95s satisfy:command-line : Depends: libhangul-dev:i386 but it is not installable 95s Depends: check but it is not going to be installed 95s Depends: pkg-config 95s Depends: build-essential:amd64 95s Depends: crossbuild-essential-i386:amd64 95s Depends: libc-dev:i386 95s Depends: libstdc++-dev:i386 95s E: Unable to satisfy dependencies. Reached two conflicting assignments: 95s 1. satisfy:command-line:amd64=1 is selected for install 95s 2. satisfy:command-line:amd64 Depends libhangul-dev:i386 95s but none of the choices are installable: 95s [no choices] 95s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 96s Reading package lists... 96s Building dependency tree... 96s Reading state information... 96s Solving dependencies... 96s Some packages could not be installed. This may mean that you have 96s requested an impossible situation or if you are using the unstable 96s distribution that some required packages have not yet been created 96s or been moved out of Incoming. 96s The following information may help to resolve the situation: 96s 96s The following packages have unmet dependencies: 96s satisfy:command-line : Depends: libhangul-dev:i386 but it is not installable 96s Depends: check but it is not going to be installed 96s Depends: pkg-config 96s Depends: build-essential:amd64 96s Depends: crossbuild-essential-i386:amd64 96s Depends: libc-dev:i386 96s Depends: libstdc++-dev:i386 96s E: Unable to satisfy dependencies. Reached two conflicting assignments: 96s 1. satisfy:command-line:amd64=1 is selected for install 96s 2. satisfy:command-line:amd64 Depends libhangul-dev:i386 96s but none of the choices are installable: 96s [no choices] 96s run-test FAIL badpkg 96s blame: libhangul 96s 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. 96s autopkgtest [13:06:10]: @@@@@@@@@@@@@@@@@@@@ summary 96s run-test FAIL badpkg 96s blame: libhangul 96s 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.