0s autopkgtest [13:50:52]: starting date and time: 2026-02-02 13:50:52+0000 0s autopkgtest [13:50:52]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [13:50:52]: host juju-7f2275-prod-proposed-migration-environment-15; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.f0sqyawu/out --timeout-copy=6000 --needs-internet=try --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:scifem,src:nanobind --apt-upgrade fenics --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 '--env=ADT_TEST_TRIGGERS=scifem/0.16.1-1build2 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-15@sto01-s390x-19.secgroup --name adt-resolute-s390x-fenics-20260202-135052-juju-7f2275-prod-proposed-migration-environment-15-f43ac27d-4ac7-4ad5-83f4-43cabf46f1fc --image adt/ubuntu-resolute-s390x-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-15 --net-id=net_prod-autopkgtest-workers-s390x -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 4s Creating nova instance adt-resolute-s390x-fenics-20260202-135052-juju-7f2275-prod-proposed-migration-environment-15-f43ac27d-4ac7-4ad5-83f4-43cabf46f1fc from image adt/ubuntu-resolute-s390x-server-20260202.img (UUID 2cf7d089-99a1-4704-af48-01d74c62f797)... 82s autopkgtest [13:52:14]: testbed dpkg architecture: s390x 82s autopkgtest [13:52:14]: testbed apt version: 3.1.14 83s autopkgtest [13:52:15]: @@@@@@@@@@@@@@@@@@@@ test bed setup 83s autopkgtest [13:52:15]: testbed release detected to be: None 84s autopkgtest [13:52:16]: updating testbed package index (apt update) 84s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 84s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 85s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 85s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 85s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [102 kB] 85s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [27.9 kB] 85s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [1266 kB] 85s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [2816 B] 85s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main s390x Packages [115 kB] 85s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/universe s390x Packages [995 kB] 85s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse s390x Packages [7016 B] 87s Fetched 2640 kB in 2s (1342 kB/s) 91s 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 98s Reading package lists... 98s Reading package lists... 99s Building dependency tree... 99s Reading state information... 100s Calculating upgrade... 101s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 101s autopkgtest [13:52:33]: upgrading testbed (apt dist-upgrade and autopurge) 101s Reading package lists... 102s Building dependency tree... 102s Reading state information... 102s Calculating upgrade... 103s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 104s Reading package lists... 105s Building dependency tree... 105s Reading state information... 105s Solving dependencies... 107s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 110s autopkgtest [13:52:42]: testbed running kernel: Linux 6.18.0-9-generic #9-Ubuntu SMP Mon Jan 12 15:39:23 UTC 2026 110s autopkgtest [13:52:42]: @@@@@@@@@@@@@@@@@@@@ apt-source fenics 115s Get:1 http://ftpmaster.internal/ubuntu resolute/universe fenics 2:0.10.0.1 (dsc) [1921 B] 115s Get:2 http://ftpmaster.internal/ubuntu resolute/universe fenics 2:0.10.0.1 (tar) [6020 B] 118s gpgv: Signature made Mon Dec 22 12:00:08 2025 UTC 118s gpgv: using RSA key 23C9A93E585819E9126D0A36573EF1E4BD5A01FA 118s gpgv: Can't check signature: No public key 118s dpkg-source: warning: cannot verify inline signature for ./fenics_0.10.0.1.dsc: no acceptable signature found 118s autopkgtest [13:52:50]: testing package fenics version 2:0.10.0.1 119s autopkgtest [13:52:51]: build not needed 119s autopkgtest [13:52:51]: test test-fenics: preparing testbed 120s Reading package lists... 121s Building dependency tree... 121s Reading state information... 122s Solving dependencies... 122s Some packages could not be installed. This may mean that you have 122s requested an impossible situation or if you are using the unstable 122s distribution that some required packages have not yet been created 122s or been moved out of Incoming. 122s The following information may help to resolve the situation: 122s 122s The following packages have unmet dependencies: 122s satisfy:command-line : Depends: fenics but it is not going to be installed 122s Depends: fenicsx but it is not going to be installed 122s Depends: debhelper-compat (= 13) 122s Depends: build-essential but it is not going to be installed 122s Depends: python3-dolfinx-mpc but it is not going to be installed 122s Depends: python3-adios4dolfinx but it is not going to be installed 122s Depends: python3-scifem but it is not going to be installed 122s Depends: python3-all but it is not going to be installed 122s E: Unable to satisfy dependencies. Reached two conflicting assignments: 122s 1. python3:s390x is selected for install because: 122s 1. satisfy:command-line:s390x=1 is selected for install 122s 2. satisfy:command-line:s390x Depends python3-dolfinx-mpc 122s 3. python3-dolfinx-mpc:s390x Depends python3 (< 3.15) and Depends python3 (>= 3.13~) 122s 2. python3:s390x is available in versions 3.13.9-3, 3.14.2-1 122s but none of the choices are installable: 122s - python3:s390x=3.13.9-3 is not selected for install 122s - python3:s390x=3.14.2-1 is not selected for install 123s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 124s Reading package lists... 125s Building dependency tree... 125s Reading state information... 125s Solving dependencies... 125s Some packages could not be installed. This may mean that you have 125s requested an impossible situation or if you are using the unstable 125s distribution that some required packages have not yet been created 125s or been moved out of Incoming. 125s The following information may help to resolve the situation: 125s 125s The following packages have unmet dependencies: 126s satisfy:command-line : Depends: fenics but it is not going to be installed 126s Depends: fenicsx but it is not going to be installed 126s Depends: debhelper-compat (= 13) 126s Depends: build-essential but it is not going to be installed 126s Depends: python3-dolfinx-mpc but it is not going to be installed 126s Depends: python3-adios4dolfinx but it is not going to be installed 126s Depends: python3-scifem but it is not going to be installed 126s Depends: python3-all but it is not going to be installed 126s E: Unable to satisfy dependencies. Reached two conflicting assignments: 126s 1. python3-pybind11:s390x=2.13.6-2 is not selected for install 126s 2. python3-pybind11:s390x=2.13.6-2 is selected for install because: 126s 1. satisfy:command-line:s390x=1 is selected for install 126s 2. satisfy:command-line:s390x Depends fenics 126s 3. fenics:s390x Depends python3-dolfin (>= 2019.2~) 126s 4. python3-dolfin:s390x Depends python3-pybind11 (< 3) 126s test-fenics FAIL badpkg 126s blame: fenicsautopkgtest [13:52:58]: test test-fenicsx: preparing testbed 126s 126s 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. 127s Reading package lists... 128s Building dependency tree... 128s Reading state information... 128s Solving dependencies... 128s Some packages could not be installed. This may mean that you have 128s requested an impossible situation or if you are using the unstable 128s distribution that some required packages have not yet been created 128s or been moved out of Incoming. 128s The following information may help to resolve the situation: 128s 128s The following packages have unmet dependencies: 129s satisfy:command-line : Depends: fenics but it is not going to be installed 129s Depends: fenicsx but it is not going to be installed 129s Depends: debhelper-compat (= 13) 129s Depends: build-essential but it is not going to be installed 129s Depends: python3-dolfinx-mpc but it is not going to be installed 129s Depends: python3-adios4dolfinx but it is not going to be installed 129s Depends: python3-scifem but it is not going to be installed 129s Depends: python3-all but it is not going to be installed 129s E: Unable to satisfy dependencies. Reached two conflicting assignments: 129s 1. python3-pybind11:s390x=2.13.6-2 is not selected for install 129s 2. python3-pybind11:s390x=2.13.6-2 is selected for install because: 129s 1. satisfy:command-line:s390x=1 is selected for install 129s 2. satisfy:command-line:s390x Depends fenics 129s 3. fenics:s390x Depends python3-dolfin (>= 2019.2~) 129s 4. python3-dolfin:s390x Depends python3-pybind11 (< 3) 129s test-fenicsx FAIL badpkg 129s blame: fenics 129s 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. 129s autopkgtest [13:53:01]: @@@@@@@@@@@@@@@@@@@@ summary 129s test-fenics FAIL badpkg 129s blame: fenics 129s 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. 129s test-fenicsx FAIL badpkg 129s blame: fenics 129s 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.