0s autopkgtest [12:55:30]: starting date and time: 2026-01-29 12:55:30+0000 0s autopkgtest [12:55:30]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [12:55:30]: host juju-7f2275-prod-proposed-migration-environment-15; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.4j0_v3b7/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 libdap --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-5.secgroup --name adt-resolute-i386-libdap-20260129-125530-juju-7f2275-prod-proposed-migration-environment-15-c6a12115-8f81-4728-bcde-524a61a3f7d4 --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-libdap-20260129-125530-juju-7f2275-prod-proposed-migration-environment-15-c6a12115-8f81-4728-bcde-524a61a3f7d4 from image adt/ubuntu-resolute-amd64-server-20260129.img (UUID c052dd91-e629-41e8-9bf0-bad94c4bd713)... 79s autopkgtest [12:56:49]: testbed dpkg architecture: amd64 79s autopkgtest [12:56:49]: testbed apt version: 3.1.14 79s autopkgtest [12:56:49]: @@@@@@@@@@@@@@@@@@@@ test bed setup 79s autopkgtest [12:56:49]: testbed release detected to be: None 80s autopkgtest [12:56: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/universe Sources [1074 kB] 80s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [106 kB] 80s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [25.4 kB] 80s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [2820 B] 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 i386 Packages [3696 B] 80s Get:13 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 Packages [12.3 kB] 80s 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 amd64 Packages [872 kB] 81s Get:16 http://ftpmaster.internal/ubuntu resolute-proposed/universe i386 Packages [357 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 i386 Packages [3336 B] 81s Get:19 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 Packages [23.2 kB] 81s Get:20 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 c-n-f Metadata [1036 B] 81s Fetched 2880 kB in 1s (3888 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:56:53]: upgrading testbed (apt dist-upgrade and autopurge) 83s Reading package lists... 83s Building dependency tree... 83s 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. 86s autopkgtest [12:56:56]: 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:56:56]: @@@@@@@@@@@@@@@@@@@@ apt-source libdap 89s Get:1 http://ftpmaster.internal/ubuntu resolute/universe libdap 3.21.1-2build1 (dsc) [2600 B] 89s Get:2 http://ftpmaster.internal/ubuntu resolute/universe libdap 3.21.1-2build1 (tar) [1621 kB] 89s Get:3 http://ftpmaster.internal/ubuntu resolute/universe libdap 3.21.1-2build1 (diff) [13.9 kB] 89s gpgv: Signature made Thu May 22 08:23:59 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 ./libdap_3.21.1-2build1.dsc: no acceptable signature found 89s autopkgtest [12:56:59]: testing package libdap version 3.21.1-2build1 90s autopkgtest [12:57:00]: build not needed 93s autopkgtest [12:57:03]: test command1: preparing testbed 94s Reading package lists... 94s Building dependency tree... 94s Reading state information... 94s Solving dependencies... 94s Some packages could not be installed. This may mean that you have 94s requested an impossible situation or if you are using the unstable 94s distribution that some required packages have not yet been created 94s or been moved out of Incoming. 94s The following information may help to resolve the situation: 94s 94s The following packages have unmet dependencies: 94s satisfy:command-line : Depends: libdap-dev:i386 but it is not installable 94s Depends: pkg-config 94s E: Unable to satisfy dependencies. Reached two conflicting assignments: 94s 1. satisfy:command-line:amd64=1 is selected for install 94s 2. satisfy:command-line:amd64 Depends libdap-dev:i386 94s but none of the choices are installable: 94s [no choices] 94s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 94s Reading package lists... 94s Building dependency tree... 94s Reading state information... 94s Solving dependencies... 94s Some packages could not be installed. This may mean that you have 94s requested an impossible situation or if you are using the unstable 94s distribution that some required packages have not yet been created 94s or been moved out of Incoming. 94s The following information may help to resolve the situation: 94s 94s The following packages have unmet dependencies: 94s satisfy:command-line : Depends: libdap-dev:i386 but it is not installable 94s Depends: pkg-config 94s E: Unable to satisfy dependencies. Reached two conflicting assignments: 94s 1. satisfy:command-line:amd64=1 is selected for install 94s 2. satisfy:command-line:amd64 Depends libdap-dev:i386 94s but none of the choices are installable: 94s [no choices] 94s autopkgtest [12:57:04]: test command2: preparing testbed 94s command1 FAIL badpkg 94s blame: libdap 94s 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. 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: libdap-dev:i386 but it is not installable 95s Depends: pkg-config 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 libdap-dev:i386 95s but none of the choices are installable: 95s [no choices] 95s command2 FAIL badpkg 95s blame: libdap 95s 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. 95s autopkgtest [12:57:05]: test command3: 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: libdap-dev:i386 but it is not installable 95s Depends: pkg-config 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 libdap-dev:i386 95s but none of the choices are installable: 95s [no choices] 95s command3 FAIL badpkg 95s blame: libdap 95s 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. 95s autopkgtest [12:57:05]: test command4: preparing testbed 114s Creating nova instance adt-resolute-i386-libdap-20260129-125530-juju-7f2275-prod-proposed-migration-environment-15-c6a12115-8f81-4728-bcde-524a61a3f7d4 from image adt/ubuntu-resolute-amd64-server-20260129.img (UUID c052dd91-e629-41e8-9bf0-bad94c4bd713)... 187s autopkgtest [12:58:37]: testbed dpkg architecture: amd64 187s autopkgtest [12:58:37]: testbed apt version: 3.1.14 188s autopkgtest [12:58:38]: @@@@@@@@@@@@@@@@@@@@ test bed setup 188s autopkgtest [12:58:38]: testbed release detected to be: resolute 188s autopkgtest [12:58:38]: updating testbed package index (apt update) 188s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 189s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 189s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 189s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 189s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [2820 B] 189s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [106 kB] 189s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [25.4 kB] 189s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [1074 kB] 189s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main i386 Packages [114 kB] 189s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 Packages [132 kB] 189s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 c-n-f Metadata [4360 B] 189s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 Packages [12.3 kB] 189s Get:13 http://ftpmaster.internal/ubuntu resolute-proposed/restricted i386 Packages [3696 B] 189s Get:14 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 c-n-f Metadata [336 B] 189s Get:15 http://ftpmaster.internal/ubuntu resolute-proposed/universe i386 Packages [357 kB] 189s Get:16 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 Packages [872 kB] 189s Get:17 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 c-n-f Metadata [23.0 kB] 189s Get:18 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 Packages [23.2 kB] 189s Get:19 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse i386 Packages [3336 B] 189s Get:20 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 c-n-f Metadata [1036 B] 190s Fetched 2880 kB in 1s (3228 kB/s) 190s Reading package lists... 191s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 191s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 191s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 191s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 192s Reading package lists... 192s Reading package lists... 192s Building dependency tree... 192s Reading state information... 192s Calculating upgrade... 192s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 192s autopkgtest [12:58:42]: upgrading testbed (apt dist-upgrade and autopurge) 192s Reading package lists... 192s Building dependency tree... 192s Reading state information... 193s Calculating upgrade... 193s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 193s Reading package lists... 193s Building dependency tree... 193s Reading state information... 193s Solving dependencies... 193s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 195s Reading package lists... 195s Building dependency tree... 195s Reading state information... 195s Solving dependencies... 195s Some packages could not be installed. This may mean that you have 195s requested an impossible situation or if you are using the unstable 195s distribution that some required packages have not yet been created 195s or been moved out of Incoming. 195s The following information may help to resolve the situation: 195s 195s The following packages have unmet dependencies: 195s satisfy:command-line : Depends: libdap-bin:i386 but it is not installable 195s E: Unable to satisfy dependencies. Reached two conflicting assignments: 195s 1. satisfy:command-line:amd64=1 is selected for install 195s 2. satisfy:command-line:amd64 Depends libdap-bin:i386 195s but none of the choices are installable: 195s [no choices] 195s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 196s Reading package lists... 196s Building dependency tree... 196s Reading state information... 196s Solving dependencies... 196s Some packages could not be installed. This may mean that you have 196s requested an impossible situation or if you are using the unstable 196s distribution that some required packages have not yet been created 196s or been moved out of Incoming. 196s The following information may help to resolve the situation: 196s 196s The following packages have unmet dependencies: 196s satisfy:command-line : Depends: libdap-bin:i386 but it is not installable 196s E: Unable to satisfy dependencies. Reached two conflicting assignments: 196s 1. satisfy:command-line:amd64=1 is selected for install 196s 2. satisfy:command-line:amd64 Depends libdap-bin:i386 196s but none of the choices are installable: 196s [no choices] 196s command4 FAIL badpkg 196s blame: libdap 196s 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. 196s autopkgtest [12:58:46]: @@@@@@@@@@@@@@@@@@@@ summary 196s command1 FAIL badpkg 196s blame: libdap 196s 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. 196s command2 FAIL badpkg 196s blame: libdap 196s 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. 196s command3 FAIL badpkg 196s blame: libdap 196s 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. 196s command4 FAIL badpkg 196s blame: libdap 196s 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.