0s autopkgtest [09:54:45]: starting date and time: 2024-12-03 09:54:45+0000 0s autopkgtest [09:54:45]: git checkout: be626eda Fix armhf LXD image generation for plucky 0s autopkgtest [09:54:45]: host juju-7f2275-prod-proposed-migration-environment-2; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.fddo_rs3/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-ppc64el --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-2@bos03-ppc64el-25.secgroup --name adt-plucky-ppc64el-lammps-20241203-093416-juju-7f2275-prod-proposed-migration-environment-2-36a5a1b5-24c8-4f91-b4a2-233c9c1f78c2 --image adt/ubuntu-plucky-ppc64el-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-2 --net-id=net_prod-proposed-migration-ppc64el -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/ 113s autopkgtest [09:56:38]: testbed dpkg architecture: ppc64el 113s autopkgtest [09:56:38]: testbed apt version: 2.9.14ubuntu1 114s autopkgtest [09:56:39]: @@@@@@@@@@@@@@@@@@@@ test bed setup 114s autopkgtest [09:56:39]: testbed release detected to be: None 115s autopkgtest [09:56:40]: updating testbed package index (apt update) 115s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB] 115s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 115s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 115s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 115s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B] 115s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [15.1 kB] 115s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [65.3 kB] 116s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [781 kB] 116s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main ppc64el Packages [127 kB] 116s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted ppc64el Packages [928 B] 116s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe ppc64el Packages [655 kB] 116s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse ppc64el Packages [11.0 kB] 116s Fetched 1739 kB in 1s (1637 kB/s) 117s Reading package lists... 118s Reading package lists... 118s Building dependency tree... 118s Reading state information... 118s Calculating upgrade... 118s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 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:56:44]: upgrading testbed (apt dist-upgrade and autopurge) 119s Reading package lists... 119s Building dependency tree... 119s Reading state information... 120s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 120s Starting 2 pkgProblemResolver with broken count: 0 120s 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:56:49]: testbed running kernel: Linux 6.11.0-8-generic #8-Ubuntu SMP Mon Sep 16 13:49:23 UTC 2024 125s autopkgtest [09:56:50]: @@@@@@@@@@@@@@@@@@@@ apt-source lammps 140s Get:1 http://ftpmaster.internal/ubuntu plucky/universe lammps 20240207+dfsg-1.1build5 (dsc) [2932 B] 140s Get:2 http://ftpmaster.internal/ubuntu plucky/universe lammps 20240207+dfsg-1.1build5 (tar) [153 MB] 140s Get:3 http://ftpmaster.internal/ubuntu plucky/universe lammps 20240207+dfsg-1.1build5 (diff) [17.2 kB] 140s gpgv: Signature made Tue Jul 30 21:05:03 2024 UTC 140s gpgv: using RSA key 883FEC247A03BE63B70FD5F920FB053CAF9559CF 140s gpgv: issuer "eeickmeyer@ubuntu.com" 140s gpgv: Can't check signature: No public key 140s dpkg-source: warning: cannot verify inline signature for ./lammps_20240207+dfsg-1.1build5.dsc: no acceptable signature found 149s autopkgtest [09:57:14]: testing package lammps version 20240207+dfsg-1.1build5 150s autopkgtest [09:57:15]: build not needed 170s autopkgtest [09:57:35]: test crack: preparing testbed 170s Reading package lists... 170s Building dependency tree... 170s Reading state information... 170s Starting pkgProblemResolver with broken count: 1 170s Starting 2 pkgProblemResolver with broken count: 1 170s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib > 170s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3) 170s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 170s Considering libopenmpi3t64:ppc64el 1 as a solution to libopenmpi40:ppc64el 1 170s Re-Instated libopenmpi3t64:ppc64el 170s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 170s Considering libopenmpi3t64:ppc64el 1 as a solution to libopenmpi40:ppc64el 1 170s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 170s Done 170s Some packages could not be installed. This may mean that you have 170s requested an impossible situation or if you are using the unstable 170s distribution that some required packages have not yet been created 170s or been moved out of Incoming. 170s The following information may help to resolve the situation: 170s 170s The following packages have unmet dependencies: 170s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 170s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 170s E: Unable to correct problems, you have held broken packages. 170s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed 171s Reading package lists... 171s Building dependency tree... 171s Reading state information... 171s Starting pkgProblemResolver with broken count: 1 171s Starting 2 pkgProblemResolver with broken count: 1 171s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib > 171s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3) 171s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 171s Considering libopenmpi3t64:ppc64el 1 as a solution to libopenmpi40:ppc64el 1 171s Re-Instated libopenmpi3t64:ppc64el 171s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 171s Considering libopenmpi3t64:ppc64el 1 as a solution to libopenmpi40:ppc64el 1 171s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 171s Done 171s Some packages could not be installed. This may mean that you have 171s requested an impossible situation or if you are using the unstable 171s distribution that some required packages have not yet been created 171s or been moved out of Incoming. 171s The following information may help to resolve the situation: 171s 171s The following packages have unmet dependencies: 171s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 171s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 171s E: Unable to correct problems, you have held broken packages. 171s autopkgtest [09:57:36]: test dipole: preparing testbed 171s crack FAIL badpkg 171s blame: lammps 171s 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. 172s Reading package lists... 172s Building dependency tree... 172s Reading state information... 172s Starting pkgProblemResolver with broken count: 1 172s Starting 2 pkgProblemResolver with broken count: 1 172s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib > 172s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3) 172s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 172s Considering libopenmpi3t64:ppc64el 1 as a solution to libopenmpi40:ppc64el 1 172s Re-Instated libopenmpi3t64:ppc64el 172s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 172s Considering libopenmpi3t64:ppc64el 1 as a solution to libopenmpi40:ppc64el 1 172s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 172s Done 172s Some packages could not be installed. This may mean that you have 172s requested an impossible situation or if you are using the unstable 172s distribution that some required packages have not yet been created 172s or been moved out of Incoming. 172s The following information may help to resolve the situation: 172s 172s The following packages have unmet dependencies: 172s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 172s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 172s E: Unable to correct problems, you have held broken packages. 172s dipole FAIL badpkg 172s blame: lammps 172s 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. 172s autopkgtest [09:57:37]: test ellipse: preparing testbed 172s Reading package lists... 173s Building dependency tree... 173s Reading state information... 173s Starting pkgProblemResolver with broken count: 1 173s Starting 2 pkgProblemResolver with broken count: 1 173s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib > 173s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3) 173s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 173s Considering libopenmpi3t64:ppc64el 1 as a solution to libopenmpi40:ppc64el 1 173s Re-Instated libopenmpi3t64:ppc64el 173s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 173s Considering libopenmpi3t64:ppc64el 1 as a solution to libopenmpi40:ppc64el 1 173s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 173s Done 173s Some packages could not be installed. This may mean that you have 173s requested an impossible situation or if you are using the unstable 173s distribution that some required packages have not yet been created 173s or been moved out of Incoming. 173s The following information may help to resolve the situation: 173s 173s The following packages have unmet dependencies: 173s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 173s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 173s E: Unable to correct problems, you have held broken packages. 173s autopkgtest [09:57:38]: test flow: preparing testbed 173s ellipse FAIL badpkg 173s blame: lammps 173s 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. 173s Reading package lists... 173s Building dependency tree... 173s Reading state information... 174s Starting pkgProblemResolver with broken count: 1 174s Starting 2 pkgProblemResolver with broken count: 1 174s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib > 174s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3) 174s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 174s Considering libopenmpi3t64:ppc64el 1 as a solution to libopenmpi40:ppc64el 1 174s Re-Instated libopenmpi3t64:ppc64el 174s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 174s Considering libopenmpi3t64:ppc64el 1 as a solution to libopenmpi40:ppc64el 1 174s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 174s Done 174s Some packages could not be installed. This may mean that you have 174s requested an impossible situation or if you are using the unstable 174s distribution that some required packages have not yet been created 174s or been moved out of Incoming. 174s The following information may help to resolve the situation: 174s 174s The following packages have unmet dependencies: 174s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 174s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 174s E: Unable to correct problems, you have held broken packages. 174s flow FAIL badpkg 174s blame: lammps 174s autopkgtest [09:57:39]: test friction: preparing testbed 174s 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. 174s Reading package lists... 174s Building dependency tree... 174s Reading state information... 174s Starting pkgProblemResolver with broken count: 1 175s Starting 2 pkgProblemResolver with broken count: 1 175s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib > 175s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3) 175s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 175s Considering libopenmpi3t64:ppc64el 1 as a solution to libopenmpi40:ppc64el 1 175s Re-Instated libopenmpi3t64:ppc64el 175s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 175s Considering libopenmpi3t64:ppc64el 1 as a solution to libopenmpi40:ppc64el 1 175s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 175s Done 175s Some packages could not be installed. This may mean that you have 175s requested an impossible situation or if you are using the unstable 175s distribution that some required packages have not yet been created 175s or been moved out of Incoming. 175s The following information may help to resolve the situation: 175s 175s The following packages have unmet dependencies: 175s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 175s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 175s E: Unable to correct problems, you have held broken packages. 175s autopkgtest [09:57:40]: test hugo: preparing testbed 175s friction FAIL badpkg 175s blame: lammps 175s 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. 175s Reading package lists... 175s Building dependency tree... 175s Reading state information... 175s Starting pkgProblemResolver with broken count: 1 175s Starting 2 pkgProblemResolver with broken count: 1 175s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib > 175s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3) 175s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 175s Considering libopenmpi3t64:ppc64el 1 as a solution to libopenmpi40:ppc64el 1 175s Re-Instated libopenmpi3t64:ppc64el 175s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 175s Considering libopenmpi3t64:ppc64el 1 as a solution to libopenmpi40:ppc64el 1 175s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 175s Done 175s Some packages could not be installed. This may mean that you have 175s requested an impossible situation or if you are using the unstable 175s distribution that some required packages have not yet been created 175s or been moved out of Incoming. 175s The following information may help to resolve the situation: 175s 175s The following packages have unmet dependencies: 176s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 176s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 176s E: Unable to correct problems, you have held broken packages. 176s autopkgtest [09:57:41]: test command1: preparing testbed 176s hugo FAIL badpkg 176s blame: lammps 176s 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. 265s autopkgtest [09:59:10]: testbed dpkg architecture: ppc64el 265s autopkgtest [09:59:10]: testbed apt version: 2.9.14ubuntu1 265s autopkgtest [09:59:10]: @@@@@@@@@@@@@@@@@@@@ test bed setup 265s autopkgtest [09:59:10]: testbed release detected to be: plucky 266s autopkgtest [09:59:11]: updating testbed package index (apt update) 267s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB] 267s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 267s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 267s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 267s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B] 267s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [65.3 kB] 267s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [781 kB] 267s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [15.1 kB] 267s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main ppc64el Packages [127 kB] 267s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted ppc64el Packages [928 B] 267s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe ppc64el Packages [655 kB] 267s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse ppc64el Packages [11.0 kB] 268s Fetched 1739 kB in 1s (1400 kB/s) 269s Reading package lists... 270s Reading package lists... 270s Building dependency tree... 270s Reading state information... 271s Calculating upgrade... 271s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 271s Reading package lists... 271s Building dependency tree... 271s Reading state information... 272s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 272s autopkgtest [09:59:17]: upgrading testbed (apt dist-upgrade and autopurge) 273s Reading package lists... 273s Building dependency tree... 273s Reading state information... 274s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 274s Starting 2 pkgProblemResolver with broken count: 0 274s Done 275s Entering ResolveByKeep 275s 276s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 276s Reading package lists... 276s Building dependency tree... 276s Reading state information... 277s Starting pkgProblemResolver with broken count: 0 277s Starting 2 pkgProblemResolver with broken count: 0 277s Done 278s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 281s Reading package lists... 281s Building dependency tree... 281s Reading state information... 282s Starting pkgProblemResolver with broken count: 1 282s Starting 2 pkgProblemResolver with broken count: 1 282s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib > 282s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3) 282s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 282s Considering libopenmpi3t64:ppc64el 0 as a solution to libopenmpi40:ppc64el 3 282s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 282s Considering libopenmpi3t64:ppc64el 0 as a solution to libopenmpi40:ppc64el 3 282s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 282s Done 282s Some packages could not be installed. This may mean that you have 282s requested an impossible situation or if you are using the unstable 282s distribution that some required packages have not yet been created 282s or been moved out of Incoming. 282s The following information may help to resolve the situation: 282s 282s The following packages have unmet dependencies: 282s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 282s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 282s E: Unable to correct problems, you have held broken packages. 282s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed 282s Reading package lists... 283s Building dependency tree... 283s Reading state information... 283s Starting pkgProblemResolver with broken count: 1 283s Starting 2 pkgProblemResolver with broken count: 1 283s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib > 283s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3) 283s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 283s Considering libopenmpi3t64:ppc64el 0 as a solution to libopenmpi40:ppc64el 3 283s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 283s Considering libopenmpi3t64:ppc64el 0 as a solution to libopenmpi40:ppc64el 3 283s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 283s Done 283s Some packages could not be installed. This may mean that you have 283s requested an impossible situation or if you are using the unstable 283s distribution that some required packages have not yet been created 283s or been moved out of Incoming. 283s The following information may help to resolve the situation: 283s 283s The following packages have unmet dependencies: 283s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 283s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 283s E: Unable to correct problems, you have held broken packages. 283s command1 FAIL badpkg 283s blame: lammps 283s 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. 283s autopkgtest [09:59:28]: @@@@@@@@@@@@@@@@@@@@ summary 283s crack FAIL badpkg 283s blame: lammps 283s 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. 283s dipole FAIL badpkg 283s blame: lammps 283s 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. 283s ellipse FAIL badpkg 283s blame: lammps 283s 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. 283s flow FAIL badpkg 283s blame: lammps 283s 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. 283s friction FAIL badpkg 283s blame: lammps 283s 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. 283s hugo FAIL badpkg 283s blame: lammps 283s 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. 283s command1 FAIL badpkg 283s blame: lammps 283s 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. 296s nova [W] Using flock in prodstack6-ppc64el 296s flock: timeout while waiting to get lock 296s Creating nova instance adt-plucky-ppc64el-lammps-20241203-093416-juju-7f2275-prod-proposed-migration-environment-2-36a5a1b5-24c8-4f91-b4a2-233c9c1f78c2 from image adt/ubuntu-plucky-ppc64el-server-20241203.img (UUID 71a10fe7-f168-4d19-8647-b89d09dd4cc0)... 296s nova [W] Using flock in prodstack6-ppc64el 296s Creating nova instance adt-plucky-ppc64el-lammps-20241203-093416-juju-7f2275-prod-proposed-migration-environment-2-36a5a1b5-24c8-4f91-b4a2-233c9c1f78c2 from image adt/ubuntu-plucky-ppc64el-server-20241203.img (UUID 71a10fe7-f168-4d19-8647-b89d09dd4cc0)...