0s autopkgtest [03:29:10]: starting date and time: 2026-01-24 03:29:10+0000 0s autopkgtest [03:29:10]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [03:29:10]: host juju-7f2275-prod-proposed-migration-environment-15; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.swxdwajw/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:underscore --apt-upgrade lammps --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 '--env=ADT_TEST_TRIGGERS=underscore/1.13.7~dfsg+~1.13.0-5' -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest-cpu2-ram4-disk20-ppc64el --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-15@sto01-ppc64el-23.secgroup --name adt-resolute-ppc64el-lammps-20260124-032910-juju-7f2275-prod-proposed-migration-environment-15-a39ab044-94a5-49ff-8b56-9b76bf255e30 --image adt/ubuntu-resolute-ppc64el-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-15 --net-id=net_prod-autopkgtest-workers-ppc64el -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 4s Creating nova instance adt-resolute-ppc64el-lammps-20260124-032910-juju-7f2275-prod-proposed-migration-environment-15-a39ab044-94a5-49ff-8b56-9b76bf255e30 from image adt/ubuntu-resolute-ppc64el-server-20260123.img (UUID 3dff1a46-d1c8-44ff-849b-7d35415debc1)... 68s autopkgtest [03:30:18]: testbed dpkg architecture: ppc64el 68s autopkgtest [03:30:18]: testbed apt version: 3.1.13 68s autopkgtest [03:30:18]: @@@@@@@@@@@@@@@@@@@@ test bed setup 69s autopkgtest [03:30:19]: testbed release detected to be: None 69s autopkgtest [03:30:19]: updating testbed package index (apt update) 70s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 70s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 70s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 70s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 70s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [2820 B] 70s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [24.3 kB] 70s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [94.5 kB] 70s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [1031 kB] 70s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el Packages [107 kB] 70s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/universe ppc64el Packages [872 kB] 70s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse ppc64el Packages [9920 B] 70s Fetched 2266 kB in 1s (2706 kB/s) 71s Reading package lists... 72s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 72s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 72s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 72s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 73s Reading package lists... 73s Reading package lists... 73s Building dependency tree... 73s Reading state information... 73s Calculating upgrade... 73s The following packages will be upgraded: 73s cloud-initramfs-copymods cloud-initramfs-dyn-netconf libgpg-error-l10n 73s libgpg-error0 liblzo2-2 libplymouth5 libtasn1-6 plymouth 73s plymouth-theme-ubuntu-text python3-jaraco.context 73s 10 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 73s Need to get 632 kB of archives. 73s After this operation, 10.2 kB disk space will be freed. 73s Get:1 http://ftpmaster.internal/ubuntu resolute/main ppc64el libgpg-error-l10n all 1.58-1build1 [9192 B] 73s Get:2 http://ftpmaster.internal/ubuntu resolute/main ppc64el libgpg-error0 ppc64el 1.58-1build1 [106 kB] 73s Get:3 http://ftpmaster.internal/ubuntu resolute/main ppc64el libtasn1-6 ppc64el 4.21.0-2 [58.0 kB] 73s Get:4 http://ftpmaster.internal/ubuntu resolute/main ppc64el libplymouth5 ppc64el 24.004.60+git20250831.4a3c171d-0ubuntu5 [174 kB] 73s Get:5 http://ftpmaster.internal/ubuntu resolute/main ppc64el plymouth-theme-ubuntu-text ppc64el 24.004.60+git20250831.4a3c171d-0ubuntu5 [11.2 kB] 73s Get:6 http://ftpmaster.internal/ubuntu resolute/main ppc64el plymouth ppc64el 24.004.60+git20250831.4a3c171d-0ubuntu5 [156 kB] 73s Get:7 http://ftpmaster.internal/ubuntu resolute/main ppc64el liblzo2-2 ppc64el 2.10-3build2 [97.2 kB] 73s Get:8 http://ftpmaster.internal/ubuntu resolute/main ppc64el python3-jaraco.context all 6.0.1-2 [8198 B] 73s Get:9 http://ftpmaster.internal/ubuntu resolute/main ppc64el cloud-initramfs-copymods all 0.50 [4528 B] 73s Get:10 http://ftpmaster.internal/ubuntu resolute/main ppc64el cloud-initramfs-dyn-netconf all 0.50 [6514 B] 74s dpkg-preconfigure: unable to re-open stdin: No such file or directory 74s Fetched 632 kB in 0s (21.8 MB/s) 74s (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 ... 120821 files and directories currently installed.) 74s Preparing to unpack .../0-libgpg-error-l10n_1.58-1build1_all.deb ... 74s Unpacking libgpg-error-l10n (1.58-1build1) over (1.58-1) ... 74s Preparing to unpack .../1-libgpg-error0_1.58-1build1_ppc64el.deb ... 75s Unpacking libgpg-error0:ppc64el (1.58-1build1) over (1.58-1) ... 75s Preparing to unpack .../2-libtasn1-6_4.21.0-2_ppc64el.deb ... 75s Unpacking libtasn1-6:ppc64el (4.21.0-2) over (4.20.0-2ubuntu1) ... 75s Preparing to unpack .../3-libplymouth5_24.004.60+git20250831.4a3c171d-0ubuntu5_ppc64el.deb ... 75s Unpacking libplymouth5:ppc64el (24.004.60+git20250831.4a3c171d-0ubuntu5) over (24.004.60+git20250831.4a3c171d-0ubuntu4) ... 75s Preparing to unpack .../4-plymouth-theme-ubuntu-text_24.004.60+git20250831.4a3c171d-0ubuntu5_ppc64el.deb ... 75s Unpacking plymouth-theme-ubuntu-text (24.004.60+git20250831.4a3c171d-0ubuntu5) over (24.004.60+git20250831.4a3c171d-0ubuntu4) ... 75s Preparing to unpack .../5-plymouth_24.004.60+git20250831.4a3c171d-0ubuntu5_ppc64el.deb ... 76s Unpacking plymouth (24.004.60+git20250831.4a3c171d-0ubuntu5) over (24.004.60+git20250831.4a3c171d-0ubuntu4) ... 76s Preparing to unpack .../6-liblzo2-2_2.10-3build2_ppc64el.deb ... 76s Unpacking liblzo2-2:ppc64el (2.10-3build2) over (2.10-3build1) ... 76s Preparing to unpack .../7-python3-jaraco.context_6.0.1-2_all.deb ... 76s Unpacking python3-jaraco.context (6.0.1-2) over (6.0.1-1build1) ... 76s Preparing to unpack .../8-cloud-initramfs-copymods_0.50_all.deb ... 76s Unpacking cloud-initramfs-copymods (0.50) over (0.49build1) ... 77s Preparing to unpack .../9-cloud-initramfs-dyn-netconf_0.50_all.deb ... 77s Unpacking cloud-initramfs-dyn-netconf (0.50) over (0.49build1) ... 77s Setting up libgpg-error0:ppc64el (1.58-1build1) ... 77s Setting up python3-jaraco.context (6.0.1-2) ... 77s Setting up liblzo2-2:ppc64el (2.10-3build2) ... 77s Setting up cloud-initramfs-copymods (0.50) ... 77s Setting up libplymouth5:ppc64el (24.004.60+git20250831.4a3c171d-0ubuntu5) ... 77s Setting up cloud-initramfs-dyn-netconf (0.50) ... 77s Setting up libtasn1-6:ppc64el (4.21.0-2) ... 77s Setting up libgpg-error-l10n (1.58-1build1) ... 77s Setting up plymouth (24.004.60+git20250831.4a3c171d-0ubuntu5) ... 77s update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults 77s update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults 78s Processing triggers for initramfs-tools (0.150ubuntu7) ... 78s update-initramfs: Generating /boot/initrd.img-6.18.0-9-generic 88s Processing triggers for libc-bin (2.42-2ubuntu4) ... 89s Processing triggers for man-db (2.13.1-1) ... 91s Setting up plymouth-theme-ubuntu-text (24.004.60+git20250831.4a3c171d-0ubuntu5) ... 91s Processing triggers for initramfs-tools (0.150ubuntu7) ... 91s update-initramfs: Generating /boot/initrd.img-6.18.0-9-generic 97s autopkgtest [03:30:47]: upgrading testbed (apt dist-upgrade and autopurge) 97s Reading package lists... 97s Building dependency tree... 97s Reading state information... 97s Calculating upgrade... 97s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 97s Reading package lists... 97s Building dependency tree... 97s Reading state information... 97s Solving dependencies... 98s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 98s autopkgtest [03:30:48]: rebooting testbed after setup commands that affected boot 135s autopkgtest [03:31:25]: testbed running kernel: Linux 6.18.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 12 16:45:54 UTC 2026 138s autopkgtest [03:31:28]: @@@@@@@@@@@@@@@@@@@@ apt-source lammps 209s Get:1 http://ftpmaster.internal/ubuntu resolute/universe lammps 20251210+dfsg-1 (dsc) [3310 B] 209s Get:2 http://ftpmaster.internal/ubuntu resolute/universe lammps 20251210+dfsg-1 (tar) [133 MB] 209s Get:3 http://ftpmaster.internal/ubuntu resolute/universe lammps 20251210+dfsg-1 (diff) [16.0 kB] 209s gpgv: Signature made Thu Jan 1 15:43:35 2026 UTC 209s gpgv: using RSA key 23C9A93E585819E9126D0A36573EF1E4BD5A01FA 209s gpgv: issuer "dparsons@debian.org" 209s gpgv: Can't check signature: No public key 209s dpkg-source: warning: cannot verify inline signature for ./lammps_20251210+dfsg-1.dsc: no acceptable signature found 216s autopkgtest [03:32:46]: testing package lammps version 20251210+dfsg-1 217s autopkgtest [03:32:47]: build not needed 235s autopkgtest [03:33:05]: test crack: preparing testbed 235s Reading package lists... 235s Building dependency tree... 235s Reading state information... 235s Solving dependencies... 235s Some packages could not be installed. This may mean that you have 235s requested an impossible situation or if you are using the unstable 235s distribution that some required packages have not yet been created 235s or been moved out of Incoming. 235s The following information may help to resolve the situation: 235s 235s The following packages have unmet dependencies: 235s satisfy:command-line : Depends: lammps but it is not going to be installed 235s E: Unable to satisfy dependencies. Reached two conflicting assignments: 235s 1. libamdhip64-6:ppc64el is selected for install because: 235s 1. satisfy:command-line:ppc64el=1 is selected for install 235s 2. satisfy:command-line:ppc64el Depends lammps 235s 3. lammps:ppc64el Depends libopenmpi40 (>= 5.0.8) 235s 4. libopenmpi40:ppc64el Depends libucx0 235s 5. libucx0:ppc64el Depends libamdhip64-6 (>= 6.1.5) 235s 2. libamdhip64-6:ppc64el Depends libamd-comgr3 235s but none of the choices are installable: 235s [no choices] 235s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 235s Reading package lists... 235s Building dependency tree... 235s Reading state information... 236s Solving dependencies... 236s Some packages could not be installed. This may mean that you have 236s requested an impossible situation or if you are using the unstable 236s distribution that some required packages have not yet been created 236s or been moved out of Incoming. 236s The following information may help to resolve the situation: 236s 236s The following packages have unmet dependencies: 236s satisfy:command-line : Depends: lammps but it is not going to be installed 236s E: Unable to satisfy dependencies. Reached two conflicting assignments: 236s 1. libamdhip64-6:ppc64el is selected for install because: 236s 1. satisfy:command-line:ppc64el=1 is selected for install 236s 2. satisfy:command-line:ppc64el Depends lammps 236s 3. lammps:ppc64el Depends libopenmpi40 (>= 5.0.8) 236s 4. libopenmpi40:ppc64el Depends libucx0 236s 5. libucx0:ppc64el Depends libamdhip64-6 (>= 6.1.5) 236s 2. libamdhip64-6:ppc64el Depends libamd-comgr3 236s but none of the choices are installable: 236s [no choices] 236s crack FAIL badpkg 236s blame: lammps 236s 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. 236s autopkgtest [03:33:06]: test dipole: preparing testbed 236s Reading package lists... 236s Building dependency tree... 236s Reading state information... 236s Solving dependencies... 236s Some packages could not be installed. This may mean that you have 236s requested an impossible situation or if you are using the unstable 236s distribution that some required packages have not yet been created 236s or been moved out of Incoming. 236s The following information may help to resolve the situation: 236s 236s The following packages have unmet dependencies: 236s satisfy:command-line : Depends: lammps but it is not going to be installed 236s E: Unable to satisfy dependencies. Reached two conflicting assignments: 236s 1. libamdhip64-6:ppc64el is selected for install because: 236s 1. satisfy:command-line:ppc64el=1 is selected for install 236s 2. satisfy:command-line:ppc64el Depends lammps 236s 3. lammps:ppc64el Depends libopenmpi40 (>= 5.0.8) 236s 4. libopenmpi40:ppc64el Depends libucx0 236s 5. libucx0:ppc64el Depends libamdhip64-6 (>= 6.1.5) 236s 2. libamdhip64-6:ppc64el Depends libamd-comgr3 236s but none of the choices are installable: 236s [no choices] 236s dipole FAIL badpkg 236s autopkgtest [03:33:06]: test ellipse: preparing testbed 236s blame: lammps 236s 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. 236s Reading package lists... 236s Building dependency tree... 236s Reading state information... 236s Solving dependencies... 236s Some packages could not be installed. This may mean that you have 236s requested an impossible situation or if you are using the unstable 236s distribution that some required packages have not yet been created 236s or been moved out of Incoming. 236s The following information may help to resolve the situation: 236s 236s The following packages have unmet dependencies: 237s satisfy:command-line : Depends: lammps but it is not going to be installed 237s E: Unable to satisfy dependencies. Reached two conflicting assignments: 237s 1. libamdhip64-6:ppc64el is selected for install because: 237s 1. satisfy:command-line:ppc64el=1 is selected for install 237s 2. satisfy:command-line:ppc64el Depends lammps 237s 3. lammps:ppc64el Depends libopenmpi40 (>= 5.0.8) 237s 4. libopenmpi40:ppc64el Depends libucx0 237s 5. libucx0:ppc64el Depends libamdhip64-6 (>= 6.1.5) 237s 2. libamdhip64-6:ppc64el Depends libamd-comgr3 237s but none of the choices are installable: 237s [no choices] 237s ellipse FAIL badpkg 237s blame: lammps 237s 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. 237s autopkgtest [03:33:07]: test flow: preparing testbed 237s Reading package lists... 237s Building dependency tree... 237s Reading state information... 237s Solving dependencies... 237s Some packages could not be installed. This may mean that you have 237s requested an impossible situation or if you are using the unstable 237s distribution that some required packages have not yet been created 237s or been moved out of Incoming. 237s The following information may help to resolve the situation: 237s 237s The following packages have unmet dependencies: 237s satisfy:command-line : Depends: lammps but it is not going to be installed 237s E: Unable to satisfy dependencies. Reached two conflicting assignments: 237s 1. libamdhip64-6:ppc64el is selected for install because: 237s 1. satisfy:command-line:ppc64el=1 is selected for install 237s 2. satisfy:command-line:ppc64el Depends lammps 237s 3. lammps:ppc64el Depends libopenmpi40 (>= 5.0.8) 237s 4. libopenmpi40:ppc64el Depends libucx0 237s 5. libucx0:ppc64el Depends libamdhip64-6 (>= 6.1.5) 237s 2. libamdhip64-6:ppc64el Depends libamd-comgr3 237s but none of the choices are installable: 237s [no choices] 237s flow FAIL badpkg 237s blame: lammps 237s 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. 237s autopkgtest [03:33:07]: test friction: preparing testbed 237s Reading package lists... 237s Building dependency tree... 237s Reading state information... 237s Solving dependencies... 237s Some packages could not be installed. This may mean that you have 237s requested an impossible situation or if you are using the unstable 237s distribution that some required packages have not yet been created 237s or been moved out of Incoming. 237s The following information may help to resolve the situation: 237s 237s The following packages have unmet dependencies: 238s satisfy:command-line : Depends: lammps but it is not going to be installed 238s E: Unable to satisfy dependencies. Reached two conflicting assignments: 238s 1. libamdhip64-6:ppc64el is selected for install because: 238s 1. satisfy:command-line:ppc64el=1 is selected for install 238s 2. satisfy:command-line:ppc64el Depends lammps 238s 3. lammps:ppc64el Depends libopenmpi40 (>= 5.0.8) 238s 4. libopenmpi40:ppc64el Depends libucx0 238s 5. libucx0:ppc64el Depends libamdhip64-6 (>= 6.1.5) 238s 2. libamdhip64-6:ppc64el Depends libamd-comgr3 238s but none of the choices are installable: 238s [no choices] 238s friction FAIL badpkg 238s blame: lammps 238s 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. 238s autopkgtest [03:33:08]: test hugo: preparing testbed 238s Reading package lists... 238s Building dependency tree... 238s Reading state information... 238s Solving dependencies... 238s Some packages could not be installed. This may mean that you have 238s requested an impossible situation or if you are using the unstable 238s distribution that some required packages have not yet been created 238s or been moved out of Incoming. 238s The following information may help to resolve the situation: 238s 238s The following packages have unmet dependencies: 238s satisfy:command-line : Depends: lammps but it is not going to be installed 238s E: Unable to satisfy dependencies. Reached two conflicting assignments: 238s 1. libamdhip64-6:ppc64el is selected for install because: 238s 1. satisfy:command-line:ppc64el=1 is selected for install 238s 2. satisfy:command-line:ppc64el Depends lammps 238s 3. lammps:ppc64el Depends libopenmpi40 (>= 5.0.8) 238s 4. libopenmpi40:ppc64el Depends libucx0 238s 5. libucx0:ppc64el Depends libamdhip64-6 (>= 6.1.5) 238s 2. libamdhip64-6:ppc64el Depends libamd-comgr3 238s but none of the choices are installable: 238s [no choices] 238s autopkgtest [03:33:08]: test command1: preparing testbed 238s hugo FAIL badpkg 238s blame: lammps 238s 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. 257s Creating nova instance adt-resolute-ppc64el-lammps-20260124-032910-juju-7f2275-prod-proposed-migration-environment-15-a39ab044-94a5-49ff-8b56-9b76bf255e30 from image adt/ubuntu-resolute-ppc64el-server-20260123.img (UUID 3dff1a46-d1c8-44ff-849b-7d35415debc1)... 307s autopkgtest [03:34:17]: testbed dpkg architecture: ppc64el 307s autopkgtest [03:34:17]: testbed apt version: 3.1.13 307s autopkgtest [03:34:17]: @@@@@@@@@@@@@@@@@@@@ test bed setup 307s autopkgtest [03:34:17]: testbed release detected to be: resolute 308s autopkgtest [03:34:18]: updating testbed package index (apt update) 308s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 308s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 308s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 308s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 308s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [1058 kB] 308s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [94.5 kB] 308s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [24.3 kB] 309s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [2820 B] 309s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el Packages [107 kB] 309s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/universe ppc64el Packages [881 kB] 309s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse ppc64el Packages [9920 B] 309s Fetched 2301 kB in 1s (4279 kB/s) 310s Reading package lists... 310s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 310s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 310s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 310s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 311s Reading package lists... 311s Reading package lists... 311s Building dependency tree... 311s Reading state information... 311s Calculating upgrade... 312s The following packages will be upgraded: 312s cloud-initramfs-copymods cloud-initramfs-dyn-netconf libgpg-error-l10n 312s libgpg-error0 liblzo2-2 libplymouth5 libtasn1-6 plymouth 312s plymouth-theme-ubuntu-text python3-jaraco.context 312s 10 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 312s Need to get 632 kB of archives. 312s After this operation, 10.2 kB disk space will be freed. 312s Get:1 http://ftpmaster.internal/ubuntu resolute/main ppc64el libgpg-error-l10n all 1.58-1build1 [9192 B] 312s Get:2 http://ftpmaster.internal/ubuntu resolute/main ppc64el libgpg-error0 ppc64el 1.58-1build1 [106 kB] 312s Get:3 http://ftpmaster.internal/ubuntu resolute/main ppc64el libtasn1-6 ppc64el 4.21.0-2 [58.0 kB] 312s Get:4 http://ftpmaster.internal/ubuntu resolute/main ppc64el libplymouth5 ppc64el 24.004.60+git20250831.4a3c171d-0ubuntu5 [174 kB] 312s Get:5 http://ftpmaster.internal/ubuntu resolute/main ppc64el plymouth-theme-ubuntu-text ppc64el 24.004.60+git20250831.4a3c171d-0ubuntu5 [11.2 kB] 312s Get:6 http://ftpmaster.internal/ubuntu resolute/main ppc64el plymouth ppc64el 24.004.60+git20250831.4a3c171d-0ubuntu5 [156 kB] 312s Get:7 http://ftpmaster.internal/ubuntu resolute/main ppc64el liblzo2-2 ppc64el 2.10-3build2 [97.2 kB] 312s Get:8 http://ftpmaster.internal/ubuntu resolute/main ppc64el python3-jaraco.context all 6.0.1-2 [8198 B] 312s Get:9 http://ftpmaster.internal/ubuntu resolute/main ppc64el cloud-initramfs-copymods all 0.50 [4528 B] 312s Get:10 http://ftpmaster.internal/ubuntu resolute/main ppc64el cloud-initramfs-dyn-netconf all 0.50 [6514 B] 312s dpkg-preconfigure: unable to re-open stdin: No such file or directory 312s Fetched 632 kB in 0s (19.3 MB/s) 312s (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 ... 120821 files and directories currently installed.) 312s Preparing to unpack .../0-libgpg-error-l10n_1.58-1build1_all.deb ... 312s Unpacking libgpg-error-l10n (1.58-1build1) over (1.58-1) ... 312s Preparing to unpack .../1-libgpg-error0_1.58-1build1_ppc64el.deb ... 312s Unpacking libgpg-error0:ppc64el (1.58-1build1) over (1.58-1) ... 312s Preparing to unpack .../2-libtasn1-6_4.21.0-2_ppc64el.deb ... 312s Unpacking libtasn1-6:ppc64el (4.21.0-2) over (4.20.0-2ubuntu1) ... 313s Preparing to unpack .../3-libplymouth5_24.004.60+git20250831.4a3c171d-0ubuntu5_ppc64el.deb ... 313s Unpacking libplymouth5:ppc64el (24.004.60+git20250831.4a3c171d-0ubuntu5) over (24.004.60+git20250831.4a3c171d-0ubuntu4) ... 313s Preparing to unpack .../4-plymouth-theme-ubuntu-text_24.004.60+git20250831.4a3c171d-0ubuntu5_ppc64el.deb ... 313s Unpacking plymouth-theme-ubuntu-text (24.004.60+git20250831.4a3c171d-0ubuntu5) over (24.004.60+git20250831.4a3c171d-0ubuntu4) ... 313s Preparing to unpack .../5-plymouth_24.004.60+git20250831.4a3c171d-0ubuntu5_ppc64el.deb ... 313s Unpacking plymouth (24.004.60+git20250831.4a3c171d-0ubuntu5) over (24.004.60+git20250831.4a3c171d-0ubuntu4) ... 313s Preparing to unpack .../6-liblzo2-2_2.10-3build2_ppc64el.deb ... 313s Unpacking liblzo2-2:ppc64el (2.10-3build2) over (2.10-3build1) ... 313s Preparing to unpack .../7-python3-jaraco.context_6.0.1-2_all.deb ... 313s Unpacking python3-jaraco.context (6.0.1-2) over (6.0.1-1build1) ... 313s Preparing to unpack .../8-cloud-initramfs-copymods_0.50_all.deb ... 313s Unpacking cloud-initramfs-copymods (0.50) over (0.49build1) ... 313s Preparing to unpack .../9-cloud-initramfs-dyn-netconf_0.50_all.deb ... 313s Unpacking cloud-initramfs-dyn-netconf (0.50) over (0.49build1) ... 314s Setting up libgpg-error0:ppc64el (1.58-1build1) ... 314s Setting up python3-jaraco.context (6.0.1-2) ... 314s Setting up liblzo2-2:ppc64el (2.10-3build2) ... 314s Setting up cloud-initramfs-copymods (0.50) ... 314s Setting up libplymouth5:ppc64el (24.004.60+git20250831.4a3c171d-0ubuntu5) ... 314s Setting up cloud-initramfs-dyn-netconf (0.50) ... 314s Setting up libtasn1-6:ppc64el (4.21.0-2) ... 314s Setting up libgpg-error-l10n (1.58-1build1) ... 314s Setting up plymouth (24.004.60+git20250831.4a3c171d-0ubuntu5) ... 314s update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults 314s update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults 314s Processing triggers for initramfs-tools (0.150ubuntu7) ... 314s update-initramfs: Generating /boot/initrd.img-6.18.0-9-generic 322s Processing triggers for libc-bin (2.42-2ubuntu4) ... 322s Processing triggers for man-db (2.13.1-1) ... 324s Setting up plymouth-theme-ubuntu-text (24.004.60+git20250831.4a3c171d-0ubuntu5) ... 324s Processing triggers for initramfs-tools (0.150ubuntu7) ... 324s update-initramfs: Generating /boot/initrd.img-6.18.0-9-generic 330s autopkgtest [03:34:40]: upgrading testbed (apt dist-upgrade and autopurge) 330s Reading package lists... 330s Building dependency tree... 330s Reading state information... 330s Calculating upgrade... 331s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 331s Reading package lists... 331s Building dependency tree... 331s Reading state information... 331s Solving dependencies... 331s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 331s autopkgtest [03:34:41]: rebooting testbed after setup commands that affected boot 374s Reading package lists... 374s Building dependency tree... 374s Reading state information... 374s Solving dependencies... 374s Some packages could not be installed. This may mean that you have 374s requested an impossible situation or if you are using the unstable 374s distribution that some required packages have not yet been created 374s or been moved out of Incoming. 374s The following information may help to resolve the situation: 374s 374s The following packages have unmet dependencies: 374s satisfy:command-line : Depends: python3-lammps but it is not going to be installed 374s E: Unable to satisfy dependencies. Reached two conflicting assignments: 374s 1. libamdhip64-6:ppc64el is selected for install because: 374s 1. satisfy:command-line:ppc64el=1 is selected for install 374s 2. satisfy:command-line:ppc64el Depends python3-lammps 374s 3. python3-lammps:ppc64el Depends liblammps-dev 374s 4. liblammps-dev:ppc64el Depends liblammps0t64 (= 20251210+dfsg-1) 374s 5. liblammps0t64:ppc64el Depends libopenmpi40 (>= 5.0.8) 374s 6. libopenmpi40:ppc64el Depends libucx0 374s 7. libucx0:ppc64el Depends libamdhip64-6 (>= 6.1.5) 374s 2. libamdhip64-6:ppc64el Depends libamd-comgr3 374s but none of the choices are installable: 374s [no choices] 374s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 374s Reading package lists... 375s Building dependency tree... 375s Reading state information... 375s Solving dependencies... 375s Some packages could not be installed. This may mean that you have 375s requested an impossible situation or if you are using the unstable 375s distribution that some required packages have not yet been created 375s or been moved out of Incoming. 375s The following information may help to resolve the situation: 375s 375s The following packages have unmet dependencies: 375s satisfy:command-line : Depends: python3-lammps but it is not going to be installed 375s E: Unable to satisfy dependencies. Reached two conflicting assignments: 375s 1. libamdhip64-6:ppc64el is selected for install because: 375s 1. satisfy:command-line:ppc64el=1 is selected for install 375s 2. satisfy:command-line:ppc64el Depends python3-lammps 375s 3. python3-lammps:ppc64el Depends liblammps-dev 375s 4. liblammps-dev:ppc64el Depends liblammps0t64 (= 20251210+dfsg-1) 375s 5. liblammps0t64:ppc64el Depends libopenmpi40 (>= 5.0.8) 375s 6. libopenmpi40:ppc64el Depends libucx0 375s 7. libucx0:ppc64el Depends libamdhip64-6 (>= 6.1.5) 375s 2. libamdhip64-6:ppc64el Depends libamd-comgr3 375s but none of the choices are installable: 375s [no choices] 375s command1 FAIL badpkg 375s blame: lammps 375s 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. 375s autopkgtest [03:35:25]: @@@@@@@@@@@@@@@@@@@@ summary 375s crack FAIL badpkg 375s blame: lammps 375s 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. 375s dipole FAIL badpkg 375s blame: lammps 375s 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. 375s ellipse FAIL badpkg 375s blame: lammps 375s 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. 375s flow FAIL badpkg 375s blame: lammps 375s 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. 375s friction FAIL badpkg 375s blame: lammps 375s 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. 375s hugo FAIL badpkg 375s blame: lammps 375s 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. 375s command1 FAIL badpkg 375s blame: lammps 375s 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.