0s autopkgtest [15:31:28]: starting date and time: 2026-02-04 15:31:28+0000 0s autopkgtest [15:31:28]: git checkout: 508d4a25 a-v-ssh wait_for_ssh: demote "ssh connection failed" to a debug message 0s autopkgtest [15:31:28]: host juju-7f2275-prod-proposed-migration-environment-9; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.b5bnaxye/out --timeout-copy=6000 --setup-commands 'ln -s /dev/null /etc/systemd/system/bluetooth.service; printf "http_proxy=http://squid.internal:3128\nhttps_proxy=http://squid.internal:3128\nno_proxy=127.0.0.1,127.0.1.1,localhost,localdomain,internal,login.ubuntu.com,archive.ubuntu.com,ports.ubuntu.com,security.ubuntu.com,ddebs.ubuntu.com,changelogs.ubuntu.com,keyserver.ubuntu.com,launchpadlibrarian.net,launchpadcontent.net,launchpad.net,keystone.ps5.canonical.com,objectstorage.prodstack5.canonical.com,radosgw.ps5.canonical.com\n" >> /etc/environment' --apt-pocket=proposed=src:pymatgen,src:sphinx-rtd-theme --apt-upgrade custodian --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 '--env=ADT_TEST_TRIGGERS=pymatgen/2025.10.7+dfsg1-1ubuntu1 sphinx-rtd-theme/3.1.0+dfsg-1' -- lxd -r lxd-armhf-10.145.243.230 lxd-armhf-10.145.243.230:autopkgtest/ubuntu/resolute/armhf 27s autopkgtest [15:31:55]: testbed dpkg architecture: armhf 29s autopkgtest [15:31:57]: testbed apt version: 3.1.14 33s autopkgtest [15:32:01]: @@@@@@@@@@@@@@@@@@@@ test bed setup 35s autopkgtest [15:32:03]: testbed release detected to be: None 42s autopkgtest [15:32:10]: updating testbed package index (apt update) 44s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 44s Get:2 http://ftpmaster.internal/ubuntu resolute InRelease [124 kB] 44s Get:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease [124 kB] 45s Get:4 http://ftpmaster.internal/ubuntu resolute-security InRelease [124 kB] 45s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [230 kB] 45s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [33.2 kB] 45s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [1714 kB] 45s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [5260 B] 45s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main armhf Packages [254 kB] 45s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/universe armhf Packages [1426 kB] 45s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse armhf Packages [8936 B] 45s Get:12 http://ftpmaster.internal/ubuntu resolute/multiverse Sources [310 kB] 45s Get:13 http://ftpmaster.internal/ubuntu resolute/main Sources [1399 kB] 45s Get:14 http://ftpmaster.internal/ubuntu resolute/universe Sources [21.3 MB] 45s Get:15 http://ftpmaster.internal/ubuntu resolute/main armhf Packages [1374 kB] 45s Get:16 http://ftpmaster.internal/ubuntu resolute/universe armhf Packages [15.3 MB] 49s Fetched 43.9 MB in 5s (8188 kB/s) 51s Reading package lists... 57s autopkgtest [15:32:25]: upgrading testbed (apt dist-upgrade and autopurge) 58s Reading package lists... 59s Building dependency tree... 59s Reading state information... 60s Calculating upgrade... 61s The following packages will be upgraded: 61s libmd0 61s 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 61s Need to get 23.4 kB of archives. 61s After this operation, 0 B of additional disk space will be used. 61s Get:1 http://ftpmaster.internal/ubuntu resolute/main armhf libmd0 armhf 1.1.0-2build4 [23.4 kB] 62s Fetched 23.4 kB in 0s (84.8 kB/s) 62s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 68395 files and directories currently installed.) 62s Preparing to unpack .../libmd0_1.1.0-2build4_armhf.deb ... 62s Unpacking libmd0:armhf (1.1.0-2build4) over (1.1.0-2build3) ... 62s Setting up libmd0:armhf (1.1.0-2build4) ... 62s Processing triggers for libc-bin (2.42-2ubuntu4) ... 64s Reading package lists... 65s Building dependency tree... 65s Reading state information... 65s Solving dependencies... 66s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 68s autopkgtest [15:32:36]: rebooting testbed after setup commands that affected boot 108s autopkgtest [15:33:16]: testbed running kernel: Linux 6.8.0-87-generic #88~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Oct 14 14:00:09 UTC 2 132s autopkgtest [15:33:40]: @@@@@@@@@@@@@@@@@@@@ apt-source custodian 148s Get:1 http://ftpmaster.internal/ubuntu resolute/universe custodian 2024.10.16-1 (dsc) [2442 B] 148s Get:2 http://ftpmaster.internal/ubuntu resolute/universe custodian 2024.10.16-1 (tar) [51.2 MB] 148s Get:3 http://ftpmaster.internal/ubuntu resolute/universe custodian 2024.10.16-1 (diff) [8360 B] 148s gpgv: Signature made Sat Feb 15 20:44:02 2025 UTC 148s gpgv: using RSA key 23C9A93E585819E9126D0A36573EF1E4BD5A01FA 148s gpgv: Can't check signature: No public key 148s dpkg-source: warning: cannot verify inline signature for ./custodian_2024.10.16-1.dsc: no acceptable signature found 150s autopkgtest [15:33:58]: testing package custodian version 2024.10.16-1 152s autopkgtest [15:34:00]: build not needed 168s autopkgtest [15:34:16]: test test-custodian: preparing testbed 169s Reading package lists... 170s Building dependency tree... 170s Reading state information... 170s Solving dependencies... 170s Some packages could not be installed. This may mean that you have 170s requested an impossible situation or if you are using the unstable 170s distribution that some required packages have not yet been created 170s or been moved out of Incoming. 170s The following information may help to resolve the situation: 170s 170s The following packages have unmet dependencies: 171s satisfy:command-line : Depends: python3-custodian but it is not going to be installed 171s Depends: python3-pymatgen but it is not installable 171s Depends: python3-pytest but it is not going to be installed 171s Depends: python3-all but it is not going to be installed 171s E: Unable to satisfy dependencies. Reached two conflicting assignments: 171s 1. satisfy:command-line:armhf=1 is selected for install 171s 2. satisfy:command-line:armhf Depends python3-pymatgen 171s but none of the choices are installable: 171s [no choices] 171s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 175s Reading package lists... 175s Building dependency tree... 175s Reading state information... 176s Solving dependencies... 176s Some packages could not be installed. This may mean that you have 176s requested an impossible situation or if you are using the unstable 176s distribution that some required packages have not yet been created 176s or been moved out of Incoming. 176s The following information may help to resolve the situation: 176s 176s The following packages have unmet dependencies: 177s satisfy:command-line : Depends: python3-custodian but it is not going to be installed 177s Depends: python3-pymatgen but it is not installable 177s Depends: python3-pytest but it is not going to be installed 177s Depends: python3-all but it is not going to be installed 177s E: Unable to satisfy dependencies. Reached two conflicting assignments: 177s 1. satisfy:command-line:armhf=1 is selected for install 177s 2. satisfy:command-line:armhf Depends python3-pymatgen 177s but none of the choices are installable: 177s [no choices] 177s test-custodian FAIL badpkg 177s blame: custodian 177s 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. 177s autopkgtest [15:34:25]: @@@@@@@@@@@@@@@@@@@@ summary 177s test-custodian FAIL badpkg 177s blame: custodian 177s 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.