0s autopkgtest [13:22:52]: starting date and time: 2025-11-17 13:22:52+0000 0s autopkgtest [13:22:52]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [13:22:52]: host juju-7f2275-prod-proposed-migration-environment-2; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.r3se5uzb/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:fenics-basix,src:python3-defaults --apt-upgrade fenics --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 '--env=ADT_TEST_TRIGGERS=fenics-basix/0.9.0-4 python3-defaults/3.13.7-2' -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-2@bos03-arm64-18.secgroup --name adt-resolute-arm64-fenics-20251117-132252-juju-7f2275-prod-proposed-migration-environment-2-a834e410-e9c2-44ba-be4f-189e2b3480e1 --image adt/ubuntu-resolute-arm64-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-2 --net-id=net_prod-proposed-migration -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 4s Creating nova instance adt-resolute-arm64-fenics-20251117-132252-juju-7f2275-prod-proposed-migration-environment-2-a834e410-e9c2-44ba-be4f-189e2b3480e1 from image adt/ubuntu-resolute-arm64-server-20251117.img (UUID 1cd33fbb-18df-4c5a-b8f0-2dcb25269485)... 65s autopkgtest [13:23:57]: testbed dpkg architecture: arm64 65s autopkgtest [13:23:57]: testbed apt version: 3.1.11 66s autopkgtest [13:23:58]: @@@@@@@@@@@@@@@@@@@@ test bed setup 66s autopkgtest [13:23:58]: testbed release detected to be: None 67s autopkgtest [13:23:59]: updating testbed package index (apt update) 67s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [87.8 kB] 68s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 68s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 68s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 68s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [868 kB] 68s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [22.9 kB] 68s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [81.1 kB] 68s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [9848 B] 68s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main arm64 Packages [149 kB] 68s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/main arm64 c-n-f Metadata [3084 B] 68s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/restricted arm64 Packages [107 kB] 68s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/restricted arm64 c-n-f Metadata [324 B] 68s Get:13 http://ftpmaster.internal/ubuntu resolute-proposed/universe arm64 Packages [577 kB] 68s Get:14 http://ftpmaster.internal/ubuntu resolute-proposed/universe arm64 c-n-f Metadata [17.8 kB] 68s Get:15 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse arm64 Packages [12.5 kB] 68s Get:16 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse arm64 c-n-f Metadata [576 B] 69s Fetched 1938 kB in 1s (1542 kB/s) 70s Reading package lists... 71s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 71s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 71s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 72s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 72s Reading package lists... 72s Reading package lists... 73s Building dependency tree... 73s Reading state information... 73s Calculating upgrade... 73s The following packages will be upgraded: 73s libpython3-stdlib python3 python3-minimal usbutils 74s 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 74s Need to get 144 kB of archives. 74s After this operation, 0 B of additional disk space will be used. 74s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed/main arm64 python3-minimal arm64 3.13.7-2 [27.8 kB] 74s Get:2 http://ftpmaster.internal/ubuntu resolute-proposed/main arm64 python3 arm64 3.13.7-2 [23.9 kB] 74s Get:3 http://ftpmaster.internal/ubuntu resolute-proposed/main arm64 libpython3-stdlib arm64 3.13.7-2 [10.6 kB] 74s Get:4 http://ftpmaster.internal/ubuntu resolute/main arm64 usbutils arm64 1:019-1 [81.7 kB] 74s dpkg-preconfigure: unable to re-open stdin: No such file or directory 74s Fetched 144 kB in 0s (344 kB/s) 75s (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 ... 88137 files and directories currently installed.) 75s Preparing to unpack .../python3-minimal_3.13.7-2_arm64.deb ... 75s Unpacking python3-minimal (3.13.7-2) over (3.13.7-1) ... 75s Setting up python3-minimal (3.13.7-2) ... 75s (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 ... 88137 files and directories currently installed.) 75s Preparing to unpack .../python3_3.13.7-2_arm64.deb ... 75s running python pre-rtupdate hooks for python3.13... 75s Unpacking python3 (3.13.7-2) over (3.13.7-1) ... 75s Preparing to unpack .../libpython3-stdlib_3.13.7-2_arm64.deb ... 75s Unpacking libpython3-stdlib:arm64 (3.13.7-2) over (3.13.7-1) ... 75s Preparing to unpack .../usbutils_1%3a019-1_arm64.deb ... 75s Unpacking usbutils (1:019-1) over (1:018-2) ... 75s Setting up usbutils (1:019-1) ... 75s Setting up libpython3-stdlib:arm64 (3.13.7-2) ... 75s Setting up python3 (3.13.7-2) ... 76s running python rtupdate hooks for python3.13... 76s running python post-rtupdate hooks for python3.13... 76s Processing triggers for man-db (2.13.1-1) ... 77s autopkgtest [13:24:09]: upgrading testbed (apt dist-upgrade and autopurge) 77s Reading package lists... 77s Building dependency tree... 77s Reading state information... 78s Calculating upgrade... 78s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 78s 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. 82s autopkgtest [13:24:14]: testbed running kernel: Linux 6.17.0-5-generic #5-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 22 09:50:31 UTC 2025 82s autopkgtest [13:24:14]: @@@@@@@@@@@@@@@@@@@@ apt-source fenics 84s Get:1 http://ftpmaster.internal/ubuntu resolute/universe fenics 2:0.9.0.3 (dsc) [1917 B] 84s Get:2 http://ftpmaster.internal/ubuntu resolute/universe fenics 2:0.9.0.3 (tar) [5964 B] 85s gpgv: Signature made Mon May 5 12:44:30 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.9.0.3.dsc: no acceptable signature found 85s autopkgtest [13:24:17]: testing package fenics version 2:0.9.0.3 85s autopkgtest [13:24:17]: build not needed 85s autopkgtest [13:24:17]: test test-fenics: preparing testbed 85s 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 decisions: 86s 1. python3-basix:arm64 is selected for install because: 86s 1. satisfy:command-line:arm64=1 is selected for install 86s 2. satisfy:command-line:arm64 Depends fenicsx 86s 3. fenicsx:arm64 Depends python3-basix (>= 0.9~) 86s 2. python3-basix:arm64 is available in versions 0.9.0-4, 0.9.0-2build2 86s but none of the choices are installable: 86s - python3-basix:arm64=0.9.0-4 is not selected for install because: 86s 1. satisfy:command-line:arm64=1 is selected for install as above 86s 2. satisfy:command-line:arm64 Depends python3-dolfinx-mpc 86s 3. python3-dolfinx-mpc:arm64 is available in version 0.9.1-2 86s 4. python3-basix:arm64=0.9.0-4 Breaks python3-dolfinx-mpc (< 0.9.3-2~) 86s - python3-basix:arm64=0.9.0-2build2 is not selected for install 86s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 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 decisions: 87s 1. python3-basix:arm64 is selected for install because: 87s 1. satisfy:command-line:arm64=1 is selected for install 87s 2. satisfy:command-line:arm64 Depends fenicsx 87s 3. fenicsx:arm64 Depends python3-basix (>= 0.9~) 87s 2. python3-basix:arm64 is available in versions 0.9.0-4, 0.9.0-2build2 87s but none of the choices are installable: 87s - python3-basix:arm64=0.9.0-4 is not selected for install because: 87s 1. satisfy:command-line:arm64=1 is selected for install as above 87s 2. satisfy:command-line:arm64 Depends python3-dolfinx-mpc 87s 3. python3-dolfinx-mpc:arm64 is available in version 0.9.1-2 87s 4. python3-basix:arm64=0.9.0-4 Breaks python3-dolfinx-mpc (< 0.9.3-2~) 87s - python3-basix:arm64=0.9.0-2build2 is not selected for install 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 [13:24:19]: test test-fenicsx: preparing testbed 88s Reading package lists... 88s Building dependency tree... 88s Reading state information... 88s Solving dependencies... 88s Some packages could not be installed. This may mean that you have 88s requested an impossible situation or if you are using the unstable 88s distribution that some required packages have not yet been created 88s or been moved out of Incoming. 88s The following information may help to resolve the situation: 88s 88s The following packages have unmet dependencies: 88s satisfy:command-line : Depends: fenics but it is not going to be installed 88s Depends: fenicsx but it is not going to be installed 88s Depends: debhelper-compat (= 13) 88s Depends: build-essential but it is not going to be installed 88s Depends: python3-dolfinx-mpc but it is not going to be installed 88s Depends: python3-adios4dolfinx but it is not going to be installed 88s Depends: python3-scifem but it is not going to be installed 88s Depends: python3-all but it is not going to be installed 88s E: Unable to satisfy dependencies. Reached two conflicting decisions: 88s 1. python3-basix:arm64 is selected for install because: 88s 1. satisfy:command-line:arm64=1 is selected for install 88s 2. satisfy:command-line:arm64 Depends fenicsx 88s 3. fenicsx:arm64 Depends python3-basix (>= 0.9~) 88s 2. python3-basix:arm64 is available in versions 0.9.0-4, 0.9.0-2build2 88s but none of the choices are installable: 88s - python3-basix:arm64=0.9.0-4 is not selected for install because: 88s 1. satisfy:command-line:arm64=1 is selected for install as above 88s 2. satisfy:command-line:arm64 Depends python3-dolfinx-mpc 88s 3. python3-dolfinx-mpc:arm64 is available in version 0.9.1-2 88s 4. python3-basix:arm64=0.9.0-4 Breaks python3-dolfinx-mpc (< 0.9.3-2~) 88s - python3-basix:arm64=0.9.0-2build2 is not selected for install 88s test-fenicsx FAIL badpkg 88s blame: fenics 88s 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. 88s autopkgtest [13:24:20]: @@@@@@@@@@@@@@@@@@@@ summary 88s test-fenics FAIL badpkg 88s blame: fenics 88s 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. 88s test-fenicsx FAIL badpkg 88s blame: fenics 88s 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.