0s autopkgtest [15:46:58]: starting date and time: 2024-12-04 15:46:58+0000 0s autopkgtest [15:46:58]: git checkout: 48af33f0 Fix --add-apt-source=ppa for focal 0s autopkgtest [15:46:58]: host juju-7f2275-prod-proposed-migration-environment-20; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.wezuu1zl/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 --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-20@bos03-arm64-41.secgroup --name adt-plucky-arm64-lammps-20241204-154657-juju-7f2275-prod-proposed-migration-environment-20-ed0f71d6-6b3c-4204-8bcd-54a1081b0f53 --image adt/ubuntu-plucky-arm64-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-20 --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/ 138s autopkgtest [15:49:16]: testbed dpkg architecture: arm64 139s autopkgtest [15:49:17]: testbed apt version: 2.9.16 139s autopkgtest [15:49:17]: @@@@@@@@@@@@@@@@@@@@ test bed setup 139s autopkgtest [15:49:17]: testbed release detected to be: None 140s autopkgtest [15:49:18]: updating testbed package index (apt update) 140s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB] 140s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 141s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 141s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 141s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [63.2 kB] 141s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B] 141s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [14.2 kB] 141s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [764 kB] 141s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main arm64 Packages [140 kB] 141s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted arm64 Packages [58.2 kB] 141s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe arm64 Packages [637 kB] 141s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse arm64 Packages [20.8 kB] 141s Fetched 1781 kB in 1s (1733 kB/s) 142s Reading package lists... 143s Reading package lists... 143s Building dependency tree... 143s Reading state information... 144s Calculating upgrade... 144s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 144s Reading package lists... 144s Building dependency tree... 144s Reading state information... 145s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 145s autopkgtest [15:49:23]: upgrading testbed (apt dist-upgrade and autopurge) 145s Reading package lists... 146s Building dependency tree... 146s Reading state information... 146s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 146s Starting 2 pkgProblemResolver with broken count: 0 146s Done 147s Entering ResolveByKeep 147s 148s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 148s Reading package lists... 148s Building dependency tree... 148s Reading state information... 149s Starting pkgProblemResolver with broken count: 0 149s Starting 2 pkgProblemResolver with broken count: 0 149s Done 150s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 154s autopkgtest [15:49:32]: testbed running kernel: Linux 6.11.0-8-generic #8-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 16 14:19:41 UTC 2024 155s autopkgtest [15:49:33]: @@@@@@@@@@@@@@@@@@@@ apt-source lammps 184s Get:1 http://ftpmaster.internal/ubuntu plucky/universe lammps 20240207+dfsg-1.1build5 (dsc) [2932 B] 184s Get:2 http://ftpmaster.internal/ubuntu plucky/universe lammps 20240207+dfsg-1.1build5 (tar) [153 MB] 184s Get:3 http://ftpmaster.internal/ubuntu plucky/universe lammps 20240207+dfsg-1.1build5 (diff) [17.2 kB] 184s gpgv: Signature made Tue Jul 30 21:05:03 2024 UTC 184s gpgv: using RSA key 883FEC247A03BE63B70FD5F920FB053CAF9559CF 184s gpgv: issuer "eeickmeyer@ubuntu.com" 184s gpgv: Can't check signature: No public key 184s dpkg-source: warning: cannot verify inline signature for ./lammps_20240207+dfsg-1.1build5.dsc: no acceptable signature found 191s autopkgtest [15:50:09]: testing package lammps version 20240207+dfsg-1.1build5 192s autopkgtest [15:50:10]: build not needed 212s autopkgtest [15:50:30]: test crack: preparing testbed 212s Reading package lists... 213s Building dependency tree... 213s Reading state information... 213s Starting pkgProblemResolver with broken count: 1 213s Starting 2 pkgProblemResolver with broken count: 1 213s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 213s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3) 213s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 213s Considering libopenmpi3t64:arm64 1 as a solution to libopenmpi40:arm64 1 213s Re-Instated libopenmpi3t64:arm64 213s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 213s Considering libopenmpi3t64:arm64 1 as a solution to libopenmpi40:arm64 1 213s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 213s Done 213s Some packages could not be installed. This may mean that you have 213s requested an impossible situation or if you are using the unstable 213s distribution that some required packages have not yet been created 213s or been moved out of Incoming. 213s The following information may help to resolve the situation: 213s 213s The following packages have unmet dependencies: 214s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 214s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 214s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed 214s E: Unable to correct problems, you have held broken packages. 214s Reading package lists... 214s Building dependency tree... 214s Reading state information... 214s Starting pkgProblemResolver with broken count: 1 215s Starting 2 pkgProblemResolver with broken count: 1 215s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 215s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3) 215s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 215s Considering libopenmpi3t64:arm64 0 as a solution to libopenmpi40:arm64 2 215s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 215s Considering libopenmpi3t64:arm64 0 as a solution to libopenmpi40:arm64 2 215s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 215s Done 215s Some packages could not be installed. This may mean that you have 215s requested an impossible situation or if you are using the unstable 215s distribution that some required packages have not yet been created 215s or been moved out of Incoming. 215s The following information may help to resolve the situation: 215s 215s The following packages have unmet dependencies: 215s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 215s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 215s E: Unable to correct problems, you have held broken packages. 215s crack FAIL badpkg 215s blame: lammps 215s 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. 215s autopkgtest [15:50:33]: test dipole: preparing testbed 215s Reading package lists... 216s Building dependency tree... 216s Reading state information... 216s Starting pkgProblemResolver with broken count: 1 216s Starting 2 pkgProblemResolver with broken count: 1 216s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 216s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3) 216s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 216s Considering libopenmpi3t64:arm64 0 as a solution to libopenmpi40:arm64 2 216s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 216s Considering libopenmpi3t64:arm64 0 as a solution to libopenmpi40:arm64 2 216s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 216s Done 216s Some packages could not be installed. This may mean that you have 216s requested an impossible situation or if you are using the unstable 216s distribution that some required packages have not yet been created 216s or been moved out of Incoming. 216s The following information may help to resolve the situation: 216s 216s The following packages have unmet dependencies: 216s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 216s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 216s E: Unable to correct problems, you have held broken packages. 216s autopkgtest [15:50:34]: test ellipse: preparing testbed 216s dipole FAIL badpkg 216s blame: lammps 216s 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. 217s Reading package lists... 217s Building dependency tree... 217s Reading state information... 217s Starting pkgProblemResolver with broken count: 1 217s Starting 2 pkgProblemResolver with broken count: 1 217s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 217s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3) 217s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 217s Considering libopenmpi3t64:arm64 0 as a solution to libopenmpi40:arm64 2 217s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 217s Considering libopenmpi3t64:arm64 0 as a solution to libopenmpi40:arm64 2 217s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 217s Done 217s Some packages could not be installed. This may mean that you have 217s requested an impossible situation or if you are using the unstable 217s distribution that some required packages have not yet been created 217s or been moved out of Incoming. 217s The following information may help to resolve the situation: 217s 217s The following packages have unmet dependencies: 218s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 218s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 218s E: Unable to correct problems, you have held broken packages. 218s autopkgtest [15:50:36]: test flow: preparing testbed 218s ellipse FAIL badpkg 218s blame: lammps 218s 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. 218s Reading package lists... 218s Building dependency tree... 218s Reading state information... 219s Starting pkgProblemResolver with broken count: 1 219s Starting 2 pkgProblemResolver with broken count: 1 219s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 219s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3) 219s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 219s Considering libopenmpi3t64:arm64 0 as a solution to libopenmpi40:arm64 2 219s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 219s Considering libopenmpi3t64:arm64 0 as a solution to libopenmpi40:arm64 2 219s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 219s Done 219s Some packages could not be installed. This may mean that you have 219s requested an impossible situation or if you are using the unstable 219s distribution that some required packages have not yet been created 219s or been moved out of Incoming. 219s The following information may help to resolve the situation: 219s 219s The following packages have unmet dependencies: 219s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 219s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 219s E: Unable to correct problems, you have held broken packages. 219s autopkgtest [15:50:37]: test friction: preparing testbed 219s flow FAIL badpkg 219s blame: lammps 219s 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. 219s Reading package lists... 220s Building dependency tree... 220s Reading state information... 220s Starting pkgProblemResolver with broken count: 1 220s Starting 2 pkgProblemResolver with broken count: 1 220s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 220s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3) 220s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 220s Considering libopenmpi3t64:arm64 0 as a solution to libopenmpi40:arm64 2 220s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 220s Considering libopenmpi3t64:arm64 0 as a solution to libopenmpi40:arm64 2 220s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 220s Done 220s Some packages could not be installed. This may mean that you have 220s requested an impossible situation or if you are using the unstable 220s distribution that some required packages have not yet been created 220s or been moved out of Incoming. 220s The following information may help to resolve the situation: 220s 220s The following packages have unmet dependencies: 221s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 221s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 221s E: Unable to correct problems, you have held broken packages. 221s autopkgtest [15:50:39]: test hugo: preparing testbed 221s friction FAIL badpkg 221s blame: lammps 221s 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. 221s Reading package lists... 221s Building dependency tree... 221s Reading state information... 222s Starting pkgProblemResolver with broken count: 1 222s Starting 2 pkgProblemResolver with broken count: 1 222s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 222s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3) 222s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 222s Considering libopenmpi3t64:arm64 0 as a solution to libopenmpi40:arm64 2 222s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 222s Considering libopenmpi3t64:arm64 0 as a solution to libopenmpi40:arm64 2 222s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 222s Done 222s Some packages could not be installed. This may mean that you have 222s requested an impossible situation or if you are using the unstable 222s distribution that some required packages have not yet been created 222s or been moved out of Incoming. 222s The following information may help to resolve the situation: 222s 222s The following packages have unmet dependencies: 222s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 222s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 222s E: Unable to correct problems, you have held broken packages. 222s autopkgtest [15:50:40]: test command1: preparing testbed 222s hugo FAIL badpkg 222s blame: lammps 222s 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. 335s autopkgtest [15:52:33]: testbed dpkg architecture: arm64 335s autopkgtest [15:52:33]: testbed apt version: 2.9.16 335s autopkgtest [15:52:33]: @@@@@@@@@@@@@@@@@@@@ test bed setup 336s autopkgtest [15:52:34]: testbed release detected to be: plucky 336s autopkgtest [15:52:34]: updating testbed package index (apt update) 337s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB] 337s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 337s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 337s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 337s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [63.2 kB] 337s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B] 337s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [764 kB] 337s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [14.2 kB] 337s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main arm64 Packages [140 kB] 337s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted arm64 Packages [58.2 kB] 337s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe arm64 Packages [637 kB] 337s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse arm64 Packages [20.8 kB] 338s Fetched 1781 kB in 1s (1976 kB/s) 339s Reading package lists... 339s Reading package lists... 340s Building dependency tree... 340s Reading state information... 340s Calculating upgrade... 341s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 341s Reading package lists... 341s Building dependency tree... 341s Reading state information... 342s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 342s autopkgtest [15:52:40]: upgrading testbed (apt dist-upgrade and autopurge) 342s Reading package lists... 342s Building dependency tree... 342s Reading state information... 343s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 343s Starting 2 pkgProblemResolver with broken count: 0 343s Done 344s Entering ResolveByKeep 344s 344s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 345s Reading package lists... 345s Building dependency tree... 345s Reading state information... 345s Starting pkgProblemResolver with broken count: 0 345s Starting 2 pkgProblemResolver with broken count: 0 345s Done 346s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 349s Reading package lists... 349s Building dependency tree... 349s Reading state information... 349s Starting pkgProblemResolver with broken count: 1 350s Starting 2 pkgProblemResolver with broken count: 1 350s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 350s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3) 350s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 350s Considering libopenmpi3t64:arm64 0 as a solution to libopenmpi40:arm64 3 350s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 350s Considering libopenmpi3t64:arm64 0 as a solution to libopenmpi40:arm64 3 350s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 350s Done 350s Some packages could not be installed. This may mean that you have 350s requested an impossible situation or if you are using the unstable 350s distribution that some required packages have not yet been created 350s or been moved out of Incoming. 350s The following information may help to resolve the situation: 350s 350s The following packages have unmet dependencies: 350s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 350s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 350s E: Unable to correct problems, you have held broken packages. 350s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed 350s Reading package lists... 351s Building dependency tree... 351s Reading state information... 351s Starting pkgProblemResolver with broken count: 1 351s Starting 2 pkgProblemResolver with broken count: 1 351s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib > 351s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3) 351s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 351s Considering libopenmpi3t64:arm64 -1 as a solution to libopenmpi40:arm64 4 351s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 351s Considering libopenmpi3t64:arm64 -1 as a solution to libopenmpi40:arm64 4 351s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 351s Done 351s Some packages could not be installed. This may mean that you have 351s requested an impossible situation or if you are using the unstable 351s distribution that some required packages have not yet been created 351s or been moved out of Incoming. 351s The following information may help to resolve the situation: 351s 351s The following packages have unmet dependencies: 351s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 351s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 351s E: Unable to correct problems, you have held broken packages. 351s autopkgtest [15:52:49]: @@@@@@@@@@@@@@@@@@@@ summary 351s crack FAIL badpkg 351s blame: lammps 351s 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. 351s dipole FAIL badpkg 351s blame: lammps 351s 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. 351s ellipse FAIL badpkg 351s blame: lammps 351s 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. 351s flow FAIL badpkg 351s blame: lammps 351s 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. 351s friction FAIL badpkg 351s blame: lammps 351s 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. 351s hugo FAIL badpkg 351s blame: lammps 351s 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. 351s command1 FAIL badpkg 351s blame: lammps 351s 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. 351s command1 FAIL badpkg 351s blame: lammps 351s 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. 363s nova [W] Using flock in prodstack6-arm64 363s flock: timeout while waiting to get lock 363s Creating nova instance adt-plucky-arm64-lammps-20241204-154657-juju-7f2275-prod-proposed-migration-environment-20-ed0f71d6-6b3c-4204-8bcd-54a1081b0f53 from image adt/ubuntu-plucky-arm64-server-20241204.img (UUID b1e2b1c6-409a-4f80-af2b-468b6b2bbda4)... 363s nova [W] Using flock in prodstack6-arm64 363s Creating nova instance adt-plucky-arm64-lammps-20241204-154657-juju-7f2275-prod-proposed-migration-environment-20-ed0f71d6-6b3c-4204-8bcd-54a1081b0f53 from image adt/ubuntu-plucky-arm64-server-20241204.img (UUID b1e2b1c6-409a-4f80-af2b-468b6b2bbda4)...