0s autopkgtest [19:22:25]: starting date and time: 2026-02-01 19:22:25+0000 0s autopkgtest [19:22:25]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [19:22:25]: host juju-7f2275-prod-proposed-migration-environment-2; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.koqps7u1/out --timeout-copy=6000 --needs-internet=try --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:fenics-basix,src:nanobind --apt-upgrade fenics --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 '--env=ADT_TEST_TRIGGERS=fenics-basix/0.10.0.post0-2build1 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-6.secgroup --name adt-resolute-amd64-fenics-20260201-192225-juju-7f2275-prod-proposed-migration-environment-2-f04eaa73-9696-4e70-91f6-75017c47c197 --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-20260201-192225-juju-7f2275-prod-proposed-migration-environment-2-f04eaa73-9696-4e70-91f6-75017c47c197 from image adt/ubuntu-resolute-amd64-server-20260201.img (UUID 3f0dc02a-532c-4fab-8f89-dfe5d9268d76)... 76s autopkgtest [19:23:41]: testbed dpkg architecture: amd64 76s autopkgtest [19:23:41]: testbed apt version: 3.1.14 76s autopkgtest [19:23:41]: @@@@@@@@@@@@@@@@@@@@ test bed setup 77s autopkgtest [19:23:42]: testbed release detected to be: None 77s autopkgtest [19:23:42]: updating testbed package index (apt update) 77s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 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 77s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [27.4 kB] 78s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [1231 kB] 78s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [103 kB] 78s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [2816 B] 78s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main i386 Packages [100.0 kB] 78s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 Packages [117 kB] 78s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 c-n-f Metadata [3616 B] 78s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 Packages [12.3 kB] 78s Get:13 http://ftpmaster.internal/ubuntu resolute-proposed/restricted i386 Packages [3692 B] 78s Get:14 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 c-n-f Metadata [336 B] 78s Get:15 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 Packages [1063 kB] 78s Get:16 http://ftpmaster.internal/ubuntu resolute-proposed/universe i386 Packages [400 kB] 78s Get:17 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 c-n-f Metadata [27.0 kB] 78s Get:18 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse i386 Packages [3336 B] 78s Get:19 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 Packages [23.7 kB] 78s Get:20 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 c-n-f Metadata [1036 B] 79s Fetched 3244 kB in 1s (3983 kB/s) 79s Reading package lists... 80s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 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 Reading package lists... 80s Reading package lists... 81s Building dependency tree... 81s Reading state information... 81s Calculating upgrade... 81s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 81s autopkgtest [19:23:46]: upgrading testbed (apt dist-upgrade and autopurge) 81s Reading package lists... 81s Building dependency tree... 81s Reading state information... 81s Calculating upgrade... 81s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 81s Reading package lists... 81s Building dependency tree... 81s Reading state information... 82s Solving dependencies... 82s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 84s autopkgtest [19:23:49]: testbed running kernel: Linux 6.18.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 12 16:49:02 UTC 2026 84s autopkgtest [19:23:49]: @@@@@@@@@@@@@@@@@@@@ apt-source fenics 85s Get:1 http://ftpmaster.internal/ubuntu resolute/universe fenics 2:0.10.0.1 (dsc) [1921 B] 85s Get:2 http://ftpmaster.internal/ubuntu resolute/universe fenics 2:0.10.0.1 (tar) [6020 B] 85s gpgv: Signature made Mon Dec 22 12:00:08 2025 UTC 85s gpgv: using RSA key 23C9A93E585819E9126D0A36573EF1E4BD5A01FA 85s gpgv: Can't check signature: No public key 85s dpkg-source: warning: cannot verify inline signature for ./fenics_0.10.0.1.dsc: no acceptable signature found 85s autopkgtest [19:23:50]: testing package fenics version 2:0.10.0.1 85s autopkgtest [19:23:50]: build not needed 86s autopkgtest [19:23:51]: test test-fenics: preparing testbed 86s Reading package lists... 86s Building dependency tree... 86s Reading state information... 86s Solving dependencies... 86s Some packages could not be installed. This may mean that you have 86s requested an impossible situation or if you are using the unstable 86s distribution that some required packages have not yet been created 86s or been moved out of Incoming. 86s The following information may help to resolve the situation: 86s 86s The following packages have unmet dependencies: 86s satisfy:command-line : Depends: fenics but it is not going to be installed 86s Depends: fenicsx but it is not going to be installed 86s Depends: debhelper-compat (= 13) 86s Depends: build-essential but it is not going to be installed 86s Depends: python3-dolfinx-mpc but it is not going to be installed 86s Depends: python3-adios4dolfinx but it is not going to be installed 86s Depends: python3-scifem but it is not going to be installed 86s Depends: python3-all but it is not going to be installed 86s E: Unable to satisfy dependencies. Reached two conflicting assignments: 86s 1. python3-nanobind:amd64=2.9.2-2 is not selected for install 86s 2. python3-nanobind:amd64=2.9.2-2 is selected for install because: 86s 1. satisfy:command-line:amd64=1 is selected for install 86s 2. satisfy:command-line:amd64 Depends python3-dolfinx-mpc 86s 3. python3-dolfinx-mpc:amd64 Depends python3-nanobind-abi16 86s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 86s Reading package lists... 87s Building dependency tree... 87s Reading state information... 87s Solving dependencies... 87s Some packages could not be installed. This may mean that you have 87s requested an impossible situation or if you are using the unstable 87s distribution that some required packages have not yet been created 87s or been moved out of Incoming. 87s The following information may help to resolve the situation: 87s 87s The following packages have unmet dependencies: 87s satisfy:command-line : Depends: fenics but it is not going to be installed 87s Depends: fenicsx but it is not going to be installed 87s Depends: debhelper-compat (= 13) 87s Depends: build-essential but it is not going to be installed 87s Depends: python3-dolfinx-mpc but it is not going to be installed 87s Depends: python3-adios4dolfinx but it is not going to be installed 87s Depends: python3-scifem but it is not going to be installed 87s Depends: python3-all but it is not going to be installed 87s E: Unable to satisfy dependencies. Reached two conflicting assignments: 87s 1. python3-nanobind:amd64=2.9.2-2 is not selected for install 87s 2. python3-nanobind:amd64=2.9.2-2 is selected for install because: 87s 1. satisfy:command-line:amd64=1 is selected for install 87s 2. satisfy:command-line:amd64 Depends python3-dolfinx-mpc 87s 3. python3-dolfinx-mpc:amd64 Depends python3-nanobind-abi16 87s test-fenics FAIL badpkg 87s blame: fenics 87s 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. 87s autopkgtest [19:23:52]: test test-fenicsx: preparing testbed 87s Reading package lists... 87s Building dependency tree... 87s Reading state information... 87s Solving dependencies... 87s Some packages could not be installed. This may mean that you have 87s requested an impossible situation or if you are using the unstable 87s distribution that some required packages have not yet been created 87s or been moved out of Incoming. 87s The following information may help to resolve the situation: 87s 87s The following packages have unmet dependencies: 87s satisfy:command-line : Depends: fenics but it is not going to be installed 87s Depends: fenicsx but it is not going to be installed 87s Depends: debhelper-compat (= 13) 87s Depends: build-essential but it is not going to be installed 87s Depends: python3-dolfinx-mpc but it is not going to be installed 87s Depends: python3-adios4dolfinx but it is not going to be installed 87s Depends: python3-scifem but it is not going to be installed 87s Depends: python3-all but it is not going to be installed 87s E: Unable to satisfy dependencies. Reached two conflicting assignments: 87s 1. python3-nanobind:amd64=2.9.2-2 is not selected for install 87s 2. python3-nanobind:amd64=2.9.2-2 is selected for install because: 87s 1. satisfy:command-line:amd64=1 is selected for install 87s 2. satisfy:command-line:amd64 Depends python3-dolfinx-mpc 87s 3. python3-dolfinx-mpc:amd64 Depends python3-nanobind-abi16 87s test-fenicsx FAIL badpkg 87s blame: fenics 87s 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. 87s autopkgtest [19:23:52]: @@@@@@@@@@@@@@@@@@@@ summary 87s test-fenics FAIL badpkg 87s blame: fenics 87s 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. 87s test-fenicsx FAIL badpkg 87s blame: fenics 87s 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.