0s autopkgtest [17:31:27]: starting date and time: 2025-10-29 17:31:27+0000 0s autopkgtest [17:31:27]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [17:31:27]: host juju-7f2275-prod-proposed-migration-environment-2; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.mj96g8sq/out --timeout-copy=6000 -a i386 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:netcdf4-python --apt-upgrade basemap --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 --env=ADT_TEST_TRIGGERS=netcdf4-python/1.7.3-1 -- 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-3.secgroup --name adt-resolute-i386-basemap-20251029-173127-juju-7f2275-prod-proposed-migration-environment-2-072e1176-d81b-460d-ae07-ecceea448ae1 --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/ 3s Creating nova instance adt-resolute-i386-basemap-20251029-173127-juju-7f2275-prod-proposed-migration-environment-2-072e1176-d81b-460d-ae07-ecceea448ae1 from image adt/ubuntu-resolute-amd64-server-20251029.img (UUID 2345c089-5627-4919-bdd0-dff8360b43c0)... 31s autopkgtest [17:31:58]: testbed dpkg architecture: amd64 31s autopkgtest [17:31:58]: testbed apt version: 3.1.11 32s autopkgtest [17:31:59]: @@@@@@@@@@@@@@@@@@@@ test bed setup 32s autopkgtest [17:31:59]: testbed release detected to be: None 33s autopkgtest [17:32:00]: updating testbed package index (apt update) 33s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [87.8 kB] 33s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 33s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 33s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 33s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [205 kB] 33s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [5856 B] 33s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [3643 kB] 34s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [70.5 kB] 34s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 Packages [287 kB] 34s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/main i386 Packages [185 kB] 34s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 c-n-f Metadata [5760 B] 34s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/restricted i386 Packages [4212 B] 34s Get:13 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 Packages [28.6 kB] 34s Get:14 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 c-n-f Metadata [336 B] 34s Get:15 http://ftpmaster.internal/ubuntu resolute-proposed/universe i386 Packages [1131 kB] 34s Get:16 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 Packages [2559 kB] 34s Get:17 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 c-n-f Metadata [71.9 kB] 34s Get:18 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 Packages [47.4 kB] 34s Get:19 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse i386 Packages [19.9 kB] 34s Get:20 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 c-n-f Metadata [2072 B] 35s Fetched 8354 kB in 2s (5302 kB/s) 35s Reading package lists... 36s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 36s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 36s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 36s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 37s Reading package lists... 37s Reading package lists... 37s Building dependency tree... 37s Reading state information... 37s Calculating upgrade... 37s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 37s autopkgtest [17:32:04]: upgrading testbed (apt dist-upgrade and autopurge) 37s Reading package lists... 38s Building dependency tree... 38s Reading state information... 38s Calculating upgrade... 38s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 38s Reading package lists... 38s Building dependency tree... 38s Reading state information... 38s Solving dependencies... 38s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 41s autopkgtest [17:32:08]: testbed running kernel: Linux 6.17.0-5-generic #5-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 22 10:00:33 UTC 2025 41s autopkgtest [17:32:08]: @@@@@@@@@@@@@@@@@@@@ apt-source basemap 48s Get:1 http://ftpmaster.internal/ubuntu resolute/universe basemap 1.4.1-1build2 (dsc) [2552 B] 48s Get:2 http://ftpmaster.internal/ubuntu resolute/universe basemap 1.4.1-1build2 (tar) [130 MB] 48s Get:3 http://ftpmaster.internal/ubuntu resolute/universe basemap 1.4.1-1build2 (diff) [31.2 kB] 48s gpgv: Signature made Tue Oct 21 17:41:12 2025 UTC 48s gpgv: using RSA key 25E3FF2D7F469DBE7D0D4E50AFCFEC8E669CE1C2 48s gpgv: Can't check signature: No public key 48s dpkg-source: warning: cannot verify inline signature for ./basemap_1.4.1-1build2.dsc: no acceptable signature found 51s autopkgtest [17:32:18]: testing package basemap version 1.4.1-1build2 51s autopkgtest [17:32:18]: build not needed 70s autopkgtest [17:32:37]: test run-unit-test: preparing testbed 70s Reading package lists... 70s Building dependency tree... 70s Reading state information... 70s Solving dependencies... 70s Some packages could not be installed. This may mean that you have 70s requested an impossible situation or if you are using the unstable 70s distribution that some required packages have not yet been created 70s or been moved out of Incoming. 70s The following information may help to resolve the situation: 70s 70s The following packages have unmet dependencies: 70s satisfy:command-line : Depends: python-mpltoolkits.basemap-data but it is not going to be installed 70s Depends: python-mpltoolkits.basemap-doc but it is not going to be installed 70s Depends: python3-mpltoolkits.basemap:i386 but it is not installable 70s Depends: python3-netcdf4 but it is not going to be installed 70s Depends: xvfb 70s E: Unable to satisfy dependencies. Reached two conflicting decisions: 70s 1. satisfy:command-line:amd64=1 is selected for install 70s 2. satisfy:command-line:amd64 Depends python3-mpltoolkits.basemap:i386 70s but none of the choices are installable: 70s [no choices] 70s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 70s Reading package lists... 71s Building dependency tree... 71s Reading state information... 71s Solving dependencies... 71s Some packages could not be installed. This may mean that you have 71s requested an impossible situation or if you are using the unstable 71s distribution that some required packages have not yet been created 71s or been moved out of Incoming. 71s The following information may help to resolve the situation: 71s 71s The following packages have unmet dependencies: 71s satisfy:command-line : Depends: python-mpltoolkits.basemap-data but it is not going to be installed 71s Depends: python-mpltoolkits.basemap-doc but it is not going to be installed 71s Depends: python3-mpltoolkits.basemap:i386 but it is not installable 71s Depends: python3-netcdf4 but it is not going to be installed 71s Depends: xvfb 71s E: Unable to satisfy dependencies. Reached two conflicting decisions: 71s 1. satisfy:command-line:amd64=1 is selected for install 71s 2. satisfy:command-line:amd64 Depends python3-mpltoolkits.basemap:i386 71s but none of the choices are installable: 71s [no choices] 71s run-unit-test FAIL badpkg 71s blame: basemap 71s 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. 71s autopkgtest [17:32:38]: @@@@@@@@@@@@@@@@@@@@ summary 71s run-unit-test FAIL badpkg 71s blame: basemap 71s 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.