0s autopkgtest [01:48:14]: starting date and time: 2024-12-03 01:48:14+0000 0s autopkgtest [01:48:14]: git checkout: be626eda Fix armhf LXD image generation for plucky 0s autopkgtest [01:48:14]: host juju-7f2275-prod-proposed-migration-environment-2; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.j_cktvlt/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:openmpi,src:ampliconnoise,src:armci-mpi,src:eztrace,src:murasaki --apt-upgrade hypre --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 '--env=ADT_TEST_TRIGGERS=openmpi/5.0.6-3 ampliconnoise/1.29-15build1 armci-mpi/0.4-4 eztrace/2.1.1-4 murasaki/1.68.6-14build1' -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest-s390x --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-2@bos03-s390x-24.secgroup --name adt-plucky-s390x-hypre-20241203-014812-juju-7f2275-prod-proposed-migration-environment-2-c42b4cc1-065b-4654-aa1b-df5aa61362d6 --image adt/ubuntu-plucky-s390x-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-2 --net-id=net_prod-proposed-migration-s390x -e TERM=linux -e ''"'"'http_proxy=http://squid.internal:3128'"'"'' -e ''"'"'https_proxy=http://squid.internal:3128'"'"'' -e ''"'"'no_proxy=127.0.0.1,127.0.1.1,login.ubuntu.com,localhost,localdomain,novalocal,internal,archive.ubuntu.com,ports.ubuntu.com,security.ubuntu.com,ddebs.ubuntu.com,changelogs.ubuntu.com,keyserver.ubuntu.com,launchpadlibrarian.net,launchpadcontent.net,launchpad.net,10.24.0.0/24,keystone.ps5.canonical.com,objectstorage.prodstack5.canonical.com'"'"'' --mirror=http://ftpmaster.internal/ubuntu/ 144s autopkgtest [01:50:38]: testbed dpkg architecture: s390x 144s autopkgtest [01:50:38]: testbed apt version: 2.9.14ubuntu1 144s autopkgtest [01:50:38]: @@@@@@@@@@@@@@@@@@@@ test bed setup 144s autopkgtest [01:50:38]: testbed release detected to be: None 145s autopkgtest [01:50:39]: updating testbed package index (apt update) 145s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB] 145s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 146s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 146s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 146s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [68.3 kB] 146s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [781 kB] 146s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [15.1 kB] 146s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B] 146s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main s390x Packages [129 kB] 146s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted s390x Packages [928 B] 146s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe s390x Packages [635 kB] 146s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse s390x Packages [7964 B] 146s Fetched 1721 kB in 1s (1949 kB/s) 147s Reading package lists... 147s Reading package lists... 147s Building dependency tree... 147s Reading state information... 147s Calculating upgrade... 148s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 148s Reading package lists... 148s Building dependency tree... 148s Reading state information... 148s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 148s autopkgtest [01:50:42]: upgrading testbed (apt dist-upgrade and autopurge) 148s Reading package lists... 148s Building dependency tree... 148s Reading state information... 148s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 148s Starting 2 pkgProblemResolver with broken count: 0 148s Done 149s Entering ResolveByKeep 149s 149s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 149s Reading package lists... 149s Building dependency tree... 149s Reading state information... 149s Starting pkgProblemResolver with broken count: 0 149s Starting 2 pkgProblemResolver with broken count: 0 149s Done 149s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 152s autopkgtest [01:50:46]: testbed running kernel: Linux 6.11.0-8-generic #8-Ubuntu SMP Mon Sep 16 12:49:35 UTC 2024 152s autopkgtest [01:50:46]: @@@@@@@@@@@@@@@@@@@@ apt-source hypre 157s Get:1 http://ftpmaster.internal/ubuntu plucky/universe hypre 2.31.0-1exp2 (dsc) [3485 B] 157s Get:2 http://ftpmaster.internal/ubuntu plucky/universe hypre 2.31.0-1exp2 (tar) [7491 kB] 157s Get:3 http://ftpmaster.internal/ubuntu plucky/universe hypre 2.31.0-1exp2 (diff) [20.8 kB] 157s gpgv: Signature made Sun Aug 4 10:09:26 2024 UTC 158s gpgv: using RSA key 23C9A93E585819E9126D0A36573EF1E4BD5A01FA 158s gpgv: Can't check signature: No public key 158s dpkg-source: warning: cannot verify inline signature for ./hypre_2.31.0-1exp2.dsc: no acceptable signature found 158s autopkgtest [01:50:52]: testing package hypre version 2.31.0-1exp2 162s autopkgtest [01:50:56]: build not needed 166s autopkgtest [01:51:00]: test test-hypre: preparing testbed 167s Reading package lists... 167s Building dependency tree... 167s Reading state information... 167s Starting pkgProblemResolver with broken count: 1 167s Starting 2 pkgProblemResolver with broken count: 1 167s Investigating (0) libopenmpi40:s390x < none -> 5.0.6-3 @un puN Ib > 167s Broken libopenmpi40:s390x Breaks on libopenmpi3:s390x < none @un H > (< 5.0.6-3) 167s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 167s Considering libopenmpi3t64:s390x 4 as a solution to libopenmpi40:s390x 1 167s Re-Instated libopenmpi3t64:s390x 167s Broken libopenmpi40:s390x Breaks on libopenmpi3t64:s390x < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 167s Considering libopenmpi3t64:s390x 1 as a solution to libopenmpi40:s390x 1 167s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 167s Done 167s Some packages could not be installed. This may mean that you have 167s requested an impossible situation or if you are using the unstable 167s distribution that some required packages have not yet been created 167s or been moved out of Incoming. 167s The following information may help to resolve the situation: 167s 167s The following packages have unmet dependencies: 167s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 167s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 167s E: Unable to correct problems, you have held broken packages. 167s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed 167s Reading package lists... 168s Building dependency tree... 168s Reading state information... 168s Starting pkgProblemResolver with broken count: 1 168s Starting 2 pkgProblemResolver with broken count: 1 168s Investigating (0) libopenmpi40:s390x < none -> 5.0.6-3 @un puN Ib > 168s Broken libopenmpi40:s390x Breaks on libopenmpi3:s390x < none @un H > (< 5.0.6-3) 168s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 168s Considering libopenmpi3t64:s390x -1 as a solution to libopenmpi40:s390x 6 168s Broken libopenmpi40:s390x Breaks on libopenmpi3t64:s390x < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 168s Considering libopenmpi3t64:s390x -1 as a solution to libopenmpi40:s390x 6 168s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 168s Done 168s Some packages could not be installed. This may mean that you have 168s requested an impossible situation or if you are using the unstable 168s distribution that some required packages have not yet been created 168s or been moved out of Incoming. 168s The following information may help to resolve the situation: 168s 168s The following packages have unmet dependencies: 168s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 168s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 168s E: Unable to correct problems, you have held broken packages. 168s autopkgtest [01:51:02]: test test-hypre64: preparing testbed 168s test-hypre FAIL badpkg 168s blame: hypre 168s 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. 596s autopkgtest [01:58:10]: testbed dpkg architecture: s390x 596s autopkgtest [01:58:10]: testbed apt version: 2.9.14ubuntu1 597s autopkgtest [01:58:11]: @@@@@@@@@@@@@@@@@@@@ test bed setup 597s autopkgtest [01:58:11]: testbed release detected to be: plucky 598s autopkgtest [01:58:12]: updating testbed package index (apt update) 598s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB] 598s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 598s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 599s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 599s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [781 kB] 599s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [15.1 kB] 599s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [68.3 kB] 599s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B] 599s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main s390x Packages [129 kB] 599s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted s390x Packages [928 B] 599s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe s390x Packages [635 kB] 599s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse s390x Packages [7964 B] 599s Fetched 1721 kB in 1s (1951 kB/s) 600s Reading package lists... 600s Reading package lists... 600s Building dependency tree... 600s Reading state information... 600s Calculating upgrade... 600s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 600s Reading package lists... 601s Building dependency tree... 601s Reading state information... 601s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 601s autopkgtest [01:58:15]: upgrading testbed (apt dist-upgrade and autopurge) 601s Reading package lists... 601s Building dependency tree... 601s Reading state information... 601s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 601s Starting 2 pkgProblemResolver with broken count: 0 601s Done 601s Entering ResolveByKeep 601s 602s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 602s Reading package lists... 602s Building dependency tree... 602s Reading state information... 602s Starting pkgProblemResolver with broken count: 0 602s Starting 2 pkgProblemResolver with broken count: 0 602s Done 602s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 605s Reading package lists... 605s Building dependency tree... 605s Reading state information... 605s Starting pkgProblemResolver with broken count: 1 605s Starting 2 pkgProblemResolver with broken count: 1 605s Investigating (0) libopenmpi40:s390x < none -> 5.0.6-3 @un puN Ib > 605s Broken libopenmpi40:s390x Breaks on libopenmpi3:s390x < none @un H > (< 5.0.6-3) 605s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 605s Considering libopenmpi3t64:s390x 6 as a solution to libopenmpi40:s390x 1 605s Re-Instated libopenmpi3t64:s390x 605s Broken libopenmpi40:s390x Breaks on libopenmpi3t64:s390x < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 605s Considering libopenmpi3t64:s390x 1 as a solution to libopenmpi40:s390x 1 605s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 605s Done 605s Some packages could not be installed. This may mean that you have 605s requested an impossible situation or if you are using the unstable 605s distribution that some required packages have not yet been created 605s or been moved out of Incoming. 605s The following information may help to resolve the situation: 605s 605s The following packages have unmet dependencies: 605s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 605s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 605s E: Unable to correct problems, you have held broken packages. 605s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed 605s Reading package lists... 605s Building dependency tree... 605s Reading state information... 606s Starting pkgProblemResolver with broken count: 1 606s Starting 2 pkgProblemResolver with broken count: 1 606s Investigating (0) libopenmpi40:s390x < none -> 5.0.6-3 @un puN Ib > 606s Broken libopenmpi40:s390x Breaks on libopenmpi3:s390x < none @un H > (< 5.0.6-3) 606s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 606s Considering libopenmpi3t64:s390x 0 as a solution to libopenmpi40:s390x 7 606s Broken libopenmpi40:s390x Breaks on libopenmpi3t64:s390x < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 606s Considering libopenmpi3t64:s390x 0 as a solution to libopenmpi40:s390x 7 606s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 606s Done 606s Some packages could not be installed. This may mean that you have 606s requested an impossible situation or if you are using the unstable 606s distribution that some required packages have not yet been created 606s or been moved out of Incoming. 606s The following information may help to resolve the situation: 606s 606s The following packages have unmet dependencies: 606s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 606s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 606s E: Unable to correct problems, you have held broken packages. 606s autopkgtest [01:58:20]: test test-hypre64m: preparing testbed 606s test-hypre64 FAIL badpkg 606s blame: hypre 606s 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. 606s Reading package lists... 606s Building dependency tree... 606s Reading state information... 606s Starting pkgProblemResolver with broken count: 1 606s Starting 2 pkgProblemResolver with broken count: 1 606s Investigating (0) libopenmpi40:s390x < none -> 5.0.6-3 @un puN Ib > 606s Broken libopenmpi40:s390x Breaks on libopenmpi3:s390x < none @un H > (< 5.0.6-3) 606s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 606s Considering libopenmpi3t64:s390x 0 as a solution to libopenmpi40:s390x 7 606s Broken libopenmpi40:s390x Breaks on libopenmpi3t64:s390x < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 606s Considering libopenmpi3t64:s390x 0 as a solution to libopenmpi40:s390x 7 606s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 606s Done 606s Some packages could not be installed. This may mean that you have 606s requested an impossible situation or if you are using the unstable 606s distribution that some required packages have not yet been created 606s or been moved out of Incoming. 606s The following information may help to resolve the situation: 606s 606s The following packages have unmet dependencies: 606s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 606s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 606s E: Unable to correct problems, you have held broken packages. 606s autopkgtest [01:58:20]: @@@@@@@@@@@@@@@@@@@@ summary 606s test-hypre FAIL badpkg 606s blame: hypre 606s 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. 606s test-hypre64 FAIL badpkg 606s blame: hypre 606s 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. 606s test-hypre64m FAIL badpkg 606s blame: hypre 606s 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. 606s test-hypre64m FAIL badpkg 606s blame: hypre 606s 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. 660s nova [W] Using flock in prodstack6-s390x 660s flock: timeout while waiting to get lock 660s Creating nova instance adt-plucky-s390x-hypre-20241203-014812-juju-7f2275-prod-proposed-migration-environment-2-c42b4cc1-065b-4654-aa1b-df5aa61362d6 from image adt/ubuntu-plucky-s390x-server-20241203.img (UUID 1a991c1c-46bc-40f7-9cba-4c8bff864ded)... 660s nova [W] Using flock in prodstack6-s390x 660s Creating nova instance adt-plucky-s390x-hypre-20241203-014812-juju-7f2275-prod-proposed-migration-environment-2-c42b4cc1-065b-4654-aa1b-df5aa61362d6 from image adt/ubuntu-plucky-s390x-server-20241203.img (UUID 1a991c1c-46bc-40f7-9cba-4c8bff864ded)...