0s autopkgtest [15:53:31]: starting date and time: 2024-12-04 15:53:31+0000 0s autopkgtest [15:53:31]: git checkout: 48af33f0 Fix --add-apt-source=ppa for focal 0s autopkgtest [15:53:31]: host juju-7f2275-prod-proposed-migration-environment-20; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.v3i_p_4q/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:vtk9,src:openmpi --apt-upgrade lammps --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 '--env=ADT_TEST_TRIGGERS=vtk9/9.3.0+dfsg1-1.1build2 openmpi/5.0.6-3' -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest-s390x --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-20@bos03-s390x-1.secgroup --name adt-plucky-s390x-lammps-20241204-154703-juju-7f2275-prod-proposed-migration-environment-20-614582c8-5a97-4067-9f28-eb878282ee83 --image adt/ubuntu-plucky-s390x-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-20 --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/ 65s autopkgtest [15:54:36]: testbed dpkg architecture: s390x 65s autopkgtest [15:54:36]: testbed apt version: 2.9.16 65s autopkgtest [15:54:36]: @@@@@@@@@@@@@@@@@@@@ test bed setup 65s autopkgtest [15:54:36]: testbed release detected to be: None 66s autopkgtest [15:54:37]: updating testbed package index (apt update) 66s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB] 66s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 66s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 66s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 67s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [63.2 kB] 67s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [14.2 kB] 67s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B] 67s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [764 kB] 67s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main s390x Packages [119 kB] 67s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted s390x Packages [928 B] 67s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe s390x Packages [599 kB] 67s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse s390x Packages [7444 B] 67s Fetched 1651 kB in 1s (1908 kB/s) 68s Reading package lists... 68s Reading package lists... 68s Building dependency tree... 68s Reading state information... 68s Calculating upgrade... 68s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 68s Reading package lists... 69s Building dependency tree... 69s Reading state information... 69s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 69s autopkgtest [15:54:40]: upgrading testbed (apt dist-upgrade and autopurge) 69s Reading package lists... 69s Building dependency tree... 69s Reading state information... 69s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 69s Starting 2 pkgProblemResolver with broken count: 0 69s Done 69s Entering ResolveByKeep 69s 70s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 70s Reading package lists... 70s Building dependency tree... 70s Reading state information... 70s Starting pkgProblemResolver with broken count: 0 70s Starting 2 pkgProblemResolver with broken count: 0 70s Done 70s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 72s autopkgtest [15:54:43]: testbed running kernel: Linux 6.11.0-8-generic #8-Ubuntu SMP Mon Sep 16 12:49:35 UTC 2024 73s autopkgtest [15:54:44]: @@@@@@@@@@@@@@@@@@@@ apt-source lammps 85s Get:1 http://ftpmaster.internal/ubuntu plucky/universe lammps 20240207+dfsg-1.1build5 (dsc) [2932 B] 85s Get:2 http://ftpmaster.internal/ubuntu plucky/universe lammps 20240207+dfsg-1.1build5 (tar) [153 MB] 85s Get:3 http://ftpmaster.internal/ubuntu plucky/universe lammps 20240207+dfsg-1.1build5 (diff) [17.2 kB] 85s gpgv: Signature made Tue Jul 30 21:05:03 2024 UTC 85s gpgv: using RSA key 883FEC247A03BE63B70FD5F920FB053CAF9559CF 85s gpgv: issuer "eeickmeyer@ubuntu.com" 85s gpgv: Can't check signature: No public key 85s dpkg-source: warning: cannot verify inline signature for ./lammps_20240207+dfsg-1.1build5.dsc: no acceptable signature found 93s autopkgtest [15:55:04]: testing package lammps version 20240207+dfsg-1.1build5 93s autopkgtest [15:55:04]: build not needed 115s autopkgtest [15:55:26]: test crack: preparing testbed 116s Reading package lists... 116s Building dependency tree... 116s Reading state information... 116s Starting pkgProblemResolver with broken count: 1 116s Starting 2 pkgProblemResolver with broken count: 1 116s Investigating (0) libopenmpi40:s390x < none -> 5.0.6-3 @un puN Ib > 116s Broken libopenmpi40:s390x Breaks on libopenmpi3:s390x < none @un H > (< 5.0.6-3) 116s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 116s Considering libopenmpi3t64:s390x 1 as a solution to libopenmpi40:s390x 1 116s Re-Instated libopenmpi3t64:s390x 116s Broken libopenmpi40:s390x Breaks on libopenmpi3t64:s390x < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 116s Considering libopenmpi3t64:s390x 1 as a solution to libopenmpi40:s390x 1 116s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 116s Done 116s Some packages could not be installed. This may mean that you have 116s requested an impossible situation or if you are using the unstable 116s distribution that some required packages have not yet been created 116s or been moved out of Incoming. 116s The following information may help to resolve the situation: 116s 116s The following packages have unmet dependencies: 116s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 116s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 116s E: Unable to correct problems, you have held broken packages. 116s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed 116s Reading package lists... 116s Building dependency tree... 116s Reading state information... 117s Starting pkgProblemResolver with broken count: 1 117s Starting 2 pkgProblemResolver with broken count: 1 117s Investigating (0) libopenmpi40:s390x < none -> 5.0.6-3 @un puN Ib > 117s Broken libopenmpi40:s390x Breaks on libopenmpi3:s390x < none @un H > (< 5.0.6-3) 117s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 117s Considering libopenmpi3t64:s390x 0 as a solution to libopenmpi40:s390x 2 117s Broken libopenmpi40:s390x Breaks on libopenmpi3t64:s390x < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 117s Considering libopenmpi3t64:s390x 0 as a solution to libopenmpi40:s390x 2 117s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 117s Done 117s Some packages could not be installed. This may mean that you have 117s requested an impossible situation or if you are using the unstable 117s distribution that some required packages have not yet been created 117s or been moved out of Incoming. 117s The following information may help to resolve the situation: 117s 117s The following packages have unmet dependencies: 117s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 117s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 117s E: Unable to correct problems, you have held broken packages. 117s autopkgtest [15:55:28]: test dipole: preparing testbed 117s crack FAIL badpkg 117s blame: lammps 117s 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. 117s Reading package lists... 117s Building dependency tree... 117s Reading state information... 117s Starting pkgProblemResolver with broken count: 1 117s Starting 2 pkgProblemResolver with broken count: 1 117s Investigating (0) libopenmpi40:s390x < none -> 5.0.6-3 @un puN Ib > 117s Broken libopenmpi40:s390x Breaks on libopenmpi3:s390x < none @un H > (< 5.0.6-3) 117s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 117s Considering libopenmpi3t64:s390x 0 as a solution to libopenmpi40:s390x 2 117s Broken libopenmpi40:s390x Breaks on libopenmpi3t64:s390x < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 117s Considering libopenmpi3t64:s390x 0 as a solution to libopenmpi40:s390x 2 117s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 117s Done 117s Some packages could not be installed. This may mean that you have 117s requested an impossible situation or if you are using the unstable 117s distribution that some required packages have not yet been created 117s or been moved out of Incoming. 117s The following information may help to resolve the situation: 117s 117s The following packages have unmet dependencies: 117s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 117s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 117s E: Unable to correct problems, you have held broken packages. 117s autopkgtest [15:55:28]: test ellipse: preparing testbed 117s dipole FAIL badpkg 117s blame: lammps 117s 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. 117s Reading package lists... 118s Building dependency tree... 118s Reading state information... 118s Starting pkgProblemResolver with broken count: 1 118s Starting 2 pkgProblemResolver with broken count: 1 118s Investigating (0) libopenmpi40:s390x < none -> 5.0.6-3 @un puN Ib > 118s Broken libopenmpi40:s390x Breaks on libopenmpi3:s390x < none @un H > (< 5.0.6-3) 118s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 118s Considering libopenmpi3t64:s390x 0 as a solution to libopenmpi40:s390x 2 118s Broken libopenmpi40:s390x Breaks on libopenmpi3t64:s390x < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 118s Considering libopenmpi3t64:s390x 0 as a solution to libopenmpi40:s390x 2 118s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 118s Done 118s Some packages could not be installed. This may mean that you have 118s requested an impossible situation or if you are using the unstable 118s distribution that some required packages have not yet been created 118s or been moved out of Incoming. 118s The following information may help to resolve the situation: 118s 118s The following packages have unmet dependencies: 118s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 118s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 118s E: Unable to correct problems, you have held broken packages. 118s ellipse FAIL badpkg 118s blame: lammps 118s 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. 118s autopkgtest [15:55:29]: test flow: preparing testbed 118s Reading package lists... 118s Building dependency tree... 118s Reading state information... 118s Starting pkgProblemResolver with broken count: 1 118s Starting 2 pkgProblemResolver with broken count: 1 118s Investigating (0) libopenmpi40:s390x < none -> 5.0.6-3 @un puN Ib > 118s Broken libopenmpi40:s390x Breaks on libopenmpi3:s390x < none @un H > (< 5.0.6-3) 118s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 118s Considering libopenmpi3t64:s390x 0 as a solution to libopenmpi40:s390x 2 118s Broken libopenmpi40:s390x Breaks on libopenmpi3t64:s390x < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 118s Considering libopenmpi3t64:s390x 0 as a solution to libopenmpi40:s390x 2 118s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 118s Done 118s Some packages could not be installed. This may mean that you have 118s requested an impossible situation or if you are using the unstable 118s distribution that some required packages have not yet been created 118s or been moved out of Incoming. 118s The following information may help to resolve the situation: 118s 118s The following packages have unmet dependencies: 118s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 118s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 118s E: Unable to correct problems, you have held broken packages. 118s autopkgtest [15:55:29]: test friction: preparing testbed 118s flow FAIL badpkg 118s blame: lammps 118s 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. 119s Reading package lists... 119s Building dependency tree... 119s Reading state information... 119s Starting pkgProblemResolver with broken count: 1 119s Starting 2 pkgProblemResolver with broken count: 1 119s Investigating (0) libopenmpi40:s390x < none -> 5.0.6-3 @un puN Ib > 119s Broken libopenmpi40:s390x Breaks on libopenmpi3:s390x < none @un H > (< 5.0.6-3) 119s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 119s Considering libopenmpi3t64:s390x 0 as a solution to libopenmpi40:s390x 2 119s Broken libopenmpi40:s390x Breaks on libopenmpi3t64:s390x < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 119s Considering libopenmpi3t64:s390x 0 as a solution to libopenmpi40:s390x 2 119s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 119s Done 119s Some packages could not be installed. This may mean that you have 119s requested an impossible situation or if you are using the unstable 119s distribution that some required packages have not yet been created 119s or been moved out of Incoming. 119s The following information may help to resolve the situation: 119s 119s The following packages have unmet dependencies: 119s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 119s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 119s E: Unable to correct problems, you have held broken packages. 119s autopkgtest [15:55:30]: test hugo: preparing testbed 119s friction FAIL badpkg 119s blame: lammps 119s 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. 119s Reading package lists... 119s Building dependency tree... 119s Reading state information... 119s Starting pkgProblemResolver with broken count: 1 120s Starting 2 pkgProblemResolver with broken count: 1 120s Investigating (0) libopenmpi40:s390x < none -> 5.0.6-3 @un puN Ib > 120s Broken libopenmpi40:s390x Breaks on libopenmpi3:s390x < none @un H > (< 5.0.6-3) 120s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 120s Considering libopenmpi3t64:s390x 0 as a solution to libopenmpi40:s390x 2 120s Broken libopenmpi40:s390x Breaks on libopenmpi3t64:s390x < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 120s Considering libopenmpi3t64:s390x 0 as a solution to libopenmpi40:s390x 2 120s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 120s Done 120s Some packages could not be installed. This may mean that you have 120s requested an impossible situation or if you are using the unstable 120s distribution that some required packages have not yet been created 120s or been moved out of Incoming. 120s The following information may help to resolve the situation: 120s 120s The following packages have unmet dependencies: 120s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 120s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 120s E: Unable to correct problems, you have held broken packages. 120s autopkgtest [15:55:31]: test command1: preparing testbed 120s hugo FAIL badpkg 120s blame: lammps 120s 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. 194s autopkgtest [15:56:45]: testbed dpkg architecture: s390x 194s autopkgtest [15:56:45]: testbed apt version: 2.9.16 194s autopkgtest [15:56:45]: @@@@@@@@@@@@@@@@@@@@ test bed setup 194s autopkgtest [15:56:45]: testbed release detected to be: plucky 195s autopkgtest [15:56:46]: updating testbed package index (apt update) 195s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB] 196s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 196s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 196s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 196s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [63.2 kB] 196s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [14.2 kB] 196s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [764 kB] 196s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B] 196s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main s390x Packages [119 kB] 196s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted s390x Packages [928 B] 196s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe s390x Packages [599 kB] 196s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse s390x Packages [7444 B] 196s Fetched 1651 kB in 1s (1780 kB/s) 197s Reading package lists... 197s Reading package lists... 197s Building dependency tree... 197s Reading state information... 198s Calculating upgrade... 198s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 198s Reading package lists... 198s Building dependency tree... 198s Reading state information... 198s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 198s autopkgtest [15:56:49]: upgrading testbed (apt dist-upgrade and autopurge) 198s Reading package lists... 198s Building dependency tree... 198s Reading state information... 198s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 198s Starting 2 pkgProblemResolver with broken count: 0 198s Done 199s Entering ResolveByKeep 199s 199s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 199s Reading package lists... 199s Building dependency tree... 199s Reading state information... 199s Starting pkgProblemResolver with broken count: 0 199s Starting 2 pkgProblemResolver with broken count: 0 199s Done 199s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 202s Reading package lists... 202s Building dependency tree... 202s Reading state information... 202s Starting pkgProblemResolver with broken count: 1 202s Starting 2 pkgProblemResolver with broken count: 1 202s Investigating (0) libopenmpi40:s390x < none -> 5.0.6-3 @un puN Ib > 202s Broken libopenmpi40:s390x Breaks on libopenmpi3:s390x < none @un H > (< 5.0.6-3) 202s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 202s Considering libopenmpi3t64:s390x 0 as a solution to libopenmpi40:s390x 3 202s Broken libopenmpi40:s390x Breaks on libopenmpi3t64:s390x < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 202s Considering libopenmpi3t64:s390x 0 as a solution to libopenmpi40:s390x 3 202s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 202s Done 202s Some packages could not be installed. This may mean that you have 202s requested an impossible situation or if you are using the unstable 202s distribution that some required packages have not yet been created 202s or been moved out of Incoming. 202s The following information may help to resolve the situation: 202s 202s The following packages have unmet dependencies: 202s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 202s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 202s E: Unable to correct problems, you have held broken packages. 202s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed 203s Reading package lists... 203s Building dependency tree... 203s Reading state information... 203s Starting pkgProblemResolver with broken count: 1 203s Starting 2 pkgProblemResolver with broken count: 1 203s Investigating (0) libopenmpi40:s390x < none -> 5.0.6-3 @un puN Ib > 203s Broken libopenmpi40:s390x Breaks on libopenmpi3:s390x < none @un H > (< 5.0.6-3) 203s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 203s Considering libopenmpi3t64:s390x -1 as a solution to libopenmpi40:s390x 4 203s Broken libopenmpi40:s390x Breaks on libopenmpi3t64:s390x < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 203s Considering libopenmpi3t64:s390x -1 as a solution to libopenmpi40:s390x 4 203s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 203s Done 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 libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 203s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 203s E: Unable to correct problems, you have held broken packages. 203s command1 FAIL badpkg 203s blame: lammps 203s 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. 203s autopkgtest [15:56:54]: @@@@@@@@@@@@@@@@@@@@ summary 203s crack FAIL badpkg 203s blame: lammps 203s 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. 203s dipole FAIL badpkg 203s blame: lammps 203s 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. 203s ellipse FAIL badpkg 203s blame: lammps 203s 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. 203s flow FAIL badpkg 203s blame: lammps 203s 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. 203s friction FAIL badpkg 203s blame: lammps 203s 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. 203s hugo FAIL badpkg 203s blame: lammps 203s 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. 203s command1 FAIL badpkg 203s blame: lammps 203s 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. 214s nova [W] Using flock in prodstack6-s390x 214s Creating nova instance adt-plucky-s390x-lammps-20241204-154703-juju-7f2275-prod-proposed-migration-environment-20-614582c8-5a97-4067-9f28-eb878282ee83 from image adt/ubuntu-plucky-s390x-server-20241204.img (UUID 89b4900b-e439-4dd9-be41-eb47bd412513)... 214s nova [W] Using flock in prodstack6-s390x 214s Creating nova instance adt-plucky-s390x-lammps-20241204-154703-juju-7f2275-prod-proposed-migration-environment-20-614582c8-5a97-4067-9f28-eb878282ee83 from image adt/ubuntu-plucky-s390x-server-20241204.img (UUID 89b4900b-e439-4dd9-be41-eb47bd412513)...