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-2; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.7sawtb6k/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 --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-2@bos03-arm64-43.secgroup --name adt-plucky-arm64-lammps-20241203-093416-juju-7f2275-prod-proposed-migration-environment-2-33ee074f-a7cc-4aa3-baea-afc209d1e514 --image adt/ubuntu-plucky-arm64-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-2 --net-id=net_prod-proposed-migration -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/ 133s autopkgtest [09:36:30]: testbed dpkg architecture: arm64 134s autopkgtest [09:36:31]: testbed apt version: 2.9.14ubuntu1 134s autopkgtest [09:36:31]: @@@@@@@@@@@@@@@@@@@@ test bed setup 134s autopkgtest [09:36:31]: testbed release detected to be: None 135s autopkgtest [09:36:32]: updating testbed package index (apt update) 135s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB] 136s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 136s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 136s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 136s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [65.3 kB] 136s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B] 136s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [15.1 kB] 136s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [781 kB] 136s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main arm64 Packages [145 kB] 136s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted arm64 Packages [58.2 kB] 136s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe arm64 Packages [669 kB] 136s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse arm64 Packages [21.3 kB] 136s Fetched 1838 kB in 1s (1828 kB/s) 137s Reading package lists... 138s Reading package lists... 138s Building dependency tree... 138s Reading state information... 139s Calculating upgrade... 139s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 139s Reading package lists... 139s Building dependency tree... 139s Reading state information... 140s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 140s autopkgtest [09:36:37]: upgrading testbed (apt dist-upgrade and autopurge) 140s Reading package lists... 141s Building dependency tree... 141s Reading state information... 141s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 141s Starting 2 pkgProblemResolver with broken count: 0 141s Done 142s Entering ResolveByKeep 142s 143s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 143s Reading package lists... 143s Building dependency tree... 143s Reading state information... 144s Starting pkgProblemResolver with broken count: 0 144s Starting 2 pkgProblemResolver with broken count: 0 144s Done 145s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 147s autopkgtest [09:36:44]: testbed running kernel: Linux 6.11.0-8-generic #8-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 16 14:19:41 UTC 2024 147s autopkgtest [09:36:44]: @@@@@@@@@@@@@@@@@@@@ apt-source lammps 157s Get:1 http://ftpmaster.internal/ubuntu plucky/universe lammps 20240207+dfsg-1.1build5 (dsc) [2932 B] 157s Get:2 http://ftpmaster.internal/ubuntu plucky/universe lammps 20240207+dfsg-1.1build5 (tar) [153 MB] 157s Get:3 http://ftpmaster.internal/ubuntu plucky/universe lammps 20240207+dfsg-1.1build5 (diff) [17.2 kB] 157s gpgv: Signature made Tue Jul 30 21:05:03 2024 UTC 157s gpgv: using RSA key 883FEC247A03BE63B70FD5F920FB053CAF9559CF 157s gpgv: issuer "eeickmeyer@ubuntu.com" 157s gpgv: Can't check signature: No public key 157s dpkg-source: warning: cannot verify inline signature for ./lammps_20240207+dfsg-1.1build5.dsc: no acceptable signature found 164s autopkgtest [09:37:01]: testing package lammps version 20240207+dfsg-1.1build5 165s autopkgtest [09:37:02]: build not needed 196s autopkgtest [09:37:33]: test crack: preparing testbed 196s Reading package lists... 197s Building dependency tree... 197s Reading state information... 197s Starting pkgProblemResolver with broken count: 1 197s Starting 2 pkgProblemResolver with broken count: 1 197s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 197s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3) 197s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 197s Considering libopenmpi3t64:arm64 1 as a solution to libopenmpi40:arm64 1 197s Re-Instated libopenmpi3t64:arm64 197s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 197s Considering libopenmpi3t64:arm64 1 as a solution to libopenmpi40:arm64 1 197s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 197s Done 197s Some packages could not be installed. This may mean that you have 197s requested an impossible situation or if you are using the unstable 197s distribution that some required packages have not yet been created 197s or been moved out of Incoming. 197s The following information may help to resolve the situation: 197s 197s The following packages have unmet dependencies: 197s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 197s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 197s E: Unable to correct problems, you have held broken packages. 197s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed 198s Reading package lists... 198s Building dependency tree... 198s Reading state information... 199s Starting pkgProblemResolver with broken count: 1 199s Starting 2 pkgProblemResolver with broken count: 1 199s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 199s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3) 199s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 199s Considering libopenmpi3t64:arm64 1 as a solution to libopenmpi40:arm64 1 199s Re-Instated libopenmpi3t64:arm64 199s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 199s Considering libopenmpi3t64:arm64 1 as a solution to libopenmpi40:arm64 1 199s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 199s Done 199s Some packages could not be installed. This may mean that you have 199s requested an impossible situation or if you are using the unstable 199s distribution that some required packages have not yet been created 199s or been moved out of Incoming. 199s The following information may help to resolve the situation: 199s 199s The following packages have unmet dependencies: 199s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 199s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 199s E: Unable to correct problems, you have held broken packages. 199s crack FAIL badpkg 199s blame: lammps 199s 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. 199s autopkgtest [09:37:36]: test dipole: preparing testbed 199s Reading package lists... 200s Building dependency tree... 200s Reading state information... 200s Starting pkgProblemResolver with broken count: 1 200s Starting 2 pkgProblemResolver with broken count: 1 200s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 200s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3) 200s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 200s Considering libopenmpi3t64:arm64 1 as a solution to libopenmpi40:arm64 1 200s Re-Instated libopenmpi3t64:arm64 200s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 200s Considering libopenmpi3t64:arm64 1 as a solution to libopenmpi40:arm64 1 200s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 200s Done 200s Some packages could not be installed. This may mean that you have 200s requested an impossible situation or if you are using the unstable 200s distribution that some required packages have not yet been created 200s or been moved out of Incoming. 200s The following information may help to resolve the situation: 200s 200s The following packages have unmet dependencies: 201s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 201s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 201s E: Unable to correct problems, you have held broken packages. 201s dipole FAIL badpkg 201s blame: lammps 201s 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. 201s autopkgtest [09:37:38]: test ellipse: preparing testbed 201s Reading package lists... 201s Building dependency tree... 201s Reading state information... 202s Starting pkgProblemResolver with broken count: 1 202s Starting 2 pkgProblemResolver with broken count: 1 202s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 202s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < 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:arm64 1 as a solution to libopenmpi40:arm64 1 202s Re-Instated libopenmpi3t64:arm64 202s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 202s Considering libopenmpi3t64:arm64 1 as a solution to libopenmpi40:arm64 1 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 ellipse FAIL badpkg 202s blame: lammps 202s 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. 202s autopkgtest [09:37:39]: test flow: preparing testbed 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:arm64 < none -> 5.0.6-3 @un puN Ib > 203s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < 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:arm64 1 as a solution to libopenmpi40:arm64 1 203s Re-Instated libopenmpi3t64:arm64 203s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 203s Considering libopenmpi3t64:arm64 1 as a solution to libopenmpi40:arm64 1 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: 204s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 204s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 204s E: Unable to correct problems, you have held broken packages. 204s autopkgtest [09:37:41]: test friction: preparing testbed 204s flow FAIL badpkg 204s blame: lammps 204s 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. 204s Reading package lists... 204s Building dependency tree... 204s Reading state information... 205s Starting pkgProblemResolver with broken count: 1 205s Starting 2 pkgProblemResolver with broken count: 1 205s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 205s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3) 205s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 205s Considering libopenmpi3t64:arm64 1 as a solution to libopenmpi40:arm64 1 205s Re-Instated libopenmpi3t64:arm64 205s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 205s Considering libopenmpi3t64:arm64 1 as a solution to libopenmpi40:arm64 1 205s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 205s Done 205s Some packages could not be installed. This may mean that you have 205s requested an impossible situation or if you are using the unstable 205s distribution that some required packages have not yet been created 205s or been moved out of Incoming. 205s The following information may help to resolve the situation: 205s 205s The following packages have unmet dependencies: 205s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 205s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 205s E: Unable to correct problems, you have held broken packages. 205s friction FAIL badpkg 205s blame: lammps 205s 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. 205s autopkgtest [09:37:42]: test hugo: preparing testbed 206s Reading package lists... 206s Building dependency tree... 206s Reading state information... 206s Starting pkgProblemResolver with broken count: 1 206s Starting 2 pkgProblemResolver with broken count: 1 206s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 206s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3) 206s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 206s Considering libopenmpi3t64:arm64 1 as a solution to libopenmpi40:arm64 1 206s Re-Instated libopenmpi3t64:arm64 206s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 206s Considering libopenmpi3t64:arm64 1 as a solution to libopenmpi40:arm64 1 206s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 206s Done 206s Some packages could not be installed. This may mean that you have 206s requested an impossible situation or if you are using the unstable 206s distribution that some required packages have not yet been created 206s or been moved out of Incoming. 206s The following information may help to resolve the situation: 206s 206s The following packages have unmet dependencies: 207s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 207s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 207s E: Unable to correct problems, you have held broken packages. 207s hugo FAIL badpkg 207s blame: lammps 207s 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. 207s autopkgtest [09:37:44]: test command1: preparing testbed 371s autopkgtest [09:40:28]: testbed dpkg architecture: arm64 372s autopkgtest [09:40:29]: testbed apt version: 2.9.14ubuntu1 372s autopkgtest [09:40:29]: @@@@@@@@@@@@@@@@@@@@ test bed setup 372s autopkgtest [09:40:29]: testbed release detected to be: plucky 373s autopkgtest [09:40:30]: updating testbed package index (apt update) 374s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB] 374s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 374s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 374s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 374s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [781 kB] 374s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B] 374s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [65.3 kB] 374s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [15.1 kB] 374s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main arm64 Packages [145 kB] 374s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted arm64 Packages [58.2 kB] 374s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe arm64 Packages [669 kB] 374s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse arm64 Packages [21.3 kB] 375s Fetched 1838 kB in 1s (1882 kB/s) 376s Reading package lists... 377s Reading package lists... 377s Building dependency tree... 377s Reading state information... 378s Calculating upgrade... 379s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 379s Reading package lists... 380s Building dependency tree... 380s Reading state information... 381s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 381s autopkgtest [09:40:38]: upgrading testbed (apt dist-upgrade and autopurge) 381s Reading package lists... 382s Building dependency tree... 382s Reading state information... 382s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 383s Starting 2 pkgProblemResolver with broken count: 0 383s Done 384s Entering ResolveByKeep 384s 385s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 385s Reading package lists... 385s Building dependency tree... 385s Reading state information... 386s Starting pkgProblemResolver with broken count: 0 386s Starting 2 pkgProblemResolver with broken count: 0 386s Done 387s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 391s Reading package lists... 391s Building dependency tree... 391s Reading state information... 392s Starting pkgProblemResolver with broken count: 1 392s Starting 2 pkgProblemResolver with broken count: 1 392s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 392s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3) 392s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 392s Considering libopenmpi3t64:arm64 0 as a solution to libopenmpi40:arm64 3 392s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 392s Considering libopenmpi3t64:arm64 0 as a solution to libopenmpi40:arm64 3 392s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 392s Done 392s Some packages could not be installed. This may mean that you have 392s requested an impossible situation or if you are using the unstable 392s distribution that some required packages have not yet been created 392s or been moved out of Incoming. 392s The following information may help to resolve the situation: 392s 392s The following packages have unmet dependencies: 392s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 392s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 392s E: Unable to correct problems, you have held broken packages. 392s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed 393s Reading package lists... 393s Building dependency tree... 393s Reading state information... 394s Starting pkgProblemResolver with broken count: 1 395s Starting 2 pkgProblemResolver with broken count: 1 395s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 395s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3) 395s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 395s Considering libopenmpi3t64:arm64 0 as a solution to libopenmpi40:arm64 3 395s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 395s Considering libopenmpi3t64:arm64 0 as a solution to libopenmpi40:arm64 3 395s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 395s Done 395s Some packages could not be installed. This may mean that you have 395s requested an impossible situation or if you are using the unstable 395s distribution that some required packages have not yet been created 395s or been moved out of Incoming. 395s The following information may help to resolve the situation: 395s 395s The following packages have unmet dependencies: 395s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 395s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 395s E: Unable to correct problems, you have held broken packages. 395s command1 FAIL badpkg 395s blame: lammps 395s 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. 395s autopkgtest [09:40:52]: @@@@@@@@@@@@@@@@@@@@ summary 395s crack FAIL badpkg 395s blame: lammps 395s 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. 395s dipole FAIL badpkg 395s blame: lammps 395s 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. 395s ellipse FAIL badpkg 395s blame: lammps 395s 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. 395s flow FAIL badpkg 395s blame: lammps 395s 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. 395s friction FAIL badpkg 395s blame: lammps 395s 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. 395s hugo FAIL badpkg 395s blame: lammps 395s 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. 395s command1 FAIL badpkg 395s blame: lammps 395s 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. 412s nova [W] Using flock in prodstack6-arm64 412s flock: timeout while waiting to get lock 412s Creating nova instance adt-plucky-arm64-lammps-20241203-093416-juju-7f2275-prod-proposed-migration-environment-2-33ee074f-a7cc-4aa3-baea-afc209d1e514 from image adt/ubuntu-plucky-arm64-server-20241203.img (UUID b9293590-1195-42ea-ba16-5ab4b1e94eab)... 412s nova [W] Using flock in prodstack6-arm64 412s flock: timeout while waiting to get lock 412s Creating nova instance adt-plucky-arm64-lammps-20241203-093416-juju-7f2275-prod-proposed-migration-environment-2-33ee074f-a7cc-4aa3-baea-afc209d1e514 from image adt/ubuntu-plucky-arm64-server-20241203.img (UUID b9293590-1195-42ea-ba16-5ab4b1e94eab)...