0s autopkgtest [09:26:55]: starting date and time: 2025-04-14 09:26:55+0000 0s autopkgtest [09:26:55]: git checkout: 9986aa8c Merge branch 'skia/fix_network_interface' into 'ubuntu/production' 0s autopkgtest [09:26:55]: host juju-7f2275-prod-proposed-migration-environment-23; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.v8qvv_px/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:llvm-toolchain-snapshot --apt-upgrade llvm-toolchain-snapshot --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 '--env=ADT_TEST_TRIGGERS=llvm-toolchain-snapshot/1:21~++20250322080030+20b5728b7b1c-1~exp1ubuntu1' -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest-ppc64el --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-23@bos03-ppc64el-3.secgroup --name adt-plucky-ppc64el-llvm-toolchain-snapshot-20250414-092655-juju-7f2275-prod-proposed-migration-environment-23-16703ba3-fd6f-4373-8ce6-d3c5d2f653f8 --image adt/ubuntu-plucky-ppc64el-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-23 --net-id=net_prod-proposed-migration-ppc64el -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 90s autopkgtest [09:28:25]: testbed dpkg architecture: ppc64el 90s autopkgtest [09:28:25]: testbed apt version: 3.0.0 90s autopkgtest [09:28:25]: @@@@@@@@@@@@@@@@@@@@ test bed setup 90s autopkgtest [09:28:25]: testbed release detected to be: None 91s autopkgtest [09:28:26]: updating testbed package index (apt update) 91s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [265 kB] 92s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 92s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 92s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 92s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [5192 B] 92s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [204 kB] 92s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [9948 B] 92s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/main ppc64el Packages [3476 B] 92s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main ppc64el c-n-f Metadata [288 B] 92s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted ppc64el c-n-f Metadata [120 B] 92s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe ppc64el Packages [120 kB] 92s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/universe ppc64el c-n-f Metadata [8688 B] 92s Get:13 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse ppc64el Packages [2008 B] 92s Get:14 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse ppc64el c-n-f Metadata [172 B] 93s Fetched 619 kB in 1s (797 kB/s) 94s Reading package lists... 95s autopkgtest [09:28:30]: upgrading testbed (apt dist-upgrade and autopurge) 95s Reading package lists... 95s Building dependency tree... 95s Reading state information... 96s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 96s Starting 2 pkgProblemResolver with broken count: 0 96s Done 96s Entering ResolveByKeep 96s 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 Starting pkgProblemResolver with broken count: 0 97s Starting 2 pkgProblemResolver with broken count: 0 97s Done 97s Solving dependencies... 98s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 100s autopkgtest [09:28:35]: testbed running kernel: Linux 6.14.0-15-generic #15-Ubuntu SMP Sun Apr 6 14:52:42 UTC 2025 100s autopkgtest [09:28:35]: @@@@@@@@@@@@@@@@@@@@ apt-source llvm-toolchain-snapshot 123s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed/universe llvm-toolchain-snapshot 1:21~++20250322080030+20b5728b7b1c-1~exp1ubuntu1 (dsc) [8684 B] 123s Get:2 http://ftpmaster.internal/ubuntu plucky-proposed/universe llvm-toolchain-snapshot 1:21~++20250322080030+20b5728b7b1c-1~exp1ubuntu1 (tar) [175 MB] 123s Get:3 http://ftpmaster.internal/ubuntu plucky-proposed/universe llvm-toolchain-snapshot 1:21~++20250322080030+20b5728b7b1c-1~exp1ubuntu1 (diff) [154 kB] 124s gpgv: Signature made Thu Apr 10 07:42:08 2025 UTC 124s gpgv: using RSA key 568BF22A66337CBFC9A6B9B72C83DBC8E9BD0E37 124s gpgv: Can't check signature: No public key 124s dpkg-source: warning: cannot verify inline signature for ./llvm-toolchain-snapshot_21~++20250322080030+20b5728b7b1c-1~exp1ubuntu1.dsc: no acceptable signature found 145s autopkgtest [09:29:20]: testing package llvm-toolchain-snapshot version 1:21~++20250322080030+20b5728b7b1c-1~exp1ubuntu1 149s command1 SKIP Test lists explicitly supported architectures, but the current architecture ppc64el isn't listed. 151s integration-test-suite-test SKIP Test lists explicitly supported architectures, but the current architecture ppc64el isn't listed. 160s autopkgtest [09:29:35]: build not needed 292s command1 SKIP Test lists explicitly supported architectures, but the current architecture ppc64el isn't listed. 294s integration-test-suite-test SKIP Test lists explicitly supported architectures, but the current architecture ppc64el isn't listed. 304s autopkgtest [09:31:59]: test cmake-llvm-test: preparing testbed 304s Reading package lists... 304s Building dependency tree... 304s Reading state information... 304s Starting pkgProblemResolver with broken count: 1 304s Starting 2 pkgProblemResolver with broken count: 1 304s Investigating (0) satisfy:command-line:ppc64el < none -> 1 @un puN Ib > 304s Broken satisfy:command-line:ppc64el Depends on gcc:ppc64el < none | 4:14.2.0-1ubuntu1 @un uH > 304s Considering gcc:ppc64el 2 as a solution to satisfy:command-line:ppc64el 9998 304s Re-Instated libisl23:ppc64el 304s Re-Instated libmpc3:ppc64el 304s Re-Instated cpp-14-powerpc64le-linux-gnu:ppc64el 304s Re-Instated cpp-14:ppc64el 304s Re-Instated cpp-powerpc64le-linux-gnu:ppc64el 304s Re-Instated cpp:ppc64el 304s Re-Instated libcc1-0:ppc64el 304s Re-Instated libgomp1:ppc64el 304s Re-Instated libitm1:ppc64el 304s Re-Instated libasan8:ppc64el 304s Re-Instated liblsan0:ppc64el 304s Re-Instated libtsan2:ppc64el 304s Re-Instated libubsan1:ppc64el 304s Re-Instated libquadmath0:ppc64el 304s Re-Instated libgcc-14-dev:ppc64el 304s Re-Instated gcc-14-powerpc64le-linux-gnu:ppc64el 304s Re-Instated gcc-14:ppc64el 304s Re-Instated gcc-powerpc64le-linux-gnu:ppc64el 304s Re-Instated gcc:ppc64el 304s Broken satisfy:command-line:ppc64el Depends on build-essential:ppc64el < none | 12.12ubuntu1 @un uH > 304s Considering build-essential:ppc64el 2 as a solution to satisfy:command-line:ppc64el 9998 304s Re-Instated libstdc++-14-dev:ppc64el 304s Re-Instated g++-14-powerpc64le-linux-gnu:ppc64el 304s Re-Instated g++-14:ppc64el 304s Re-Instated g++-powerpc64le-linux-gnu:ppc64el 304s Re-Instated g++:ppc64el 304s Re-Instated build-essential:ppc64el 304s Broken satisfy:command-line:ppc64el Depends on cmake:ppc64el < none | 3.31.6-1ubuntu1 @un uH > 304s Considering cmake:ppc64el 1 as a solution to satisfy:command-line:ppc64el 9998 304s Re-Instated cmake-data:ppc64el 304s Re-Instated libjsoncpp26:ppc64el 304s Re-Instated librhash1:ppc64el 304s Re-Instated cmake:ppc64el 304s Broken satisfy:command-line:ppc64el Depends on llvm-21-dev:ppc64el < none @un H > 304s Done 304s Some packages could not be installed. This may mean that you have 304s requested an impossible situation or if you are using the unstable 304s distribution that some required packages have not yet been created 304s or been moved out of Incoming. 304s The following information may help to resolve the situation: 304s 304s The following packages have unmet dependencies: 304s satisfy:command-line : Depends: llvm-21-dev but it is not installable 304s E: Unable to correct problems, you have held broken packages. 304s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed 305s Reading package lists... 305s Building dependency tree... 305s Reading state information... 305s Starting pkgProblemResolver with broken count: 1 305s Starting 2 pkgProblemResolver with broken count: 1 305s Investigating (0) satisfy:command-line:ppc64el < none -> 1 @un puN Ib > 305s Broken satisfy:command-line:ppc64el Depends on gcc:ppc64el < none | 4:14.2.0-1ubuntu1 @un uH > 305s Considering gcc:ppc64el 2 as a solution to satisfy:command-line:ppc64el 9998 305s Re-Instated libisl23:ppc64el 305s Re-Instated libmpc3:ppc64el 305s Re-Instated cpp-14-powerpc64le-linux-gnu:ppc64el 305s Re-Instated cpp-14:ppc64el 305s Re-Instated cpp-powerpc64le-linux-gnu:ppc64el 305s Re-Instated cpp:ppc64el 305s Re-Instated libcc1-0:ppc64el 305s Re-Instated libgomp1:ppc64el 305s Re-Instated libitm1:ppc64el 305s Re-Instated libasan8:ppc64el 305s Re-Instated liblsan0:ppc64el 305s Re-Instated libtsan2:ppc64el 305s Re-Instated libubsan1:ppc64el 305s Re-Instated libquadmath0:ppc64el 305s Re-Instated libgcc-14-dev:ppc64el 305s Re-Instated gcc-14-powerpc64le-linux-gnu:ppc64el 305s Re-Instated gcc-14:ppc64el 305s Re-Instated gcc-powerpc64le-linux-gnu:ppc64el 305s Re-Instated gcc:ppc64el 305s Broken satisfy:command-line:ppc64el Depends on build-essential:ppc64el < none | 12.12ubuntu1 @un uH > 305s Considering build-essential:ppc64el 2 as a solution to satisfy:command-line:ppc64el 9998 305s Re-Instated libstdc++-14-dev:ppc64el 305s Re-Instated g++-14-powerpc64le-linux-gnu:ppc64el 305s Re-Instated g++-14:ppc64el 305s Re-Instated g++-powerpc64le-linux-gnu:ppc64el 305s Re-Instated g++:ppc64el 305s Re-Instated build-essential:ppc64el 305s Broken satisfy:command-line:ppc64el Depends on cmake:ppc64el < none | 3.31.6-1ubuntu1 @un uH > 305s Considering cmake:ppc64el 1 as a solution to satisfy:command-line:ppc64el 9998 305s Re-Instated cmake-data:ppc64el 305s Re-Instated libjsoncpp26:ppc64el 305s Re-Instated librhash1:ppc64el 305s Re-Instated cmake:ppc64el 305s Broken satisfy:command-line:ppc64el Depends on llvm-21-dev:ppc64el < none @un H > 305s Done 305s Some packages could not be installed. This may mean that you have 305s requested an impossible situation or if you are using the unstable 305s distribution that some required packages have not yet been created 305s or been moved out of Incoming. 305s The following information may help to resolve the situation: 305s 305s The following packages have unmet dependencies: 305s satisfy:command-line : Depends: llvm-21-dev but it is not installable 305s E: Unable to correct problems, you have held broken packages. 305s cmake-llvm-test FAIL badpkg 305s blame: llvm-toolchain-snapshot 305s 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. 305s autopkgtest [09:32:00]: test cmake-clang-test: preparing testbed 306s Reading package lists... 306s Building dependency tree... 306s Reading state information... 306s Starting pkgProblemResolver with broken count: 1 306s Starting 2 pkgProblemResolver with broken count: 1 306s Investigating (0) satisfy:command-line:ppc64el < none -> 1 @un puN Ib > 306s Broken satisfy:command-line:ppc64el Depends on gcc:ppc64el < none | 4:14.2.0-1ubuntu1 @un uH > 306s Considering gcc:ppc64el 2 as a solution to satisfy:command-line:ppc64el 9998 306s Re-Instated libisl23:ppc64el 306s Re-Instated libmpc3:ppc64el 306s Re-Instated cpp-14-powerpc64le-linux-gnu:ppc64el 306s Re-Instated cpp-14:ppc64el 306s Re-Instated cpp-powerpc64le-linux-gnu:ppc64el 306s Re-Instated cpp:ppc64el 306s Re-Instated libcc1-0:ppc64el 306s Re-Instated libgomp1:ppc64el 306s Re-Instated libitm1:ppc64el 306s Re-Instated libasan8:ppc64el 306s Re-Instated liblsan0:ppc64el 306s Re-Instated libtsan2:ppc64el 306s Re-Instated libubsan1:ppc64el 306s Re-Instated libquadmath0:ppc64el 306s Re-Instated libgcc-14-dev:ppc64el 306s Re-Instated gcc-14-powerpc64le-linux-gnu:ppc64el 306s Re-Instated gcc-14:ppc64el 306s Re-Instated gcc-powerpc64le-linux-gnu:ppc64el 306s Re-Instated gcc:ppc64el 306s Broken satisfy:command-line:ppc64el Depends on build-essential:ppc64el < none | 12.12ubuntu1 @un uH > 306s Considering build-essential:ppc64el 2 as a solution to satisfy:command-line:ppc64el 9998 306s Re-Instated libstdc++-14-dev:ppc64el 306s Re-Instated g++-14-powerpc64le-linux-gnu:ppc64el 306s Re-Instated g++-14:ppc64el 306s Re-Instated g++-powerpc64le-linux-gnu:ppc64el 306s Re-Instated g++:ppc64el 306s Re-Instated build-essential:ppc64el 306s Broken satisfy:command-line:ppc64el Depends on cmake:ppc64el < none | 3.31.6-1ubuntu1 @un uH > 306s Considering cmake:ppc64el 1 as a solution to satisfy:command-line:ppc64el 9998 306s Re-Instated cmake-data:ppc64el 306s Re-Instated libjsoncpp26:ppc64el 306s Re-Instated librhash1:ppc64el 306s Re-Instated cmake:ppc64el 306s Broken satisfy:command-line:ppc64el Depends on llvm-21-dev:ppc64el < none @un H > 306s Broken satisfy:command-line:ppc64el Depends on clang-21:ppc64el < none @un H > 306s Broken satisfy:command-line:ppc64el Depends on libclang-21-dev:ppc64el < none @un H > 306s Done 306s Some packages could not be installed. This may mean that you have 306s requested an impossible situation or if you are using the unstable 306s distribution that some required packages have not yet been created 306s or been moved out of Incoming. 306s The following information may help to resolve the situation: 306s 306s The following packages have unmet dependencies: 306s satisfy:command-line : Depends: llvm-21-dev but it is not installable 306s Depends: clang-21 but it is not installable 306s Depends: libclang-21-dev but it is not installable 306s E: Unable to correct problems, you have held broken packages. 306s cmake-clang-test FAIL badpkg 306s blame: llvm-toolchain-snapshot 306s 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. 306s autopkgtest [09:32:01]: test command2: preparing testbed 391s autopkgtest [09:33:26]: testbed dpkg architecture: ppc64el 392s autopkgtest [09:33:27]: testbed apt version: 3.0.0 392s autopkgtest [09:33:27]: @@@@@@@@@@@@@@@@@@@@ test bed setup 392s autopkgtest [09:33:27]: testbed release detected to be: plucky 393s autopkgtest [09:33:28]: updating testbed package index (apt update) 393s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [265 kB] 393s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 393s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 394s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 394s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [204 kB] 394s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [5192 B] 394s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [9948 B] 394s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/main ppc64el Packages [3476 B] 394s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main ppc64el c-n-f Metadata [288 B] 394s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted ppc64el c-n-f Metadata [120 B] 394s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe ppc64el Packages [120 kB] 394s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/universe ppc64el c-n-f Metadata [8688 B] 394s Get:13 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse ppc64el Packages [2008 B] 394s Get:14 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse ppc64el c-n-f Metadata [172 B] 395s Fetched 619 kB in 1s (783 kB/s) 396s Reading package lists... 397s autopkgtest [09:33:32]: upgrading testbed (apt dist-upgrade and autopurge) 397s Reading package lists... 397s Building dependency tree... 397s Reading state information... 397s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 397s Starting 2 pkgProblemResolver with broken count: 0 397s Done 398s Entering ResolveByKeep 398s 398s Calculating upgrade... 398s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 398s Reading package lists... 398s Building dependency tree... 398s Reading state information... 399s Starting pkgProblemResolver with broken count: 0 399s Starting 2 pkgProblemResolver with broken count: 0 399s Done 399s Solving dependencies... 399s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 402s Reading package lists... 402s Building dependency tree... 402s Reading state information... 402s Starting pkgProblemResolver with broken count: 1 402s Starting 2 pkgProblemResolver with broken count: 1 402s Investigating (0) satisfy:command-line:ppc64el < none -> 1 @un puN Ib > 402s Broken satisfy:command-line:ppc64el Depends on python3-lldb-21:ppc64el < none @un H > 402s Done 402s Some packages could not be installed. This may mean that you have 402s requested an impossible situation or if you are using the unstable 402s distribution that some required packages have not yet been created 402s or been moved out of Incoming. 402s The following information may help to resolve the situation: 402s 402s The following packages have unmet dependencies: 402s satisfy:command-line : Depends: python3-lldb-21 but it is not installable 402s E: Unable to correct problems, you have held broken packages. 402s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed 403s Reading package lists... 403s Building dependency tree... 403s Reading state information... 403s Starting pkgProblemResolver with broken count: 1 403s Starting 2 pkgProblemResolver with broken count: 1 403s Investigating (0) satisfy:command-line:ppc64el < none -> 1 @un puN Ib > 403s Broken satisfy:command-line:ppc64el Depends on python3-lldb-21:ppc64el < none @un H > 403s Done 403s Some packages could not be installed. This may mean that you have 403s requested an impossible situation or if you are using the unstable 403s distribution that some required packages have not yet been created 403s or been moved out of Incoming. 403s The following information may help to resolve the situation: 403s 403s The following packages have unmet dependencies: 403s satisfy:command-line : Depends: python3-lldb-21 but it is not installable 403s E: Unable to correct problems, you have held broken packages. 403s command2 FAIL badpkg 403s blame: llvm-toolchain-snapshot 403s 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. 403s autopkgtest [09:33:38]: test command3: preparing testbed 480s autopkgtest [09:34:55]: testbed dpkg architecture: ppc64el 481s autopkgtest [09:34:56]: testbed apt version: 3.0.0 481s autopkgtest [09:34:56]: @@@@@@@@@@@@@@@@@@@@ test bed setup 481s autopkgtest [09:34:56]: testbed release detected to be: plucky 482s autopkgtest [09:34:57]: updating testbed package index (apt update) 482s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [265 kB] 483s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 483s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 483s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 483s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [5192 B] 483s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [204 kB] 483s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [9948 B] 483s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/main ppc64el Packages [3476 B] 483s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main ppc64el c-n-f Metadata [288 B] 483s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted ppc64el c-n-f Metadata [120 B] 483s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe ppc64el Packages [120 kB] 483s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/universe ppc64el c-n-f Metadata [8688 B] 483s Get:13 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse ppc64el Packages [2008 B] 483s Get:14 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse ppc64el c-n-f Metadata [172 B] 484s Fetched 619 kB in 1s (807 kB/s) 485s Reading package lists... 486s autopkgtest [09:35:01]: upgrading testbed (apt dist-upgrade and autopurge) 486s Reading package lists... 486s Building dependency tree... 486s Reading state information... 486s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 486s Starting 2 pkgProblemResolver with broken count: 0 486s Done 487s Entering ResolveByKeep 487s 487s Calculating upgrade... 487s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 487s Reading package lists... 487s Building dependency tree... 487s Reading state information... 487s Starting pkgProblemResolver with broken count: 0 488s Starting 2 pkgProblemResolver with broken count: 0 488s Done 488s Solving dependencies... 488s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 491s Reading package lists... 491s Building dependency tree... 491s Reading state information... 491s Starting pkgProblemResolver with broken count: 1 491s Starting 2 pkgProblemResolver with broken count: 1 491s Investigating (0) satisfy:command-line:ppc64el < none -> 1 @un puN Ib > 491s Broken satisfy:command-line:ppc64el Depends on python3-clang-21:ppc64el < none @un H > 491s Done 491s Some packages could not be installed. This may mean that you have 491s requested an impossible situation or if you are using the unstable 491s distribution that some required packages have not yet been created 491s or been moved out of Incoming. 491s The following information may help to resolve the situation: 491s 491s The following packages have unmet dependencies: 491s satisfy:command-line : Depends: python3-clang-21 but it is not installable 491s E: Unable to correct problems, you have held broken packages. 491s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed 491s Reading package lists... 491s Building dependency tree... 491s Reading state information... 492s Starting pkgProblemResolver with broken count: 1 492s Starting 2 pkgProblemResolver with broken count: 1 492s Investigating (0) satisfy:command-line:ppc64el < none -> 1 @un puN Ib > 492s Broken satisfy:command-line:ppc64el Depends on python3-clang-21:ppc64el < none @un H > 492s Done 492s Some packages could not be installed. This may mean that you have 492s requested an impossible situation or if you are using the unstable 492s distribution that some required packages have not yet been created 492s or been moved out of Incoming. 492s The following information may help to resolve the situation: 492s 492s The following packages have unmet dependencies: 492s satisfy:command-line : Depends: python3-clang-21 but it is not installable 492s E: Unable to correct problems, you have held broken packages. 492s command3 FAIL badpkg 492s blame: llvm-toolchain-snapshot 492s 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. 492s autopkgtest [09:35:07]: @@@@@@@@@@@@@@@@@@@@ summary 492s command1 SKIP Test lists explicitly supported architectures, but the current architecture ppc64el isn't listed. 492s integration-test-suite-test SKIP Test lists explicitly supported architectures, but the current architecture ppc64el isn't listed. 492s command1 SKIP Test lists explicitly supported architectures, but the current architecture ppc64el isn't listed. 492s integration-test-suite-test SKIP Test lists explicitly supported architectures, but the current architecture ppc64el isn't listed. 492s cmake-llvm-test FAIL badpkg 492s blame: llvm-toolchain-snapshot 492s 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. 492s cmake-clang-test FAIL badpkg 492s blame: llvm-toolchain-snapshot 492s 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. 492s command2 FAIL badpkg 492s blame: llvm-toolchain-snapshot 492s 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. 492s command3 FAIL badpkg 492s blame: llvm-toolchain-snapshot 492s 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. 508s nova [W] Using flock in prodstack6-ppc64el 508s Creating nova instance adt-plucky-ppc64el-llvm-toolchain-snapshot-20250414-092655-juju-7f2275-prod-proposed-migration-environment-23-16703ba3-fd6f-4373-8ce6-d3c5d2f653f8 from image adt/ubuntu-plucky-ppc64el-server-20250414.img (UUID 643589a2-ed02-4b24-8397-93850cd38c96)... 508s nova [W] Timed out waiting for 64ce4029-6272-43d8-826f-3dfafe620345 to get deleted. 508s nova [W] Using flock in prodstack6-ppc64el 508s Creating nova instance adt-plucky-ppc64el-llvm-toolchain-snapshot-20250414-092655-juju-7f2275-prod-proposed-migration-environment-23-16703ba3-fd6f-4373-8ce6-d3c5d2f653f8 from image adt/ubuntu-plucky-ppc64el-server-20250414.img (UUID 643589a2-ed02-4b24-8397-93850cd38c96)... 508s nova [W] Timed out waiting for 8c31c83f-0d0f-4b8e-bdd8-ac2d64c9ee8c to get deleted. 508s nova [W] Using flock in prodstack6-ppc64el 508s Creating nova instance adt-plucky-ppc64el-llvm-toolchain-snapshot-20250414-092655-juju-7f2275-prod-proposed-migration-environment-23-16703ba3-fd6f-4373-8ce6-d3c5d2f653f8 from image adt/ubuntu-plucky-ppc64el-server-20250414.img (UUID 643589a2-ed02-4b24-8397-93850cd38c96)... 508s nova [W] Timed out waiting for 39ade6fe-d7fd-45a7-8a1c-01162d96cc09 to get deleted.