0s autopkgtest [14:10:43]: starting date and time: 2026-02-02 14:10:43+0000 0s autopkgtest [14:10:43]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [14:10:43]: host juju-7f2275-prod-proposed-migration-environment-2; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.xi9pjq21/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-s390x --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-2@sto01-s390x-18.secgroup --name adt-resolute-s390x-fenics-20260202-133629-juju-7f2275-prod-proposed-migration-environment-2-45e418f6-95ba-4a85-abc2-2f3f4428d097 --image adt/ubuntu-resolute-s390x-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-2 --net-id=net_prod-autopkgtest-workers-s390x -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 3s Creating nova instance adt-resolute-s390x-fenics-20260202-133629-juju-7f2275-prod-proposed-migration-environment-2-45e418f6-95ba-4a85-abc2-2f3f4428d097 from image adt/ubuntu-resolute-s390x-server-20260202.img (UUID 2cf7d089-99a1-4704-af48-01d74c62f797)... 133s autopkgtest [14:12:56]: testbed dpkg architecture: s390x 134s autopkgtest [14:12:57]: testbed apt version: 3.1.14 135s autopkgtest [14:12:58]: @@@@@@@@@@@@@@@@@@@@ test bed setup 136s autopkgtest [14:12:59]: testbed release detected to be: None 139s autopkgtest [14:13:02]: updating testbed package index (apt update) 139s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 139s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 140s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 140s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 140s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [27.9 kB] 140s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [102 kB] 140s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [2816 B] 140s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [1266 kB] 140s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main s390x Packages [115 kB] 140s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/universe s390x Packages [995 kB] 140s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse s390x Packages [7016 B] 142s Fetched 2640 kB in 3s (1011 kB/s) 147s Reading package lists... 149s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 149s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 149s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 149s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 155s Reading package lists... 155s Reading package lists... 157s Building dependency tree... 157s Reading state information... 157s Calculating upgrade... 159s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 159s autopkgtest [14:13:22]: upgrading testbed (apt dist-upgrade and autopurge) 159s Reading package lists... 160s Building dependency tree... 160s Reading state information... 161s Calculating upgrade... 161s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 162s Reading package lists... 163s Building dependency tree... 163s Reading state information... 163s Solving dependencies... 164s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 169s autopkgtest [14:13:32]: testbed running kernel: Linux 6.18.0-9-generic #9-Ubuntu SMP Mon Jan 12 15:39:23 UTC 2026 169s autopkgtest [14:13:32]: @@@@@@@@@@@@@@@@@@@@ apt-source fenics 175s Get:1 http://ftpmaster.internal/ubuntu resolute/universe fenics 2:0.10.0.1 (dsc) [1921 B] 175s Get:2 http://ftpmaster.internal/ubuntu resolute/universe fenics 2:0.10.0.1 (tar) [6020 B] 177s gpgv: Signature made Mon Dec 22 12:00:08 2025 UTC 177s gpgv: using RSA key 23C9A93E585819E9126D0A36573EF1E4BD5A01FA 177s gpgv: Can't check signature: No public key 177s dpkg-source: warning: cannot verify inline signature for ./fenics_0.10.0.1.dsc: no acceptable signature found 177s autopkgtest [14:13:40]: testing package fenics version 2:0.10.0.1 177s autopkgtest [14:13:40]: build not needed 178s autopkgtest [14:13:41]: test test-fenics: preparing testbed 178s Reading package lists... 180s Building dependency tree... 180s Reading state information... 181s Solving dependencies... 181s Some packages could not be installed. This may mean that you have 181s requested an impossible situation or if you are using the unstable 181s distribution that some required packages have not yet been created 181s or been moved out of Incoming. 181s The following information may help to resolve the situation: 181s 181s The following packages have unmet dependencies: 182s satisfy:command-line : Depends: fenics but it is not going to be installed 182s Depends: fenicsx but it is not going to be installed 182s Depends: debhelper-compat (= 13) 182s Depends: build-essential but it is not going to be installed 182s Depends: python3-dolfinx-mpc but it is not going to be installed 182s Depends: python3-adios4dolfinx but it is not going to be installed 182s Depends: python3-scifem but it is not going to be installed 182s Depends: python3-all but it is not going to be installed 182s E: Unable to satisfy dependencies. Reached two conflicting assignments: 182s 1. python3:s390x is selected for install because: 182s 1. satisfy:command-line:s390x=1 is selected for install 182s 2. satisfy:command-line:s390x Depends python3-dolfinx-mpc 182s 3. python3-dolfinx-mpc:s390x Depends python3 (< 3.15) and Depends python3 (>= 3.13~) 182s 2. python3:s390x is available in versions 3.13.9-3, 3.14.2-1 182s but none of the choices are installable: 182s - python3:s390x=3.13.9-3 is not selected for install 182s - python3:s390x=3.14.2-1 is not selected for install 182s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 183s Reading package lists... 184s Building dependency tree... 184s Reading state information... 185s Solving dependencies... 185s Some packages could not be installed. This may mean that you have 185s requested an impossible situation or if you are using the unstable 185s distribution that some required packages have not yet been created 185s or been moved out of Incoming. 185s The following information may help to resolve the situation: 185s 185s The following packages have unmet dependencies: 186s satisfy:command-line : Depends: fenics but it is not going to be installed 186s Depends: fenicsx but it is not going to be installed 186s Depends: debhelper-compat (= 13) 186s Depends: build-essential but it is not going to be installed 186s Depends: python3-dolfinx-mpc but it is not going to be installed 186s Depends: python3-adios4dolfinx but it is not going to be installed 186s Depends: python3-scifem but it is not going to be installed 186s Depends: python3-all but it is not going to be installed 186s E: Unable to satisfy dependencies. Reached two conflicting assignments: 186s 1. python3-pybind11:s390x=2.13.6-2 is not selected for install 186s 2. python3-pybind11:s390x=2.13.6-2 is selected for install because: 186s 1. satisfy:command-line:s390x=1 is selected for install 186s 2. satisfy:command-line:s390x Depends fenics 186s 3. fenics:s390x Depends python3-dolfin (>= 2019.2~) 186s 4. python3-dolfin:s390x Depends python3-pybind11 (< 3) 186s test-fenics FAIL badpkg 186s blame: fenics 186s 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. 186s autopkgtest [14:13:49]: test test-fenicsx: preparing testbed 187s Reading package lists... 189s Building dependency tree... 189s Reading state information... 189s Solving dependencies... 189s Some packages could not be installed. This may mean that you have 189s requested an impossible situation or if you are using the unstable 189s distribution that some required packages have not yet been created 189s or been moved out of Incoming. 189s The following information may help to resolve the situation: 189s 190s The following packages have unmet dependencies: 190s satisfy:command-line : Depends: fenics but it is not going to be installed 190s Depends: fenicsx but it is not going to be installed 190s Depends: debhelper-compat (= 13) 190s Depends: build-essential but it is not going to be installed 190s Depends: python3-dolfinx-mpc but it is not going to be installed 190s Depends: python3-adios4dolfinx but it is not going to be installed 190s Depends: python3-scifem but it is not going to be installed 190s Depends: python3-all but it is not going to be installed 190s E: Unable to satisfy dependencies. Reached two conflicting assignments: 190s 1. python3-pybind11:s390x=2.13.6-2 is not selected for install 190s 2. python3-pybind11:s390x=2.13.6-2 is selected for install because: 190s 1. satisfy:command-line:s390x=1 is selected for install 190s 2. satisfy:command-line:s390x Depends fenics 190s 3. fenics:s390x Depends python3-dolfin (>= 2019.2~) 190s 4. python3-dolfin:s390x Depends python3-pybind11 (< 3) 191s test-fenicsx FAIL badpkg 191s blame: fenics 191s 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. 191s autopkgtest [14:13:54]: @@@@@@@@@@@@@@@@@@@@ summary 191s test-fenics FAIL badpkg 191s blame: fenics 191s 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. 191s test-fenicsx FAIL badpkg 191s blame: fenics 191s 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.