0s autopkgtest [08:09:52]: starting date and time: 2026-02-05 08:09:52+0000 0s autopkgtest [08:09:52]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [08:09:52]: host juju-7f2275-prod-proposed-migration-environment-2; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.93p4t2g6/out --timeout-copy=6000 --needs-internet=try --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:dolfin,src:pybind11,src:sphinx-rtd-theme --apt-upgrade mshr --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 '--env=ADT_TEST_TRIGGERS=dolfin/2019.2.0~legacy20240219.1c52e83-26build2 pybind11/3.0.1-3 sphinx-rtd-theme/3.1.0+dfsg-1' -- 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-21.secgroup --name adt-resolute-s390x-mshr-20260205-080951-juju-7f2275-prod-proposed-migration-environment-2-57c253c2-0956-4ee6-a529-4aa81fc9a3d7 --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/ 7s Creating nova instance adt-resolute-s390x-mshr-20260205-080951-juju-7f2275-prod-proposed-migration-environment-2-57c253c2-0956-4ee6-a529-4aa81fc9a3d7 from image adt/ubuntu-resolute-s390x-server-20260204.img (UUID d74a484e-59af-441a-876a-2930c3686f89)... 109s autopkgtest [08:11:41]: testbed dpkg architecture: s390x 110s autopkgtest [08:11:42]: testbed apt version: 3.1.14 111s autopkgtest [08:11:43]: @@@@@@@@@@@@@@@@@@@@ test bed setup 112s autopkgtest [08:11:44]: testbed release detected to be: None 113s autopkgtest [08:11:45]: updating testbed package index (apt update) 113s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 113s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 113s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 114s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 114s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [1719 kB] 114s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [35.4 kB] 114s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [5260 B] 114s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [228 kB] 114s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main s390x Packages [257 kB] 114s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/universe s390x Packages [1447 kB] 114s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse s390x Packages [10.4 kB] 115s Fetched 3827 kB in 2s (2204 kB/s) 118s Reading package lists... 118s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 118s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 118s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 118s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 120s Reading package lists... 120s Reading package lists... 121s Building dependency tree... 121s Reading state information... 121s Calculating upgrade... 121s The following packages will be upgraded: 121s pollinate python3-linkify-it python3-referencing sed 121s 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 121s Need to get 254 kB of archives. 121s After this operation, 0 B of additional disk space will be used. 121s Get:1 http://ftpmaster.internal/ubuntu resolute/main s390x sed s390x 4.9-2build3 [198 kB] 121s Get:2 http://ftpmaster.internal/ubuntu resolute/main s390x python3-linkify-it all 2.0.3-1ubuntu3 [19.4 kB] 121s Get:3 http://ftpmaster.internal/ubuntu resolute/main s390x pollinate all 4.33-4ubuntu5 [14.0 kB] 121s Get:4 http://ftpmaster.internal/ubuntu resolute/main s390x python3-referencing all 0.36.2-1ubuntu2 [22.2 kB] 122s dpkg-preconfigure: unable to re-open stdin: No such file or directory 122s Fetched 254 kB in 0s (6544 kB/s) 122s (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 ... 61954 files and directories currently installed.) 122s Preparing to unpack .../sed_4.9-2build3_s390x.deb ... 122s Unpacking sed (4.9-2build3) over (4.9-2build2) ... 123s Setting up sed (4.9-2build3) ... 123s (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 ... 61954 files and directories currently installed.) 123s Preparing to unpack .../python3-linkify-it_2.0.3-1ubuntu3_all.deb ... 123s Unpacking python3-linkify-it (2.0.3-1ubuntu3) over (2.0.3-1ubuntu2) ... 123s Preparing to unpack .../pollinate_4.33-4ubuntu5_all.deb ... 123s Unpacking pollinate (4.33-4ubuntu5) over (4.33-4ubuntu4) ... 123s Preparing to unpack .../python3-referencing_0.36.2-1ubuntu2_all.deb ... 123s Unpacking python3-referencing (0.36.2-1ubuntu2) over (0.36.2-1ubuntu1) ... 124s Setting up pollinate (4.33-4ubuntu5) ... 136s Setting up python3-linkify-it (2.0.3-1ubuntu3) ... 136s Setting up python3-referencing (0.36.2-1ubuntu2) ... 136s Processing triggers for install-info (7.2-5) ... 136s Processing triggers for man-db (2.13.1-1) ... 139s autopkgtest [08:12:11]: upgrading testbed (apt dist-upgrade and autopurge) 145s Reading package lists... 146s Building dependency tree... 146s Reading state information... 146s Calculating upgrade... 146s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 147s Reading package lists... 147s Building dependency tree... 147s Reading state information... 147s Solving dependencies... 148s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 149s autopkgtest [08:12:21]: rebooting testbed after setup commands that affected boot 250s autopkgtest [08:14:02]: testbed running kernel: Linux 6.18.0-9-generic #9-Ubuntu SMP Mon Jan 12 15:39:23 UTC 2026 275s autopkgtest [08:14:27]: @@@@@@@@@@@@@@@@@@@@ apt-source mshr 316s Get:1 http://ftpmaster.internal/ubuntu resolute/universe mshr 2019.2.0~git20230811.ff54a68+dfsg1-7 (dsc) [3027 B] 316s Get:2 http://ftpmaster.internal/ubuntu resolute/universe mshr 2019.2.0~git20230811.ff54a68+dfsg1-7 (tar) [122 kB] 316s Get:3 http://ftpmaster.internal/ubuntu resolute/universe mshr 2019.2.0~git20230811.ff54a68+dfsg1-7 (diff) [15.1 kB] 317s gpgv: Signature made Sun Oct 5 21:12:15 2025 UTC 317s gpgv: using RSA key 23C9A93E585819E9126D0A36573EF1E4BD5A01FA 317s gpgv: Can't check signature: No public key 317s dpkg-source: warning: cannot verify inline signature for ./mshr_2019.2.0~git20230811.ff54a68+dfsg1-7.dsc: no acceptable signature found 318s autopkgtest [08:15:10]: testing package mshr version 2019.2.0~git20230811.ff54a68+dfsg1-7 323s autopkgtest [08:15:15]: build not needed 332s autopkgtest [08:15:24]: test test-mshr-python: preparing testbed 333s Reading package lists... 335s Building dependency tree... 335s Reading state information... 345s Solving dependencies... 345s Some packages could not be installed. This may mean that you have 345s requested an impossible situation or if you are using the unstable 345s distribution that some required packages have not yet been created 345s or been moved out of Incoming. 345s The following information may help to resolve the situation: 345s 345s The following packages have unmet dependencies: 345s satisfy:command-line : Depends: python3-mshr but it is not going to be installed 345s Depends: python3-pytest but it is not going to be installed 345s E: Unable to satisfy dependencies. Reached two conflicting assignments: 345s 1. libssh2-1-dev:s390x is selected for install because: 345s 1. satisfy:command-line:s390x=1 is selected for install 345s 2. satisfy:command-line:s390x Depends python3-mshr 345s 3. python3-mshr:s390x Depends libmshr-dev (>= 2019.2.0~git20230811.ff54a68+dfsg1-7) 345s 4. libmshr-dev:s390x Depends libdolfin-dev (>= 2019.2) 345s 5. libdolfin-dev:s390x Depends libhdf5-mpi-dev 345s 6. libhdf5-mpi-dev:s390x Depends libhdf5-openmpi-dev 345s 7. libhdf5-openmpi-dev:s390x Depends libcurl4-openssl-dev | libcurl-dev 345s [selected libcurl4-gnutls-dev:s390x=8.18.0-1ubuntu1 for install] 345s 8. libcurl4-gnutls-dev:s390x Depends libssh2-1-dev 345s For context, additional choices that could not be installed: 345s * In libhdf5-openmpi-dev:s390x Depends libcurl4-openssl-dev | libcurl-dev: 345s - libcurl4-openssl-dev:s390x is not selected for install 345s - libcurl4-openssl-dev:s390x=8.18.0-1ubuntu1 -> | libcurl4-openssl-dev:s390x 345s but none of the choices are installable: 345s - libcurl4-openssl-dev:s390x is not selected for install 345s 2. libssh2-1-dev:s390x is available in versions 1.11.1-1build1, 1.11.1-1build2 345s but none of the choices are installable: 345s - libssh2-1-dev:s390x=1.11.1-1build1 is not selected for install 345s - libssh2-1-dev:s390x=1.11.1-1build2 is not selected for install 345s E: Solver timed out. 346s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 387s Reading package lists... 388s Building dependency tree... 389s Reading state information... 398s Solving dependencies... 398s Some packages could not be installed. This may mean that you have 398s requested an impossible situation or if you are using the unstable 398s distribution that some required packages have not yet been created 398s or been moved out of Incoming. 398s The following information may help to resolve the situation: 398s 398s The following packages have unmet dependencies: 398s satisfy:command-line : Depends: python3-mshr but it is not going to be installed 398s Depends: python3-pytest but it is not going to be installed 398s E: Unable to satisfy dependencies. Reached two conflicting assignments: 398s 1. python3-pybind11:s390x=2.13.6-2 is not selected for install 398s 2. python3-pybind11:s390x=2.13.6-2 is selected for install because: 398s 1. satisfy:command-line:s390x=1 is selected for install 398s 2. satisfy:command-line:s390x Depends python3-mshr 398s 3. python3-mshr:s390x Depends python3-mshr-real | python3-mshr64-real 398s [selected python3-mshr64-real:s390x for install] 398s 4. python3-mshr64-real:s390x Depends python3-pybind11 (< 3) 398s For context, additional choices that could not be installed: 398s * In python3-mshr:s390x Depends python3-mshr-real | python3-mshr64-real: 398s - python3-mshr-real:s390x Depends python3-dolfin-real (>= 2019.2) 398s but none of the choices are installable: 398s - python3-dolfin-real:s390x is not selected for install 398s E: Solver timed out. 398s autopkgtest [08:16:30]: test test-mshr64-python: preparing testbed 398s test-mshr-python FAIL badpkg 398s blame: mshr 398s 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. 399s Reading package lists... 401s Building dependency tree... 405s Reading state information... 405s Solving dependencies... 405s Some packages could not be installed. This may mean that you have 405s requested an impossible situation or if you are using the unstable 405s distribution that some required packages have not yet been created 405s or been moved out of Incoming. 405s The following information may help to resolve the situation: 405s 405s The following packages have unmet dependencies: 405s satisfy:command-line : Depends: python3-mshr64-real but it is not going to be installed 405s Depends: python3-mshr but it is not going to be installed 405s Depends: python3-pytest but it is not going to be installed 405s E: Unable to satisfy dependencies. Reached two conflicting assignments: 405s 1. python3-pybind11:s390x=2.13.6-2 is not selected for install 405s 2. python3-pybind11:s390x=2.13.6-2 is selected for install because: 405s 1. satisfy:command-line:s390x=1 is selected for install 405s 2. satisfy:command-line:s390x Depends python3-mshr64-real 405s 3. python3-mshr64-real:s390x Depends python3-pybind11 (< 3) 405s test-mshr64-python FAIL badpkg 405s blame: mshr 405s 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. 405s autopkgtest [08:16:34]: @@@@@@@@@@@@@@@@@@@@ summary 405s test-mshr-python FAIL badpkg 405s blame: mshr 405s 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. 405s test-mshr64-python FAIL badpkg 405s blame: mshr 405s 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.