0s autopkgtest [09:34:17]: starting date and time: 2024-12-03 09:34:17+0000 0s autopkgtest [09:34:17]: git checkout: be626eda Fix armhf LXD image generation for plucky 0s autopkgtest [09:34:17]: host juju-7f2275-prod-proposed-migration-environment-15; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.jonj1hs1/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:openmpi,src:fftw3,src:pnetcdf --apt-upgrade lammps --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 '--env=ADT_TEST_TRIGGERS=openmpi/5.0.6-3 fftw3/3.3.10-2fakesync1build1 pnetcdf/1.13.0-1build1' -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest-s390x --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-15@bos03-s390x-16.secgroup --name adt-plucky-s390x-lammps-20241203-093417-juju-7f2275-prod-proposed-migration-environment-15-80c7de62-1150-4d3e-91e9-738548827bea --image adt/ubuntu-plucky-s390x-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-15 --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/ 108s autopkgtest [09:36:05]: testbed dpkg architecture: s390x 108s autopkgtest [09:36:05]: testbed apt version: 2.9.14ubuntu1 109s autopkgtest [09:36:06]: @@@@@@@@@@@@@@@@@@@@ test bed setup 109s autopkgtest [09:36:06]: testbed release detected to be: None 110s autopkgtest [09:36:07]: updating testbed package index (apt update) 110s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB] 111s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 111s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 111s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 111s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [781 kB] 112s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [65.3 kB] 112s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [15.1 kB] 112s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B] 112s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main s390x Packages [125 kB] 112s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted s390x Packages [928 B] 112s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe s390x Packages [627 kB] 112s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse s390x Packages [7964 B] 112s Fetched 1705 kB in 2s (876 kB/s) 114s Reading package lists... 116s Reading package lists... 116s Building dependency tree... 116s Reading state information... 116s Calculating upgrade... 116s The following packages will be upgraded: 116s gcc-14-base libatomic1 libgcc-s1 libstdc++6 116s 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 116s Need to get 994 kB of archives. 116s After this operation, 1024 B of additional disk space will be used. 116s Get:1 http://ftpmaster.internal/ubuntu plucky/main s390x libatomic1 s390x 14.2.0-9ubuntu1 [9424 B] 116s Get:2 http://ftpmaster.internal/ubuntu plucky/main s390x gcc-14-base s390x 14.2.0-9ubuntu1 [51.9 kB] 116s Get:3 http://ftpmaster.internal/ubuntu plucky/main s390x libstdc++6 s390x 14.2.0-9ubuntu1 [897 kB] 117s Get:4 http://ftpmaster.internal/ubuntu plucky/main s390x libgcc-s1 s390x 14.2.0-9ubuntu1 [35.9 kB] 117s Fetched 994 kB in 1s (907 kB/s) 118s (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 ... 55869 files and directories currently installed.) 118s Preparing to unpack .../libatomic1_14.2.0-9ubuntu1_s390x.deb ... 118s Unpacking libatomic1:s390x (14.2.0-9ubuntu1) over (14.2.0-8ubuntu1) ... 118s Preparing to unpack .../gcc-14-base_14.2.0-9ubuntu1_s390x.deb ... 118s Unpacking gcc-14-base:s390x (14.2.0-9ubuntu1) over (14.2.0-8ubuntu1) ... 118s Setting up gcc-14-base:s390x (14.2.0-9ubuntu1) ... 118s (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 ... 55869 files and directories currently installed.) 118s Preparing to unpack .../libstdc++6_14.2.0-9ubuntu1_s390x.deb ... 118s Unpacking libstdc++6:s390x (14.2.0-9ubuntu1) over (14.2.0-8ubuntu1) ... 118s Setting up libstdc++6:s390x (14.2.0-9ubuntu1) ... 118s (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 ... 55869 files and directories currently installed.) 118s Preparing to unpack .../libgcc-s1_14.2.0-9ubuntu1_s390x.deb ... 118s Unpacking libgcc-s1:s390x (14.2.0-9ubuntu1) over (14.2.0-8ubuntu1) ... 118s Setting up libgcc-s1:s390x (14.2.0-9ubuntu1) ... 118s Setting up libatomic1:s390x (14.2.0-9ubuntu1) ... 118s Processing triggers for libc-bin (2.40-1ubuntu3) ... 118s Reading package lists... 118s Building dependency tree... 118s Reading state information... 119s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 119s autopkgtest [09:36:16]: upgrading testbed (apt dist-upgrade and autopurge) 119s Reading package lists... 119s Building dependency tree... 119s Reading state information... 119s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 119s Starting 2 pkgProblemResolver with broken count: 0 119s Done 120s Entering ResolveByKeep 120s 120s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 121s Reading package lists... 121s Building dependency tree... 121s Reading state information... 121s Starting pkgProblemResolver with broken count: 0 121s Starting 2 pkgProblemResolver with broken count: 0 121s Done 121s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 124s autopkgtest [09:36:21]: testbed running kernel: Linux 6.11.0-8-generic #8-Ubuntu SMP Mon Sep 16 12:49:35 UTC 2024 125s autopkgtest [09:36:22]: @@@@@@@@@@@@@@@@@@@@ apt-source lammps 147s Get:1 http://ftpmaster.internal/ubuntu plucky/universe lammps 20240207+dfsg-1.1build5 (dsc) [2932 B] 147s Get:2 http://ftpmaster.internal/ubuntu plucky/universe lammps 20240207+dfsg-1.1build5 (tar) [153 MB] 147s Get:3 http://ftpmaster.internal/ubuntu plucky/universe lammps 20240207+dfsg-1.1build5 (diff) [17.2 kB] 148s gpgv: Signature made Tue Jul 30 21:05:03 2024 UTC 148s gpgv: using RSA key 883FEC247A03BE63B70FD5F920FB053CAF9559CF 148s gpgv: issuer "eeickmeyer@ubuntu.com" 148s gpgv: Can't check signature: No public key 148s dpkg-source: warning: cannot verify inline signature for ./lammps_20240207+dfsg-1.1build5.dsc: no acceptable signature found 158s autopkgtest [09:36:55]: testing package lammps version 20240207+dfsg-1.1build5 159s autopkgtest [09:36:56]: build not needed 183s autopkgtest [09:37:20]: test crack: preparing testbed 183s Reading package lists... 183s Building dependency tree... 183s Reading state information... 183s Starting pkgProblemResolver with broken count: 1 183s Starting 2 pkgProblemResolver with broken count: 1 183s Investigating (0) libopenmpi40:s390x < none -> 5.0.6-3 @un puN Ib > 183s Broken libopenmpi40:s390x Breaks on libopenmpi3:s390x < none @un H > (< 5.0.6-3) 183s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 183s Considering libopenmpi3t64:s390x 1 as a solution to libopenmpi40:s390x 1 183s Re-Instated libopenmpi3t64:s390x 183s Broken libopenmpi40:s390x Breaks on libopenmpi3t64:s390x < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 183s Considering libopenmpi3t64:s390x 1 as a solution to libopenmpi40:s390x 1 183s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 183s Done 183s Some packages could not be installed. This may mean that you have 183s requested an impossible situation or if you are using the unstable 183s distribution that some required packages have not yet been created 183s or been moved out of Incoming. 183s The following information may help to resolve the situation: 183s 183s The following packages have unmet dependencies: 183s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 183s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 183s E: Unable to correct problems, you have held broken packages. 183s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed 184s Reading package lists... 184s Building dependency tree... 184s Reading state information... 184s Starting pkgProblemResolver with broken count: 1 184s Starting 2 pkgProblemResolver with broken count: 1 184s Investigating (0) libopenmpi40:s390x < none -> 5.0.6-3 @un puN Ib > 184s Broken libopenmpi40:s390x Breaks on libopenmpi3:s390x < none @un H > (< 5.0.6-3) 184s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 184s Considering libopenmpi3t64:s390x 1 as a solution to libopenmpi40:s390x 1 184s Re-Instated libopenmpi3t64:s390x 184s Broken libopenmpi40:s390x Breaks on libopenmpi3t64:s390x < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 184s Considering libopenmpi3t64:s390x 1 as a solution to libopenmpi40:s390x 1 184s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 184s Done 184s Some packages could not be installed. This may mean that you have 184s requested an impossible situation or if you are using the unstable 184s distribution that some required packages have not yet been created 184s or been moved out of Incoming. 184s The following information may help to resolve the situation: 184s 184s The following packages have unmet dependencies: 184s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 184s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 184s E: Unable to correct problems, you have held broken packages. 184s crack FAIL badpkg 184s blame: lammps 184s 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. 184s autopkgtest [09:37:21]: test dipole: preparing testbed 184s Reading package lists... 185s Building dependency tree... 185s Reading state information... 185s Starting pkgProblemResolver with broken count: 1 185s Starting 2 pkgProblemResolver with broken count: 1 185s Investigating (0) libopenmpi40:s390x < none -> 5.0.6-3 @un puN Ib > 185s Broken libopenmpi40:s390x Breaks on libopenmpi3:s390x < none @un H > (< 5.0.6-3) 185s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 185s Considering libopenmpi3t64:s390x 1 as a solution to libopenmpi40:s390x 1 185s Re-Instated libopenmpi3t64:s390x 185s Broken libopenmpi40:s390x Breaks on libopenmpi3t64:s390x < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 185s Considering libopenmpi3t64:s390x 1 as a solution to libopenmpi40:s390x 1 185s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 185s Done 185s Some packages could not be installed. This may mean that you have 185s requested an impossible situation or if you are using the unstable 185s distribution that some required packages have not yet been created 185s or been moved out of Incoming. 185s The following information may help to resolve the situation: 185s 185s The following packages have unmet dependencies: 185s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 185s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 185s E: Unable to correct problems, you have held broken packages. 185s dipole FAIL badpkg 185s blame: lammps 185s 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. 185s autopkgtest [09:37:22]: test ellipse: preparing testbed 185s Reading package lists... 185s Building dependency tree... 185s Reading state information... 186s Starting pkgProblemResolver with broken count: 1 186s Starting 2 pkgProblemResolver with broken count: 1 186s Investigating (0) libopenmpi40:s390x < none -> 5.0.6-3 @un puN Ib > 186s Broken libopenmpi40:s390x Breaks on libopenmpi3:s390x < none @un H > (< 5.0.6-3) 186s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 186s Considering libopenmpi3t64:s390x 1 as a solution to libopenmpi40:s390x 1 186s Re-Instated libopenmpi3t64:s390x 186s Broken libopenmpi40:s390x Breaks on libopenmpi3t64:s390x < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 186s Considering libopenmpi3t64:s390x 1 as a solution to libopenmpi40:s390x 1 186s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 186s Done 186s Some packages could not be installed. This may mean that you have 186s requested an impossible situation or if you are using the unstable 186s distribution that some required packages have not yet been created 186s or been moved out of Incoming. 186s The following information may help to resolve the situation: 186s 186s The following packages have unmet dependencies: 186s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 186s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 186s E: Unable to correct problems, you have held broken packages. 186s autopkgtest [09:37:23]: test flow: preparing testbed 186s ellipse FAIL badpkg 186s blame: lammps 186s 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. 186s Reading package lists... 186s Building dependency tree... 186s Reading state information... 187s Starting pkgProblemResolver with broken count: 1 187s Starting 2 pkgProblemResolver with broken count: 1 187s Investigating (0) libopenmpi40:s390x < none -> 5.0.6-3 @un puN Ib > 187s Broken libopenmpi40:s390x Breaks on libopenmpi3:s390x < none @un H > (< 5.0.6-3) 187s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 187s Considering libopenmpi3t64:s390x 1 as a solution to libopenmpi40:s390x 1 187s Re-Instated libopenmpi3t64:s390x 187s Broken libopenmpi40:s390x Breaks on libopenmpi3t64:s390x < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 187s Considering libopenmpi3t64:s390x 1 as a solution to libopenmpi40:s390x 1 187s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 187s Done 187s Some packages could not be installed. This may mean that you have 187s requested an impossible situation or if you are using the unstable 187s distribution that some required packages have not yet been created 187s or been moved out of Incoming. 187s The following information may help to resolve the situation: 187s 187s The following packages have unmet dependencies: 187s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 187s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 187s E: Unable to correct problems, you have held broken packages. 187s flow FAIL badpkg 187s blame: lammps 187s 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. 187s autopkgtest [09:37:24]: test friction: preparing testbed 187s Reading package lists... 188s Building dependency tree... 188s Reading state information... 188s Starting pkgProblemResolver with broken count: 1 188s Starting 2 pkgProblemResolver with broken count: 1 188s Investigating (0) libopenmpi40:s390x < none -> 5.0.6-3 @un puN Ib > 188s Broken libopenmpi40:s390x Breaks on libopenmpi3:s390x < none @un H > (< 5.0.6-3) 188s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 188s Considering libopenmpi3t64:s390x 1 as a solution to libopenmpi40:s390x 1 188s Re-Instated libopenmpi3t64:s390x 188s Broken libopenmpi40:s390x Breaks on libopenmpi3t64:s390x < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 188s Considering libopenmpi3t64:s390x 1 as a solution to libopenmpi40:s390x 1 188s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 188s Done 188s Some packages could not be installed. This may mean that you have 188s requested an impossible situation or if you are using the unstable 188s distribution that some required packages have not yet been created 188s or been moved out of Incoming. 188s The following information may help to resolve the situation: 188s 188s The following packages have unmet dependencies: 188s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 188s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 188s E: Unable to correct problems, you have held broken packages. 188s autopkgtest [09:37:25]: test hugo: preparing testbed 188s friction FAIL badpkg 188s blame: lammps 188s 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. 188s Reading package lists... 188s Building dependency tree... 188s Reading state information... 189s Starting pkgProblemResolver with broken count: 1 189s Starting 2 pkgProblemResolver with broken count: 1 189s Investigating (0) libopenmpi40:s390x < none -> 5.0.6-3 @un puN Ib > 189s Broken libopenmpi40:s390x Breaks on libopenmpi3:s390x < none @un H > (< 5.0.6-3) 189s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 189s Considering libopenmpi3t64:s390x 1 as a solution to libopenmpi40:s390x 1 189s Re-Instated libopenmpi3t64:s390x 189s Broken libopenmpi40:s390x Breaks on libopenmpi3t64:s390x < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 189s Considering libopenmpi3t64:s390x 1 as a solution to libopenmpi40:s390x 1 189s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 189s Done 189s Some packages could not be installed. This may mean that you have 189s requested an impossible situation or if you are using the unstable 189s distribution that some required packages have not yet been created 189s or been moved out of Incoming. 189s The following information may help to resolve the situation: 189s 189s The following packages have unmet dependencies: 189s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 189s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 189s E: Unable to correct problems, you have held broken packages. 189s hugo FAIL badpkg 189s blame: lammps 189s 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. 189s autopkgtest [09:37:26]: test command1: preparing testbed 317s autopkgtest [09:39:34]: testbed dpkg architecture: s390x 317s autopkgtest [09:39:34]: testbed apt version: 2.9.14ubuntu1 317s autopkgtest [09:39:34]: @@@@@@@@@@@@@@@@@@@@ test bed setup 317s autopkgtest [09:39:34]: testbed release detected to be: plucky 318s autopkgtest [09:39:35]: updating testbed package index (apt update) 318s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB] 318s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 319s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 319s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 319s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [781 kB] 319s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [65.3 kB] 319s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [15.1 kB] 319s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B] 319s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main s390x Packages [125 kB] 319s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted s390x Packages [928 B] 319s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe s390x Packages [627 kB] 319s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse s390x Packages [7964 B] 319s Fetched 1705 kB in 1s (1883 kB/s) 320s Reading package lists... 320s Reading package lists... 320s Building dependency tree... 320s Reading state information... 321s Calculating upgrade... 321s The following packages will be upgraded: 321s gcc-14-base libatomic1 libgcc-s1 libstdc++6 321s 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 321s Need to get 994 kB of archives. 321s After this operation, 1024 B of additional disk space will be used. 321s Get:1 http://ftpmaster.internal/ubuntu plucky/main s390x libatomic1 s390x 14.2.0-9ubuntu1 [9424 B] 321s Get:2 http://ftpmaster.internal/ubuntu plucky/main s390x gcc-14-base s390x 14.2.0-9ubuntu1 [51.9 kB] 321s Get:3 http://ftpmaster.internal/ubuntu plucky/main s390x libstdc++6 s390x 14.2.0-9ubuntu1 [897 kB] 321s Get:4 http://ftpmaster.internal/ubuntu plucky/main s390x libgcc-s1 s390x 14.2.0-9ubuntu1 [35.9 kB] 321s Fetched 994 kB in 1s (1805 kB/s) 322s (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 ... 55869 files and directories currently installed.) 322s Preparing to unpack .../libatomic1_14.2.0-9ubuntu1_s390x.deb ... 322s Unpacking libatomic1:s390x (14.2.0-9ubuntu1) over (14.2.0-8ubuntu1) ... 322s Preparing to unpack .../gcc-14-base_14.2.0-9ubuntu1_s390x.deb ... 322s Unpacking gcc-14-base:s390x (14.2.0-9ubuntu1) over (14.2.0-8ubuntu1) ... 322s Setting up gcc-14-base:s390x (14.2.0-9ubuntu1) ... 322s (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 ... 55869 files and directories currently installed.) 322s Preparing to unpack .../libstdc++6_14.2.0-9ubuntu1_s390x.deb ... 322s Unpacking libstdc++6:s390x (14.2.0-9ubuntu1) over (14.2.0-8ubuntu1) ... 322s Setting up libstdc++6:s390x (14.2.0-9ubuntu1) ... 322s (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 ... 55869 files and directories currently installed.) 322s Preparing to unpack .../libgcc-s1_14.2.0-9ubuntu1_s390x.deb ... 322s Unpacking libgcc-s1:s390x (14.2.0-9ubuntu1) over (14.2.0-8ubuntu1) ... 322s Setting up libgcc-s1:s390x (14.2.0-9ubuntu1) ... 322s Setting up libatomic1:s390x (14.2.0-9ubuntu1) ... 322s Processing triggers for libc-bin (2.40-1ubuntu3) ... 322s Reading package lists... 322s Building dependency tree... 322s Reading state information... 322s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 322s autopkgtest [09:39:39]: upgrading testbed (apt dist-upgrade and autopurge) 323s Reading package lists... 323s Building dependency tree... 323s Reading state information... 323s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 323s Starting 2 pkgProblemResolver with broken count: 0 323s Done 323s Entering ResolveByKeep 323s 323s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 323s Reading package lists... 324s Building dependency tree... 324s Reading state information... 324s Starting pkgProblemResolver with broken count: 0 324s Starting 2 pkgProblemResolver with broken count: 0 324s Done 324s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 326s Reading package lists... 327s Building dependency tree... 327s Reading state information... 327s Starting pkgProblemResolver with broken count: 1 327s Starting 2 pkgProblemResolver with broken count: 1 327s Investigating (0) libopenmpi40:s390x < none -> 5.0.6-3 @un puN Ib > 327s Broken libopenmpi40:s390x Breaks on libopenmpi3:s390x < none @un H > (< 5.0.6-3) 327s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 327s Considering libopenmpi3t64:s390x 0 as a solution to libopenmpi40:s390x 3 327s Broken libopenmpi40:s390x Breaks on libopenmpi3t64:s390x < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 327s Considering libopenmpi3t64:s390x 0 as a solution to libopenmpi40:s390x 3 327s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 327s Done 327s Some packages could not be installed. This may mean that you have 327s requested an impossible situation or if you are using the unstable 327s distribution that some required packages have not yet been created 327s or been moved out of Incoming. 327s The following information may help to resolve the situation: 327s 327s The following packages have unmet dependencies: 327s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 327s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 327s E: Unable to correct problems, you have held broken packages. 327s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed 327s Reading package lists... 327s Building dependency tree... 327s Reading state information... 327s Starting pkgProblemResolver with broken count: 1 327s Starting 2 pkgProblemResolver with broken count: 1 327s Investigating (0) libopenmpi40:s390x < none -> 5.0.6-3 @un puN Ib > 327s Broken libopenmpi40:s390x Breaks on libopenmpi3:s390x < none @un H > (< 5.0.6-3) 327s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 327s Considering libopenmpi3t64:s390x 0 as a solution to libopenmpi40:s390x 3 327s Broken libopenmpi40:s390x Breaks on libopenmpi3t64:s390x < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 327s Considering libopenmpi3t64:s390x 0 as a solution to libopenmpi40:s390x 3 327s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 327s Done 327s Some packages could not be installed. This may mean that you have 327s requested an impossible situation or if you are using the unstable 327s distribution that some required packages have not yet been created 327s or been moved out of Incoming. 327s The following information may help to resolve the situation: 327s 327s The following packages have unmet dependencies: 328s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 328s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 328s E: Unable to correct problems, you have held broken packages. 328s command1 FAIL badpkg 328s blame: lammps 328s 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. 328s autopkgtest [09:39:45]: @@@@@@@@@@@@@@@@@@@@ summary 328s crack FAIL badpkg 328s blame: lammps 328s 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. 328s dipole FAIL badpkg 328s blame: lammps 328s 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. 328s ellipse FAIL badpkg 328s blame: lammps 328s 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. 328s flow FAIL badpkg 328s blame: lammps 328s 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. 328s friction FAIL badpkg 328s blame: lammps 328s 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. 328s hugo FAIL badpkg 328s blame: lammps 328s 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. 328s command1 FAIL badpkg 328s blame: lammps 328s 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. 339s nova [W] Using flock in prodstack6-s390x 339s flock: timeout while waiting to get lock 339s Creating nova instance adt-plucky-s390x-lammps-20241203-093417-juju-7f2275-prod-proposed-migration-environment-15-80c7de62-1150-4d3e-91e9-738548827bea from image adt/ubuntu-plucky-s390x-server-20241203.img (UUID 1a991c1c-46bc-40f7-9cba-4c8bff864ded)... 339s nova [W] Using flock in prodstack6-s390x 339s Creating nova instance adt-plucky-s390x-lammps-20241203-093417-juju-7f2275-prod-proposed-migration-environment-15-80c7de62-1150-4d3e-91e9-738548827bea from image adt/ubuntu-plucky-s390x-server-20241203.img (UUID 1a991c1c-46bc-40f7-9cba-4c8bff864ded)...