0s autopkgtest [13:23:24]: starting date and time: 2026-02-02 13:23:24+0000 0s autopkgtest [13:23:24]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [13:23:24]: host juju-7f2275-prod-proposed-migration-environment-2; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.10drizhv/out --timeout-copy=6000 --needs-internet=try --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:dolfinx-mpc,src:nanobind --apt-upgrade fenics --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 '--env=ADT_TEST_TRIGGERS=dolfinx-mpc/0.10.1-1build1 nanobind/2.10.2-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-13.secgroup --name adt-resolute-amd64-fenics-20260202-132324-juju-7f2275-prod-proposed-migration-environment-2-6ef05dda-54a1-4b6f-9fdd-e0bc6294316f --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-amd64-fenics-20260202-132324-juju-7f2275-prod-proposed-migration-environment-2-6ef05dda-54a1-4b6f-9fdd-e0bc6294316f from image adt/ubuntu-resolute-amd64-server-20260202.img (UUID 54e94ad2-f1e5-466e-b281-ee6f460760b3)... 73s autopkgtest [13:24:37]: testbed dpkg architecture: amd64 73s autopkgtest [13:24:37]: testbed apt version: 3.1.14 73s autopkgtest [13:24:37]: @@@@@@@@@@@@@@@@@@@@ test bed setup 73s autopkgtest [13:24:37]: testbed release detected to be: None 74s autopkgtest [13:24:38]: updating testbed package index (apt update) 74s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 74s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 74s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 74s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 74s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [27.3 kB] 74s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [1241 kB] 75s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [99.2 kB] 75s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [2816 B] 75s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main i386 Packages [95.3 kB] 75s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 Packages [113 kB] 75s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 c-n-f Metadata [3536 B] 75s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 Packages [12.3 kB] 75s Get:13 http://ftpmaster.internal/ubuntu resolute-proposed/restricted i386 Packages [3692 B] 75s Get:14 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 c-n-f Metadata [336 B] 75s Get:15 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 Packages [1065 kB] 75s Get:16 http://ftpmaster.internal/ubuntu resolute-proposed/universe i386 Packages [401 kB] 75s Get:17 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 c-n-f Metadata [27.3 kB] 75s Get:18 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse i386 Packages [3632 B] 75s Get:19 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 Packages [24.4 kB] 75s Get:20 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 c-n-f Metadata [1060 B] 76s Fetched 3245 kB in 1s (2480 kB/s) 76s Reading package lists... 77s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 77s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 77s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 77s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 78s Reading package lists... 78s Reading package lists... 78s Building dependency tree... 78s Reading state information... 78s Calculating upgrade... 78s The following packages will be upgraded: 78s libgpg-error-l10n libgpg-error0 pci.ids 78s 3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 78s Need to get 391 kB of archives. 78s After this operation, 12.3 kB of additional disk space will be used. 78s Get:1 http://ftpmaster.internal/ubuntu resolute/main amd64 libgpg-error-l10n all 1.58-2 [9244 B] 78s Get:2 http://ftpmaster.internal/ubuntu resolute/main amd64 libgpg-error0 amd64 1.58-2 [83.3 kB] 78s Get:3 http://ftpmaster.internal/ubuntu resolute/main amd64 pci.ids all 0.0~2026.01.31-1 [299 kB] 78s dpkg-preconfigure: unable to re-open stdin: No such file or directory 78s Fetched 391 kB in 0s (27.1 MB/s) 78s (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 ... 83956 files and directories currently installed.) 78s Preparing to unpack .../libgpg-error-l10n_1.58-2_all.deb ... 78s Unpacking libgpg-error-l10n (1.58-2) over (1.58-1build1) ... 78s Preparing to unpack .../libgpg-error0_1.58-2_amd64.deb ... 78s Unpacking libgpg-error0:amd64 (1.58-2) over (1.58-1build1) ... 78s Preparing to unpack .../pci.ids_0.0~2026.01.31-1_all.deb ... 78s Unpacking pci.ids (0.0~2026.01.31-1) over (0.0~2025.12.16-1) ... 78s Setting up pci.ids (0.0~2026.01.31-1) ... 78s Setting up libgpg-error0:amd64 (1.58-2) ... 78s Setting up libgpg-error-l10n (1.58-2) ... 78s Processing triggers for libc-bin (2.42-2ubuntu4) ... 78s autopkgtest [13:24:42]: upgrading testbed (apt dist-upgrade and autopurge) 79s Reading package lists... 79s Building dependency tree... 79s Reading state information... 79s Calculating upgrade... 79s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 79s Reading package lists... 79s Building dependency tree... 79s Reading state information... 79s Solving dependencies... 79s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 81s autopkgtest [13:24:45]: testbed running kernel: Linux 6.18.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 12 16:49:02 UTC 2026 82s autopkgtest [13:24:46]: @@@@@@@@@@@@@@@@@@@@ apt-source fenics 83s Get:1 http://ftpmaster.internal/ubuntu resolute/universe fenics 2:0.10.0.1 (dsc) [1921 B] 83s Get:2 http://ftpmaster.internal/ubuntu resolute/universe fenics 2:0.10.0.1 (tar) [6020 B] 83s gpgv: Signature made Mon Dec 22 12:00:08 2025 UTC 83s gpgv: using RSA key 23C9A93E585819E9126D0A36573EF1E4BD5A01FA 83s gpgv: Can't check signature: No public key 83s dpkg-source: warning: cannot verify inline signature for ./fenics_0.10.0.1.dsc: no acceptable signature found 83s autopkgtest [13:24:47]: testing package fenics version 2:0.10.0.1 83s autopkgtest [13:24:47]: build not needed 83s autopkgtest [13:24:47]: test test-fenics: preparing testbed 84s Reading package lists... 84s Building dependency tree... 84s Reading state information... 84s Solving dependencies... 84s Some packages could not be installed. This may mean that you have 84s requested an impossible situation or if you are using the unstable 84s distribution that some required packages have not yet been created 84s or been moved out of Incoming. 84s The following information may help to resolve the situation: 84s 84s The following packages have unmet dependencies: 84s satisfy:command-line : Depends: fenics but it is not going to be installed 84s Depends: fenicsx but it is not going to be installed 84s Depends: debhelper-compat (= 13) 84s Depends: build-essential but it is not going to be installed 84s Depends: python3-dolfinx-mpc but it is not going to be installed 84s Depends: python3-adios4dolfinx but it is not going to be installed 84s Depends: python3-scifem but it is not going to be installed 84s Depends: python3-all but it is not going to be installed 84s E: Unable to satisfy dependencies. Reached two conflicting assignments: 84s 1. libdolfinx-dev:amd64 is selected for install because: 84s 1. satisfy:command-line:amd64=1 is selected for install 84s 2. satisfy:command-line:amd64 Depends fenicsx 84s 3. fenicsx:amd64 Depends libdolfinx-dev (>= 1:0.10~) 84s 2. libdolfinx-dev:amd64 is available in versions 1:0.10.0.post5-4, 1:0.10.0.post5-5build1 84s but none of the choices are installable: 84s - libdolfinx-dev:amd64=1:0.10.0.post5-4 is not selected for install 84s - libdolfinx-dev:amd64=1:0.10.0.post5-5build1 is not selected for install 84s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 84s Reading package lists... 84s Building dependency tree... 84s Reading state information... 84s Solving dependencies... 84s Some packages could not be installed. This may mean that you have 84s requested an impossible situation or if you are using the unstable 84s distribution that some required packages have not yet been created 84s or been moved out of Incoming. 84s The following information may help to resolve the situation: 84s 84s The following packages have unmet dependencies: 84s satisfy:command-line : Depends: fenics but it is not going to be installed 84s Depends: fenicsx but it is not going to be installed 84s Depends: debhelper-compat (= 13) 84s Depends: build-essential but it is not going to be installed 84s Depends: python3-dolfinx-mpc but it is not going to be installed 84s Depends: python3-adios4dolfinx but it is not going to be installed 84s Depends: python3-scifem but it is not going to be installed 84s Depends: python3-all but it is not going to be installed 84s E: Unable to satisfy dependencies. Reached two conflicting assignments: 84s 1. python3-pybind11:amd64=2.13.6-2 is not selected for install 84s 2. python3-pybind11:amd64=2.13.6-2 is selected for install because: 84s 1. satisfy:command-line:amd64=1 is selected for install 84s 2. satisfy:command-line:amd64 Depends fenics 84s 3. fenics:amd64 Depends python3-dolfin (>= 2019.2~) 84s 4. python3-dolfin:amd64 Depends python3-pybind11 (< 3) 85s test-fenics FAIL badpkg 85s blame: fenics 85s 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. 85s autopkgtest [13:24:49]: test test-fenicsx: preparing testbed 85s Reading package lists... 85s Building dependency tree... 85s Reading state information... 85s Solving dependencies... 85s Some packages could not be installed. This may mean that you have 85s requested an impossible situation or if you are using the unstable 85s distribution that some required packages have not yet been created 85s or been moved out of Incoming. 85s The following information may help to resolve the situation: 85s 85s The following packages have unmet dependencies: 85s satisfy:command-line : Depends: fenics but it is not going to be installed 85s Depends: fenicsx but it is not going to be installed 85s Depends: debhelper-compat (= 13) 85s Depends: build-essential but it is not going to be installed 85s Depends: python3-dolfinx-mpc but it is not going to be installed 85s Depends: python3-adios4dolfinx but it is not going to be installed 85s Depends: python3-scifem but it is not going to be installed 85s Depends: python3-all but it is not going to be installed 85s E: Unable to satisfy dependencies. Reached two conflicting assignments: 85s 1. python3-pybind11:amd64=2.13.6-2 is not selected for install 85s 2. python3-pybind11:amd64=2.13.6-2 is selected for install because: 85s 1. satisfy:command-line:amd64=1 is selected for install 85s 2. satisfy:command-line:amd64 Depends fenics 85s 3. fenics:amd64 Depends python3-dolfin (>= 2019.2~) 85s 4. python3-dolfin:amd64 Depends python3-pybind11 (< 3) 85s autopkgtest [13:24:49]: @@@@@@@@@@@@@@@@@@@@ summary 85s test-fenics FAIL badpkg 85s blame: fenics 85s 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. 85s test-fenicsx FAIL badpkg 85s blame: fenics 85s 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. 85s test-fenicsx FAIL badpkg 85s blame: fenics 85s 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.