0s autopkgtest [12:10:08]: starting date and time: 2025-11-17 12:10:08+0000 0s autopkgtest [12:10:08]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [12:10:08]: host juju-7f2275-prod-proposed-migration-environment-20; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.fdc9hbva/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-s390x --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-20@bos03-s390x-9.secgroup --name adt-resolute-s390x-fenics-20251117-121008-juju-7f2275-prod-proposed-migration-environment-20-4cd9b8af-d0ae-4273-bb7a-368e3b8cd0a1 --image adt/ubuntu-resolute-s390x-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-20 --net-id=net_prod-proposed-migration-s390x -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 3s Creating nova instance adt-resolute-s390x-fenics-20251117-121008-juju-7f2275-prod-proposed-migration-environment-20-4cd9b8af-d0ae-4273-bb7a-368e3b8cd0a1 from image adt/ubuntu-resolute-s390x-server-20251117.img (UUID a3a3e3b9-e6ba-478c-a5e9-fce6f0982a95)... 56s autopkgtest [12:11:04]: testbed dpkg architecture: s390x 56s autopkgtest [12:11:04]: testbed apt version: 3.1.11 56s autopkgtest [12:11:04]: @@@@@@@@@@@@@@@@@@@@ test bed setup 56s autopkgtest [12:11:04]: testbed release detected to be: None 57s autopkgtest [12:11:05]: updating testbed package index (apt update) 57s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [87.8 kB] 58s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 58s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 58s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 58s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [22.9 kB] 58s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [868 kB] 58s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [9848 B] 58s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [81.1 kB] 58s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main s390x Packages [138 kB] 58s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/restricted s390x Packages [940 B] 58s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/universe s390x Packages [545 kB] 58s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse s390x Packages [10.6 kB] 58s Fetched 1764 kB in 1s (1555 kB/s) 59s Reading package lists... 60s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 60s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 60s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 60s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 60s Reading package lists... 61s Reading package lists... 61s Building dependency tree... 61s Reading state information... 61s Calculating upgrade... 61s The following packages will be upgraded: 61s libpython3-stdlib python3 python3-minimal usbutils 61s 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 61s Need to get 148 kB of archives. 61s After this operation, 4096 B disk space will be freed. 61s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed/main s390x python3-minimal s390x 3.13.7-2 [27.8 kB] 61s Get:2 http://ftpmaster.internal/ubuntu resolute-proposed/main s390x python3 s390x 3.13.7-2 [23.9 kB] 61s Get:3 http://ftpmaster.internal/ubuntu resolute-proposed/main s390x libpython3-stdlib s390x 3.13.7-2 [10.6 kB] 61s Get:4 http://ftpmaster.internal/ubuntu resolute/main s390x usbutils s390x 1:019-1 [85.6 kB] 62s dpkg-preconfigure: unable to re-open stdin: No such file or directory 62s Fetched 148 kB in 1s (276 kB/s) 62s (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 ... 61309 files and directories currently installed.) 62s Preparing to unpack .../python3-minimal_3.13.7-2_s390x.deb ... 62s Unpacking python3-minimal (3.13.7-2) over (3.13.7-1) ... 62s Setting up python3-minimal (3.13.7-2) ... 62s (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 ... 61309 files and directories currently installed.) 62s Preparing to unpack .../python3_3.13.7-2_s390x.deb ... 62s running python pre-rtupdate hooks for python3.13... 62s Unpacking python3 (3.13.7-2) over (3.13.7-1) ... 62s Preparing to unpack .../libpython3-stdlib_3.13.7-2_s390x.deb ... 62s Unpacking libpython3-stdlib:s390x (3.13.7-2) over (3.13.7-1) ... 62s Preparing to unpack .../usbutils_1%3a019-1_s390x.deb ... 62s Unpacking usbutils (1:019-1) over (1:018-2) ... 62s Setting up usbutils (1:019-1) ... 62s Setting up libpython3-stdlib:s390x (3.13.7-2) ... 62s Setting up python3 (3.13.7-2) ... 62s running python rtupdate hooks for python3.13... 62s running python post-rtupdate hooks for python3.13... 62s Processing triggers for man-db (2.13.1-1) ... 63s autopkgtest [12:11:11]: upgrading testbed (apt dist-upgrade and autopurge) 63s Reading package lists... 63s Building dependency tree... 63s Reading state information... 63s Calculating upgrade... 63s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 64s Reading package lists... 64s Building dependency tree... 64s Reading state information... 64s Solving dependencies... 64s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 66s autopkgtest [12:11:14]: testbed running kernel: Linux 6.17.0-5-generic #5-Ubuntu SMP Mon Sep 22 08:56:47 UTC 2025 66s autopkgtest [12:11:14]: @@@@@@@@@@@@@@@@@@@@ apt-source fenics 68s Get:1 http://ftpmaster.internal/ubuntu resolute/universe fenics 2:0.9.0.3 (dsc) [1917 B] 68s Get:2 http://ftpmaster.internal/ubuntu resolute/universe fenics 2:0.9.0.3 (tar) [5964 B] 68s gpgv: Signature made Mon May 5 12:44:30 2025 UTC 68s gpgv: using RSA key 23C9A93E585819E9126D0A36573EF1E4BD5A01FA 68s gpgv: Can't check signature: No public key 68s dpkg-source: warning: cannot verify inline signature for ./fenics_0.9.0.3.dsc: no acceptable signature found 68s autopkgtest [12:11:16]: testing package fenics version 2:0.9.0.3 69s autopkgtest [12:11:17]: build not needed 69s autopkgtest [12:11:17]: test test-fenics: preparing testbed 69s Reading package lists... 69s Building dependency tree... 69s Reading state information... 69s Solving dependencies... 69s Some packages could not be installed. This may mean that you have 69s requested an impossible situation or if you are using the unstable 69s distribution that some required packages have not yet been created 69s or been moved out of Incoming. 69s The following information may help to resolve the situation: 69s 69s The following packages have unmet dependencies: 70s satisfy:command-line : Depends: fenics but it is not going to be installed 70s Depends: fenicsx but it is not going to be installed 70s Depends: debhelper-compat (= 13) 70s Depends: build-essential but it is not going to be installed 70s Depends: python3-dolfinx-mpc but it is not going to be installed 70s Depends: python3-adios4dolfinx but it is not going to be installed 70s Depends: python3-scifem but it is not going to be installed 70s Depends: python3-all but it is not going to be installed 70s E: Unable to satisfy dependencies. Reached two conflicting decisions: 70s 1. python3-basix:s390x is selected for install because: 70s 1. satisfy:command-line:s390x=1 is selected for install 70s 2. satisfy:command-line:s390x Depends fenicsx 70s 3. fenicsx:s390x Depends python3-basix (>= 0.9~) 70s 2. python3-basix:s390x is available in versions 0.9.0-4, 0.9.0-2build2 70s but none of the choices are installable: 70s - python3-basix:s390x=0.9.0-4 is not selected for install because: 70s 1. satisfy:command-line:s390x=1 is selected for install as above 70s 2. satisfy:command-line:s390x Depends python3-dolfinx-mpc 70s 3. python3-dolfinx-mpc:s390x is available in version 0.9.1-2 70s 4. python3-basix:s390x=0.9.0-4 Breaks python3-dolfinx-mpc (< 0.9.3-2~) 70s - python3-basix:s390x=0.9.0-2build2 is not selected for install 70s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 70s Reading package lists... 70s Building dependency tree... 70s Reading state information... 70s Solving dependencies... 70s Some packages could not be installed. This may mean that you have 70s requested an impossible situation or if you are using the unstable 70s distribution that some required packages have not yet been created 70s or been moved out of Incoming. 70s The following information may help to resolve the situation: 70s 70s The following packages have unmet dependencies: 70s satisfy:command-line : Depends: fenics but it is not going to be installed 70s Depends: fenicsx but it is not going to be installed 70s Depends: debhelper-compat (= 13) 70s Depends: build-essential but it is not going to be installed 70s Depends: python3-dolfinx-mpc but it is not going to be installed 70s Depends: python3-adios4dolfinx but it is not going to be installed 70s Depends: python3-scifem but it is not going to be installed 70s Depends: python3-all but it is not going to be installed 70s E: Unable to satisfy dependencies. Reached two conflicting decisions: 70s 1. python3-basix:s390x is selected for install because: 70s 1. satisfy:command-line:s390x=1 is selected for install 70s 2. satisfy:command-line:s390x Depends fenicsx 70s 3. fenicsx:s390x Depends python3-basix (>= 0.9~) 70s 2. python3-basix:s390x is available in versions 0.9.0-4, 0.9.0-2build2 70s but none of the choices are installable: 70s - python3-basix:s390x=0.9.0-4 is not selected for install because: 70s 1. satisfy:command-line:s390x=1 is selected for install as above 70s 2. satisfy:command-line:s390x Depends python3-dolfinx-mpc 70s 3. python3-dolfinx-mpc:s390x is available in version 0.9.1-2 70s 4. python3-basix:s390x=0.9.0-4 Breaks python3-dolfinx-mpc (< 0.9.3-2~) 70s - python3-basix:s390x=0.9.0-2build2 is not selected for install 70s autopkgtest [12:11:18]: test test-fenicsx: preparing testbed 70s test-fenics FAIL badpkg 70s blame: fenics 70s 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. 71s Reading package lists... 71s Building dependency tree... 71s Reading state information... 71s Solving dependencies... 71s Some packages could not be installed. This may mean that you have 71s requested an impossible situation or if you are using the unstable 71s distribution that some required packages have not yet been created 71s or been moved out of Incoming. 71s The following information may help to resolve the situation: 71s 71s The following packages have unmet dependencies: 71s satisfy:command-line : Depends: fenics but it is not going to be installed 71s Depends: fenicsx but it is not going to be installed 71s Depends: debhelper-compat (= 13) 71s Depends: build-essential but it is not going to be installed 71s Depends: python3-dolfinx-mpc but it is not going to be installed 71s Depends: python3-adios4dolfinx but it is not going to be installed 71s Depends: python3-scifem but it is not going to be installed 71s Depends: python3-all but it is not going to be installed 71s E: Unable to satisfy dependencies. Reached two conflicting decisions: 71s 1. python3-basix:s390x is selected for install because: 71s 1. satisfy:command-line:s390x=1 is selected for install 71s 2. satisfy:command-line:s390x Depends fenicsx 71s 3. fenicsx:s390x Depends python3-basix (>= 0.9~) 71s 2. python3-basix:s390x is available in versions 0.9.0-4, 0.9.0-2build2 71s but none of the choices are installable: 71s - python3-basix:s390x=0.9.0-4 is not selected for install because: 71s 1. satisfy:command-line:s390x=1 is selected for install as above 71s 2. satisfy:command-line:s390x Depends python3-dolfinx-mpc 71s 3. python3-dolfinx-mpc:s390x is available in version 0.9.1-2 71s 4. python3-basix:s390x=0.9.0-4 Breaks python3-dolfinx-mpc (< 0.9.3-2~) 71s - python3-basix:s390x=0.9.0-2build2 is not selected for install 71s autopkgtest [12:11:19]: @@@@@@@@@@@@@@@@@@@@ summary 71s test-fenics FAIL badpkg 71s blame: fenics 71s 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. 71s test-fenicsx FAIL badpkg 71s blame: fenics 71s 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. 71s test-fenicsx FAIL badpkg 71s blame: fenics 71s 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.