0s autopkgtest [16:34:41]: starting date and time: 2026-02-01 16:34:41+0000 0s autopkgtest [16:34:41]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [16:34:41]: host juju-7f2275-prod-proposed-migration-environment-2; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.hmp8otvd/out --timeout-copy=6000 --needs-internet=try --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:fenics-basix,src:nanobind --apt-upgrade fenics --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 '--env=ADT_TEST_TRIGGERS=fenics-basix/0.10.0.post0-2build1 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-17.secgroup --name adt-resolute-s390x-fenics-20260201-163441-juju-7f2275-prod-proposed-migration-environment-2-af533d68-9edc-4658-a085-2d6466a1a8d0 --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/ 4s Creating nova instance adt-resolute-s390x-fenics-20260201-163441-juju-7f2275-prod-proposed-migration-environment-2-af533d68-9edc-4658-a085-2d6466a1a8d0 from image adt/ubuntu-resolute-s390x-server-20260201.img (UUID 58b979f6-37d7-4dc9-b749-1a4b999f15f8)... 85s autopkgtest [16:36:06]: testbed dpkg architecture: s390x 85s autopkgtest [16:36:06]: testbed apt version: 3.1.14 86s autopkgtest [16:36:07]: @@@@@@@@@@@@@@@@@@@@ test bed setup 86s autopkgtest [16:36:07]: testbed release detected to be: None 87s autopkgtest [16:36:08]: updating testbed package index (apt update) 87s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 87s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 87s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 87s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 88s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [26.6 kB] 88s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [2816 B] 88s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [1210 kB] 88s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [101 kB] 88s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main s390x Packages [109 kB] 88s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/universe s390x Packages [976 kB] 88s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse s390x Packages [6428 B] 89s Fetched 2557 kB in 1s (1705 kB/s) 93s Reading package lists... 95s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 95s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 95s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 95s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 100s Reading package lists... 100s Reading package lists... 100s Building dependency tree... 100s Reading state information... 102s Calculating upgrade... 103s The following packages will be upgraded: 103s rust-coreutils xfsprogs 103s 2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 103s Need to get 4993 kB of archives. 103s After this operation, 1751 kB of additional disk space will be used. 103s Get:1 http://ftpmaster.internal/ubuntu resolute/main s390x rust-coreutils s390x 0.5.0-0ubuntu2 [3863 kB] 103s Get:2 http://ftpmaster.internal/ubuntu resolute/main s390x xfsprogs s390x 6.18.0-3 [1131 kB] 104s dpkg-preconfigure: unable to re-open stdin: No such file or directory 104s Fetched 4993 kB in 0s (12.6 MB/s) 106s (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 ... 87701 files and directories currently installed.) 106s Preparing to unpack .../rust-coreutils_0.5.0-0ubuntu2_s390x.deb ... 106s Unpacking rust-coreutils (0.5.0-0ubuntu2) over (0.5.0-0ubuntu1) ... 108s Setting up rust-coreutils (0.5.0-0ubuntu2) ... 108s (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 ... 89601 files and directories currently installed.) 108s Preparing to unpack .../xfsprogs_6.18.0-3_s390x.deb ... 108s Unpacking xfsprogs (6.18.0-3) over (6.17.0-2) ... 109s Setting up xfsprogs (6.18.0-3) ... 109s update-initramfs: deferring update (trigger activated) 113s Processing triggers for libc-bin (2.42-2ubuntu4) ... 113s Processing triggers for man-db (2.13.1-1) ... 120s Processing triggers for initramfs-tools (0.150ubuntu7) ... 120s update-initramfs: Generating /boot/initrd.img-6.18.0-9-generic 137s Using config file '/etc/zipl.conf' 137s Building bootmap in '/boot' 137s Adding IPL section 'ubuntu' (default) 137s Preparing boot device: vda. 137s Done. 139s autopkgtest [16:37:00]: upgrading testbed (apt dist-upgrade and autopurge) 139s Reading package lists... 140s Building dependency tree... 140s Reading state information... 140s Calculating upgrade... 141s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 141s Reading package lists... 142s Building dependency tree... 142s Reading state information... 142s Solving dependencies... 143s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 143s autopkgtest [16:37:04]: rebooting testbed after setup commands that affected boot 188s autopkgtest [16:37:49]: testbed running kernel: Linux 6.18.0-9-generic #9-Ubuntu SMP Mon Jan 12 15:39:23 UTC 2026 192s autopkgtest [16:37:53]: @@@@@@@@@@@@@@@@@@@@ apt-source fenics 196s Get:1 http://ftpmaster.internal/ubuntu resolute/universe fenics 2:0.10.0.1 (dsc) [1921 B] 196s Get:2 http://ftpmaster.internal/ubuntu resolute/universe fenics 2:0.10.0.1 (tar) [6020 B] 196s gpgv: Signature made Mon Dec 22 12:00:08 2025 UTC 196s gpgv: using RSA key 23C9A93E585819E9126D0A36573EF1E4BD5A01FA 196s gpgv: Can't check signature: No public key 196s dpkg-source: warning: cannot verify inline signature for ./fenics_0.10.0.1.dsc: no acceptable signature found 196s autopkgtest [16:37:57]: testing package fenics version 2:0.10.0.1 197s autopkgtest [16:37:58]: build not needed 197s autopkgtest [16:37:58]: test test-fenics: preparing testbed 197s Reading package lists... 198s Building dependency tree... 198s Reading state information... 199s Solving dependencies... 199s Some packages could not be installed. This may mean that you have 199s requested an impossible situation or if you are using the unstable 199s distribution that some required packages have not yet been created 199s or been moved out of Incoming. 199s The following information may help to resolve the situation: 199s 199s The following packages have unmet dependencies: 199s satisfy:command-line : Depends: fenics but it is not going to be installed 199s Depends: fenicsx but it is not going to be installed 199s Depends: debhelper-compat (= 13) 199s Depends: build-essential but it is not going to be installed 199s Depends: python3-dolfinx-mpc but it is not going to be installed 199s Depends: python3-adios4dolfinx but it is not going to be installed 199s Depends: python3-scifem but it is not going to be installed 199s Depends: python3-all but it is not going to be installed 199s E: Unable to satisfy dependencies. Reached two conflicting assignments: 199s 1. python3-nanobind:s390x=2.9.2-2 is not selected for install 199s 2. python3-nanobind:s390x=2.9.2-2 is selected for install because: 199s 1. satisfy:command-line:s390x=1 is selected for install 199s 2. satisfy:command-line:s390x Depends python3-dolfinx-mpc 199s 3. python3-dolfinx-mpc:s390x Depends python3-nanobind-abi16 199s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 200s Reading package lists... 201s Building dependency tree... 201s Reading state information... 201s Solving dependencies... 201s Some packages could not be installed. This may mean that you have 201s requested an impossible situation or if you are using the unstable 201s distribution that some required packages have not yet been created 201s or been moved out of Incoming. 201s The following information may help to resolve the situation: 201s 201s The following packages have unmet dependencies: 201s satisfy:command-line : Depends: fenics but it is not going to be installed 201s Depends: fenicsx but it is not going to be installed 201s Depends: debhelper-compat (= 13) 201s Depends: build-essential but it is not going to be installed 201s Depends: python3-dolfinx-mpc but it is not going to be installed 201s Depends: python3-adios4dolfinx but it is not going to be installed 201s Depends: python3-scifem but it is not going to be installed 201s Depends: python3-all but it is not going to be installed 201s E: Unable to satisfy dependencies. Reached two conflicting assignments: 201s 1. python3-nanobind:s390x=2.9.2-2 is not selected for install 201s 2. python3-nanobind:s390x=2.9.2-2 is selected for install because: 201s 1. satisfy:command-line:s390x=1 is selected for install 201s 2. satisfy:command-line:s390x Depends python3-dolfinx-mpc 201s 3. python3-dolfinx-mpc:s390x Depends python3-nanobind-abi16 201s test-fenics FAIL badpkg 201s blame: fenics 201s 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. 201s autopkgtest [16:38:02]: test test-fenicsx: preparing testbed 202s Reading package lists... 203s Building dependency tree... 203s Reading state information... 203s Solving dependencies... 203s Some packages could not be installed. This may mean that you have 203s requested an impossible situation or if you are using the unstable 203s distribution that some required packages have not yet been created 203s or been moved out of Incoming. 203s The following information may help to resolve the situation: 203s 203s The following packages have unmet dependencies: 203s satisfy:command-line : Depends: fenics but it is not going to be installed 203s Depends: fenicsx but it is not going to be installed 203s Depends: debhelper-compat (= 13) 203s Depends: build-essential but it is not going to be installed 203s Depends: python3-dolfinx-mpc but it is not going to be installed 203s Depends: python3-adios4dolfinx but it is not going to be installed 203s Depends: python3-scifem but it is not going to be installed 203s Depends: python3-all but it is not going to be installed 203s E: Unable to satisfy dependencies. Reached two conflicting assignments: 203s 1. python3-nanobind:s390x=2.9.2-2 is not selected for install 203s 2. python3-nanobind:s390x=2.9.2-2 is selected for install because: 203s 1. satisfy:command-line:s390x=1 is selected for install 203s 2. satisfy:command-line:s390x Depends python3-dolfinx-mpc 203s 3. python3-dolfinx-mpc:s390x Depends python3-nanobind-abi16 204s test-fenicsx FAIL badpkg 204s blame: fenics 204s 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. 204s autopkgtest [16:38:05]: @@@@@@@@@@@@@@@@@@@@ summary 204s test-fenics FAIL badpkg 204s blame: fenics 204s 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. 204s test-fenicsx FAIL badpkg 204s blame: fenics 204s 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.