0s autopkgtest [12:10:13]: starting date and time: 2025-11-17 12:10:13+0000 0s autopkgtest [12:10:13]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [12:10:13]: host juju-7f2275-prod-proposed-migration-environment-20; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.k82kpdpc/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 scifem --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-2.secgroup --name adt-resolute-s390x-scifem-20251117-121012-juju-7f2275-prod-proposed-migration-environment-20-ff5212d3-b003-4b13-8491-3def00e69a05 --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-scifem-20251117-121012-juju-7f2275-prod-proposed-migration-environment-20-ff5212d3-b003-4b13-8491-3def00e69a05 from image adt/ubuntu-resolute-s390x-server-20251117.img (UUID a3a3e3b9-e6ba-478c-a5e9-fce6f0982a95)... 52s autopkgtest [12:11:05]: testbed dpkg architecture: s390x 53s autopkgtest [12:11:06]: testbed apt version: 3.1.11 53s autopkgtest [12:11:06]: @@@@@@@@@@@@@@@@@@@@ test bed setup 53s autopkgtest [12:11:06]: testbed release detected to be: None 54s autopkgtest [12:11:07]: updating testbed package index (apt update) 54s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [87.8 kB] 54s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 54s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 54s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 54s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [868 kB] 55s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [9848 B] 55s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [22.9 kB] 55s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [81.1 kB] 55s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main s390x Packages [138 kB] 55s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/restricted s390x Packages [940 B] 55s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/universe s390x Packages [545 kB] 55s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse s390x Packages [10.6 kB] 55s Fetched 1764 kB in 1s (1512 kB/s) 56s Reading package lists... 57s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 57s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 57s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 57s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 57s Reading package lists... 57s Reading package lists... 58s Building dependency tree... 58s Reading state information... 58s Calculating upgrade... 58s The following packages will be upgraded: 58s libpython3-stdlib python3 python3-minimal usbutils 58s 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 58s Need to get 148 kB of archives. 58s After this operation, 4096 B disk space will be freed. 58s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed/main s390x python3-minimal s390x 3.13.7-2 [27.8 kB] 58s Get:2 http://ftpmaster.internal/ubuntu resolute-proposed/main s390x python3 s390x 3.13.7-2 [23.9 kB] 58s Get:3 http://ftpmaster.internal/ubuntu resolute-proposed/main s390x libpython3-stdlib s390x 3.13.7-2 [10.6 kB] 58s Get:4 http://ftpmaster.internal/ubuntu resolute/main s390x usbutils s390x 1:019-1 [85.6 kB] 58s dpkg-preconfigure: unable to re-open stdin: No such file or directory 58s Fetched 148 kB in 0s (351 kB/s) 59s (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.) 59s Preparing to unpack .../python3-minimal_3.13.7-2_s390x.deb ... 59s Unpacking python3-minimal (3.13.7-2) over (3.13.7-1) ... 59s Setting up python3-minimal (3.13.7-2) ... 59s (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.) 59s Preparing to unpack .../python3_3.13.7-2_s390x.deb ... 59s running python pre-rtupdate hooks for python3.13... 59s Unpacking python3 (3.13.7-2) over (3.13.7-1) ... 59s Preparing to unpack .../libpython3-stdlib_3.13.7-2_s390x.deb ... 59s Unpacking libpython3-stdlib:s390x (3.13.7-2) over (3.13.7-1) ... 59s Preparing to unpack .../usbutils_1%3a019-1_s390x.deb ... 59s Unpacking usbutils (1:019-1) over (1:018-2) ... 59s Setting up usbutils (1:019-1) ... 59s Setting up libpython3-stdlib:s390x (3.13.7-2) ... 59s Setting up python3 (3.13.7-2) ... 59s running python rtupdate hooks for python3.13... 59s running python post-rtupdate hooks for python3.13... 59s Processing triggers for man-db (2.13.1-1) ... 60s autopkgtest [12:11:13]: upgrading testbed (apt dist-upgrade and autopurge) 60s Reading package lists... 60s Building dependency tree... 60s Reading state information... 60s Calculating upgrade... 60s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 60s Reading package lists... 61s Building dependency tree... 61s Reading state information... 61s Solving dependencies... 61s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 63s autopkgtest [12:11:16]: testbed running kernel: Linux 6.17.0-5-generic #5-Ubuntu SMP Mon Sep 22 08:56:47 UTC 2025 63s autopkgtest [12:11:16]: @@@@@@@@@@@@@@@@@@@@ apt-source scifem 65s Get:1 http://ftpmaster.internal/ubuntu resolute/universe scifem 0.6.0-2 (dsc) [2418 B] 65s Get:2 http://ftpmaster.internal/ubuntu resolute/universe scifem 0.6.0-2 (tar) [1931 kB] 65s Get:3 http://ftpmaster.internal/ubuntu resolute/universe scifem 0.6.0-2 (diff) [4496 B] 65s gpgv: Signature made Fri May 30 11:06:51 2025 UTC 65s gpgv: using RSA key 23C9A93E585819E9126D0A36573EF1E4BD5A01FA 65s gpgv: Can't check signature: No public key 65s dpkg-source: warning: cannot verify inline signature for ./scifem_0.6.0-2.dsc: no acceptable signature found 65s autopkgtest [12:11:18]: testing package scifem version 0.6.0-2 66s autopkgtest [12:11:19]: build not needed 70s autopkgtest [12:11:23]: test command1: preparing testbed 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: python3-scifem but it is not going to be installed 70s Depends: python3-nibabel but it is not going to be installed 70s Depends: python3-pytest but it is not going to be installed 70s Depends: python3-all-dev 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 python3-scifem 70s 3. python3-scifem:s390x Depends python3-basix 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 1-2. python3-scifem:s390x is selected for install as above 70s 3. python3-scifem:s390x is available in version 0.6.0-2 70s 4. python3-basix:s390x=0.9.0-4 Breaks python3-scifem (< 0.10.0-1~) 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 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: python3-scifem but it is not going to be installed 71s Depends: python3-nibabel but it is not going to be installed 71s Depends: python3-pytest but it is not going to be installed 71s Depends: python3-all-dev 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 python3-scifem 71s 3. python3-scifem:s390x Depends python3-basix 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 1-2. python3-scifem:s390x is selected for install as above 71s 3. python3-scifem:s390x is available in version 0.6.0-2 71s 4. python3-basix:s390x=0.9.0-4 Breaks python3-scifem (< 0.10.0-1~) 71s - python3-basix:s390x=0.9.0-2build2 is not selected for install 71s autopkgtest [12:11:24]: test command2: preparing testbed 71s command1 FAIL badpkg 71s blame: scifem 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. 92s Creating nova instance adt-resolute-s390x-scifem-20251117-121012-juju-7f2275-prod-proposed-migration-environment-20-ff5212d3-b003-4b13-8491-3def00e69a05 from image adt/ubuntu-resolute-s390x-server-20251117.img (UUID a3a3e3b9-e6ba-478c-a5e9-fce6f0982a95)... 131s autopkgtest [12:12:24]: testbed dpkg architecture: s390x 132s autopkgtest [12:12:25]: testbed apt version: 3.1.11 132s autopkgtest [12:12:25]: @@@@@@@@@@@@@@@@@@@@ test bed setup 132s autopkgtest [12:12:25]: testbed release detected to be: resolute 133s autopkgtest [12:12:26]: updating testbed package index (apt update) 133s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [87.8 kB] 133s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 133s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 133s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 133s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [81.1 kB] 133s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [22.9 kB] 133s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [868 kB] 134s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [9848 B] 134s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main s390x Packages [138 kB] 134s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/restricted s390x Packages [940 B] 134s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/universe s390x Packages [545 kB] 134s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse s390x Packages [10.6 kB] 134s Fetched 1764 kB in 1s (1558 kB/s) 135s Reading package lists... 135s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 135s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 135s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 135s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 136s Reading package lists... 136s Reading package lists... 136s Building dependency tree... 136s Reading state information... 136s Calculating upgrade... 136s The following packages will be upgraded: 136s libpython3-stdlib python3 python3-minimal usbutils 137s 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 137s Need to get 148 kB of archives. 137s After this operation, 4096 B disk space will be freed. 137s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed/main s390x python3-minimal s390x 3.13.7-2 [27.8 kB] 137s Get:2 http://ftpmaster.internal/ubuntu resolute-proposed/main s390x python3 s390x 3.13.7-2 [23.9 kB] 137s Get:3 http://ftpmaster.internal/ubuntu resolute-proposed/main s390x libpython3-stdlib s390x 3.13.7-2 [10.6 kB] 137s Get:4 http://ftpmaster.internal/ubuntu resolute/main s390x usbutils s390x 1:019-1 [85.6 kB] 137s dpkg-preconfigure: unable to re-open stdin: No such file or directory 137s Fetched 148 kB in 0s (331 kB/s) 137s (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.) 137s Preparing to unpack .../python3-minimal_3.13.7-2_s390x.deb ... 137s Unpacking python3-minimal (3.13.7-2) over (3.13.7-1) ... 137s Setting up python3-minimal (3.13.7-2) ... 137s (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.) 137s Preparing to unpack .../python3_3.13.7-2_s390x.deb ... 137s running python pre-rtupdate hooks for python3.13... 137s Unpacking python3 (3.13.7-2) over (3.13.7-1) ... 137s Preparing to unpack .../libpython3-stdlib_3.13.7-2_s390x.deb ... 137s Unpacking libpython3-stdlib:s390x (3.13.7-2) over (3.13.7-1) ... 137s Preparing to unpack .../usbutils_1%3a019-1_s390x.deb ... 137s Unpacking usbutils (1:019-1) over (1:018-2) ... 137s Setting up usbutils (1:019-1) ... 137s Setting up libpython3-stdlib:s390x (3.13.7-2) ... 137s Setting up python3 (3.13.7-2) ... 137s running python rtupdate hooks for python3.13... 137s running python post-rtupdate hooks for python3.13... 137s Processing triggers for man-db (2.13.1-1) ... 138s autopkgtest [12:12:31]: upgrading testbed (apt dist-upgrade and autopurge) 138s Reading package lists... 139s Building dependency tree... 139s Reading state information... 139s Calculating upgrade... 139s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 139s Reading package lists... 139s Building dependency tree... 139s Reading state information... 139s Solving dependencies... 139s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 143s Reading package lists... 144s Building dependency tree... 144s Reading state information... 144s Solving dependencies... 144s Some packages could not be installed. This may mean that you have 144s requested an impossible situation or if you are using the unstable 144s distribution that some required packages have not yet been created 144s or been moved out of Incoming. 144s The following information may help to resolve the situation: 144s 144s The following packages have unmet dependencies: 144s satisfy:command-line : Depends: python3-scifem but it is not going to be installed 144s Depends: python3-pytest but it is not going to be installed 144s Depends: python3-all-dev but it is not going to be installed 144s E: Unable to satisfy dependencies. Reached two conflicting decisions: 144s 1. python3-basix:s390x is selected for install because: 144s 1. satisfy:command-line:s390x=1 is selected for install 144s 2. satisfy:command-line:s390x Depends python3-scifem 144s 3. python3-scifem:s390x Depends python3-basix 144s 2. python3-basix:s390x is available in versions 0.9.0-4, 0.9.0-2build2 144s but none of the choices are installable: 144s - python3-basix:s390x=0.9.0-4 is not selected for install because: 144s 1. satisfy:command-line:s390x=1 is selected for install as above 144s 1-2. python3-scifem:s390x is selected for install as above 144s 3. python3-scifem:s390x is available in version 0.6.0-2 144s 4. python3-basix:s390x=0.9.0-4 Breaks python3-scifem (< 0.10.0-1~) 144s - python3-basix:s390x=0.9.0-2build2 is not selected for install 144s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 144s Reading package lists... 144s Building dependency tree... 144s Reading state information... 144s Solving dependencies... 144s Some packages could not be installed. This may mean that you have 144s requested an impossible situation or if you are using the unstable 144s distribution that some required packages have not yet been created 144s or been moved out of Incoming. 144s The following information may help to resolve the situation: 144s 144s The following packages have unmet dependencies: 144s satisfy:command-line : Depends: python3-scifem but it is not going to be installed 144s Depends: python3-pytest but it is not going to be installed 144s Depends: python3-all-dev but it is not going to be installed 144s E: Unable to satisfy dependencies. Reached two conflicting decisions: 144s 1. python3-basix:s390x is selected for install because: 144s 1. satisfy:command-line:s390x=1 is selected for install 144s 2. satisfy:command-line:s390x Depends python3-scifem 144s 3. python3-scifem:s390x Depends python3-basix 144s 2. python3-basix:s390x is available in versions 0.9.0-4, 0.9.0-2build2 144s but none of the choices are installable: 144s - python3-basix:s390x=0.9.0-4 is not selected for install because: 144s 1. satisfy:command-line:s390x=1 is selected for install as above 144s 1-2. python3-scifem:s390x is selected for install as above 144s 3. python3-scifem:s390x is available in version 0.6.0-2 144s 4. python3-basix:s390x=0.9.0-4 Breaks python3-scifem (< 0.10.0-1~) 144s - python3-basix:s390x=0.9.0-2build2 is not selected for install 144s command2 FAIL badpkg 144s blame: scifem 144s 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. 144s autopkgtest [12:12:37]: test test-MPI: preparing testbed 145s Reading package lists... 145s Building dependency tree... 145s Reading state information... 145s Solving dependencies... 145s Some packages could not be installed. This may mean that you have 145s requested an impossible situation or if you are using the unstable 145s distribution that some required packages have not yet been created 145s or been moved out of Incoming. 145s The following information may help to resolve the situation: 145s 145s The following packages have unmet dependencies: 145s satisfy:command-line : Depends: python3-scifem but it is not going to be installed 145s Depends: python3-nibabel but it is not going to be installed 145s Depends: python3-pytest but it is not going to be installed 145s Depends: python3-all-dev but it is not going to be installed 145s Depends: python3-h5py-mpi but it is not going to be installed 145s Depends: mpi-default-dev but it is not going to be installed 145s E: Unable to satisfy dependencies. Reached two conflicting decisions: 145s 1. python3-basix:s390x is selected for install because: 145s 1. satisfy:command-line:s390x=1 is selected for install 145s 2. satisfy:command-line:s390x Depends python3-scifem 145s 3. python3-scifem:s390x Depends python3-basix 145s 2. python3-basix:s390x is available in versions 0.9.0-4, 0.9.0-2build2 145s but none of the choices are installable: 145s - python3-basix:s390x=0.9.0-4 is not selected for install because: 145s 1. satisfy:command-line:s390x=1 is selected for install as above 145s 1-2. python3-scifem:s390x is selected for install as above 145s 3. python3-scifem:s390x is available in version 0.6.0-2 145s 4. python3-basix:s390x=0.9.0-4 Breaks python3-scifem (< 0.10.0-1~) 145s - python3-basix:s390x=0.9.0-2build2 is not selected for install 145s test-MPI FAIL badpkg 145s blame: scifem 145s 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. 145s autopkgtest [12:12:38]: @@@@@@@@@@@@@@@@@@@@ summary 145s command1 FAIL badpkg 145s blame: scifem 145s 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. 145s command2 FAIL badpkg 145s blame: scifem 145s 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. 145s test-MPI FAIL badpkg 145s blame: scifem 145s 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.