0s autopkgtest [01:53:32]: starting date and time: 2026-02-06 01:53:32+0000 1s autopkgtest [01:53:33]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 1s autopkgtest [01:53:33]: host juju-7f2275-prod-proposed-migration-environment-20; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.iupc_i4m/out --timeout-copy=6000 --needs-internet=try --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:dolfin,src:dolfinx-mpc,src:fenics-dolfinx,src:scifem,src:fenics-basix --apt-upgrade fenics --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 '--env=ADT_TEST_TRIGGERS=dolfin/2019.2.0~legacy20240219.1c52e83-26build2 dolfinx-mpc/0.10.1-1build1 fenics-dolfinx/1:0.10.0.post5-5build1 scifem/0.16.1-1build2 fenics-basix/0.10.0.post0-2build1' -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest-cpu2-ram4-disk20-arm64 --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-20@sto01-arm64-12.secgroup --name adt-resolute-arm64-fenics-20260206-015331-juju-7f2275-prod-proposed-migration-environment-20-1aea10cc-15ff-4e99-94ac-f4717c7f0bdc --image adt/ubuntu-resolute-arm64-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-20 --net-id=net_prod-autopkgtest-workers-arm64 -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 6s Creating nova instance adt-resolute-arm64-fenics-20260206-015331-juju-7f2275-prod-proposed-migration-environment-20-1aea10cc-15ff-4e99-94ac-f4717c7f0bdc from image adt/ubuntu-resolute-arm64-server-20260205.img (UUID 88169191-3954-4b52-b471-25031b32a3a0)... 281s autopkgtest [01:58:13]: testbed dpkg architecture: arm64 281s autopkgtest [01:58:13]: testbed apt version: 3.1.14 282s autopkgtest [01:58:14]: @@@@@@@@@@@@@@@@@@@@ test bed setup 282s autopkgtest [01:58:14]: testbed release detected to be: None 301s autopkgtest [01:58:33]: updating testbed package index (apt update) 302s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 302s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 302s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 302s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 302s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [221 kB] 302s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [5260 B] 302s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [1631 kB] 303s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [31.4 kB] 303s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main arm64 Packages [269 kB] 303s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/main arm64 c-n-f Metadata [7344 B] 303s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/restricted arm64 Packages [52.9 kB] 303s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/restricted arm64 c-n-f Metadata [328 B] 303s Get:13 http://ftpmaster.internal/ubuntu resolute-proposed/universe arm64 Packages [1462 kB] 303s Get:14 http://ftpmaster.internal/ubuntu resolute-proposed/universe arm64 c-n-f Metadata [42.1 kB] 303s Get:15 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse arm64 Packages [23.6 kB] 303s Get:16 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse arm64 c-n-f Metadata [776 B] 307s Fetched 3872 kB in 2s (2063 kB/s) 308s Reading package lists... 310s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 310s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 310s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 310s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 311s Reading package lists... 311s Reading package lists... 311s Building dependency tree... 311s Reading state information... 311s Calculating upgrade... 312s The following packages will be upgraded: 312s libdrm-amdgpu1 libdrm-common libdrm2 mawk 312s 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 312s Need to get 203 kB of archives. 312s After this operation, 0 B of additional disk space will be used. 312s Get:1 http://ftpmaster.internal/ubuntu resolute/main arm64 mawk arm64 1.3.4.20260129-1 [128 kB] 312s Get:2 http://ftpmaster.internal/ubuntu resolute/main arm64 libdrm-common all 2.4.131-1 [9774 B] 312s Get:3 http://ftpmaster.internal/ubuntu resolute/main arm64 libdrm2 arm64 2.4.131-1 [42.6 kB] 312s Get:4 http://ftpmaster.internal/ubuntu resolute/main arm64 libdrm-amdgpu1 arm64 2.4.131-1 [22.6 kB] 312s dpkg-preconfigure: unable to re-open stdin: No such file or directory 312s Fetched 203 kB in 0s (1217 kB/s) 312s (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 ... 89360 files and directories currently installed.) 312s Preparing to unpack .../mawk_1.3.4.20260129-1_arm64.deb ... 312s Unpacking mawk (1.3.4.20260129-1) over (1.3.4.20250131-2) ... 312s Preparing to unpack .../libdrm-common_2.4.131-1_all.deb ... 312s Unpacking libdrm-common (2.4.131-1) over (2.4.129-1) ... 313s Preparing to unpack .../libdrm2_2.4.131-1_arm64.deb ... 313s Unpacking libdrm2:arm64 (2.4.131-1) over (2.4.129-1) ... 313s Preparing to unpack .../libdrm-amdgpu1_2.4.131-1_arm64.deb ... 313s Unpacking libdrm-amdgpu1:arm64 (2.4.131-1) over (2.4.129-1) ... 313s Setting up mawk (1.3.4.20260129-1) ... 313s Setting up libdrm-common (2.4.131-1) ... 313s Setting up libdrm2:arm64 (2.4.131-1) ... 313s Setting up libdrm-amdgpu1:arm64 (2.4.131-1) ... 313s Processing triggers for man-db (2.13.1-1) ... 313s Processing triggers for libc-bin (2.42-2ubuntu4) ... 314s autopkgtest [01:58:46]: upgrading testbed (apt dist-upgrade and autopurge) 314s Reading package lists... 314s Building dependency tree... 314s Reading state information... 314s Calculating upgrade... 315s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 315s Reading package lists... 315s Building dependency tree... 315s Reading state information... 315s Solving dependencies... 316s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 337s autopkgtest [01:59:09]: testbed running kernel: Linux 6.18.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 12 16:41:39 UTC 2026 337s autopkgtest [01:59:09]: @@@@@@@@@@@@@@@@@@@@ apt-source fenics 339s Get:1 http://ftpmaster.internal/ubuntu resolute/universe fenics 2:0.10.0.1 (dsc) [1921 B] 339s Get:2 http://ftpmaster.internal/ubuntu resolute/universe fenics 2:0.10.0.1 (tar) [6020 B] 339s gpgv: Signature made Mon Dec 22 12:00:08 2025 UTC 339s gpgv: using RSA key 23C9A93E585819E9126D0A36573EF1E4BD5A01FA 339s gpgv: Can't check signature: No public key 339s dpkg-source: warning: cannot verify inline signature for ./fenics_0.10.0.1.dsc: no acceptable signature found 339s autopkgtest [01:59:11]: testing package fenics version 2:0.10.0.1 339s autopkgtest [01:59:11]: build not needed 339s autopkgtest [01:59:11]: test test-fenics: preparing testbed 339s Reading package lists... 340s Building dependency tree... 340s Reading state information... 340s Solving dependencies... 340s Some packages could not be installed. This may mean that you have 340s requested an impossible situation or if you are using the unstable 340s distribution that some required packages have not yet been created 340s or been moved out of Incoming. 340s The following information may help to resolve the situation: 340s 340s The following packages have unmet dependencies: 340s satisfy:command-line : Depends: fenics but it is not going to be installed 340s Depends: fenicsx but it is not going to be installed 340s Depends: debhelper-compat (= 13) 340s Depends: build-essential but it is not going to be installed 340s Depends: python3-dolfinx-mpc but it is not going to be installed 340s Depends: python3-adios4dolfinx but it is not going to be installed 340s Depends: python3-scifem but it is not going to be installed 340s Depends: python3-all but it is not going to be installed 340s E: Unable to satisfy dependencies. Reached two conflicting assignments: 340s 1. python3:arm64 is selected for install because: 340s 1. shim-signed:arm64 is selected for install 340s 2. shim-signed:arm64 Depends grub2-common (>= 2.04-1ubuntu24) 340s 3. grub2-common:arm64 Depends python3 340s 2. python3:arm64 is available in versions 3.13.9-3, 3.14.2-1 340s but none of the choices are installable: 340s - python3:arm64=3.13.9-3 is not selected for install 340s - python3:arm64=3.14.2-1 is not selected for install 340s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 341s Reading package lists... 341s Building dependency tree... 341s Reading state information... 350s Solving dependencies... 351s Some packages could not be installed. This may mean that you have 351s requested an impossible situation or if you are using the unstable 351s distribution that some required packages have not yet been created 351s or been moved out of Incoming. 351s The following information may help to resolve the situation: 351s 351s The following packages have unmet dependencies: 351s satisfy:command-line : Depends: fenics but it is not going to be installed 351s Depends: fenicsx but it is not going to be installed 351s Depends: debhelper-compat (= 13) 351s Depends: build-essential but it is not going to be installed 351s Depends: python3-dolfinx-mpc but it is not going to be installed 351s Depends: python3-adios4dolfinx but it is not going to be installed 351s Depends: python3-scifem but it is not going to be installed 351s Depends: python3-all but it is not going to be installed 351s E: Unable to satisfy dependencies. Reached two conflicting assignments: 351s 1. libunbound8:arm64 is selected for install because: 351s 1. satisfy:command-line:arm64=1 is selected for install 351s 2. satisfy:command-line:arm64 Depends fenics 351s 3. fenics:arm64 Depends libdolfin-dev (>= 2019.2~) 351s 4. libdolfin-dev:arm64 Depends libhdf5-mpi-dev 351s 5. libhdf5-mpi-dev:arm64 Depends libhdf5-openmpi-dev 351s 6. libhdf5-openmpi-dev:arm64 Depends libcurl4-openssl-dev | libcurl-dev 351s [selected libcurl4-gnutls-dev:arm64=8.18.0-1ubuntu1 for install] 351s 7. libcurl4-gnutls-dev:arm64 Depends libgnutls28-dev 351s 8. libgnutls28-dev:arm64 Depends libgnutls-dane0t64 (= 3.8.10-3ubuntu1) 351s 9. libgnutls-dane0t64:arm64 Depends libunbound8 (>= 1.8.0) 351s For context, additional choices that could not be installed: 351s * In libhdf5-openmpi-dev:arm64 Depends libcurl4-openssl-dev | libcurl-dev: 351s - libcurl4-openssl-dev:arm64 is not selected for install 351s - libcurl4-openssl-dev:arm64=8.18.0-1ubuntu1 -> | libcurl4-openssl-dev:arm64 351s but none of the choices are installable: 351s - libcurl4-openssl-dev:arm64 is not selected for install 351s 2. libunbound8:arm64 is available in versions 1.24.2-1ubuntu2, 1.24.2-1ubuntu1 351s but none of the choices are installable: 351s - libunbound8:arm64=1.24.2-1ubuntu2 is not selected for install 351s - libunbound8:arm64=1.24.2-1ubuntu1 is not selected for install 351s E: Solver timed out. 351s test-fenics FAIL badpkg 351s blame: fenics 351s 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. 351s autopkgtest [01:59:23]: test test-fenicsx: preparing testbed 377s Reading package lists... 377s Building dependency tree... 377s Reading state information... 387s Solving dependencies... 387s Some packages could not be installed. This may mean that you have 387s requested an impossible situation or if you are using the unstable 387s distribution that some required packages have not yet been created 387s or been moved out of Incoming. 387s The following information may help to resolve the situation: 387s 387s The following packages have unmet dependencies: 387s satisfy:command-line : Depends: fenics but it is not going to be installed 387s Depends: fenicsx but it is not going to be installed 387s Depends: debhelper-compat (= 13) 387s Depends: build-essential but it is not going to be installed 387s Depends: python3-dolfinx-mpc but it is not going to be installed 387s Depends: python3-adios4dolfinx but it is not going to be installed 387s Depends: python3-scifem but it is not going to be installed 387s Depends: python3-all but it is not going to be installed 387s E: Unable to satisfy dependencies. Reached two conflicting assignments: 387s 1. libboost-dev:arm64 is selected for install because: 387s 1. satisfy:command-line:arm64=1 is selected for install 387s 2. satisfy:command-line:arm64 Depends fenics 387s 3. fenics:arm64 Depends libdolfin-dev (>= 2019.2~) 387s 4. libdolfin-dev:arm64 Depends libboost-dev 387s 2. libboost-dev:arm64 is available in versions 1.90.0.0ubuntu3, 1.88.0.0ubuntu3 387s but none of the choices are installable: 387s - libboost-dev:arm64=1.90.0.0ubuntu3 is not selected for install 387s - libboost-dev:arm64=1.88.0.0ubuntu3 is not selected for install 387s E: Solver timed out. 387s test-fenicsx FAIL badpkg 387s blame: fenics 387s 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. 387s autopkgtest [01:59:59]: @@@@@@@@@@@@@@@@@@@@ summary 387s test-fenics FAIL badpkg 387s blame: fenics 387s 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. 387s test-fenicsx FAIL badpkg 387s blame: fenics 387s 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.