0s autopkgtest [09:34:17]: starting date and time: 2024-12-03 09:34:17+0000 0s autopkgtest [09:34:17]: git checkout: be626eda Fix armhf LXD image generation for plucky 0s autopkgtest [09:34:17]: host juju-7f2275-prod-proposed-migration-environment-15; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.huphsvsi/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:openmpi,src:hdf5,src:vtk9,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 hdf5/1.10.10+repack-5ubuntu1 vtk9/9.3.0+dfsg1-1.1build2 fftw3/3.3.10-2fakesync1build1 pnetcdf/1.13.0-1build1' -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor builder-cpu2-ram4-disk20 --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-15@bos03-4.secgroup --name adt-plucky-amd64-lammps-20241203-093417-juju-7f2275-prod-proposed-migration-environment-15-222d1a13-c6ad-49b9-8918-1ea03412431e --image adt/ubuntu-plucky-amd64-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-15 --net-id=net_prod-proposed-migration-amd64 -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/ 62s autopkgtest [09:35:19]: testbed dpkg architecture: amd64 62s autopkgtest [09:35:19]: testbed apt version: 2.9.14ubuntu1 62s autopkgtest [09:35:19]: @@@@@@@@@@@@@@@@@@@@ test bed setup 62s autopkgtest [09:35:19]: testbed release detected to be: None 63s autopkgtest [09:35:20]: updating testbed package index (apt update) 63s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB] 64s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 64s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 64s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 64s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [15.1 kB] 64s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [65.3 kB] 64s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [781 kB] 64s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B] 64s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main amd64 Packages [153 kB] 64s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/main i386 Packages [104 kB] 64s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/restricted i386 Packages [2572 B] 64s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/restricted amd64 Packages [40.6 kB] 64s Get:13 http://ftpmaster.internal/ubuntu plucky-proposed/universe i386 Packages [256 kB] 64s Get:14 http://ftpmaster.internal/ubuntu plucky-proposed/universe amd64 Packages [687 kB] 64s Get:15 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse amd64 Packages [21.9 kB] 64s Get:16 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse i386 Packages [6364 B] 64s Fetched 2217 kB in 1s (2506 kB/s) 65s Reading package lists... 65s Reading package lists... 66s Building dependency tree... 66s Reading state information... 66s Calculating upgrade... 66s The following packages will be upgraded: 66s gcc-14-base libatomic1 libgcc-s1 libstdc++6 66s 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 66s Need to get 928 kB of archives. 66s After this operation, 1024 B of additional disk space will be used. 66s Get:1 http://ftpmaster.internal/ubuntu plucky/main amd64 libatomic1 amd64 14.2.0-9ubuntu1 [10.3 kB] 66s Get:2 http://ftpmaster.internal/ubuntu plucky/main amd64 gcc-14-base amd64 14.2.0-9ubuntu1 [52.0 kB] 67s Get:3 http://ftpmaster.internal/ubuntu plucky/main amd64 libstdc++6 amd64 14.2.0-9ubuntu1 [788 kB] 67s Get:4 http://ftpmaster.internal/ubuntu plucky/main amd64 libgcc-s1 amd64 14.2.0-9ubuntu1 [78.4 kB] 67s Fetched 928 kB in 1s (1667 kB/s) 67s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 75952 files and directories currently installed.) 67s Preparing to unpack .../libatomic1_14.2.0-9ubuntu1_amd64.deb ... 67s Unpacking libatomic1:amd64 (14.2.0-9ubuntu1) over (14.2.0-8ubuntu1) ... 67s Preparing to unpack .../gcc-14-base_14.2.0-9ubuntu1_amd64.deb ... 67s Unpacking gcc-14-base:amd64 (14.2.0-9ubuntu1) over (14.2.0-8ubuntu1) ... 67s Setting up gcc-14-base:amd64 (14.2.0-9ubuntu1) ... 68s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 75952 files and directories currently installed.) 68s Preparing to unpack .../libstdc++6_14.2.0-9ubuntu1_amd64.deb ... 68s Unpacking libstdc++6:amd64 (14.2.0-9ubuntu1) over (14.2.0-8ubuntu1) ... 68s Setting up libstdc++6:amd64 (14.2.0-9ubuntu1) ... 68s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 75952 files and directories currently installed.) 68s Preparing to unpack .../libgcc-s1_14.2.0-9ubuntu1_amd64.deb ... 68s Unpacking libgcc-s1:amd64 (14.2.0-9ubuntu1) over (14.2.0-8ubuntu1) ... 68s Setting up libgcc-s1:amd64 (14.2.0-9ubuntu1) ... 68s Setting up libatomic1:amd64 (14.2.0-9ubuntu1) ... 68s Processing triggers for libc-bin (2.40-1ubuntu3) ... 68s Reading package lists... 68s Building dependency tree... 68s Reading state information... 68s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 69s autopkgtest [09:35:26]: 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 70s Entering ResolveByKeep 70s 70s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 71s Reading package lists... 71s Building dependency tree... 71s Reading state information... 71s Starting pkgProblemResolver with broken count: 0 71s Starting 2 pkgProblemResolver with broken count: 0 71s Done 72s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 74s autopkgtest [09:35:31]: testbed running kernel: Linux 6.11.0-8-generic #8-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 16 13:41:20 UTC 2024 74s autopkgtest [09:35:31]: @@@@@@@@@@@@@@@@@@@@ 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 90s autopkgtest [09:35:47]: testing package lammps version 20240207+dfsg-1.1build5 90s autopkgtest [09:35:47]: build not needed 117s autopkgtest [09:36:14]: test crack: 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:amd64 < none -> 5.0.6-3 @un puN Ib > 118s Broken libopenmpi40:amd64 Breaks on libopenmpi3:amd64 < 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:amd64 0 as a solution to libopenmpi40:amd64 2 118s Broken libopenmpi40:amd64 Breaks on libopenmpi3t64:amd64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 118s Considering libopenmpi3t64:amd64 0 as a solution to libopenmpi40:amd64 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 autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed 118s E: Unable to correct problems, you have held broken packages. 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:amd64 < none -> 5.0.6-3 @un puN Ib > 120s Broken libopenmpi40:amd64 Breaks on libopenmpi3:amd64 < 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:amd64 0 as a solution to libopenmpi40:amd64 2 120s Broken libopenmpi40:amd64 Breaks on libopenmpi3t64:amd64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 120s Considering libopenmpi3t64:amd64 0 as a solution to libopenmpi40:amd64 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 crack 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. 120s autopkgtest [09:36:17]: test dipole: preparing testbed 120s Reading package lists... 120s Building dependency tree... 120s Reading state information... 121s Starting pkgProblemResolver with broken count: 1 121s Starting 2 pkgProblemResolver with broken count: 1 121s Investigating (0) libopenmpi40:amd64 < none -> 5.0.6-3 @un puN Ib > 121s Broken libopenmpi40:amd64 Breaks on libopenmpi3:amd64 < none @un H > (< 5.0.6-3) 121s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 121s Considering libopenmpi3t64:amd64 0 as a solution to libopenmpi40:amd64 2 121s Broken libopenmpi40:amd64 Breaks on libopenmpi3t64:amd64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 121s Considering libopenmpi3t64:amd64 0 as a solution to libopenmpi40:amd64 2 121s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 121s Done 121s Some packages could not be installed. This may mean that you have 121s requested an impossible situation or if you are using the unstable 121s distribution that some required packages have not yet been created 121s or been moved out of Incoming. 121s The following information may help to resolve the situation: 121s 121s The following packages have unmet dependencies: 121s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 121s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 121s E: Unable to correct problems, you have held broken packages. 121s dipole FAIL badpkg 121s blame: lammps 121s 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. 121s autopkgtest [09:36:18]: test ellipse: preparing testbed 121s Reading package lists... 121s Building dependency tree... 121s Reading state information... 122s Starting pkgProblemResolver with broken count: 1 122s Starting 2 pkgProblemResolver with broken count: 1 122s Investigating (0) libopenmpi40:amd64 < none -> 5.0.6-3 @un puN Ib > 122s Broken libopenmpi40:amd64 Breaks on libopenmpi3:amd64 < none @un H > (< 5.0.6-3) 122s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 122s Considering libopenmpi3t64:amd64 0 as a solution to libopenmpi40:amd64 2 122s Broken libopenmpi40:amd64 Breaks on libopenmpi3t64:amd64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 122s Considering libopenmpi3t64:amd64 0 as a solution to libopenmpi40:amd64 2 122s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 122s Done 122s Some packages could not be installed. This may mean that you have 122s requested an impossible situation or if you are using the unstable 122s distribution that some required packages have not yet been created 122s or been moved out of Incoming. 122s The following information may help to resolve the situation: 122s 122s The following packages have unmet dependencies: 122s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 122s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 122s E: Unable to correct problems, you have held broken packages. 122s ellipse FAIL badpkg 122s blame: lammps 122s 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. 122s autopkgtest [09:36:19]: test flow: preparing testbed 122s Reading package lists... 122s Building dependency tree... 122s Reading state information... 123s Starting pkgProblemResolver with broken count: 1 123s Starting 2 pkgProblemResolver with broken count: 1 123s Investigating (0) libopenmpi40:amd64 < none -> 5.0.6-3 @un puN Ib > 123s Broken libopenmpi40:amd64 Breaks on libopenmpi3:amd64 < none @un H > (< 5.0.6-3) 123s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 123s Considering libopenmpi3t64:amd64 0 as a solution to libopenmpi40:amd64 2 123s Broken libopenmpi40:amd64 Breaks on libopenmpi3t64:amd64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 123s Considering libopenmpi3t64:amd64 0 as a solution to libopenmpi40:amd64 2 123s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 123s Done 123s Some packages could not be installed. This may mean that you have 123s requested an impossible situation or if you are using the unstable 123s distribution that some required packages have not yet been created 123s or been moved out of Incoming. 123s The following information may help to resolve the situation: 123s 123s The following packages have unmet dependencies: 123s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 123s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 123s E: Unable to correct problems, you have held broken packages. 123s flow FAIL badpkg 123s blame: lammps 123s 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. 123s autopkgtest [09:36:20]: test friction: preparing testbed 123s Reading package lists... 124s Building dependency tree... 124s Reading state information... 124s Starting pkgProblemResolver with broken count: 1 124s Starting 2 pkgProblemResolver with broken count: 1 124s Investigating (0) libopenmpi40:amd64 < none -> 5.0.6-3 @un puN Ib > 124s Broken libopenmpi40:amd64 Breaks on libopenmpi3:amd64 < none @un H > (< 5.0.6-3) 124s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 124s Considering libopenmpi3t64:amd64 0 as a solution to libopenmpi40:amd64 2 124s Broken libopenmpi40:amd64 Breaks on libopenmpi3t64:amd64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 124s Considering libopenmpi3t64:amd64 0 as a solution to libopenmpi40:amd64 2 124s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 124s Done 124s Some packages could not be installed. This may mean that you have 124s requested an impossible situation or if you are using the unstable 124s distribution that some required packages have not yet been created 124s or been moved out of Incoming. 124s The following information may help to resolve the situation: 124s 124s The following packages have unmet dependencies: 124s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 124s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 124s E: Unable to correct problems, you have held broken packages. 124s friction FAIL badpkg 124s blame: lammps 124s 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. 124s autopkgtest [09:36:21]: test hugo: preparing testbed 124s Reading package lists... 124s Building dependency tree... 124s Reading state information... 125s Starting pkgProblemResolver with broken count: 1 125s Starting 2 pkgProblemResolver with broken count: 1 125s Investigating (0) libopenmpi40:amd64 < none -> 5.0.6-3 @un puN Ib > 125s Broken libopenmpi40:amd64 Breaks on libopenmpi3:amd64 < none @un H > (< 5.0.6-3) 125s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 125s Considering libopenmpi3t64:amd64 0 as a solution to libopenmpi40:amd64 2 125s Broken libopenmpi40:amd64 Breaks on libopenmpi3t64:amd64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 125s Considering libopenmpi3t64:amd64 0 as a solution to libopenmpi40:amd64 2 125s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 125s Done 125s Some packages could not be installed. This may mean that you have 125s requested an impossible situation or if you are using the unstable 125s distribution that some required packages have not yet been created 125s or been moved out of Incoming. 125s The following information may help to resolve the situation: 125s 125s The following packages have unmet dependencies: 125s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 125s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 125s E: Unable to correct problems, you have held broken packages. 125s hugo FAIL badpkg 125s blame: lammps 125s 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. 125s autopkgtest [09:36:22]: test command1: preparing testbed 188s autopkgtest [09:37:25]: testbed dpkg architecture: amd64 189s autopkgtest [09:37:26]: testbed apt version: 2.9.14ubuntu1 189s autopkgtest [09:37:26]: @@@@@@@@@@@@@@@@@@@@ test bed setup 189s autopkgtest [09:37:26]: testbed release detected to be: plucky 190s autopkgtest [09:37:27]: updating testbed package index (apt update) 190s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB] 190s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 191s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 191s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 191s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [781 kB] 191s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [65.3 kB] 191s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [15.1 kB] 191s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B] 191s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main amd64 Packages [153 kB] 191s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/main i386 Packages [104 kB] 191s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/restricted amd64 Packages [40.6 kB] 191s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/restricted i386 Packages [2572 B] 191s Get:13 http://ftpmaster.internal/ubuntu plucky-proposed/universe amd64 Packages [687 kB] 191s Get:14 http://ftpmaster.internal/ubuntu plucky-proposed/universe i386 Packages [256 kB] 191s Get:15 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse amd64 Packages [21.9 kB] 191s Get:16 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse i386 Packages [6364 B] 191s Fetched 2217 kB in 1s (2045 kB/s) 192s Reading package lists... 192s Reading package lists... 193s Building dependency tree... 193s Reading state information... 193s Calculating upgrade... 193s The following packages will be upgraded: 193s gcc-14-base libatomic1 libgcc-s1 libstdc++6 193s 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 193s Need to get 928 kB of archives. 193s After this operation, 1024 B of additional disk space will be used. 193s Get:1 http://ftpmaster.internal/ubuntu plucky/main amd64 libatomic1 amd64 14.2.0-9ubuntu1 [10.3 kB] 193s Get:2 http://ftpmaster.internal/ubuntu plucky/main amd64 gcc-14-base amd64 14.2.0-9ubuntu1 [52.0 kB] 193s Get:3 http://ftpmaster.internal/ubuntu plucky/main amd64 libstdc++6 amd64 14.2.0-9ubuntu1 [788 kB] 193s Get:4 http://ftpmaster.internal/ubuntu plucky/main amd64 libgcc-s1 amd64 14.2.0-9ubuntu1 [78.4 kB] 194s Fetched 928 kB in 1s (1539 kB/s) 194s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 75952 files and directories currently installed.) 194s Preparing to unpack .../libatomic1_14.2.0-9ubuntu1_amd64.deb ... 194s Unpacking libatomic1:amd64 (14.2.0-9ubuntu1) over (14.2.0-8ubuntu1) ... 194s Preparing to unpack .../gcc-14-base_14.2.0-9ubuntu1_amd64.deb ... 194s Unpacking gcc-14-base:amd64 (14.2.0-9ubuntu1) over (14.2.0-8ubuntu1) ... 194s Setting up gcc-14-base:amd64 (14.2.0-9ubuntu1) ... 194s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 75952 files and directories currently installed.) 194s Preparing to unpack .../libstdc++6_14.2.0-9ubuntu1_amd64.deb ... 194s Unpacking libstdc++6:amd64 (14.2.0-9ubuntu1) over (14.2.0-8ubuntu1) ... 194s Setting up libstdc++6:amd64 (14.2.0-9ubuntu1) ... 194s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 75952 files and directories currently installed.) 194s Preparing to unpack .../libgcc-s1_14.2.0-9ubuntu1_amd64.deb ... 194s Unpacking libgcc-s1:amd64 (14.2.0-9ubuntu1) over (14.2.0-8ubuntu1) ... 194s Setting up libgcc-s1:amd64 (14.2.0-9ubuntu1) ... 194s Setting up libatomic1:amd64 (14.2.0-9ubuntu1) ... 194s Processing triggers for libc-bin (2.40-1ubuntu3) ... 194s Reading package lists... 194s Building dependency tree... 194s Reading state information... 195s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 195s autopkgtest [09:37:32]: upgrading testbed (apt dist-upgrade and autopurge) 195s Reading package lists... 195s Building dependency tree... 195s Reading state information... 195s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 195s Starting 2 pkgProblemResolver with broken count: 0 195s Done 196s Entering ResolveByKeep 196s 196s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 196s Reading package lists... 196s Building dependency tree... 196s Reading state information... 196s Starting pkgProblemResolver with broken count: 0 196s Starting 2 pkgProblemResolver with broken count: 0 196s Done 197s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 199s Reading package lists... 199s Building dependency tree... 199s Reading state information... 200s Starting pkgProblemResolver with broken count: 1 200s Starting 2 pkgProblemResolver with broken count: 1 200s Investigating (0) libopenmpi40:amd64 < none -> 5.0.6-3 @un puN Ib > 200s Broken libopenmpi40:amd64 Breaks on libopenmpi3:amd64 < 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:amd64 -1 as a solution to libopenmpi40:amd64 4 200s Broken libopenmpi40:amd64 Breaks on libopenmpi3t64:amd64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 200s Considering libopenmpi3t64:amd64 -1 as a solution to libopenmpi40:amd64 4 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: 200s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 200s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 200s E: Unable to correct problems, you have held broken packages. 200s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed 200s 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:amd64 < none -> 5.0.6-3 @un puN Ib > 200s Broken libopenmpi40:amd64 Breaks on libopenmpi3:amd64 < 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:amd64 -1 as a solution to libopenmpi40:amd64 4 200s Broken libopenmpi40:amd64 Breaks on libopenmpi3t64:amd64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 200s Considering libopenmpi3t64:amd64 -1 as a solution to libopenmpi40:amd64 4 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 command1 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]: @@@@@@@@@@@@@@@@@@@@ summary 201s crack 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 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 ellipse 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 flow 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 friction 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 hugo 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 command1 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. 212s nova [W] Skipping flock for amd64 212s Creating nova instance adt-plucky-amd64-lammps-20241203-093417-juju-7f2275-prod-proposed-migration-environment-15-222d1a13-c6ad-49b9-8918-1ea03412431e from image adt/ubuntu-plucky-amd64-server-20241203.img (UUID 9e8e99d5-3366-42e6-8f42-63b527e5abcc)... 212s nova [W] Skipping flock for amd64 212s Creating nova instance adt-plucky-amd64-lammps-20241203-093417-juju-7f2275-prod-proposed-migration-environment-15-222d1a13-c6ad-49b9-8918-1ea03412431e from image adt/ubuntu-plucky-amd64-server-20241203.img (UUID 9e8e99d5-3366-42e6-8f42-63b527e5abcc)...