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