0s autopkgtest [05:02:20]: starting date and time: 2026-02-02 05:02:20+0000 0s autopkgtest [05:02:20]: git checkout: 508d4a25 a-v-ssh wait_for_ssh: demote "ssh connection failed" to a debug message 0s autopkgtest [05:02:20]: host juju-7f2275-prod-proposed-migration-environment-9; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.imi1xcbu/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:fenics-dolfinx,src:nanobind,src:sphinx-rtd-theme --apt-upgrade adios4dolfinx --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 '--env=ADT_TEST_TRIGGERS=fenics-dolfinx/1:0.10.0.post5-5build1 nanobind/2.10.2-2 sphinx-rtd-theme/3.1.0+dfsg-1' -- lxd -r lxd-armhf-10.145.243.115 lxd-armhf-10.145.243.115:autopkgtest/ubuntu/resolute/armhf 22s autopkgtest [05:02:42]: testbed dpkg architecture: armhf 24s autopkgtest [05:02:44]: testbed apt version: 3.1.14 28s autopkgtest [05:02:48]: @@@@@@@@@@@@@@@@@@@@ test bed setup 30s autopkgtest [05:02:50]: testbed release detected to be: None 37s autopkgtest [05:02:57]: updating testbed package index (apt update) 39s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 39s Get:2 http://ftpmaster.internal/ubuntu resolute InRelease [124 kB] 39s Get:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease [124 kB] 40s Get:4 http://ftpmaster.internal/ubuntu resolute-security InRelease [124 kB] 40s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [28.6 kB] 40s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [2816 B] 40s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [1274 kB] 40s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [101 kB] 40s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main armhf Packages [112 kB] 40s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/universe armhf Packages [968 kB] 40s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse armhf Packages [6540 B] 40s Get:12 http://ftpmaster.internal/ubuntu resolute/universe Sources [21.3 MB] 42s Get:13 http://ftpmaster.internal/ubuntu resolute/main Sources [1408 kB] 42s Get:14 http://ftpmaster.internal/ubuntu resolute/main armhf Packages [1374 kB] 42s Get:15 http://ftpmaster.internal/ubuntu resolute/universe armhf Packages [14.8 MB] 46s Fetched 41.9 MB in 7s (6178 kB/s) 47s Reading package lists... 53s autopkgtest [05:03:13]: upgrading testbed (apt dist-upgrade and autopurge) 55s Reading package lists... 55s Building dependency tree... 55s Reading state information... 55s Calculating upgrade... 56s The following packages will be upgraded: 56s libgpg-error-l10n libgpg-error0 56s 2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 56s Need to get 79.1 kB of archives. 56s After this operation, 1024 B of additional disk space will be used. 56s Get:1 http://ftpmaster.internal/ubuntu resolute/main armhf libgpg-error-l10n all 1.58-2 [9244 B] 57s Get:2 http://ftpmaster.internal/ubuntu resolute/main armhf libgpg-error0 armhf 1.58-2 [69.8 kB] 57s Fetched 79.1 kB in 1s (85.8 kB/s) 57s (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 ... 68394 files and directories currently installed.) 57s Preparing to unpack .../libgpg-error-l10n_1.58-2_all.deb ... 57s Unpacking libgpg-error-l10n (1.58-2) over (1.58-1build1) ... 57s Preparing to unpack .../libgpg-error0_1.58-2_armhf.deb ... 57s Unpacking libgpg-error0:armhf (1.58-2) over (1.58-1build1) ... 57s Setting up libgpg-error0:armhf (1.58-2) ... 57s Setting up libgpg-error-l10n (1.58-2) ... 57s Processing triggers for libc-bin (2.42-2ubuntu4) ... 61s Reading package lists... 62s Building dependency tree... 62s Reading state information... 62s Solving dependencies... 62s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 64s autopkgtest [05:03:24]: rebooting testbed after setup commands that affected boot 106s autopkgtest [05:04:06]: 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 133s autopkgtest [05:04:33]: @@@@@@@@@@@@@@@@@@@@ apt-source adios4dolfinx 145s Get:1 http://ftpmaster.internal/ubuntu resolute/universe adios4dolfinx 0.10.0.post0-3 (dsc) [2487 B] 145s Get:2 http://ftpmaster.internal/ubuntu resolute/universe adios4dolfinx 0.10.0.post0-3 (tar) [74.5 kB] 145s Get:3 http://ftpmaster.internal/ubuntu resolute/universe adios4dolfinx 0.10.0.post0-3 (diff) [6532 B] 145s gpgv: Signature made Sat Jan 3 01:23:03 2026 UTC 145s gpgv: using RSA key 23C9A93E585819E9126D0A36573EF1E4BD5A01FA 145s gpgv: Can't check signature: No public key 145s dpkg-source: warning: cannot verify inline signature for ./adios4dolfinx_0.10.0.post0-3.dsc: no acceptable signature found 145s autopkgtest [05:04:45]: testing package adios4dolfinx version 0.10.0.post0-3 149s autopkgtest [05:04:49]: build not needed 151s autopkgtest [05:04:51]: test test-adios4dolfinx: preparing testbed 153s Reading package lists... 153s Building dependency tree... 153s Reading state information... 153s Solving dependencies... 153s Some packages could not be installed. This may mean that you have 153s requested an impossible situation or if you are using the unstable 153s distribution that some required packages have not yet been created 153s or been moved out of Incoming. 153s The following information may help to resolve the situation: 153s 153s The following packages have unmet dependencies: 154s satisfy:command-line : Depends: python3-adios4dolfinx but it is not going to be installed 154s Depends: python3-ipyparallel but it is not going to be installed 154s Depends: python3-pytest but it is not going to be installed 154s Depends: python3-all-dev but it is not going to be installed 154s E: Unable to satisfy dependencies. Reached two conflicting assignments: 154s 1. python3-adios2:armhf is selected for install because: 154s 1. satisfy:command-line:armhf=1 is selected for install 154s 2. satisfy:command-line:armhf Depends python3-adios4dolfinx 154s 3. python3-adios4dolfinx:armhf Depends python3-adios2 154s 2. python3-adios2:armhf Depends python3-adios2-serial | python3-adios2-mpi 154s but none of the choices are installable: 154s [no choices] 154s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 157s Reading package lists... 158s Building dependency tree... 158s Reading state information... 158s Solving dependencies... 158s Some packages could not be installed. This may mean that you have 158s requested an impossible situation or if you are using the unstable 158s distribution that some required packages have not yet been created 158s or been moved out of Incoming. 158s The following information may help to resolve the situation: 158s 158s The following packages have unmet dependencies: 159s satisfy:command-line : Depends: python3-adios4dolfinx but it is not going to be installed 159s Depends: python3-ipyparallel but it is not going to be installed 159s Depends: python3-pytest but it is not going to be installed 159s Depends: python3-all-dev but it is not going to be installed 159s E: Unable to satisfy dependencies. Reached two conflicting assignments: 159s 1. python3-adios2:armhf is selected for install because: 159s 1. satisfy:command-line:armhf=1 is selected for install 159s 2. satisfy:command-line:armhf Depends python3-adios4dolfinx 159s 3. python3-adios4dolfinx:armhf Depends python3-adios2 159s 2. python3-adios2:armhf Depends python3-adios2-serial | python3-adios2-mpi 159s but none of the choices are installable: 159s [no choices] 159s test-adios4dolfinx FAIL badpkg 159s blame: adios4dolfinx 159s 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. 159s autopkgtest [05:04:59]: test test-adios4dolfinx-mpi: preparing testbed 161s Reading package lists... 161s Building dependency tree... 161s Reading state information... 162s Solving dependencies... 162s Some packages could not be installed. This may mean that you have 162s requested an impossible situation or if you are using the unstable 162s distribution that some required packages have not yet been created 162s or been moved out of Incoming. 162s The following information may help to resolve the situation: 162s 162s The following packages have unmet dependencies: 162s satisfy:command-line : Depends: python3-adios4dolfinx but it is not going to be installed 162s Depends: python3-ipyparallel but it is not going to be installed 162s Depends: python3-pytest but it is not going to be installed 162s Depends: python3-all-dev but it is not going to be installed 162s E: Unable to satisfy dependencies. Reached two conflicting assignments: 162s 1. python3-adios2:armhf is selected for install because: 162s 1. satisfy:command-line:armhf=1 is selected for install 162s 2. satisfy:command-line:armhf Depends python3-adios4dolfinx 162s 3. python3-adios4dolfinx:armhf Depends python3-adios2 162s 2. python3-adios2:armhf Depends python3-adios2-serial | python3-adios2-mpi 162s but none of the choices are installable: 162s [no choices] 162s test-adios4dolfinx-mpi FAIL badpkg 162s blame: adios4dolfinx 162s 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. 162s autopkgtest [05:05:02]: test test-adios4dolfinx-complex: preparing testbed 164s Reading package lists... 165s Building dependency tree... 165s Reading state information... 165s Solving dependencies... 165s Some packages could not be installed. This may mean that you have 165s requested an impossible situation or if you are using the unstable 165s distribution that some required packages have not yet been created 165s or been moved out of Incoming. 165s The following information may help to resolve the situation: 165s 165s The following packages have unmet dependencies: 165s satisfy:command-line : Depends: python3-adios4dolfinx but it is not going to be installed 165s Depends: python3-dolfinx-complex (>= 1:0.9.0~) but it is not going to be installed 165s Depends: python3-ipyparallel but it is not going to be installed 165s Depends: python3-pytest but it is not going to be installed 165s Depends: python3-all-dev but it is not going to be installed 165s E: Unable to satisfy dependencies. Reached two conflicting assignments: 165s 1. python3-adios4dolfinx:armhf is selected for install because: 165s 1. satisfy:command-line:armhf=1 is selected for install 165s 2. satisfy:command-line:armhf Depends python3-adios4dolfinx 165s 2. python3-adios4dolfinx:armhf Depends python3-adios2-mpi 165s but none of the choices are installable: 165s [no choices] 165s test-adios4dolfinx-complex FAIL badpkg 165s blame: adios4dolfinx 165s 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. 165s autopkgtest [05:05:05]: test test-adios4dolfinx-complex-mpi: preparing testbed 167s Reading package lists... 167s Building dependency tree... 167s Reading state information... 168s Solving dependencies... 168s Some packages could not be installed. This may mean that you have 168s requested an impossible situation or if you are using the unstable 168s distribution that some required packages have not yet been created 168s or been moved out of Incoming. 168s The following information may help to resolve the situation: 168s 168s The following packages have unmet dependencies: 168s satisfy:command-line : Depends: python3-adios4dolfinx but it is not going to be installed 168s Depends: python3-dolfinx-complex (>= 1:0.9.0~) but it is not going to be installed 168s Depends: python3-ipyparallel but it is not going to be installed 168s Depends: python3-pytest but it is not going to be installed 168s Depends: python3-all-dev but it is not going to be installed 168s E: Unable to satisfy dependencies. Reached two conflicting assignments: 168s 1. python3-adios4dolfinx:armhf is selected for install because: 168s 1. satisfy:command-line:armhf=1 is selected for install 168s 2. satisfy:command-line:armhf Depends python3-adios4dolfinx 168s 2. python3-adios4dolfinx:armhf Depends python3-adios2-mpi 168s but none of the choices are installable: 168s [no choices] 168s autopkgtest [05:05:08]: @@@@@@@@@@@@@@@@@@@@ summary 168s test-adios4dolfinx FAIL badpkg 168s blame: adios4dolfinx 168s 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. 168s test-adios4dolfinx-mpi FAIL badpkg 168s blame: adios4dolfinx 168s 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. 168s test-adios4dolfinx-complex FAIL badpkg 168s blame: adios4dolfinx 168s 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. 168s test-adios4dolfinx-complex-mpi FAIL badpkg 168s blame: adios4dolfinx 168s 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. 168s test-adios4dolfinx-complex-mpi FAIL badpkg 168s blame: adios4dolfinx 168s 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.