0s autopkgtest [14:05:28]: starting date and time: 2026-01-24 14:05:28+0000 0s autopkgtest [14:05:28]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [14:05:28]: host juju-7f2275-prod-proposed-migration-environment-15; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.6ig5fvy8/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:zlib --apt-upgrade pytorch --timeout-short=300 --timeout-copy=40000 --timeout-test=40000 --timeout-build=40000 --env=ADT_TEST_TRIGGERS=zlib/1:1.3.dfsg+really1.3.1-1ubuntu3 -- 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-13.secgroup --name adt-resolute-ppc64el-pytorch-20260124-140528-juju-7f2275-prod-proposed-migration-environment-15-0f46b6e6-8c48-4ebd-ac8e-8a1f28116be7 --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/ 3s Creating nova instance adt-resolute-ppc64el-pytorch-20260124-140528-juju-7f2275-prod-proposed-migration-environment-15-0f46b6e6-8c48-4ebd-ac8e-8a1f28116be7 from image adt/ubuntu-resolute-ppc64el-server-20260124.img (UUID a269ca64-3301-4299-8bab-2247218fc911)... 46s autopkgtest [14:06:14]: testbed dpkg architecture: ppc64el 47s autopkgtest [14:06:15]: testbed apt version: 3.1.13 47s autopkgtest [14:06:15]: @@@@@@@@@@@@@@@@@@@@ test bed setup 47s autopkgtest [14:06:15]: testbed release detected to be: None 48s autopkgtest [14:06:16]: updating testbed package index (apt update) 48s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 48s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 48s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 48s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 48s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [2820 B] 48s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [994 kB] 48s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [24.3 kB] 48s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [91.5 kB] 48s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el Packages [106 kB] 48s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/universe ppc64el Packages [811 kB] 49s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse ppc64el Packages [9920 B] 49s Fetched 2163 kB in 1s (2882 kB/s) 50s Reading package lists... 50s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 50s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 50s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 50s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 51s Reading package lists... 51s Reading package lists... 51s Building dependency tree... 51s Reading state information... 51s Calculating upgrade... 51s The following packages will be upgraded: 51s zlib1g 52s 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 52s Need to get 74.6 kB of archives. 52s After this operation, 0 B of additional disk space will be used. 52s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el zlib1g ppc64el 1:1.3.dfsg+really1.3.1-1ubuntu3 [74.6 kB] 52s dpkg-preconfigure: unable to re-open stdin: No such file or directory 52s Fetched 74.6 kB in 0s (3434 kB/s) 52s (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 ... 120851 files and directories currently installed.) 52s Preparing to unpack .../zlib1g_1%3a1.3.dfsg+really1.3.1-1ubuntu3_ppc64el.deb ... 52s Unpacking zlib1g:ppc64el (1:1.3.dfsg+really1.3.1-1ubuntu3) over (1:1.3.dfsg+really1.3.1-1ubuntu2) ... 52s Setting up zlib1g:ppc64el (1:1.3.dfsg+really1.3.1-1ubuntu3) ... 53s Processing triggers for libc-bin (2.42-2ubuntu4) ... 53s autopkgtest [14:06:21]: upgrading testbed (apt dist-upgrade and autopurge) 53s Reading package lists... 53s Building dependency tree... 53s Reading state information... 53s Calculating upgrade... 53s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 53s Reading package lists... 53s Building dependency tree... 53s Reading state information... 54s Solving dependencies... 54s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 56s autopkgtest [14:06:24]: testbed running kernel: Linux 6.18.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 12 16:45:54 UTC 2026 56s autopkgtest [14:06:24]: @@@@@@@@@@@@@@@@@@@@ apt-source pytorch 60s Get:1 http://ftpmaster.internal/ubuntu resolute/universe pytorch 2.6.0+dfsg-9 (dsc) [3621 B] 60s Get:2 http://ftpmaster.internal/ubuntu resolute/universe pytorch 2.6.0+dfsg-9 (tar) [27.2 MB] 60s Get:3 http://ftpmaster.internal/ubuntu resolute/universe pytorch 2.6.0+dfsg-9 (diff) [219 kB] 61s gpgv: Signature made Thu Sep 18 12:26:19 2025 UTC 61s gpgv: using RSA key F8583EFAA9A91F3AA34B3C92CE11A7B07B3AB946 61s gpgv: Can't check signature: No public key 61s dpkg-source: warning: cannot verify inline signature for ./pytorch_2.6.0+dfsg-9.dsc: no acceptable signature found 63s autopkgtest [14:06:31]: testing package pytorch version 2.6.0+dfsg-9 82s autopkgtest [14:06:50]: build not needed 112s autopkgtest [14:07:20]: test py_import_and_version: preparing testbed 113s Reading package lists... 113s Building dependency tree... 113s Reading state information... 113s Solving dependencies... 113s Some packages could not be installed. This may mean that you have 113s requested an impossible situation or if you are using the unstable 113s distribution that some required packages have not yet been created 113s or been moved out of Incoming. 113s The following information may help to resolve the situation: 113s 113s The following packages have unmet dependencies: 113s satisfy:command-line : Depends: python3-torch but it is not going to be installed 113s E: Unable to satisfy dependencies. Reached two conflicting assignments: 113s 1. libamdhip64-6:ppc64el is selected for install because: 113s 1. satisfy:command-line:ppc64el=1 is selected for install 113s 2. satisfy:command-line:ppc64el Depends python3-torch 113s 3. python3-torch:ppc64el Depends libopenmpi40 (>= 5.0.8) 113s 4. libopenmpi40:ppc64el Depends libucx0 113s 5. libucx0:ppc64el Depends libamdhip64-6 (>= 6.1.5) 113s 2. libamdhip64-6:ppc64el Depends libamd-comgr3 113s but none of the choices are installable: 113s [no choices] 113s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 113s Reading package lists... 113s Building dependency tree... 113s Reading state information... 113s Solving dependencies... 113s Some packages could not be installed. This may mean that you have 113s requested an impossible situation or if you are using the unstable 113s distribution that some required packages have not yet been created 113s or been moved out of Incoming. 113s The following information may help to resolve the situation: 113s 113s The following packages have unmet dependencies: 113s satisfy:command-line : Depends: python3-torch but it is not going to be installed 113s E: Unable to satisfy dependencies. Reached two conflicting assignments: 113s 1. libamdhip64-6:ppc64el is selected for install because: 113s 1. satisfy:command-line:ppc64el=1 is selected for install 113s 2. satisfy:command-line:ppc64el Depends python3-torch 113s 3. python3-torch:ppc64el Depends libopenmpi40 (>= 5.0.8) 113s 4. libopenmpi40:ppc64el Depends libucx0 113s 5. libucx0:ppc64el Depends libamdhip64-6 (>= 6.1.5) 113s 2. libamdhip64-6:ppc64el Depends libamd-comgr3 113s but none of the choices are installable: 113s [no choices] 113s py_import_and_version FAIL badpkg 113s blame: pytorch 113s 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. 113s autopkgtest [14:07:21]: test py_blas_openblas: preparing testbed 114s Reading package lists... 114s Building dependency tree... 114s Reading state information... 114s Solving dependencies... 114s Some packages could not be installed. This may mean that you have 114s requested an impossible situation or if you are using the unstable 114s distribution that some required packages have not yet been created 114s or been moved out of Incoming. 114s The following information may help to resolve the situation: 114s 114s The following packages have unmet dependencies: 114s satisfy:command-line : Depends: python3-torch but it is not going to be installed 114s Depends: libopenblas0 but it is not going to be installed 114s E: Unable to satisfy dependencies. Reached two conflicting assignments: 114s 1. libamdhip64-6:ppc64el is selected for install because: 114s 1. satisfy:command-line:ppc64el=1 is selected for install 114s 2. satisfy:command-line:ppc64el Depends python3-torch 114s 3. python3-torch:ppc64el Depends libopenmpi40 (>= 5.0.8) 114s 4. libopenmpi40:ppc64el Depends libucx0 114s 5. libucx0:ppc64el Depends libamdhip64-6 (>= 6.1.5) 114s 2. libamdhip64-6:ppc64el Depends libamd-comgr3 114s but none of the choices are installable: 114s [no choices] 114s autopkgtest [14:07:22]: test py_blas_blis: preparing testbed 114s py_blas_openblas FAIL badpkg 114s blame: pytorch 114s 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. 132s Creating nova instance adt-resolute-ppc64el-pytorch-20260124-140528-juju-7f2275-prod-proposed-migration-environment-15-0f46b6e6-8c48-4ebd-ac8e-8a1f28116be7 from image adt/ubuntu-resolute-ppc64el-server-20260124.img (UUID a269ca64-3301-4299-8bab-2247218fc911)... 178s autopkgtest [14:08:26]: testbed dpkg architecture: ppc64el 178s autopkgtest [14:08:26]: testbed apt version: 3.1.13 179s autopkgtest [14:08:27]: @@@@@@@@@@@@@@@@@@@@ test bed setup 179s autopkgtest [14:08:27]: testbed release detected to be: resolute 180s autopkgtest [14:08:28]: updating testbed package index (apt update) 180s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 180s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 180s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 180s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 180s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [994 kB] 180s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [24.3 kB] 180s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [2820 B] 180s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [91.5 kB] 180s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el Packages [106 kB] 181s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/universe ppc64el Packages [811 kB] 181s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse ppc64el Packages [9920 B] 181s Fetched 2163 kB in 1s (2860 kB/s) 181s Reading package lists... 182s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 182s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 182s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 182s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 183s Reading package lists... 183s Reading package lists... 183s Building dependency tree... 183s Reading state information... 183s Calculating upgrade... 183s The following packages will be upgraded: 183s zlib1g 183s 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 183s Need to get 74.6 kB of archives. 183s After this operation, 0 B of additional disk space will be used. 183s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el zlib1g ppc64el 1:1.3.dfsg+really1.3.1-1ubuntu3 [74.6 kB] 184s dpkg-preconfigure: unable to re-open stdin: No such file or directory 184s Fetched 74.6 kB in 0s (3739 kB/s) 184s (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 ... 120851 files and directories currently installed.) 184s Preparing to unpack .../zlib1g_1%3a1.3.dfsg+really1.3.1-1ubuntu3_ppc64el.deb ... 184s Unpacking zlib1g:ppc64el (1:1.3.dfsg+really1.3.1-1ubuntu3) over (1:1.3.dfsg+really1.3.1-1ubuntu2) ... 185s Setting up zlib1g:ppc64el (1:1.3.dfsg+really1.3.1-1ubuntu3) ... 185s Processing triggers for libc-bin (2.42-2ubuntu4) ... 185s autopkgtest [14:08:33]: upgrading testbed (apt dist-upgrade and autopurge) 185s Reading package lists... 185s Building dependency tree... 185s Reading state information... 185s Calculating upgrade... 185s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 186s Reading package lists... 186s Building dependency tree... 186s Reading state information... 186s Solving dependencies... 186s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 189s Reading package lists... 189s Building dependency tree... 189s Reading state information... 189s Solving dependencies... 189s Some packages could not be installed. This may mean that you have 189s requested an impossible situation or if you are using the unstable 189s distribution that some required packages have not yet been created 189s or been moved out of Incoming. 189s The following information may help to resolve the situation: 189s 189s The following packages have unmet dependencies: 189s satisfy:command-line : Depends: python3-torch but it is not going to be installed 189s Depends: libblis4 but it is not going to be installed 189s E: Unable to satisfy dependencies. Reached two conflicting assignments: 189s 1. libamdhip64-6:ppc64el is selected for install because: 189s 1. satisfy:command-line:ppc64el=1 is selected for install 189s 2. satisfy:command-line:ppc64el Depends python3-torch 189s 3. python3-torch:ppc64el Depends libopenmpi40 (>= 5.0.8) 189s 4. libopenmpi40:ppc64el Depends libucx0 189s 5. libucx0:ppc64el Depends libamdhip64-6 (>= 6.1.5) 189s 2. libamdhip64-6:ppc64el Depends libamd-comgr3 189s but none of the choices are installable: 189s [no choices] 189s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 189s Reading package lists... 189s Building dependency tree... 189s Reading state information... 189s Solving dependencies... 189s Some packages could not be installed. This may mean that you have 189s requested an impossible situation or if you are using the unstable 189s distribution that some required packages have not yet been created 189s or been moved out of Incoming. 189s The following information may help to resolve the situation: 189s 189s The following packages have unmet dependencies: 189s satisfy:command-line : Depends: python3-torch but it is not going to be installed 189s Depends: libblis4 but it is not going to be installed 189s E: Unable to satisfy dependencies. Reached two conflicting assignments: 189s 1. libamdhip64-6:ppc64el is selected for install because: 189s 1. satisfy:command-line:ppc64el=1 is selected for install 189s 2. satisfy:command-line:ppc64el Depends python3-torch 189s 3. python3-torch:ppc64el Depends libopenmpi40 (>= 5.0.8) 189s 4. libopenmpi40:ppc64el Depends libucx0 189s 5. libucx0:ppc64el Depends libamdhip64-6 (>= 6.1.5) 189s 2. libamdhip64-6:ppc64el Depends libamd-comgr3 189s but none of the choices are installable: 189s [no choices] 189s autopkgtest [14:08:37]: test py_sequential: preparing testbed 189s py_blas_blis FAIL badpkg 189s blame: pytorch 189s 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. 196s Creating nova instance adt-resolute-ppc64el-pytorch-20260124-140528-juju-7f2275-prod-proposed-migration-environment-15-0f46b6e6-8c48-4ebd-ac8e-8a1f28116be7 from image adt/ubuntu-resolute-ppc64el-server-20260124.img (UUID a269ca64-3301-4299-8bab-2247218fc911)... 240s autopkgtest [14:09:28]: testbed dpkg architecture: ppc64el 240s autopkgtest [14:09:28]: testbed apt version: 3.1.13 240s autopkgtest [14:09:28]: @@@@@@@@@@@@@@@@@@@@ test bed setup 241s autopkgtest [14:09:29]: testbed release detected to be: resolute 241s autopkgtest [14:09:29]: updating testbed package index (apt update) 242s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 242s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 242s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 242s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 242s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [91.5 kB] 242s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [994 kB] 242s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [2820 B] 242s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [24.3 kB] 242s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el Packages [106 kB] 242s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/universe ppc64el Packages [811 kB] 242s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse ppc64el Packages [9920 B] 242s Fetched 2163 kB in 1s (3713 kB/s) 243s Reading package lists... 244s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 244s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 244s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 244s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 244s Reading package lists... 244s Reading package lists... 245s Building dependency tree... 245s Reading state information... 245s Calculating upgrade... 245s The following packages will be upgraded: 245s zlib1g 245s 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 245s Need to get 74.6 kB of archives. 245s After this operation, 0 B of additional disk space will be used. 245s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el zlib1g ppc64el 1:1.3.dfsg+really1.3.1-1ubuntu3 [74.6 kB] 245s dpkg-preconfigure: unable to re-open stdin: No such file or directory 245s Fetched 74.6 kB in 0s (5247 kB/s) 245s (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 ... 120851 files and directories currently installed.) 245s Preparing to unpack .../zlib1g_1%3a1.3.dfsg+really1.3.1-1ubuntu3_ppc64el.deb ... 246s Unpacking zlib1g:ppc64el (1:1.3.dfsg+really1.3.1-1ubuntu3) over (1:1.3.dfsg+really1.3.1-1ubuntu2) ... 246s Setting up zlib1g:ppc64el (1:1.3.dfsg+really1.3.1-1ubuntu3) ... 246s Processing triggers for libc-bin (2.42-2ubuntu4) ... 246s autopkgtest [14:09:34]: upgrading testbed (apt dist-upgrade and autopurge) 246s Reading package lists... 246s Building dependency tree... 246s Reading state information... 246s Calculating upgrade... 247s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 247s Reading package lists... 247s Building dependency tree... 247s Reading state information... 247s Solving dependencies... 247s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 250s Reading package lists... 250s Building dependency tree... 250s Reading state information... 250s Solving dependencies... 250s Some packages could not be installed. This may mean that you have 250s requested an impossible situation or if you are using the unstable 250s distribution that some required packages have not yet been created 250s or been moved out of Incoming. 250s The following information may help to resolve the situation: 250s 250s The following packages have unmet dependencies: 250s satisfy:command-line : Depends: python3-torch but it is not going to be installed 250s E: Unable to satisfy dependencies. Reached two conflicting assignments: 250s 1. libamdhip64-6:ppc64el is selected for install because: 250s 1. satisfy:command-line:ppc64el=1 is selected for install 250s 2. satisfy:command-line:ppc64el Depends python3-torch 250s 3. python3-torch:ppc64el Depends libopenmpi40 (>= 5.0.8) 250s 4. libopenmpi40:ppc64el Depends libucx0 250s 5. libucx0:ppc64el Depends libamdhip64-6 (>= 6.1.5) 250s 2. libamdhip64-6:ppc64el Depends libamd-comgr3 250s but none of the choices are installable: 250s [no choices] 250s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 250s Reading package lists... 250s Building dependency tree... 250s Reading state information... 250s Solving dependencies... 250s Some packages could not be installed. This may mean that you have 250s requested an impossible situation or if you are using the unstable 250s distribution that some required packages have not yet been created 250s or been moved out of Incoming. 250s The following information may help to resolve the situation: 250s 250s The following packages have unmet dependencies: 250s satisfy:command-line : Depends: python3-torch but it is not going to be installed 250s E: Unable to satisfy dependencies. Reached two conflicting assignments: 250s 1. libamdhip64-6:ppc64el is selected for install because: 250s 1. satisfy:command-line:ppc64el=1 is selected for install 250s 2. satisfy:command-line:ppc64el Depends python3-torch 250s 3. python3-torch:ppc64el Depends libopenmpi40 (>= 5.0.8) 250s 4. libopenmpi40:ppc64el Depends libucx0 250s 5. libucx0:ppc64el Depends libamdhip64-6 (>= 6.1.5) 250s 2. libamdhip64-6:ppc64el Depends libamd-comgr3 250s but none of the choices are installable: 250s [no choices] 250s py_sequential FAIL badpkg 250s blame: pytorch 250s 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. 250s autopkgtest [14:09:38]: test show_dangling_symlink_if_any: preparing testbed 251s Reading package lists... 251s Building dependency tree... 251s Reading state information... 251s Solving dependencies... 251s Some packages could not be installed. This may mean that you have 251s requested an impossible situation or if you are using the unstable 251s distribution that some required packages have not yet been created 251s or been moved out of Incoming. 251s The following information may help to resolve the situation: 251s 251s The following packages have unmet dependencies: 251s satisfy:command-line : Depends: python3-torch but it is not going to be installed 251s Depends: libtorch-dev but it is not going to be installed 251s Depends: libtorch2.6 but it is not going to be installed 251s Depends: libtorch-test but it is not going to be installed 251s E: Unable to satisfy dependencies. Reached two conflicting assignments: 251s 1. python3-dev:ppc64el is selected for install because: 251s 1. satisfy:command-line:ppc64el=1 is selected for install 251s 2. satisfy:command-line:ppc64el Depends libtorch-dev 251s 3. libtorch-dev:ppc64el Depends python3-dev 251s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 251s but none of the choices are installable: 251s - python3-dev:ppc64el=3.14.2-1 Depends python3 (= 3.14.2-1) 251s but none of the choices are installable: 251s - python3:ppc64el=3.14.2-1 is not selected for install because: 251s 1. satisfy:command-line:ppc64el=1 is selected for install as above 251s 2. satisfy:command-line:ppc64el Depends python3-torch 251s 3. python3-torch:ppc64el Depends python3 (< 3.14) 251s 4. python3:ppc64el=3.13.9-3 conflicts with other versions of itself 251s - python3-dev:ppc64el=3.13.9-3 is not selected for install 251s show_dangling_symlink_if_any FAIL badpkg 251s blame: pytorch 251s 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. 251s autopkgtest [14:09:39]: test real_train_mnist: preparing testbed 251s Reading package lists... 251s Building dependency tree... 251s Reading state information... 251s Solving dependencies... 251s Some packages could not be installed. This may mean that you have 251s requested an impossible situation or if you are using the unstable 251s distribution that some required packages have not yet been created 251s or been moved out of Incoming. 251s The following information may help to resolve the situation: 251s 251s The following packages have unmet dependencies: 251s satisfy:command-line : Depends: python3-torch but it is not going to be installed 251s Depends: libtorch-dev but it is not going to be installed 251s Depends: libtorch2.6 but it is not going to be installed 251s Depends: libtorch-test but it is not going to be installed 251s Depends: python3-torchvision but it is not going to be installed 251s Depends: dataset-fashion-mnist but it is not going to be installed 251s Depends: libopenblas0 but it is not going to be installed 251s E: Unable to satisfy dependencies. Reached two conflicting assignments: 251s 1. python3-dev:ppc64el is selected for install because: 251s 1. satisfy:command-line:ppc64el=1 is selected for install 251s 2. satisfy:command-line:ppc64el Depends libtorch-dev 251s 3. libtorch-dev:ppc64el Depends python3-dev 251s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 251s but none of the choices are installable: 251s - python3-dev:ppc64el=3.14.2-1 Depends python3 (= 3.14.2-1) 251s but none of the choices are installable: 251s - python3:ppc64el=3.14.2-1 is not selected for install because: 251s 1. satisfy:command-line:ppc64el=1 is selected for install as above 251s 2. satisfy:command-line:ppc64el Depends python3-torch 251s 3. python3-torch:ppc64el Depends python3 (< 3.14) 251s 4. python3:ppc64el=3.13.9-3 conflicts with other versions of itself 251s - python3-dev:ppc64el=3.13.9-3 is not selected for install 251s real_train_mnist FAIL badpkg 251s blame: pytorch 251s 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. 251s autopkgtest [14:09:39]: test 1_of_104__cpptest__CppSignature_test: preparing testbed 270s Creating nova instance adt-resolute-ppc64el-pytorch-20260124-140528-juju-7f2275-prod-proposed-migration-environment-15-0f46b6e6-8c48-4ebd-ac8e-8a1f28116be7 from image adt/ubuntu-resolute-ppc64el-server-20260124.img (UUID a269ca64-3301-4299-8bab-2247218fc911)... 310s autopkgtest [14:10:38]: testbed dpkg architecture: ppc64el 311s autopkgtest [14:10:39]: testbed apt version: 3.1.13 311s autopkgtest [14:10:39]: @@@@@@@@@@@@@@@@@@@@ test bed setup 311s autopkgtest [14:10:39]: testbed release detected to be: resolute 312s autopkgtest [14:10:40]: updating testbed package index (apt update) 312s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 312s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 312s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 312s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 313s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [91.5 kB] 313s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [2820 B] 313s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [994 kB] 313s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [24.3 kB] 313s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el Packages [106 kB] 313s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/universe ppc64el Packages [811 kB] 313s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse ppc64el Packages [9920 B] 313s Fetched 2163 kB in 1s (2836 kB/s) 314s Reading package lists... 314s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 314s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 314s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 315s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 315s Reading package lists... 315s Reading package lists... 315s Building dependency tree... 315s Reading state information... 316s Calculating upgrade... 316s The following packages will be upgraded: 316s zlib1g 316s 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 316s Need to get 74.6 kB of archives. 316s After this operation, 0 B of additional disk space will be used. 316s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el zlib1g ppc64el 1:1.3.dfsg+really1.3.1-1ubuntu3 [74.6 kB] 316s dpkg-preconfigure: unable to re-open stdin: No such file or directory 316s Fetched 74.6 kB in 0s (592 kB/s) 316s (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 ... 120851 files and directories currently installed.) 316s Preparing to unpack .../zlib1g_1%3a1.3.dfsg+really1.3.1-1ubuntu3_ppc64el.deb ... 316s Unpacking zlib1g:ppc64el (1:1.3.dfsg+really1.3.1-1ubuntu3) over (1:1.3.dfsg+really1.3.1-1ubuntu2) ... 317s Setting up zlib1g:ppc64el (1:1.3.dfsg+really1.3.1-1ubuntu3) ... 317s Processing triggers for libc-bin (2.42-2ubuntu4) ... 317s autopkgtest [14:10:45]: upgrading testbed (apt dist-upgrade and autopurge) 317s Reading package lists... 317s Building dependency tree... 317s Reading state information... 317s Calculating upgrade... 317s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 317s Reading package lists... 317s Building dependency tree... 317s Reading state information... 318s Solving dependencies... 318s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 321s Reading package lists... 321s Building dependency tree... 321s Reading state information... 321s Solving dependencies... 321s Some packages could not be installed. This may mean that you have 321s requested an impossible situation or if you are using the unstable 321s distribution that some required packages have not yet been created 321s or been moved out of Incoming. 321s The following information may help to resolve the situation: 321s 321s The following packages have unmet dependencies: 321s satisfy:command-line : Depends: build-essential but it is not going to be installed 321s Depends: ninja-build but it is not going to be installed 321s Depends: libtorch-dev but it is not going to be installed 321s Depends: libtorch-test but it is not going to be installed 321s E: Unable to satisfy dependencies. Reached two conflicting assignments: 321s 1. binutils-powerpc64le-linux-gnu:ppc64el is selected for install because: 321s 1. satisfy:command-line:ppc64el=1 is selected for install 321s 2. satisfy:command-line:ppc64el Depends build-essential 321s 3. build-essential:ppc64el Depends gcc (>= 4:14.2) 321s 4. gcc:ppc64el Depends gcc-powerpc64le-linux-gnu (= 4:15.2.0-4ubuntu1) 321s 5. gcc-powerpc64le-linux-gnu:ppc64el Depends gcc-15-powerpc64le-linux-gnu (>= 15.2.0-2~) 321s 6. gcc-15-powerpc64le-linux-gnu:ppc64el Depends binutils-powerpc64le-linux-gnu (>= 2.39) 321s 2. binutils-powerpc64le-linux-gnu:ppc64el is available in versions 2.45.50.20251209-1ubuntu1, 2.45.50.20260119-1ubuntu1 321s but none of the choices are installable: 321s - binutils-powerpc64le-linux-gnu:ppc64el=2.45.50.20251209-1ubuntu1 is not selected for install 321s - binutils-powerpc64le-linux-gnu:ppc64el=2.45.50.20260119-1ubuntu1 is not selected for install 321s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 321s Reading package lists... 321s Building dependency tree... 321s Reading state information... 322s Solving dependencies... 322s Some packages could not be installed. This may mean that you have 322s requested an impossible situation or if you are using the unstable 322s distribution that some required packages have not yet been created 322s or been moved out of Incoming. 322s The following information may help to resolve the situation: 322s 322s The following packages have unmet dependencies: 322s satisfy:command-line : Depends: build-essential but it is not going to be installed 322s Depends: ninja-build but it is not going to be installed 322s Depends: libtorch-dev but it is not going to be installed 322s Depends: libtorch-test but it is not going to be installed 322s E: Unable to satisfy dependencies. Reached two conflicting assignments: 322s 1. python3-dev:ppc64el is selected for install because: 322s 1. satisfy:command-line:ppc64el=1 is selected for install 322s 2. satisfy:command-line:ppc64el Depends libtorch-dev 322s 3. libtorch-dev:ppc64el Depends python3-dev 322s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 322s but none of the choices are installable: 322s - python3-dev:ppc64el=3.14.2-1 is not selected for install 322s - python3-dev:ppc64el=3.13.9-3 is not selected for install 322s 1_of_104__cpptest__CppSignature_test FAIL badpkg 322s autopkgtest [14:10:50]: test 2_of_104__cpptest__Dict_test: preparing testbed 322s blame: pytorch 322s 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. 322s Reading package lists... 322s Building dependency tree... 322s Reading state information... 322s Solving dependencies... 322s Some packages could not be installed. This may mean that you have 322s requested an impossible situation or if you are using the unstable 322s distribution that some required packages have not yet been created 322s or been moved out of Incoming. 322s The following information may help to resolve the situation: 322s 322s The following packages have unmet dependencies: 322s satisfy:command-line : Depends: build-essential but it is not going to be installed 322s Depends: ninja-build but it is not going to be installed 322s Depends: libtorch-dev but it is not going to be installed 322s Depends: libtorch-test but it is not going to be installed 322s E: Unable to satisfy dependencies. Reached two conflicting assignments: 322s 1. python3-dev:ppc64el is selected for install because: 322s 1. satisfy:command-line:ppc64el=1 is selected for install 322s 2. satisfy:command-line:ppc64el Depends libtorch-dev 322s 3. libtorch-dev:ppc64el Depends python3-dev 322s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 322s but none of the choices are installable: 322s - python3-dev:ppc64el=3.14.2-1 is not selected for install 322s - python3-dev:ppc64el=3.13.9-3 is not selected for install 322s 2_of_104__cpptest__Dict_test FAIL badpkg 322s blame: pytorch 322s 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. 322s autopkgtest [14:10:50]: test 3_of_104__cpptest__Dimname_test: preparing testbed 322s Reading package lists... 322s Building dependency tree... 322s Reading state information... 322s Solving dependencies... 322s Some packages could not be installed. This may mean that you have 322s requested an impossible situation or if you are using the unstable 322s distribution that some required packages have not yet been created 322s or been moved out of Incoming. 322s The following information may help to resolve the situation: 322s 322s The following packages have unmet dependencies: 323s satisfy:command-line : Depends: build-essential but it is not going to be installed 323s Depends: ninja-build but it is not going to be installed 323s Depends: libtorch-dev but it is not going to be installed 323s Depends: libtorch-test but it is not going to be installed 323s E: Unable to satisfy dependencies. Reached two conflicting assignments: 323s 1. python3-dev:ppc64el is selected for install because: 323s 1. satisfy:command-line:ppc64el=1 is selected for install 323s 2. satisfy:command-line:ppc64el Depends libtorch-dev 323s 3. libtorch-dev:ppc64el Depends python3-dev 323s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 323s but none of the choices are installable: 323s - python3-dev:ppc64el=3.14.2-1 is not selected for install 323s - python3-dev:ppc64el=3.13.9-3 is not selected for install 323s 3_of_104__cpptest__Dimname_test FAIL badpkg 323s blame: pytorch 323s 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. 323s autopkgtest [14:10:51]: test 4_of_104__cpptest__IListRef_test: preparing testbed 323s Reading package lists... 323s Building dependency tree... 323s Reading state information... 323s Solving dependencies... 323s Some packages could not be installed. This may mean that you have 323s requested an impossible situation or if you are using the unstable 323s distribution that some required packages have not yet been created 323s or been moved out of Incoming. 323s The following information may help to resolve the situation: 323s 323s The following packages have unmet dependencies: 323s satisfy:command-line : Depends: build-essential but it is not going to be installed 323s Depends: ninja-build but it is not going to be installed 323s Depends: libtorch-dev but it is not going to be installed 323s Depends: libtorch-test but it is not going to be installed 323s E: Unable to satisfy dependencies. Reached two conflicting assignments: 323s 1. python3-dev:ppc64el is selected for install because: 323s 1. satisfy:command-line:ppc64el=1 is selected for install 323s 2. satisfy:command-line:ppc64el Depends libtorch-dev 323s 3. libtorch-dev:ppc64el Depends python3-dev 323s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 323s but none of the choices are installable: 323s - python3-dev:ppc64el=3.14.2-1 is not selected for install 323s - python3-dev:ppc64el=3.13.9-3 is not selected for install 323s 4_of_104__cpptest__IListRef_test FAIL badpkg 323s blame: pytorch 323s 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. 323s autopkgtest [14:10:51]: test 5_of_104__cpptest__KernelFunction_test: preparing testbed 323s Reading package lists... 323s Building dependency tree... 323s Reading state information... 323s Solving dependencies... 323s Some packages could not be installed. This may mean that you have 323s requested an impossible situation or if you are using the unstable 323s distribution that some required packages have not yet been created 323s or been moved out of Incoming. 323s The following information may help to resolve the situation: 323s 323s The following packages have unmet dependencies: 323s satisfy:command-line : Depends: build-essential but it is not going to be installed 323s Depends: ninja-build but it is not going to be installed 323s Depends: libtorch-dev but it is not going to be installed 323s Depends: libtorch-test but it is not going to be installed 323s E: Unable to satisfy dependencies. Reached two conflicting assignments: 323s 1. python3-dev:ppc64el is selected for install because: 323s 1. satisfy:command-line:ppc64el=1 is selected for install 323s 2. satisfy:command-line:ppc64el Depends libtorch-dev 323s 3. libtorch-dev:ppc64el Depends python3-dev 323s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 323s but none of the choices are installable: 323s - python3-dev:ppc64el=3.14.2-1 is not selected for install 323s - python3-dev:ppc64el=3.13.9-3 is not selected for install 323s 5_of_104__cpptest__KernelFunction_test FAIL badpkg 323s blame: pytorch 323s 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. 323s autopkgtest [14:10:51]: test 6_of_104__cpptest__List_test: preparing testbed 324s Reading package lists... 324s Building dependency tree... 324s Reading state information... 324s Solving dependencies... 324s Some packages could not be installed. This may mean that you have 324s requested an impossible situation or if you are using the unstable 324s distribution that some required packages have not yet been created 324s or been moved out of Incoming. 324s The following information may help to resolve the situation: 324s 324s The following packages have unmet dependencies: 324s satisfy:command-line : Depends: build-essential but it is not going to be installed 324s Depends: ninja-build but it is not going to be installed 324s Depends: libtorch-dev but it is not going to be installed 324s Depends: libtorch-test but it is not going to be installed 324s E: Unable to satisfy dependencies. Reached two conflicting assignments: 324s 1. python3-dev:ppc64el is selected for install because: 324s 1. satisfy:command-line:ppc64el=1 is selected for install 324s 2. satisfy:command-line:ppc64el Depends libtorch-dev 324s 3. libtorch-dev:ppc64el Depends python3-dev 324s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 324s but none of the choices are installable: 324s - python3-dev:ppc64el=3.14.2-1 is not selected for install 324s - python3-dev:ppc64el=3.13.9-3 is not selected for install 324s 6_of_104__cpptest__List_test FAIL badpkg 324s blame: pytorch 324s 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. 324s autopkgtest [14:10:52]: test 7_of_104__cpptest__MaybeOwned_test: preparing testbed 324s Reading package lists... 324s Building dependency tree... 324s Reading state information... 324s Solving dependencies... 324s Some packages could not be installed. This may mean that you have 324s requested an impossible situation or if you are using the unstable 324s distribution that some required packages have not yet been created 324s or been moved out of Incoming. 324s The following information may help to resolve the situation: 324s 324s The following packages have unmet dependencies: 324s satisfy:command-line : Depends: build-essential but it is not going to be installed 324s Depends: ninja-build but it is not going to be installed 324s Depends: libtorch-dev but it is not going to be installed 324s Depends: libtorch-test but it is not going to be installed 324s E: Unable to satisfy dependencies. Reached two conflicting assignments: 324s 1. python3-dev:ppc64el is selected for install because: 324s 1. satisfy:command-line:ppc64el=1 is selected for install 324s 2. satisfy:command-line:ppc64el Depends libtorch-dev 324s 3. libtorch-dev:ppc64el Depends python3-dev 324s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 324s but none of the choices are installable: 324s - python3-dev:ppc64el=3.14.2-1 is not selected for install 324s - python3-dev:ppc64el=3.13.9-3 is not selected for install 324s 7_of_104__cpptest__MaybeOwned_test FAIL badpkg 324s blame: pytorch 324s 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. 324s autopkgtest [14:10:52]: test 8_of_104__cpptest__NamedTensor_test: preparing testbed 325s Reading package lists... 325s Building dependency tree... 325s Reading state information... 325s Solving dependencies... 325s Some packages could not be installed. This may mean that you have 325s requested an impossible situation or if you are using the unstable 325s distribution that some required packages have not yet been created 325s or been moved out of Incoming. 325s The following information may help to resolve the situation: 325s 325s The following packages have unmet dependencies: 325s satisfy:command-line : Depends: build-essential but it is not going to be installed 325s Depends: ninja-build but it is not going to be installed 325s Depends: libtorch-dev but it is not going to be installed 325s Depends: libtorch-test but it is not going to be installed 325s E: Unable to satisfy dependencies. Reached two conflicting assignments: 325s 1. python3-dev:ppc64el is selected for install because: 325s 1. satisfy:command-line:ppc64el=1 is selected for install 325s 2. satisfy:command-line:ppc64el Depends libtorch-dev 325s 3. libtorch-dev:ppc64el Depends python3-dev 325s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 325s but none of the choices are installable: 325s - python3-dev:ppc64el=3.14.2-1 is not selected for install 325s - python3-dev:ppc64el=3.13.9-3 is not selected for install 325s 8_of_104__cpptest__NamedTensor_test FAIL badpkg 325s blame: pytorch 325s 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. 325s autopkgtest [14:10:53]: test 9_of_104__cpptest__StorageUtils_test: preparing testbed 325s Reading package lists... 325s Building dependency tree... 325s Reading state information... 325s Solving dependencies... 325s Some packages could not be installed. This may mean that you have 325s requested an impossible situation or if you are using the unstable 325s distribution that some required packages have not yet been created 325s or been moved out of Incoming. 325s The following information may help to resolve the situation: 325s 325s The following packages have unmet dependencies: 325s satisfy:command-line : Depends: build-essential but it is not going to be installed 325s Depends: ninja-build but it is not going to be installed 325s Depends: libtorch-dev but it is not going to be installed 325s Depends: libtorch-test but it is not going to be installed 325s E: Unable to satisfy dependencies. Reached two conflicting assignments: 325s 1. python3-dev:ppc64el is selected for install because: 325s 1. satisfy:command-line:ppc64el=1 is selected for install 325s 2. satisfy:command-line:ppc64el Depends libtorch-dev 325s 3. libtorch-dev:ppc64el Depends python3-dev 325s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 325s but none of the choices are installable: 325s - python3-dev:ppc64el=3.14.2-1 is not selected for install 325s - python3-dev:ppc64el=3.13.9-3 is not selected for install 325s 9_of_104__cpptest__StorageUtils_test FAIL badpkg 325s blame: pytorch 325s 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. 325s autopkgtest [14:10:53]: test 10_of_104__cpptest__apply_utils_test: preparing testbed 326s Reading package lists... 326s Building dependency tree... 326s Reading state information... 326s Solving dependencies... 326s Some packages could not be installed. This may mean that you have 326s requested an impossible situation or if you are using the unstable 326s distribution that some required packages have not yet been created 326s or been moved out of Incoming. 326s The following information may help to resolve the situation: 326s 326s The following packages have unmet dependencies: 326s satisfy:command-line : Depends: build-essential but it is not going to be installed 326s Depends: ninja-build but it is not going to be installed 326s Depends: libtorch-dev but it is not going to be installed 326s Depends: libtorch-test but it is not going to be installed 326s E: Unable to satisfy dependencies. Reached two conflicting assignments: 326s 1. python3-dev:ppc64el is selected for install because: 326s 1. satisfy:command-line:ppc64el=1 is selected for install 326s 2. satisfy:command-line:ppc64el Depends libtorch-dev 326s 3. libtorch-dev:ppc64el Depends python3-dev 326s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 326s but none of the choices are installable: 326s - python3-dev:ppc64el=3.14.2-1 is not selected for install 326s - python3-dev:ppc64el=3.13.9-3 is not selected for install 326s 10_of_104__cpptest__apply_utils_test FAIL badpkg 326s blame: pytorch 326s 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. 326s autopkgtest [14:10:54]: test 11_of_104__cpptest__atest: preparing testbed 326s Reading package lists... 326s Building dependency tree... 326s Reading state information... 326s Solving dependencies... 326s Some packages could not be installed. This may mean that you have 326s requested an impossible situation or if you are using the unstable 326s distribution that some required packages have not yet been created 326s or been moved out of Incoming. 326s The following information may help to resolve the situation: 326s 326s The following packages have unmet dependencies: 326s satisfy:command-line : Depends: build-essential but it is not going to be installed 326s Depends: ninja-build but it is not going to be installed 326s Depends: libtorch-dev but it is not going to be installed 326s Depends: libtorch-test but it is not going to be installed 326s E: Unable to satisfy dependencies. Reached two conflicting assignments: 326s 1. python3-dev:ppc64el is selected for install because: 326s 1. satisfy:command-line:ppc64el=1 is selected for install 326s 2. satisfy:command-line:ppc64el Depends libtorch-dev 326s 3. libtorch-dev:ppc64el Depends python3-dev 326s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 326s but none of the choices are installable: 326s - python3-dev:ppc64el=3.14.2-1 is not selected for install 326s - python3-dev:ppc64el=3.13.9-3 is not selected for install 326s 11_of_104__cpptest__atest FAIL badpkg 326s blame: pytorch 326s 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. 326s autopkgtest [14:10:54]: test 12_of_104__cpptest__backend_fallback_test: preparing testbed 327s Reading package lists... 327s Building dependency tree... 327s Reading state information... 327s Solving dependencies... 327s Some packages could not be installed. This may mean that you have 327s requested an impossible situation or if you are using the unstable 327s distribution that some required packages have not yet been created 327s or been moved out of Incoming. 327s The following information may help to resolve the situation: 327s 327s The following packages have unmet dependencies: 327s satisfy:command-line : Depends: build-essential but it is not going to be installed 327s Depends: ninja-build but it is not going to be installed 327s Depends: libtorch-dev but it is not going to be installed 327s Depends: libtorch-test but it is not going to be installed 327s E: Unable to satisfy dependencies. Reached two conflicting assignments: 327s 1. python3-dev:ppc64el is selected for install because: 327s 1. satisfy:command-line:ppc64el=1 is selected for install 327s 2. satisfy:command-line:ppc64el Depends libtorch-dev 327s 3. libtorch-dev:ppc64el Depends python3-dev 327s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 327s but none of the choices are installable: 327s - python3-dev:ppc64el=3.14.2-1 is not selected for install 327s - python3-dev:ppc64el=3.13.9-3 is not selected for install 327s 12_of_104__cpptest__backend_fallback_test FAIL badpkg 327s blame: pytorch 327s 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. 327s autopkgtest [14:10:55]: test 13_of_104__cpptest__basic: preparing testbed 327s Reading package lists... 327s Building dependency tree... 327s Reading state information... 327s Solving dependencies... 327s Some packages could not be installed. This may mean that you have 327s requested an impossible situation or if you are using the unstable 327s distribution that some required packages have not yet been created 327s or been moved out of Incoming. 327s The following information may help to resolve the situation: 327s 327s The following packages have unmet dependencies: 327s satisfy:command-line : Depends: build-essential but it is not going to be installed 327s Depends: ninja-build but it is not going to be installed 327s Depends: libtorch-dev but it is not going to be installed 327s Depends: libtorch-test but it is not going to be installed 327s E: Unable to satisfy dependencies. Reached two conflicting assignments: 327s 1. python3-dev:ppc64el is selected for install because: 327s 1. satisfy:command-line:ppc64el=1 is selected for install 327s 2. satisfy:command-line:ppc64el Depends libtorch-dev 327s 3. libtorch-dev:ppc64el Depends python3-dev 327s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 327s but none of the choices are installable: 327s - python3-dev:ppc64el=3.14.2-1 is not selected for install 327s - python3-dev:ppc64el=3.13.9-3 is not selected for install 327s autopkgtest [14:10:55]: test 14_of_104__cpptest__broadcast_test: preparing testbed 327s 13_of_104__cpptest__basic FAIL badpkg 327s blame: pytorch 327s 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. 327s Reading package lists... 328s Building dependency tree... 328s Reading state information... 328s Solving dependencies... 328s Some packages could not be installed. This may mean that you have 328s requested an impossible situation or if you are using the unstable 328s distribution that some required packages have not yet been created 328s or been moved out of Incoming. 328s The following information may help to resolve the situation: 328s 328s The following packages have unmet dependencies: 328s satisfy:command-line : Depends: build-essential but it is not going to be installed 328s Depends: ninja-build but it is not going to be installed 328s Depends: libtorch-dev but it is not going to be installed 328s Depends: libtorch-test but it is not going to be installed 328s E: Unable to satisfy dependencies. Reached two conflicting assignments: 328s 1. python3-dev:ppc64el is selected for install because: 328s 1. satisfy:command-line:ppc64el=1 is selected for install 328s 2. satisfy:command-line:ppc64el Depends libtorch-dev 328s 3. libtorch-dev:ppc64el Depends python3-dev 328s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 328s but none of the choices are installable: 328s - python3-dev:ppc64el=3.14.2-1 is not selected for install 328s - python3-dev:ppc64el=3.13.9-3 is not selected for install 328s autopkgtest [14:10:56]: test 15_of_104__cpptest__c10_Bitset_test: preparing testbed 328s 14_of_104__cpptest__broadcast_test FAIL badpkg 328s blame: pytorch 328s 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. 328s Reading package lists... 328s Building dependency tree... 328s Reading state information... 328s Solving dependencies... 328s Some packages could not be installed. This may mean that you have 328s requested an impossible situation or if you are using the unstable 328s distribution that some required packages have not yet been created 328s or been moved out of Incoming. 328s The following information may help to resolve the situation: 328s 328s The following packages have unmet dependencies: 328s satisfy:command-line : Depends: build-essential but it is not going to be installed 328s Depends: ninja-build but it is not going to be installed 328s Depends: libtorch-dev but it is not going to be installed 328s Depends: libtorch-test but it is not going to be installed 328s E: Unable to satisfy dependencies. Reached two conflicting assignments: 328s 1. python3-dev:ppc64el is selected for install because: 328s 1. satisfy:command-line:ppc64el=1 is selected for install 328s 2. satisfy:command-line:ppc64el Depends libtorch-dev 328s 3. libtorch-dev:ppc64el Depends python3-dev 328s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 328s but none of the choices are installable: 328s - python3-dev:ppc64el=3.14.2-1 is not selected for install 328s - python3-dev:ppc64el=3.13.9-3 is not selected for install 328s autopkgtest [14:10:56]: test 16_of_104__cpptest__c10_CompileTimeFunctionPointer_test: preparing testbed 328s 15_of_104__cpptest__c10_Bitset_test FAIL badpkg 328s blame: pytorch 328s 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. 328s Reading package lists... 329s Building dependency tree... 329s Reading state information... 329s Solving dependencies... 329s Some packages could not be installed. This may mean that you have 329s requested an impossible situation or if you are using the unstable 329s distribution that some required packages have not yet been created 329s or been moved out of Incoming. 329s The following information may help to resolve the situation: 329s 329s The following packages have unmet dependencies: 329s satisfy:command-line : Depends: build-essential but it is not going to be installed 329s Depends: ninja-build but it is not going to be installed 329s Depends: libtorch-dev but it is not going to be installed 329s Depends: libtorch-test but it is not going to be installed 329s E: Unable to satisfy dependencies. Reached two conflicting assignments: 329s 1. python3-dev:ppc64el is selected for install because: 329s 1. satisfy:command-line:ppc64el=1 is selected for install 329s 2. satisfy:command-line:ppc64el Depends libtorch-dev 329s 3. libtorch-dev:ppc64el Depends python3-dev 329s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 329s but none of the choices are installable: 329s - python3-dev:ppc64el=3.14.2-1 is not selected for install 329s - python3-dev:ppc64el=3.13.9-3 is not selected for install 329s autopkgtest [14:10:57]: test 17_of_104__cpptest__c10_ConstexprCrc_test: preparing testbed 329s 16_of_104__cpptest__c10_CompileTimeFunctionPointer_test FAIL badpkg 329s blame: pytorch 329s 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. 329s Reading package lists... 329s Building dependency tree... 329s Reading state information... 329s Solving dependencies... 329s Some packages could not be installed. This may mean that you have 329s requested an impossible situation or if you are using the unstable 329s distribution that some required packages have not yet been created 329s or been moved out of Incoming. 329s The following information may help to resolve the situation: 329s 329s The following packages have unmet dependencies: 329s satisfy:command-line : Depends: build-essential but it is not going to be installed 329s Depends: ninja-build but it is not going to be installed 329s Depends: libtorch-dev but it is not going to be installed 329s Depends: libtorch-test but it is not going to be installed 329s E: Unable to satisfy dependencies. Reached two conflicting assignments: 329s 1. python3-dev:ppc64el is selected for install because: 329s 1. satisfy:command-line:ppc64el=1 is selected for install 329s 2. satisfy:command-line:ppc64el Depends libtorch-dev 329s 3. libtorch-dev:ppc64el Depends python3-dev 329s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 329s but none of the choices are installable: 329s - python3-dev:ppc64el=3.14.2-1 is not selected for install 329s - python3-dev:ppc64el=3.13.9-3 is not selected for install 329s 17_of_104__cpptest__c10_ConstexprCrc_test FAIL badpkg 329s blame: pytorch 329s 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. 329s autopkgtest [14:10:57]: test 18_of_104__cpptest__c10_DeadlockDetection_test: preparing testbed 329s Reading package lists... 329s Building dependency tree... 329s Reading state information... 330s Solving dependencies... 330s Some packages could not be installed. This may mean that you have 330s requested an impossible situation or if you are using the unstable 330s distribution that some required packages have not yet been created 330s or been moved out of Incoming. 330s The following information may help to resolve the situation: 330s 330s The following packages have unmet dependencies: 330s satisfy:command-line : Depends: build-essential but it is not going to be installed 330s Depends: ninja-build but it is not going to be installed 330s Depends: libtorch-dev but it is not going to be installed 330s Depends: libtorch-test but it is not going to be installed 330s E: Unable to satisfy dependencies. Reached two conflicting assignments: 330s 1. python3-dev:ppc64el is selected for install because: 330s 1. satisfy:command-line:ppc64el=1 is selected for install 330s 2. satisfy:command-line:ppc64el Depends libtorch-dev 330s 3. libtorch-dev:ppc64el Depends python3-dev 330s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 330s but none of the choices are installable: 330s - python3-dev:ppc64el=3.14.2-1 is not selected for install 330s - python3-dev:ppc64el=3.13.9-3 is not selected for install 330s 18_of_104__cpptest__c10_DeadlockDetection_test FAIL badpkg 330s blame: pytorch 330s 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. 330s autopkgtest [14:10:58]: test 19_of_104__cpptest__c10_DeviceGuard_test: preparing testbed 330s Reading package lists... 330s Building dependency tree... 330s Reading state information... 330s Solving dependencies... 330s Some packages could not be installed. This may mean that you have 330s requested an impossible situation or if you are using the unstable 330s distribution that some required packages have not yet been created 330s or been moved out of Incoming. 330s The following information may help to resolve the situation: 330s 330s The following packages have unmet dependencies: 330s satisfy:command-line : Depends: build-essential but it is not going to be installed 330s Depends: ninja-build but it is not going to be installed 330s Depends: libtorch-dev but it is not going to be installed 330s Depends: libtorch-test but it is not going to be installed 330s E: Unable to satisfy dependencies. Reached two conflicting assignments: 330s 1. python3-dev:ppc64el is selected for install because: 330s 1. satisfy:command-line:ppc64el=1 is selected for install 330s 2. satisfy:command-line:ppc64el Depends libtorch-dev 330s 3. libtorch-dev:ppc64el Depends python3-dev 330s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 330s but none of the choices are installable: 330s - python3-dev:ppc64el=3.14.2-1 is not selected for install 330s - python3-dev:ppc64el=3.13.9-3 is not selected for install 330s 19_of_104__cpptest__c10_DeviceGuard_test FAIL badpkg 330s blame: pytorch 330s 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. 330s autopkgtest [14:10:58]: test 20_of_104__cpptest__c10_Device_test: preparing testbed 330s Reading package lists... 330s Building dependency tree... 330s Reading state information... 331s Solving dependencies... 331s Some packages could not be installed. This may mean that you have 331s requested an impossible situation or if you are using the unstable 331s distribution that some required packages have not yet been created 331s or been moved out of Incoming. 331s The following information may help to resolve the situation: 331s 331s The following packages have unmet dependencies: 331s satisfy:command-line : Depends: build-essential but it is not going to be installed 331s Depends: ninja-build but it is not going to be installed 331s Depends: libtorch-dev but it is not going to be installed 331s Depends: libtorch-test but it is not going to be installed 331s E: Unable to satisfy dependencies. Reached two conflicting assignments: 331s 1. python3-dev:ppc64el is selected for install because: 331s 1. satisfy:command-line:ppc64el=1 is selected for install 331s 2. satisfy:command-line:ppc64el Depends libtorch-dev 331s 3. libtorch-dev:ppc64el Depends python3-dev 331s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 331s but none of the choices are installable: 331s - python3-dev:ppc64el=3.14.2-1 is not selected for install 331s - python3-dev:ppc64el=3.13.9-3 is not selected for install 331s autopkgtest [14:10:59]: test 21_of_104__cpptest__c10_DispatchKeySet_test: preparing testbed 331s 20_of_104__cpptest__c10_Device_test FAIL badpkg 331s blame: pytorch 331s 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. 331s Reading package lists... 331s Building dependency tree... 331s Reading state information... 331s Solving dependencies... 331s Some packages could not be installed. This may mean that you have 331s requested an impossible situation or if you are using the unstable 331s distribution that some required packages have not yet been created 331s or been moved out of Incoming. 331s The following information may help to resolve the situation: 331s 331s The following packages have unmet dependencies: 331s satisfy:command-line : Depends: build-essential but it is not going to be installed 331s Depends: ninja-build but it is not going to be installed 331s Depends: libtorch-dev but it is not going to be installed 331s Depends: libtorch-test but it is not going to be installed 331s E: Unable to satisfy dependencies. Reached two conflicting assignments: 331s 1. python3-dev:ppc64el is selected for install because: 331s 1. satisfy:command-line:ppc64el=1 is selected for install 331s 2. satisfy:command-line:ppc64el Depends libtorch-dev 331s 3. libtorch-dev:ppc64el Depends python3-dev 331s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 331s but none of the choices are installable: 331s - python3-dev:ppc64el=3.14.2-1 is not selected for install 331s - python3-dev:ppc64el=3.13.9-3 is not selected for install 331s autopkgtest [14:10:59]: test 22_of_104__cpptest__c10_Half_test: preparing testbed 331s 21_of_104__cpptest__c10_DispatchKeySet_test FAIL badpkg 331s blame: pytorch 331s 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. 331s Reading package lists... 331s Building dependency tree... 331s Reading state information... 331s Solving dependencies... 331s Some packages could not be installed. This may mean that you have 331s requested an impossible situation or if you are using the unstable 331s distribution that some required packages have not yet been created 331s or been moved out of Incoming. 331s The following information may help to resolve the situation: 331s 331s The following packages have unmet dependencies: 332s satisfy:command-line : Depends: build-essential but it is not going to be installed 332s Depends: ninja-build but it is not going to be installed 332s Depends: libtorch-dev but it is not going to be installed 332s Depends: libtorch-test but it is not going to be installed 332s E: Unable to satisfy dependencies. Reached two conflicting assignments: 332s 1. python3-dev:ppc64el is selected for install because: 332s 1. satisfy:command-line:ppc64el=1 is selected for install 332s 2. satisfy:command-line:ppc64el Depends libtorch-dev 332s 3. libtorch-dev:ppc64el Depends python3-dev 332s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 332s but none of the choices are installable: 332s - python3-dev:ppc64el=3.14.2-1 is not selected for install 332s - python3-dev:ppc64el=3.13.9-3 is not selected for install 332s autopkgtest [14:11:00]: test 23_of_104__cpptest__c10_InlineDeviceGuard_test: preparing testbed 332s 22_of_104__cpptest__c10_Half_test FAIL badpkg 332s blame: pytorch 332s 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. 332s Reading package lists... 332s Building dependency tree... 332s Reading state information... 332s Solving dependencies... 332s Some packages could not be installed. This may mean that you have 332s requested an impossible situation or if you are using the unstable 332s distribution that some required packages have not yet been created 332s or been moved out of Incoming. 332s The following information may help to resolve the situation: 332s 332s The following packages have unmet dependencies: 332s satisfy:command-line : Depends: build-essential but it is not going to be installed 332s Depends: ninja-build but it is not going to be installed 332s Depends: libtorch-dev but it is not going to be installed 332s Depends: libtorch-test but it is not going to be installed 332s E: Unable to satisfy dependencies. Reached two conflicting assignments: 332s 1. python3-dev:ppc64el is selected for install because: 332s 1. satisfy:command-line:ppc64el=1 is selected for install 332s 2. satisfy:command-line:ppc64el Depends libtorch-dev 332s 3. libtorch-dev:ppc64el Depends python3-dev 332s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 332s but none of the choices are installable: 332s - python3-dev:ppc64el=3.14.2-1 is not selected for install 332s - python3-dev:ppc64el=3.13.9-3 is not selected for install 332s autopkgtest [14:11:00]: test 24_of_104__cpptest__c10_InlineStreamGuard_test: preparing testbed 332s 23_of_104__cpptest__c10_InlineDeviceGuard_test FAIL badpkg 332s blame: pytorch 332s 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. 332s Reading package lists... 332s Building dependency tree... 332s Reading state information... 332s Solving dependencies... 332s Some packages could not be installed. This may mean that you have 332s requested an impossible situation or if you are using the unstable 332s distribution that some required packages have not yet been created 332s or been moved out of Incoming. 332s The following information may help to resolve the situation: 332s 332s The following packages have unmet dependencies: 333s satisfy:command-line : Depends: build-essential but it is not going to be installed 333s Depends: ninja-build but it is not going to be installed 333s Depends: libtorch-dev but it is not going to be installed 333s Depends: libtorch-test but it is not going to be installed 333s E: Unable to satisfy dependencies. Reached two conflicting assignments: 333s 1. python3-dev:ppc64el is selected for install because: 333s 1. satisfy:command-line:ppc64el=1 is selected for install 333s 2. satisfy:command-line:ppc64el Depends libtorch-dev 333s 3. libtorch-dev:ppc64el Depends python3-dev 333s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 333s but none of the choices are installable: 333s - python3-dev:ppc64el=3.14.2-1 is not selected for install 333s - python3-dev:ppc64el=3.13.9-3 is not selected for install 333s 24_of_104__cpptest__c10_InlineStreamGuard_test FAIL badpkg 333s blame: pytorch 333s 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. 333s autopkgtest [14:11:01]: test 25_of_104__cpptest__c10_LeftRight_test: preparing testbed 333s Reading package lists... 333s Building dependency tree... 333s Reading state information... 333s Solving dependencies... 333s Some packages could not be installed. This may mean that you have 333s requested an impossible situation or if you are using the unstable 333s distribution that some required packages have not yet been created 333s or been moved out of Incoming. 333s The following information may help to resolve the situation: 333s 333s The following packages have unmet dependencies: 333s satisfy:command-line : Depends: build-essential but it is not going to be installed 333s Depends: ninja-build but it is not going to be installed 333s Depends: libtorch-dev but it is not going to be installed 333s Depends: libtorch-test but it is not going to be installed 333s E: Unable to satisfy dependencies. Reached two conflicting assignments: 333s 1. python3-dev:ppc64el is selected for install because: 333s 1. satisfy:command-line:ppc64el=1 is selected for install 333s 2. satisfy:command-line:ppc64el Depends libtorch-dev 333s 3. libtorch-dev:ppc64el Depends python3-dev 333s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 333s but none of the choices are installable: 333s - python3-dev:ppc64el=3.14.2-1 is not selected for install 333s - python3-dev:ppc64el=3.13.9-3 is not selected for install 333s autopkgtest [14:11:01]: test 26_of_104__cpptest__c10_Metaprogramming_test: preparing testbed 333s 25_of_104__cpptest__c10_LeftRight_test FAIL badpkg 333s blame: pytorch 333s 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. 333s Reading package lists... 333s Building dependency tree... 333s Reading state information... 333s Solving dependencies... 333s Some packages could not be installed. This may mean that you have 333s requested an impossible situation or if you are using the unstable 333s distribution that some required packages have not yet been created 333s or been moved out of Incoming. 333s The following information may help to resolve the situation: 333s 333s The following packages have unmet dependencies: 333s satisfy:command-line : Depends: build-essential but it is not going to be installed 333s Depends: ninja-build but it is not going to be installed 333s Depends: libtorch-dev but it is not going to be installed 333s Depends: libtorch-test but it is not going to be installed 333s E: Unable to satisfy dependencies. Reached two conflicting assignments: 333s 1. python3-dev:ppc64el is selected for install because: 333s 1. satisfy:command-line:ppc64el=1 is selected for install 333s 2. satisfy:command-line:ppc64el Depends libtorch-dev 333s 3. libtorch-dev:ppc64el Depends python3-dev 333s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 333s but none of the choices are installable: 333s - python3-dev:ppc64el=3.14.2-1 is not selected for install 333s - python3-dev:ppc64el=3.13.9-3 is not selected for install 333s autopkgtest [14:11:01]: test 27_of_104__cpptest__c10_NetworkFlow_test: preparing testbed 333s 26_of_104__cpptest__c10_Metaprogramming_test FAIL badpkg 333s blame: pytorch 333s 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. 334s Reading package lists... 334s Building dependency tree... 334s Reading state information... 334s Solving dependencies... 334s Some packages could not be installed. This may mean that you have 334s requested an impossible situation or if you are using the unstable 334s distribution that some required packages have not yet been created 334s or been moved out of Incoming. 334s The following information may help to resolve the situation: 334s 334s The following packages have unmet dependencies: 334s satisfy:command-line : Depends: build-essential but it is not going to be installed 334s Depends: ninja-build but it is not going to be installed 334s Depends: libtorch-dev but it is not going to be installed 334s Depends: libtorch-test but it is not going to be installed 334s E: Unable to satisfy dependencies. Reached two conflicting assignments: 334s 1. python3-dev:ppc64el is selected for install because: 334s 1. satisfy:command-line:ppc64el=1 is selected for install 334s 2. satisfy:command-line:ppc64el Depends libtorch-dev 334s 3. libtorch-dev:ppc64el Depends python3-dev 334s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 334s but none of the choices are installable: 334s - python3-dev:ppc64el=3.14.2-1 is not selected for install 334s - python3-dev:ppc64el=3.13.9-3 is not selected for install 334s 27_of_104__cpptest__c10_NetworkFlow_test FAIL badpkg 334s blame: pytorch 334s 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. 334s autopkgtest [14:11:02]: test 28_of_104__cpptest__c10_Scalar_test: preparing testbed 334s Reading package lists... 334s Building dependency tree... 334s Reading state information... 334s Solving dependencies... 334s Some packages could not be installed. This may mean that you have 334s requested an impossible situation or if you are using the unstable 334s distribution that some required packages have not yet been created 334s or been moved out of Incoming. 334s The following information may help to resolve the situation: 334s 334s The following packages have unmet dependencies: 334s satisfy:command-line : Depends: build-essential but it is not going to be installed 334s Depends: ninja-build but it is not going to be installed 334s Depends: libtorch-dev but it is not going to be installed 334s Depends: libtorch-test but it is not going to be installed 334s E: Unable to satisfy dependencies. Reached two conflicting assignments: 334s 1. python3-dev:ppc64el is selected for install because: 334s 1. satisfy:command-line:ppc64el=1 is selected for install 334s 2. satisfy:command-line:ppc64el Depends libtorch-dev 334s 3. libtorch-dev:ppc64el Depends python3-dev 334s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 334s but none of the choices are installable: 334s - python3-dev:ppc64el=3.14.2-1 is not selected for install 334s - python3-dev:ppc64el=3.13.9-3 is not selected for install 334s autopkgtest [14:11:02]: test 29_of_104__cpptest__c10_SizesAndStrides_test: preparing testbed 334s 28_of_104__cpptest__c10_Scalar_test FAIL badpkg 334s blame: pytorch 334s 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 Reading package lists... 335s Building dependency tree... 335s Reading state information... 335s Solving dependencies... 335s Some packages could not be installed. This may mean that you have 335s requested an impossible situation or if you are using the unstable 335s distribution that some required packages have not yet been created 335s or been moved out of Incoming. 335s The following information may help to resolve the situation: 335s 335s The following packages have unmet dependencies: 335s satisfy:command-line : Depends: build-essential but it is not going to be installed 335s Depends: ninja-build but it is not going to be installed 335s Depends: libtorch-dev but it is not going to be installed 335s Depends: libtorch-test but it is not going to be installed 335s E: Unable to satisfy dependencies. Reached two conflicting assignments: 335s 1. python3-dev:ppc64el is selected for install because: 335s 1. satisfy:command-line:ppc64el=1 is selected for install 335s 2. satisfy:command-line:ppc64el Depends libtorch-dev 335s 3. libtorch-dev:ppc64el Depends python3-dev 335s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 335s but none of the choices are installable: 335s - python3-dev:ppc64el=3.14.2-1 is not selected for install 335s - python3-dev:ppc64el=3.13.9-3 is not selected for install 335s autopkgtest [14:11:03]: test 30_of_104__cpptest__c10_StreamGuard_test: preparing testbed 335s 29_of_104__cpptest__c10_SizesAndStrides_test FAIL badpkg 335s blame: pytorch 335s 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 Reading package lists... 335s Building dependency tree... 335s Reading state information... 335s Solving dependencies... 335s Some packages could not be installed. This may mean that you have 335s requested an impossible situation or if you are using the unstable 335s distribution that some required packages have not yet been created 335s or been moved out of Incoming. 335s The following information may help to resolve the situation: 335s 335s The following packages have unmet dependencies: 335s satisfy:command-line : Depends: build-essential but it is not going to be installed 335s Depends: ninja-build but it is not going to be installed 335s Depends: libtorch-dev but it is not going to be installed 335s Depends: libtorch-test but it is not going to be installed 335s E: Unable to satisfy dependencies. Reached two conflicting assignments: 335s 1. python3-dev:ppc64el is selected for install because: 335s 1. satisfy:command-line:ppc64el=1 is selected for install 335s 2. satisfy:command-line:ppc64el Depends libtorch-dev 335s 3. libtorch-dev:ppc64el Depends python3-dev 335s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 335s but none of the choices are installable: 335s - python3-dev:ppc64el=3.14.2-1 is not selected for install 335s - python3-dev:ppc64el=3.13.9-3 is not selected for install 335s autopkgtest [14:11:03]: test 31_of_104__cpptest__c10_SymInt_test: preparing testbed 335s 30_of_104__cpptest__c10_StreamGuard_test FAIL badpkg 335s blame: pytorch 335s 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. 336s Reading package lists... 336s Building dependency tree... 336s Reading state information... 336s Solving dependencies... 336s Some packages could not be installed. This may mean that you have 336s requested an impossible situation or if you are using the unstable 336s distribution that some required packages have not yet been created 336s or been moved out of Incoming. 336s The following information may help to resolve the situation: 336s 336s The following packages have unmet dependencies: 336s satisfy:command-line : Depends: build-essential but it is not going to be installed 336s Depends: ninja-build but it is not going to be installed 336s Depends: libtorch-dev but it is not going to be installed 336s Depends: libtorch-test but it is not going to be installed 336s E: Unable to satisfy dependencies. Reached two conflicting assignments: 336s 1. python3-dev:ppc64el is selected for install because: 336s 1. satisfy:command-line:ppc64el=1 is selected for install 336s 2. satisfy:command-line:ppc64el Depends libtorch-dev 336s 3. libtorch-dev:ppc64el Depends python3-dev 336s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 336s but none of the choices are installable: 336s - python3-dev:ppc64el=3.14.2-1 is not selected for install 336s - python3-dev:ppc64el=3.13.9-3 is not selected for install 336s 31_of_104__cpptest__c10_SymInt_test FAIL badpkg 336s blame: pytorch 336s 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. 336s autopkgtest [14:11:04]: test 32_of_104__cpptest__c10_Synchronized_test: preparing testbed 336s Reading package lists... 336s Building dependency tree... 336s Reading state information... 336s Solving dependencies... 336s Some packages could not be installed. This may mean that you have 336s requested an impossible situation or if you are using the unstable 336s distribution that some required packages have not yet been created 336s or been moved out of Incoming. 336s The following information may help to resolve the situation: 336s 336s The following packages have unmet dependencies: 336s satisfy:command-line : Depends: build-essential but it is not going to be installed 336s Depends: ninja-build but it is not going to be installed 336s Depends: libtorch-dev but it is not going to be installed 336s Depends: libtorch-test but it is not going to be installed 336s E: Unable to satisfy dependencies. Reached two conflicting assignments: 336s 1. python3-dev:ppc64el is selected for install because: 336s 1. satisfy:command-line:ppc64el=1 is selected for install 336s 2. satisfy:command-line:ppc64el Depends libtorch-dev 336s 3. libtorch-dev:ppc64el Depends python3-dev 336s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 336s but none of the choices are installable: 336s - python3-dev:ppc64el=3.14.2-1 is not selected for install 336s - python3-dev:ppc64el=3.13.9-3 is not selected for install 336s autopkgtest [14:11:04]: test 33_of_104__cpptest__c10_ThreadLocal_test: preparing testbed 336s 32_of_104__cpptest__c10_Synchronized_test FAIL badpkg 336s blame: pytorch 336s 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. 337s Reading package lists... 337s Building dependency tree... 337s Reading state information... 337s Solving dependencies... 337s Some packages could not be installed. This may mean that you have 337s requested an impossible situation or if you are using the unstable 337s distribution that some required packages have not yet been created 337s or been moved out of Incoming. 337s The following information may help to resolve the situation: 337s 337s The following packages have unmet dependencies: 337s satisfy:command-line : Depends: build-essential but it is not going to be installed 337s Depends: ninja-build but it is not going to be installed 337s Depends: libtorch-dev but it is not going to be installed 337s Depends: libtorch-test but it is not going to be installed 337s E: Unable to satisfy dependencies. Reached two conflicting assignments: 337s 1. python3-dev:ppc64el is selected for install because: 337s 1. satisfy:command-line:ppc64el=1 is selected for install 337s 2. satisfy:command-line:ppc64el Depends libtorch-dev 337s 3. libtorch-dev:ppc64el Depends python3-dev 337s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 337s but none of the choices are installable: 337s - python3-dev:ppc64el=3.14.2-1 is not selected for install 337s - python3-dev:ppc64el=3.13.9-3 is not selected for install 337s autopkgtest [14:11:05]: test 34_of_104__cpptest__c10_TypeIndex_test: preparing testbed 337s 33_of_104__cpptest__c10_ThreadLocal_test FAIL badpkg 337s blame: pytorch 337s 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. 337s Reading package lists... 337s Building dependency tree... 337s Reading state information... 337s Solving dependencies... 337s Some packages could not be installed. This may mean that you have 337s requested an impossible situation or if you are using the unstable 337s distribution that some required packages have not yet been created 337s or been moved out of Incoming. 337s The following information may help to resolve the situation: 337s 337s The following packages have unmet dependencies: 337s satisfy:command-line : Depends: build-essential but it is not going to be installed 337s Depends: ninja-build but it is not going to be installed 337s Depends: libtorch-dev but it is not going to be installed 337s Depends: libtorch-test but it is not going to be installed 337s E: Unable to satisfy dependencies. Reached two conflicting assignments: 337s 1. python3-dev:ppc64el is selected for install because: 337s 1. satisfy:command-line:ppc64el=1 is selected for install 337s 2. satisfy:command-line:ppc64el Depends libtorch-dev 337s 3. libtorch-dev:ppc64el Depends python3-dev 337s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 337s but none of the choices are installable: 337s - python3-dev:ppc64el=3.14.2-1 is not selected for install 337s - python3-dev:ppc64el=3.13.9-3 is not selected for install 337s autopkgtest [14:11:05]: test 35_of_104__cpptest__c10_TypeList_test: preparing testbed 337s 34_of_104__cpptest__c10_TypeIndex_test FAIL badpkg 337s blame: pytorch 337s 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. 338s Reading package lists... 338s Building dependency tree... 338s Reading state information... 338s Solving dependencies... 338s Some packages could not be installed. This may mean that you have 338s requested an impossible situation or if you are using the unstable 338s distribution that some required packages have not yet been created 338s or been moved out of Incoming. 338s The following information may help to resolve the situation: 338s 338s The following packages have unmet dependencies: 338s satisfy:command-line : Depends: build-essential but it is not going to be installed 338s Depends: ninja-build but it is not going to be installed 338s Depends: libtorch-dev but it is not going to be installed 338s Depends: libtorch-test but it is not going to be installed 338s E: Unable to satisfy dependencies. Reached two conflicting assignments: 338s 1. python3-dev:ppc64el is selected for install because: 338s 1. satisfy:command-line:ppc64el=1 is selected for install 338s 2. satisfy:command-line:ppc64el Depends libtorch-dev 338s 3. libtorch-dev:ppc64el Depends python3-dev 338s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 338s but none of the choices are installable: 338s - python3-dev:ppc64el=3.14.2-1 is not selected for install 338s - python3-dev:ppc64el=3.13.9-3 is not selected for install 338s autopkgtest [14:11:06]: test 36_of_104__cpptest__c10_TypeTraits_test: preparing testbed 338s 35_of_104__cpptest__c10_TypeList_test FAIL badpkg 338s blame: pytorch 338s 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. 338s Reading package lists... 338s Building dependency tree... 338s Reading state information... 338s Solving dependencies... 338s Some packages could not be installed. This may mean that you have 338s requested an impossible situation or if you are using the unstable 338s distribution that some required packages have not yet been created 338s or been moved out of Incoming. 338s The following information may help to resolve the situation: 338s 338s The following packages have unmet dependencies: 338s satisfy:command-line : Depends: build-essential but it is not going to be installed 338s Depends: ninja-build but it is not going to be installed 338s Depends: libtorch-dev but it is not going to be installed 338s Depends: libtorch-test but it is not going to be installed 338s E: Unable to satisfy dependencies. Reached two conflicting assignments: 338s 1. python3-dev:ppc64el is selected for install because: 338s 1. satisfy:command-line:ppc64el=1 is selected for install 338s 2. satisfy:command-line:ppc64el Depends libtorch-dev 338s 3. libtorch-dev:ppc64el Depends python3-dev 338s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 338s but none of the choices are installable: 338s - python3-dev:ppc64el=3.14.2-1 is not selected for install 338s - python3-dev:ppc64el=3.13.9-3 is not selected for install 338s 36_of_104__cpptest__c10_TypeTraits_test FAIL badpkg 338s blame: pytorch 338s autopkgtest [14:11:06]: test 37_of_104__cpptest__c10_accumulate_test: preparing testbed 338s 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. 338s Reading package lists... 339s Building dependency tree... 339s Reading state information... 339s Solving dependencies... 339s Some packages could not be installed. This may mean that you have 339s requested an impossible situation or if you are using the unstable 339s distribution that some required packages have not yet been created 339s or been moved out of Incoming. 339s The following information may help to resolve the situation: 339s 339s The following packages have unmet dependencies: 339s satisfy:command-line : Depends: build-essential but it is not going to be installed 339s Depends: ninja-build but it is not going to be installed 339s Depends: libtorch-dev but it is not going to be installed 339s Depends: libtorch-test but it is not going to be installed 339s E: Unable to satisfy dependencies. Reached two conflicting assignments: 339s 1. python3-dev:ppc64el is selected for install because: 339s 1. satisfy:command-line:ppc64el=1 is selected for install 339s 2. satisfy:command-line:ppc64el Depends libtorch-dev 339s 3. libtorch-dev:ppc64el Depends python3-dev 339s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 339s but none of the choices are installable: 339s - python3-dev:ppc64el=3.14.2-1 is not selected for install 339s - python3-dev:ppc64el=3.13.9-3 is not selected for install 339s 37_of_104__cpptest__c10_accumulate_test FAIL badpkg 339s blame: pytorch 339s 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. 339s autopkgtest [14:11:07]: test 38_of_104__cpptest__c10_bfloat16_test: preparing testbed 339s Reading package lists... 339s Building dependency tree... 339s Reading state information... 339s Solving dependencies... 339s Some packages could not be installed. This may mean that you have 339s requested an impossible situation or if you are using the unstable 339s distribution that some required packages have not yet been created 339s or been moved out of Incoming. 339s The following information may help to resolve the situation: 339s 339s The following packages have unmet dependencies: 339s satisfy:command-line : Depends: build-essential but it is not going to be installed 339s Depends: ninja-build but it is not going to be installed 339s Depends: libtorch-dev but it is not going to be installed 339s Depends: libtorch-test but it is not going to be installed 339s E: Unable to satisfy dependencies. Reached two conflicting assignments: 339s 1. python3-dev:ppc64el is selected for install because: 339s 1. satisfy:command-line:ppc64el=1 is selected for install 339s 2. satisfy:command-line:ppc64el Depends libtorch-dev 339s 3. libtorch-dev:ppc64el Depends python3-dev 339s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 339s but none of the choices are installable: 339s - python3-dev:ppc64el=3.14.2-1 is not selected for install 339s - python3-dev:ppc64el=3.13.9-3 is not selected for install 339s 38_of_104__cpptest__c10_bfloat16_test FAIL badpkg 339s blame: pytorch 339s 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. 339s autopkgtest [14:11:07]: test 39_of_104__cpptest__c10_bit_cast_test: preparing testbed 339s Reading package lists... 340s Building dependency tree... 340s Reading state information... 340s Solving dependencies... 340s Some packages could not be installed. This may mean that you have 340s requested an impossible situation or if you are using the unstable 340s distribution that some required packages have not yet been created 340s or been moved out of Incoming. 340s The following information may help to resolve the situation: 340s 340s The following packages have unmet dependencies: 340s satisfy:command-line : Depends: build-essential but it is not going to be installed 340s Depends: ninja-build but it is not going to be installed 340s Depends: libtorch-dev but it is not going to be installed 340s Depends: libtorch-test but it is not going to be installed 340s E: Unable to satisfy dependencies. Reached two conflicting assignments: 340s 1. python3-dev:ppc64el is selected for install because: 340s 1. satisfy:command-line:ppc64el=1 is selected for install 340s 2. satisfy:command-line:ppc64el Depends libtorch-dev 340s 3. libtorch-dev:ppc64el Depends python3-dev 340s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 340s but none of the choices are installable: 340s - python3-dev:ppc64el=3.14.2-1 is not selected for install 340s - python3-dev:ppc64el=3.13.9-3 is not selected for install 340s 39_of_104__cpptest__c10_bit_cast_test FAIL badpkg 340s blame: pytorch 340s 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. 340s autopkgtest [14:11:08]: test 40_of_104__cpptest__c10_complex_math_test: preparing testbed 340s Reading package lists... 340s Building dependency tree... 340s Reading state information... 340s Solving dependencies... 340s Some packages could not be installed. This may mean that you have 340s requested an impossible situation or if you are using the unstable 340s distribution that some required packages have not yet been created 340s or been moved out of Incoming. 340s The following information may help to resolve the situation: 340s 340s The following packages have unmet dependencies: 340s satisfy:command-line : Depends: build-essential but it is not going to be installed 340s Depends: ninja-build but it is not going to be installed 340s Depends: libtorch-dev but it is not going to be installed 340s Depends: libtorch-test but it is not going to be installed 340s E: Unable to satisfy dependencies. Reached two conflicting assignments: 340s 1. python3-dev:ppc64el is selected for install because: 340s 1. satisfy:command-line:ppc64el=1 is selected for install 340s 2. satisfy:command-line:ppc64el Depends libtorch-dev 340s 3. libtorch-dev:ppc64el Depends python3-dev 340s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 340s but none of the choices are installable: 340s - python3-dev:ppc64el=3.14.2-1 is not selected for install 340s - python3-dev:ppc64el=3.13.9-3 is not selected for install 340s 40_of_104__cpptest__c10_complex_math_test FAIL badpkg 340s blame: pytorch 340s 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. 340s autopkgtest [14:11:08]: test 41_of_104__cpptest__c10_complex_test: preparing testbed 340s Reading package lists... 341s Building dependency tree... 341s Reading state information... 341s Solving dependencies... 341s Some packages could not be installed. This may mean that you have 341s requested an impossible situation or if you are using the unstable 341s distribution that some required packages have not yet been created 341s or been moved out of Incoming. 341s The following information may help to resolve the situation: 341s 341s The following packages have unmet dependencies: 341s satisfy:command-line : Depends: build-essential but it is not going to be installed 341s Depends: ninja-build but it is not going to be installed 341s Depends: libtorch-dev but it is not going to be installed 341s Depends: libtorch-test but it is not going to be installed 341s E: Unable to satisfy dependencies. Reached two conflicting assignments: 341s 1. python3-dev:ppc64el is selected for install because: 341s 1. satisfy:command-line:ppc64el=1 is selected for install 341s 2. satisfy:command-line:ppc64el Depends libtorch-dev 341s 3. libtorch-dev:ppc64el Depends python3-dev 341s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 341s but none of the choices are installable: 341s - python3-dev:ppc64el=3.14.2-1 is not selected for install 341s - python3-dev:ppc64el=3.13.9-3 is not selected for install 341s 41_of_104__cpptest__c10_complex_test FAIL badpkg 341s blame: pytorch 341s 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. 341s autopkgtest [14:11:09]: test 42_of_104__cpptest__c10_cow_test: preparing testbed 341s Reading package lists... 341s Building dependency tree... 341s Reading state information... 341s Solving dependencies... 341s Some packages could not be installed. This may mean that you have 341s requested an impossible situation or if you are using the unstable 341s distribution that some required packages have not yet been created 341s or been moved out of Incoming. 341s The following information may help to resolve the situation: 341s 341s The following packages have unmet dependencies: 341s satisfy:command-line : Depends: build-essential but it is not going to be installed 341s Depends: ninja-build but it is not going to be installed 341s Depends: libtorch-dev but it is not going to be installed 341s Depends: libtorch-test but it is not going to be installed 341s E: Unable to satisfy dependencies. Reached two conflicting assignments: 341s 1. python3-dev:ppc64el is selected for install because: 341s 1. satisfy:command-line:ppc64el=1 is selected for install 341s 2. satisfy:command-line:ppc64el Depends libtorch-dev 341s 3. libtorch-dev:ppc64el Depends python3-dev 341s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 341s but none of the choices are installable: 341s - python3-dev:ppc64el=3.14.2-1 is not selected for install 341s - python3-dev:ppc64el=3.13.9-3 is not selected for install 341s autopkgtest [14:11:09]: test 43_of_104__cpptest__c10_exception_test: preparing testbed 341s 42_of_104__cpptest__c10_cow_test FAIL badpkg 341s blame: pytorch 341s 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. 341s Reading package lists... 342s Building dependency tree... 342s Reading state information... 342s Solving dependencies... 342s Some packages could not be installed. This may mean that you have 342s requested an impossible situation or if you are using the unstable 342s distribution that some required packages have not yet been created 342s or been moved out of Incoming. 342s The following information may help to resolve the situation: 342s 342s The following packages have unmet dependencies: 342s satisfy:command-line : Depends: build-essential but it is not going to be installed 342s Depends: ninja-build but it is not going to be installed 342s Depends: libtorch-dev but it is not going to be installed 342s Depends: libtorch-test but it is not going to be installed 342s E: Unable to satisfy dependencies. Reached two conflicting assignments: 342s 1. python3-dev:ppc64el is selected for install because: 342s 1. satisfy:command-line:ppc64el=1 is selected for install 342s 2. satisfy:command-line:ppc64el Depends libtorch-dev 342s 3. libtorch-dev:ppc64el Depends python3-dev 342s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 342s but none of the choices are installable: 342s - python3-dev:ppc64el=3.14.2-1 is not selected for install 342s - python3-dev:ppc64el=3.13.9-3 is not selected for install 342s autopkgtest [14:11:10]: test 44_of_104__cpptest__c10_flags_test: preparing testbed 342s 43_of_104__cpptest__c10_exception_test FAIL badpkg 342s blame: pytorch 342s 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. 342s Reading package lists... 342s Building dependency tree... 342s Reading state information... 342s Solving dependencies... 342s Some packages could not be installed. This may mean that you have 342s requested an impossible situation or if you are using the unstable 342s distribution that some required packages have not yet been created 342s or been moved out of Incoming. 342s The following information may help to resolve the situation: 342s 342s The following packages have unmet dependencies: 342s satisfy:command-line : Depends: build-essential but it is not going to be installed 342s Depends: ninja-build but it is not going to be installed 342s Depends: libtorch-dev but it is not going to be installed 342s Depends: libtorch-test but it is not going to be installed 342s E: Unable to satisfy dependencies. Reached two conflicting assignments: 342s 1. python3-dev:ppc64el is selected for install because: 342s 1. satisfy:command-line:ppc64el=1 is selected for install 342s 2. satisfy:command-line:ppc64el Depends libtorch-dev 342s 3. libtorch-dev:ppc64el Depends python3-dev 342s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 342s but none of the choices are installable: 342s - python3-dev:ppc64el=3.14.2-1 is not selected for install 342s - python3-dev:ppc64el=3.13.9-3 is not selected for install 342s 44_of_104__cpptest__c10_flags_test FAIL badpkg 342s blame: pytorch 342s 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. 342s autopkgtest [14:11:10]: test 45_of_104__cpptest__c10_generic_math_test: preparing testbed 342s Reading package lists... 342s Building dependency tree... 343s Reading state information... 343s Solving dependencies... 343s Some packages could not be installed. This may mean that you have 343s requested an impossible situation or if you are using the unstable 343s distribution that some required packages have not yet been created 343s or been moved out of Incoming. 343s The following information may help to resolve the situation: 343s 343s The following packages have unmet dependencies: 343s satisfy:command-line : Depends: build-essential but it is not going to be installed 343s Depends: ninja-build but it is not going to be installed 343s Depends: libtorch-dev but it is not going to be installed 343s Depends: libtorch-test but it is not going to be installed 343s E: Unable to satisfy dependencies. Reached two conflicting assignments: 343s 1. python3-dev:ppc64el is selected for install because: 343s 1. satisfy:command-line:ppc64el=1 is selected for install 343s 2. satisfy:command-line:ppc64el Depends libtorch-dev 343s 3. libtorch-dev:ppc64el Depends python3-dev 343s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 343s but none of the choices are installable: 343s - python3-dev:ppc64el=3.14.2-1 is not selected for install 343s - python3-dev:ppc64el=3.13.9-3 is not selected for install 343s 45_of_104__cpptest__c10_generic_math_test FAIL badpkg 343s blame: pytorch 343s 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. 343s autopkgtest [14:11:11]: test 46_of_104__cpptest__c10_intrusive_ptr_benchmark: preparing testbed 343s Reading package lists... 343s Building dependency tree... 343s Reading state information... 343s Solving dependencies... 343s Some packages could not be installed. This may mean that you have 343s requested an impossible situation or if you are using the unstable 343s distribution that some required packages have not yet been created 343s or been moved out of Incoming. 343s The following information may help to resolve the situation: 343s 343s The following packages have unmet dependencies: 343s satisfy:command-line : Depends: build-essential but it is not going to be installed 343s Depends: ninja-build but it is not going to be installed 343s Depends: libtorch-dev but it is not going to be installed 343s Depends: libtorch-test but it is not going to be installed 343s E: Unable to satisfy dependencies. Reached two conflicting assignments: 343s 1. python3-dev:ppc64el is selected for install because: 343s 1. satisfy:command-line:ppc64el=1 is selected for install 343s 2. satisfy:command-line:ppc64el Depends libtorch-dev 343s 3. libtorch-dev:ppc64el Depends python3-dev 343s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 343s but none of the choices are installable: 343s - python3-dev:ppc64el=3.14.2-1 is not selected for install 343s - python3-dev:ppc64el=3.13.9-3 is not selected for install 343s autopkgtest [14:11:11]: test 47_of_104__cpptest__c10_intrusive_ptr_test: preparing testbed 343s 46_of_104__cpptest__c10_intrusive_ptr_benchmark FAIL badpkg 343s blame: pytorch 343s 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. 343s Reading package lists... 343s Building dependency tree... 343s Reading state information... 344s Solving dependencies... 344s Some packages could not be installed. This may mean that you have 344s requested an impossible situation or if you are using the unstable 344s distribution that some required packages have not yet been created 344s or been moved out of Incoming. 344s The following information may help to resolve the situation: 344s 344s The following packages have unmet dependencies: 344s satisfy:command-line : Depends: build-essential but it is not going to be installed 344s Depends: ninja-build but it is not going to be installed 344s Depends: libtorch-dev but it is not going to be installed 344s Depends: libtorch-test but it is not going to be installed 344s E: Unable to satisfy dependencies. Reached two conflicting assignments: 344s 1. python3-dev:ppc64el is selected for install because: 344s 1. satisfy:command-line:ppc64el=1 is selected for install 344s 2. satisfy:command-line:ppc64el Depends libtorch-dev 344s 3. libtorch-dev:ppc64el Depends python3-dev 344s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 344s but none of the choices are installable: 344s - python3-dev:ppc64el=3.14.2-1 is not selected for install 344s - python3-dev:ppc64el=3.13.9-3 is not selected for install 344s autopkgtest [14:11:12]: test 48_of_104__cpptest__c10_irange_test: preparing testbed 344s 47_of_104__cpptest__c10_intrusive_ptr_test FAIL badpkg 344s blame: pytorch 344s 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. 344s Reading package lists... 344s Building dependency tree... 344s Reading state information... 344s Solving dependencies... 344s Some packages could not be installed. This may mean that you have 344s requested an impossible situation or if you are using the unstable 344s distribution that some required packages have not yet been created 344s or been moved out of Incoming. 344s The following information may help to resolve the situation: 344s 344s The following packages have unmet dependencies: 344s satisfy:command-line : Depends: build-essential but it is not going to be installed 344s Depends: ninja-build but it is not going to be installed 344s Depends: libtorch-dev but it is not going to be installed 344s Depends: libtorch-test but it is not going to be installed 344s E: Unable to satisfy dependencies. Reached two conflicting assignments: 344s 1. python3-dev:ppc64el is selected for install because: 344s 1. satisfy:command-line:ppc64el=1 is selected for install 344s 2. satisfy:command-line:ppc64el Depends libtorch-dev 344s 3. libtorch-dev:ppc64el Depends python3-dev 344s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 344s but none of the choices are installable: 344s - python3-dev:ppc64el=3.14.2-1 is not selected for install 344s - python3-dev:ppc64el=3.13.9-3 is not selected for install 344s autopkgtest [14:11:12]: test 49_of_104__cpptest__c10_lazy_test: preparing testbed 344s 48_of_104__cpptest__c10_irange_test FAIL badpkg 344s blame: pytorch 344s 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. 344s Reading package lists... 344s Building dependency tree... 344s Reading state information... 344s Solving dependencies... 344s Some packages could not be installed. This may mean that you have 344s requested an impossible situation or if you are using the unstable 344s distribution that some required packages have not yet been created 344s or been moved out of Incoming. 344s The following information may help to resolve the situation: 344s 344s The following packages have unmet dependencies: 345s satisfy:command-line : Depends: build-essential but it is not going to be installed 345s Depends: ninja-build but it is not going to be installed 345s Depends: libtorch-dev but it is not going to be installed 345s Depends: libtorch-test but it is not going to be installed 345s E: Unable to satisfy dependencies. Reached two conflicting assignments: 345s 1. python3-dev:ppc64el is selected for install because: 345s 1. satisfy:command-line:ppc64el=1 is selected for install 345s 2. satisfy:command-line:ppc64el Depends libtorch-dev 345s 3. libtorch-dev:ppc64el Depends python3-dev 345s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 345s but none of the choices are installable: 345s - python3-dev:ppc64el=3.14.2-1 is not selected for install 345s - python3-dev:ppc64el=3.13.9-3 is not selected for install 345s autopkgtest [14:11:13]: test 50_of_104__cpptest__c10_logging_test: preparing testbed 345s 49_of_104__cpptest__c10_lazy_test FAIL badpkg 345s blame: pytorch 345s 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. 345s Reading package lists... 345s Building dependency tree... 345s Reading state information... 345s Solving dependencies... 345s Some packages could not be installed. This may mean that you have 345s requested an impossible situation or if you are using the unstable 345s distribution that some required packages have not yet been created 345s or been moved out of Incoming. 345s The following information may help to resolve the situation: 345s 345s The following packages have unmet dependencies: 345s satisfy:command-line : Depends: build-essential but it is not going to be installed 345s Depends: ninja-build but it is not going to be installed 345s Depends: libtorch-dev but it is not going to be installed 345s Depends: libtorch-test but it is not going to be installed 345s E: Unable to satisfy dependencies. Reached two conflicting assignments: 345s 1. python3-dev:ppc64el is selected for install because: 345s 1. satisfy:command-line:ppc64el=1 is selected for install 345s 2. satisfy:command-line:ppc64el Depends libtorch-dev 345s 3. libtorch-dev:ppc64el Depends python3-dev 345s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 345s but none of the choices are installable: 345s - python3-dev:ppc64el=3.14.2-1 is not selected for install 345s - python3-dev:ppc64el=3.13.9-3 is not selected for install 345s 50_of_104__cpptest__c10_logging_test FAIL badpkg 345s blame: pytorch 345s 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. 345s autopkgtest [14:11:13]: test 51_of_104__cpptest__c10_optional_test: preparing testbed 345s Reading package lists... 345s Building dependency tree... 345s Reading state information... 345s Solving dependencies... 345s Some packages could not be installed. This may mean that you have 345s requested an impossible situation or if you are using the unstable 345s distribution that some required packages have not yet been created 345s or been moved out of Incoming. 345s The following information may help to resolve the situation: 345s 345s The following packages have unmet dependencies: 346s satisfy:command-line : Depends: build-essential but it is not going to be installed 346s Depends: ninja-build but it is not going to be installed 346s Depends: libtorch-dev but it is not going to be installed 346s Depends: libtorch-test but it is not going to be installed 346s E: Unable to satisfy dependencies. Reached two conflicting assignments: 346s 1. python3-dev:ppc64el is selected for install because: 346s 1. satisfy:command-line:ppc64el=1 is selected for install 346s 2. satisfy:command-line:ppc64el Depends libtorch-dev 346s 3. libtorch-dev:ppc64el Depends python3-dev 346s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 346s but none of the choices are installable: 346s - python3-dev:ppc64el=3.14.2-1 is not selected for install 346s - python3-dev:ppc64el=3.13.9-3 is not selected for install 346s 51_of_104__cpptest__c10_optional_test FAIL badpkg 346s blame: pytorch 346s 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. 346s autopkgtest [14:11:14]: test 52_of_104__cpptest__c10_ordered_preserving_dict_test: preparing testbed 346s Reading package lists... 346s Building dependency tree... 346s Reading state information... 346s Solving dependencies... 346s Some packages could not be installed. This may mean that you have 346s requested an impossible situation or if you are using the unstable 346s distribution that some required packages have not yet been created 346s or been moved out of Incoming. 346s The following information may help to resolve the situation: 346s 346s The following packages have unmet dependencies: 346s satisfy:command-line : Depends: build-essential but it is not going to be installed 346s Depends: ninja-build but it is not going to be installed 346s Depends: libtorch-dev but it is not going to be installed 346s Depends: libtorch-test but it is not going to be installed 346s E: Unable to satisfy dependencies. Reached two conflicting assignments: 346s 1. python3-dev:ppc64el is selected for install because: 346s 1. satisfy:command-line:ppc64el=1 is selected for install 346s 2. satisfy:command-line:ppc64el Depends libtorch-dev 346s 3. libtorch-dev:ppc64el Depends python3-dev 346s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 346s but none of the choices are installable: 346s - python3-dev:ppc64el=3.14.2-1 is not selected for install 346s - python3-dev:ppc64el=3.13.9-3 is not selected for install 346s autopkgtest [14:11:14]: test 53_of_104__cpptest__c10_registry_test: preparing testbed 346s 52_of_104__cpptest__c10_ordered_preserving_dict_test FAIL badpkg 346s blame: pytorch 346s 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. 346s Reading package lists... 346s Building dependency tree... 346s Reading state information... 346s Solving dependencies... 346s Some packages could not be installed. This may mean that you have 346s requested an impossible situation or if you are using the unstable 346s distribution that some required packages have not yet been created 346s or been moved out of Incoming. 346s The following information may help to resolve the situation: 346s 346s The following packages have unmet dependencies: 346s satisfy:command-line : Depends: build-essential but it is not going to be installed 346s Depends: ninja-build but it is not going to be installed 346s Depends: libtorch-dev but it is not going to be installed 346s Depends: libtorch-test but it is not going to be installed 346s E: Unable to satisfy dependencies. Reached two conflicting assignments: 346s 1. python3-dev:ppc64el is selected for install because: 346s 1. satisfy:command-line:ppc64el=1 is selected for install 346s 2. satisfy:command-line:ppc64el Depends libtorch-dev 346s 3. libtorch-dev:ppc64el Depends python3-dev 346s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 346s but none of the choices are installable: 346s - python3-dev:ppc64el=3.14.2-1 is not selected for install 346s - python3-dev:ppc64el=3.13.9-3 is not selected for install 346s 53_of_104__cpptest__c10_registry_test FAIL badpkg 346s blame: pytorch 346s 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. 346s autopkgtest [14:11:14]: test 54_of_104__cpptest__c10_small_vector_test: preparing testbed 347s Reading package lists... 347s Building dependency tree... 347s Reading state information... 347s Solving dependencies... 347s Some packages could not be installed. This may mean that you have 347s requested an impossible situation or if you are using the unstable 347s distribution that some required packages have not yet been created 347s or been moved out of Incoming. 347s The following information may help to resolve the situation: 347s 347s The following packages have unmet dependencies: 347s satisfy:command-line : Depends: build-essential but it is not going to be installed 347s Depends: ninja-build but it is not going to be installed 347s Depends: libtorch-dev but it is not going to be installed 347s Depends: libtorch-test but it is not going to be installed 347s E: Unable to satisfy dependencies. Reached two conflicting assignments: 347s 1. python3-dev:ppc64el is selected for install because: 347s 1. satisfy:command-line:ppc64el=1 is selected for install 347s 2. satisfy:command-line:ppc64el Depends libtorch-dev 347s 3. libtorch-dev:ppc64el Depends python3-dev 347s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 347s but none of the choices are installable: 347s - python3-dev:ppc64el=3.14.2-1 is not selected for install 347s - python3-dev:ppc64el=3.13.9-3 is not selected for install 347s 54_of_104__cpptest__c10_small_vector_test FAIL badpkg 347s blame: pytorch 347s 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. 347s autopkgtest [14:11:15]: test 55_of_104__cpptest__c10_ssize_test: preparing testbed 347s Reading package lists... 347s Building dependency tree... 347s Reading state information... 347s Solving dependencies... 347s Some packages could not be installed. This may mean that you have 347s requested an impossible situation or if you are using the unstable 347s distribution that some required packages have not yet been created 347s or been moved out of Incoming. 347s The following information may help to resolve the situation: 347s 347s The following packages have unmet dependencies: 347s satisfy:command-line : Depends: build-essential but it is not going to be installed 347s Depends: ninja-build but it is not going to be installed 347s Depends: libtorch-dev but it is not going to be installed 347s Depends: libtorch-test but it is not going to be installed 347s E: Unable to satisfy dependencies. Reached two conflicting assignments: 347s 1. python3-dev:ppc64el is selected for install because: 347s 1. satisfy:command-line:ppc64el=1 is selected for install 347s 2. satisfy:command-line:ppc64el Depends libtorch-dev 347s 3. libtorch-dev:ppc64el Depends python3-dev 347s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 347s but none of the choices are installable: 347s - python3-dev:ppc64el=3.14.2-1 is not selected for install 347s - python3-dev:ppc64el=3.13.9-3 is not selected for install 347s 55_of_104__cpptest__c10_ssize_test FAIL badpkg 347s blame: pytorch 347s 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. 347s autopkgtest [14:11:15]: test 56_of_104__cpptest__c10_string_util_test: preparing testbed 348s Reading package lists... 348s Building dependency tree... 348s Reading state information... 348s Solving dependencies... 348s Some packages could not be installed. This may mean that you have 348s requested an impossible situation or if you are using the unstable 348s distribution that some required packages have not yet been created 348s or been moved out of Incoming. 348s The following information may help to resolve the situation: 348s 348s The following packages have unmet dependencies: 348s satisfy:command-line : Depends: build-essential but it is not going to be installed 348s Depends: ninja-build but it is not going to be installed 348s Depends: libtorch-dev but it is not going to be installed 348s Depends: libtorch-test but it is not going to be installed 348s E: Unable to satisfy dependencies. Reached two conflicting assignments: 348s 1. python3-dev:ppc64el is selected for install because: 348s 1. satisfy:command-line:ppc64el=1 is selected for install 348s 2. satisfy:command-line:ppc64el Depends libtorch-dev 348s 3. libtorch-dev:ppc64el Depends python3-dev 348s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 348s but none of the choices are installable: 348s - python3-dev:ppc64el=3.14.2-1 is not selected for install 348s - python3-dev:ppc64el=3.13.9-3 is not selected for install 348s 56_of_104__cpptest__c10_string_util_test FAIL badpkg 348s blame: pytorch 348s 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. 348s autopkgtest [14:11:16]: test 57_of_104__cpptest__c10_string_view_test: preparing testbed 348s Reading package lists... 348s Building dependency tree... 348s Reading state information... 348s Solving dependencies... 348s Some packages could not be installed. This may mean that you have 348s requested an impossible situation or if you are using the unstable 348s distribution that some required packages have not yet been created 348s or been moved out of Incoming. 348s The following information may help to resolve the situation: 348s 348s The following packages have unmet dependencies: 348s satisfy:command-line : Depends: build-essential but it is not going to be installed 348s Depends: ninja-build but it is not going to be installed 348s Depends: libtorch-dev but it is not going to be installed 348s Depends: libtorch-test but it is not going to be installed 348s E: Unable to satisfy dependencies. Reached two conflicting assignments: 348s 1. python3-dev:ppc64el is selected for install because: 348s 1. satisfy:command-line:ppc64el=1 is selected for install 348s 2. satisfy:command-line:ppc64el Depends libtorch-dev 348s 3. libtorch-dev:ppc64el Depends python3-dev 348s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 348s but none of the choices are installable: 348s - python3-dev:ppc64el=3.14.2-1 is not selected for install 348s - python3-dev:ppc64el=3.13.9-3 is not selected for install 348s autopkgtest [14:11:16]: test 58_of_104__cpptest__c10_tempfile_test: preparing testbed 348s 57_of_104__cpptest__c10_string_view_test FAIL badpkg 348s blame: pytorch 348s 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. 349s Reading package lists... 349s Building dependency tree... 349s Reading state information... 349s Solving dependencies... 349s Some packages could not be installed. This may mean that you have 349s requested an impossible situation or if you are using the unstable 349s distribution that some required packages have not yet been created 349s or been moved out of Incoming. 349s The following information may help to resolve the situation: 349s 349s The following packages have unmet dependencies: 349s satisfy:command-line : Depends: build-essential but it is not going to be installed 349s Depends: ninja-build but it is not going to be installed 349s Depends: libtorch-dev but it is not going to be installed 349s Depends: libtorch-test but it is not going to be installed 349s E: Unable to satisfy dependencies. Reached two conflicting assignments: 349s 1. python3-dev:ppc64el is selected for install because: 349s 1. satisfy:command-line:ppc64el=1 is selected for install 349s 2. satisfy:command-line:ppc64el Depends libtorch-dev 349s 3. libtorch-dev:ppc64el Depends python3-dev 349s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 349s but none of the choices are installable: 349s - python3-dev:ppc64el=3.14.2-1 is not selected for install 349s - python3-dev:ppc64el=3.13.9-3 is not selected for install 349s autopkgtest [14:11:17]: test 59_of_104__cpptest__c10_typeid_test: preparing testbed 349s 58_of_104__cpptest__c10_tempfile_test FAIL badpkg 349s blame: pytorch 349s 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. 349s Reading package lists... 349s Building dependency tree... 349s Reading state information... 349s Solving dependencies... 349s Some packages could not be installed. This may mean that you have 349s requested an impossible situation or if you are using the unstable 349s distribution that some required packages have not yet been created 349s or been moved out of Incoming. 349s The following information may help to resolve the situation: 349s 349s The following packages have unmet dependencies: 349s satisfy:command-line : Depends: build-essential but it is not going to be installed 349s Depends: ninja-build but it is not going to be installed 349s Depends: libtorch-dev but it is not going to be installed 349s Depends: libtorch-test but it is not going to be installed 349s E: Unable to satisfy dependencies. Reached two conflicting assignments: 349s 1. python3-dev:ppc64el is selected for install because: 349s 1. satisfy:command-line:ppc64el=1 is selected for install 349s 2. satisfy:command-line:ppc64el Depends libtorch-dev 349s 3. libtorch-dev:ppc64el Depends python3-dev 349s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 349s but none of the choices are installable: 349s - python3-dev:ppc64el=3.14.2-1 is not selected for install 349s - python3-dev:ppc64el=3.13.9-3 is not selected for install 349s autopkgtest [14:11:17]: test 60_of_104__cpptest__cpu_allocator_test: preparing testbed 349s 59_of_104__cpptest__c10_typeid_test FAIL badpkg 349s blame: pytorch 349s 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. 350s Reading package lists... 350s Building dependency tree... 350s Reading state information... 350s Solving dependencies... 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 satisfy:command-line : Depends: build-essential but it is not going to be installed 350s Depends: ninja-build but it is not going to be installed 350s Depends: libtorch-dev but it is not going to be installed 350s Depends: libtorch-test but it is not going to be installed 350s E: Unable to satisfy dependencies. Reached two conflicting assignments: 350s 1. python3-dev:ppc64el is selected for install because: 350s 1. satisfy:command-line:ppc64el=1 is selected for install 350s 2. satisfy:command-line:ppc64el Depends libtorch-dev 350s 3. libtorch-dev:ppc64el Depends python3-dev 350s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 350s but none of the choices are installable: 350s - python3-dev:ppc64el=3.14.2-1 is not selected for install 350s - python3-dev:ppc64el=3.13.9-3 is not selected for install 350s autopkgtest [14:11:18]: test 61_of_104__cpptest__cpu_generator_test: preparing testbed 350s 60_of_104__cpptest__cpu_allocator_test FAIL badpkg 350s blame: pytorch 350s 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. 350s Reading package lists... 350s Building dependency tree... 350s Reading state information... 350s Solving dependencies... 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 satisfy:command-line : Depends: build-essential but it is not going to be installed 350s Depends: ninja-build but it is not going to be installed 350s Depends: libtorch-dev but it is not going to be installed 350s Depends: libtorch-test but it is not going to be installed 350s E: Unable to satisfy dependencies. Reached two conflicting assignments: 350s 1. python3-dev:ppc64el is selected for install because: 350s 1. satisfy:command-line:ppc64el=1 is selected for install 350s 2. satisfy:command-line:ppc64el Depends libtorch-dev 350s 3. libtorch-dev:ppc64el Depends python3-dev 350s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 350s but none of the choices are installable: 350s - python3-dev:ppc64el=3.14.2-1 is not selected for install 350s - python3-dev:ppc64el=3.13.9-3 is not selected for install 350s autopkgtest [14:11:18]: test 62_of_104__cpptest__cpu_profiling_allocator_test: preparing testbed 350s 61_of_104__cpptest__cpu_generator_test FAIL badpkg 350s blame: pytorch 350s 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 Reading package lists... 351s Building dependency tree... 351s Reading state information... 351s Solving dependencies... 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 satisfy:command-line : Depends: build-essential but it is not going to be installed 351s Depends: ninja-build but it is not going to be installed 351s Depends: libtorch-dev but it is not going to be installed 351s Depends: libtorch-test but it is not going to be installed 351s E: Unable to satisfy dependencies. Reached two conflicting assignments: 351s 1. python3-dev:ppc64el is selected for install because: 351s 1. satisfy:command-line:ppc64el=1 is selected for install 351s 2. satisfy:command-line:ppc64el Depends libtorch-dev 351s 3. libtorch-dev:ppc64el Depends python3-dev 351s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 351s but none of the choices are installable: 351s - python3-dev:ppc64el=3.14.2-1 is not selected for install 351s - python3-dev:ppc64el=3.13.9-3 is not selected for install 351s autopkgtest [14:11:19]: test 63_of_104__cpptest__cpu_rng_test: preparing testbed 351s 62_of_104__cpptest__cpu_profiling_allocator_test FAIL badpkg 351s blame: pytorch 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 Reading package lists... 351s Building dependency tree... 351s Reading state information... 351s Solving dependencies... 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 satisfy:command-line : Depends: build-essential but it is not going to be installed 351s Depends: ninja-build but it is not going to be installed 351s Depends: libtorch-dev but it is not going to be installed 351s Depends: libtorch-test but it is not going to be installed 351s E: Unable to satisfy dependencies. Reached two conflicting assignments: 351s 1. python3-dev:ppc64el is selected for install because: 351s 1. satisfy:command-line:ppc64el=1 is selected for install 351s 2. satisfy:command-line:ppc64el Depends libtorch-dev 351s 3. libtorch-dev:ppc64el Depends python3-dev 351s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 351s but none of the choices are installable: 351s - python3-dev:ppc64el=3.14.2-1 is not selected for install 351s - python3-dev:ppc64el=3.13.9-3 is not selected for install 351s autopkgtest [14:11:19]: test 64_of_104__cpptest__dispatch_key_set_test: preparing testbed 351s 63_of_104__cpptest__cpu_rng_test FAIL badpkg 351s blame: pytorch 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. 352s Reading package lists... 352s Building dependency tree... 352s Reading state information... 352s Solving dependencies... 352s Some packages could not be installed. This may mean that you have 352s requested an impossible situation or if you are using the unstable 352s distribution that some required packages have not yet been created 352s or been moved out of Incoming. 352s The following information may help to resolve the situation: 352s 352s The following packages have unmet dependencies: 352s satisfy:command-line : Depends: build-essential but it is not going to be installed 352s Depends: ninja-build but it is not going to be installed 352s Depends: libtorch-dev but it is not going to be installed 352s Depends: libtorch-test but it is not going to be installed 352s E: Unable to satisfy dependencies. Reached two conflicting assignments: 352s 1. python3-dev:ppc64el is selected for install because: 352s 1. satisfy:command-line:ppc64el=1 is selected for install 352s 2. satisfy:command-line:ppc64el Depends libtorch-dev 352s 3. libtorch-dev:ppc64el Depends python3-dev 352s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 352s but none of the choices are installable: 352s - python3-dev:ppc64el=3.14.2-1 is not selected for install 352s - python3-dev:ppc64el=3.13.9-3 is not selected for install 352s autopkgtest [14:11:20]: test 65_of_104__cpptest__dlconvertor_test: preparing testbed 352s 64_of_104__cpptest__dispatch_key_set_test FAIL badpkg 352s blame: pytorch 352s 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. 352s Reading package lists... 352s Building dependency tree... 352s Reading state information... 352s Solving dependencies... 352s Some packages could not be installed. This may mean that you have 352s requested an impossible situation or if you are using the unstable 352s distribution that some required packages have not yet been created 352s or been moved out of Incoming. 352s The following information may help to resolve the situation: 352s 352s The following packages have unmet dependencies: 352s satisfy:command-line : Depends: build-essential but it is not going to be installed 352s Depends: ninja-build but it is not going to be installed 352s Depends: libtorch-dev but it is not going to be installed 352s Depends: libtorch-test but it is not going to be installed 352s E: Unable to satisfy dependencies. Reached two conflicting assignments: 352s 1. python3-dev:ppc64el is selected for install because: 352s 1. satisfy:command-line:ppc64el=1 is selected for install 352s 2. satisfy:command-line:ppc64el Depends libtorch-dev 352s 3. libtorch-dev:ppc64el Depends python3-dev 352s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 352s but none of the choices are installable: 352s - python3-dev:ppc64el=3.14.2-1 is not selected for install 352s - python3-dev:ppc64el=3.13.9-3 is not selected for install 352s autopkgtest [14:11:20]: test 66_of_104__cpptest__extension_backend_test: preparing testbed 352s 65_of_104__cpptest__dlconvertor_test FAIL badpkg 352s blame: pytorch 352s 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. 352s Reading package lists... 353s Building dependency tree... 353s Reading state information... 353s Solving dependencies... 353s Some packages could not be installed. This may mean that you have 353s requested an impossible situation or if you are using the unstable 353s distribution that some required packages have not yet been created 353s or been moved out of Incoming. 353s The following information may help to resolve the situation: 353s 353s The following packages have unmet dependencies: 353s satisfy:command-line : Depends: build-essential but it is not going to be installed 353s Depends: ninja-build but it is not going to be installed 353s Depends: libtorch-dev but it is not going to be installed 353s Depends: libtorch-test but it is not going to be installed 353s E: Unable to satisfy dependencies. Reached two conflicting assignments: 353s 1. python3-dev:ppc64el is selected for install because: 353s 1. satisfy:command-line:ppc64el=1 is selected for install 353s 2. satisfy:command-line:ppc64el Depends libtorch-dev 353s 3. libtorch-dev:ppc64el Depends python3-dev 353s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 353s but none of the choices are installable: 353s - python3-dev:ppc64el=3.14.2-1 is not selected for install 353s - python3-dev:ppc64el=3.13.9-3 is not selected for install 353s autopkgtest [14:11:21]: test 67_of_104__cpptest__half_test: preparing testbed 353s 66_of_104__cpptest__extension_backend_test FAIL badpkg 353s blame: pytorch 353s 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. 353s Reading package lists... 353s Building dependency tree... 353s Reading state information... 353s Solving dependencies... 353s Some packages could not be installed. This may mean that you have 353s requested an impossible situation or if you are using the unstable 353s distribution that some required packages have not yet been created 353s or been moved out of Incoming. 353s The following information may help to resolve the situation: 353s 353s The following packages have unmet dependencies: 353s satisfy:command-line : Depends: build-essential but it is not going to be installed 353s Depends: ninja-build but it is not going to be installed 353s Depends: libtorch-dev but it is not going to be installed 353s Depends: libtorch-test but it is not going to be installed 353s E: Unable to satisfy dependencies. Reached two conflicting assignments: 353s 1. python3-dev:ppc64el is selected for install because: 353s 1. satisfy:command-line:ppc64el=1 is selected for install 353s 2. satisfy:command-line:ppc64el Depends libtorch-dev 353s 3. libtorch-dev:ppc64el Depends python3-dev 353s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 353s but none of the choices are installable: 353s - python3-dev:ppc64el=3.14.2-1 is not selected for install 353s - python3-dev:ppc64el=3.13.9-3 is not selected for install 353s autopkgtest [14:11:21]: test 68_of_104__cpptest__inline_container_test: preparing testbed 353s 67_of_104__cpptest__half_test FAIL badpkg 353s blame: pytorch 353s 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. 353s Reading package lists... 354s Building dependency tree... 354s Reading state information... 354s Solving dependencies... 354s Some packages could not be installed. This may mean that you have 354s requested an impossible situation or if you are using the unstable 354s distribution that some required packages have not yet been created 354s or been moved out of Incoming. 354s The following information may help to resolve the situation: 354s 354s The following packages have unmet dependencies: 354s satisfy:command-line : Depends: build-essential but it is not going to be installed 354s Depends: ninja-build but it is not going to be installed 354s Depends: libtorch-dev but it is not going to be installed 354s Depends: libtorch-test but it is not going to be installed 354s E: Unable to satisfy dependencies. Reached two conflicting assignments: 354s 1. python3-dev:ppc64el is selected for install because: 354s 1. satisfy:command-line:ppc64el=1 is selected for install 354s 2. satisfy:command-line:ppc64el Depends libtorch-dev 354s 3. libtorch-dev:ppc64el Depends python3-dev 354s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 354s but none of the choices are installable: 354s - python3-dev:ppc64el=3.14.2-1 is not selected for install 354s - python3-dev:ppc64el=3.13.9-3 is not selected for install 354s autopkgtest [14:11:22]: test 69_of_104__cpptest__ivalue_test: preparing testbed 354s 68_of_104__cpptest__inline_container_test FAIL badpkg 354s blame: pytorch 354s 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. 354s Reading package lists... 354s Building dependency tree... 354s Reading state information... 354s Solving dependencies... 354s Some packages could not be installed. This may mean that you have 354s requested an impossible situation or if you are using the unstable 354s distribution that some required packages have not yet been created 354s or been moved out of Incoming. 354s The following information may help to resolve the situation: 354s 354s The following packages have unmet dependencies: 354s satisfy:command-line : Depends: build-essential but it is not going to be installed 354s Depends: ninja-build but it is not going to be installed 354s Depends: libtorch-dev but it is not going to be installed 354s Depends: libtorch-test but it is not going to be installed 354s E: Unable to satisfy dependencies. Reached two conflicting assignments: 354s 1. python3-dev:ppc64el is selected for install because: 354s 1. satisfy:command-line:ppc64el=1 is selected for install 354s 2. satisfy:command-line:ppc64el Depends libtorch-dev 354s 3. libtorch-dev:ppc64el Depends python3-dev 354s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 354s but none of the choices are installable: 354s - python3-dev:ppc64el=3.14.2-1 is not selected for install 354s - python3-dev:ppc64el=3.13.9-3 is not selected for install 354s autopkgtest [14:11:22]: test 70_of_104__cpptest__kernel_function_legacy_test: preparing testbed 354s 69_of_104__cpptest__ivalue_test FAIL badpkg 354s blame: pytorch 354s 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. 354s Reading package lists... 355s Building dependency tree... 355s Reading state information... 355s Solving dependencies... 355s Some packages could not be installed. This may mean that you have 355s requested an impossible situation or if you are using the unstable 355s distribution that some required packages have not yet been created 355s or been moved out of Incoming. 355s The following information may help to resolve the situation: 355s 355s The following packages have unmet dependencies: 355s satisfy:command-line : Depends: build-essential but it is not going to be installed 355s Depends: ninja-build but it is not going to be installed 355s Depends: libtorch-dev but it is not going to be installed 355s Depends: libtorch-test but it is not going to be installed 355s E: Unable to satisfy dependencies. Reached two conflicting assignments: 355s 1. python3-dev:ppc64el is selected for install because: 355s 1. satisfy:command-line:ppc64el=1 is selected for install 355s 2. satisfy:command-line:ppc64el Depends libtorch-dev 355s 3. libtorch-dev:ppc64el Depends python3-dev 355s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 355s but none of the choices are installable: 355s - python3-dev:ppc64el=3.14.2-1 is not selected for install 355s - python3-dev:ppc64el=3.13.9-3 is not selected for install 355s autopkgtest [14:11:23]: test 71_of_104__cpptest__kernel_function_test: preparing testbed 355s 70_of_104__cpptest__kernel_function_legacy_test FAIL badpkg 355s blame: pytorch 355s 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. 355s Reading package lists... 355s Building dependency tree... 355s Reading state information... 355s Solving dependencies... 355s Some packages could not be installed. This may mean that you have 355s requested an impossible situation or if you are using the unstable 355s distribution that some required packages have not yet been created 355s or been moved out of Incoming. 355s The following information may help to resolve the situation: 355s 355s The following packages have unmet dependencies: 355s satisfy:command-line : Depends: build-essential but it is not going to be installed 355s Depends: ninja-build but it is not going to be installed 355s Depends: libtorch-dev but it is not going to be installed 355s Depends: libtorch-test but it is not going to be installed 355s E: Unable to satisfy dependencies. Reached two conflicting assignments: 355s 1. python3-dev:ppc64el is selected for install because: 355s 1. satisfy:command-line:ppc64el=1 is selected for install 355s 2. satisfy:command-line:ppc64el Depends libtorch-dev 355s 3. libtorch-dev:ppc64el Depends python3-dev 355s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 355s but none of the choices are installable: 355s - python3-dev:ppc64el=3.14.2-1 is not selected for install 355s - python3-dev:ppc64el=3.13.9-3 is not selected for install 355s autopkgtest [14:11:23]: test 72_of_104__cpptest__kernel_lambda_legacy_test: preparing testbed 355s 71_of_104__cpptest__kernel_function_test FAIL badpkg 355s blame: pytorch 355s 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. 355s Reading package lists... 356s Building dependency tree... 356s Reading state information... 356s Solving dependencies... 356s Some packages could not be installed. This may mean that you have 356s requested an impossible situation or if you are using the unstable 356s distribution that some required packages have not yet been created 356s or been moved out of Incoming. 356s The following information may help to resolve the situation: 356s 356s The following packages have unmet dependencies: 356s satisfy:command-line : Depends: build-essential but it is not going to be installed 356s Depends: ninja-build but it is not going to be installed 356s Depends: libtorch-dev but it is not going to be installed 356s Depends: libtorch-test but it is not going to be installed 356s E: Unable to satisfy dependencies. Reached two conflicting assignments: 356s 1. python3-dev:ppc64el is selected for install because: 356s 1. satisfy:command-line:ppc64el=1 is selected for install 356s 2. satisfy:command-line:ppc64el Depends libtorch-dev 356s 3. libtorch-dev:ppc64el Depends python3-dev 356s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 356s but none of the choices are installable: 356s - python3-dev:ppc64el=3.14.2-1 is not selected for install 356s - python3-dev:ppc64el=3.13.9-3 is not selected for install 356s autopkgtest [14:11:24]: test 73_of_104__cpptest__kernel_lambda_test: preparing testbed 356s 72_of_104__cpptest__kernel_lambda_legacy_test FAIL badpkg 356s blame: pytorch 356s 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. 356s Reading package lists... 356s Building dependency tree... 356s Reading state information... 356s Solving dependencies... 356s Some packages could not be installed. This may mean that you have 356s requested an impossible situation or if you are using the unstable 356s distribution that some required packages have not yet been created 356s or been moved out of Incoming. 356s The following information may help to resolve the situation: 356s 356s The following packages have unmet dependencies: 356s satisfy:command-line : Depends: build-essential but it is not going to be installed 356s Depends: ninja-build but it is not going to be installed 356s Depends: libtorch-dev but it is not going to be installed 356s Depends: libtorch-test but it is not going to be installed 356s E: Unable to satisfy dependencies. Reached two conflicting assignments: 356s 1. python3-dev:ppc64el is selected for install because: 356s 1. satisfy:command-line:ppc64el=1 is selected for install 356s 2. satisfy:command-line:ppc64el Depends libtorch-dev 356s 3. libtorch-dev:ppc64el Depends python3-dev 356s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 356s but none of the choices are installable: 356s - python3-dev:ppc64el=3.14.2-1 is not selected for install 356s - python3-dev:ppc64el=3.13.9-3 is not selected for install 356s autopkgtest [14:11:24]: test 74_of_104__cpptest__kernel_stackbased_test: preparing testbed 356s 73_of_104__cpptest__kernel_lambda_test FAIL badpkg 356s blame: pytorch 356s 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. 356s Reading package lists... 357s Building dependency tree... 357s Reading state information... 357s Solving dependencies... 357s Some packages could not be installed. This may mean that you have 357s requested an impossible situation or if you are using the unstable 357s distribution that some required packages have not yet been created 357s or been moved out of Incoming. 357s The following information may help to resolve the situation: 357s 357s The following packages have unmet dependencies: 357s satisfy:command-line : Depends: build-essential but it is not going to be installed 357s Depends: ninja-build but it is not going to be installed 357s Depends: libtorch-dev but it is not going to be installed 357s Depends: libtorch-test but it is not going to be installed 357s E: Unable to satisfy dependencies. Reached two conflicting assignments: 357s 1. python3-dev:ppc64el is selected for install because: 357s 1. satisfy:command-line:ppc64el=1 is selected for install 357s 2. satisfy:command-line:ppc64el Depends libtorch-dev 357s 3. libtorch-dev:ppc64el Depends python3-dev 357s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 357s but none of the choices are installable: 357s - python3-dev:ppc64el=3.14.2-1 is not selected for install 357s - python3-dev:ppc64el=3.13.9-3 is not selected for install 357s 74_of_104__cpptest__kernel_stackbased_test FAIL badpkg 357s blame: pytorch 357s 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. 357s autopkgtest [14:11:25]: test 75_of_104__cpptest__lazy_tensor_test: preparing testbed 357s Reading package lists... 357s Building dependency tree... 357s Reading state information... 357s Solving dependencies... 357s Some packages could not be installed. This may mean that you have 357s requested an impossible situation or if you are using the unstable 357s distribution that some required packages have not yet been created 357s or been moved out of Incoming. 357s The following information may help to resolve the situation: 357s 357s The following packages have unmet dependencies: 357s satisfy:command-line : Depends: build-essential but it is not going to be installed 357s Depends: ninja-build but it is not going to be installed 357s Depends: libtorch-dev but it is not going to be installed 357s Depends: libtorch-test but it is not going to be installed 357s E: Unable to satisfy dependencies. Reached two conflicting assignments: 357s 1. python3-dev:ppc64el is selected for install because: 357s 1. satisfy:command-line:ppc64el=1 is selected for install 357s 2. satisfy:command-line:ppc64el Depends libtorch-dev 357s 3. libtorch-dev:ppc64el Depends python3-dev 357s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 357s but none of the choices are installable: 357s - python3-dev:ppc64el=3.14.2-1 is not selected for install 357s - python3-dev:ppc64el=3.13.9-3 is not selected for install 357s autopkgtest [14:11:25]: test 76_of_104__cpptest__legacy_vmap_test: preparing testbed 357s 75_of_104__cpptest__lazy_tensor_test FAIL badpkg 357s blame: pytorch 357s 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. 357s Reading package lists... 358s Building dependency tree... 358s Reading state information... 358s Solving dependencies... 358s Some packages could not be installed. This may mean that you have 358s requested an impossible situation or if you are using the unstable 358s distribution that some required packages have not yet been created 358s or been moved out of Incoming. 358s The following information may help to resolve the situation: 358s 358s The following packages have unmet dependencies: 358s satisfy:command-line : Depends: build-essential but it is not going to be installed 358s Depends: ninja-build but it is not going to be installed 358s Depends: libtorch-dev but it is not going to be installed 358s Depends: libtorch-test but it is not going to be installed 358s E: Unable to satisfy dependencies. Reached two conflicting assignments: 358s 1. python3-dev:ppc64el is selected for install because: 358s 1. satisfy:command-line:ppc64el=1 is selected for install 358s 2. satisfy:command-line:ppc64el Depends libtorch-dev 358s 3. libtorch-dev:ppc64el Depends python3-dev 358s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 358s but none of the choices are installable: 358s - python3-dev:ppc64el=3.14.2-1 is not selected for install 358s - python3-dev:ppc64el=3.13.9-3 is not selected for install 358s 76_of_104__cpptest__legacy_vmap_test FAIL badpkg 358s autopkgtest [14:11:26]: test 77_of_104__cpptest__make_boxed_from_unboxed_functor_test: preparing testbed 358s blame: pytorch 358s 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. 358s Reading package lists... 358s Building dependency tree... 358s Reading state information... 358s Solving dependencies... 358s Some packages could not be installed. This may mean that you have 358s requested an impossible situation or if you are using the unstable 358s distribution that some required packages have not yet been created 358s or been moved out of Incoming. 358s The following information may help to resolve the situation: 358s 358s The following packages have unmet dependencies: 358s satisfy:command-line : Depends: build-essential but it is not going to be installed 358s Depends: ninja-build but it is not going to be installed 358s Depends: libtorch-dev but it is not going to be installed 358s Depends: libtorch-test but it is not going to be installed 358s E: Unable to satisfy dependencies. Reached two conflicting assignments: 358s 1. python3-dev:ppc64el is selected for install because: 358s 1. satisfy:command-line:ppc64el=1 is selected for install 358s 2. satisfy:command-line:ppc64el Depends libtorch-dev 358s 3. libtorch-dev:ppc64el Depends python3-dev 358s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 358s but none of the choices are installable: 358s - python3-dev:ppc64el=3.14.2-1 is not selected for install 358s - python3-dev:ppc64el=3.13.9-3 is not selected for install 358s autopkgtest [14:11:26]: test 78_of_104__cpptest__math_kernel_test: preparing testbed 358s 77_of_104__cpptest__make_boxed_from_unboxed_functor_test FAIL badpkg 358s blame: pytorch 358s 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. 358s Reading package lists... 359s Building dependency tree... 359s Reading state information... 359s Solving dependencies... 359s Some packages could not be installed. This may mean that you have 359s requested an impossible situation or if you are using the unstable 359s distribution that some required packages have not yet been created 359s or been moved out of Incoming. 359s The following information may help to resolve the situation: 359s 359s The following packages have unmet dependencies: 359s satisfy:command-line : Depends: build-essential but it is not going to be installed 359s Depends: ninja-build but it is not going to be installed 359s Depends: libtorch-dev but it is not going to be installed 359s Depends: libtorch-test but it is not going to be installed 359s E: Unable to satisfy dependencies. Reached two conflicting assignments: 359s 1. python3-dev:ppc64el is selected for install because: 359s 1. satisfy:command-line:ppc64el=1 is selected for install 359s 2. satisfy:command-line:ppc64el Depends libtorch-dev 359s 3. libtorch-dev:ppc64el Depends python3-dev 359s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 359s but none of the choices are installable: 359s - python3-dev:ppc64el=3.14.2-1 is not selected for install 359s - python3-dev:ppc64el=3.13.9-3 is not selected for install 359s autopkgtest [14:11:27]: test 79_of_104__cpptest__memory_format_test: preparing testbed 359s 78_of_104__cpptest__math_kernel_test FAIL badpkg 359s blame: pytorch 359s 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. 359s Reading package lists... 359s Building dependency tree... 359s Reading state information... 359s Solving dependencies... 359s Some packages could not be installed. This may mean that you have 359s requested an impossible situation or if you are using the unstable 359s distribution that some required packages have not yet been created 359s or been moved out of Incoming. 359s The following information may help to resolve the situation: 359s 359s The following packages have unmet dependencies: 359s satisfy:command-line : Depends: build-essential but it is not going to be installed 359s Depends: ninja-build but it is not going to be installed 359s Depends: libtorch-dev but it is not going to be installed 359s Depends: libtorch-test but it is not going to be installed 359s E: Unable to satisfy dependencies. Reached two conflicting assignments: 359s 1. python3-dev:ppc64el is selected for install because: 359s 1. satisfy:command-line:ppc64el=1 is selected for install 359s 2. satisfy:command-line:ppc64el Depends libtorch-dev 359s 3. libtorch-dev:ppc64el Depends python3-dev 359s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 359s but none of the choices are installable: 359s - python3-dev:ppc64el=3.14.2-1 is not selected for install 359s - python3-dev:ppc64el=3.13.9-3 is not selected for install 359s autopkgtest [14:11:27]: test 80_of_104__cpptest__memory_overlapping_test: preparing testbed 359s 79_of_104__cpptest__memory_format_test FAIL badpkg 359s blame: pytorch 359s 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. 359s Reading package lists... 359s Building dependency tree... 360s Reading state information... 360s Solving dependencies... 360s Some packages could not be installed. This may mean that you have 360s requested an impossible situation or if you are using the unstable 360s distribution that some required packages have not yet been created 360s or been moved out of Incoming. 360s The following information may help to resolve the situation: 360s 360s The following packages have unmet dependencies: 360s satisfy:command-line : Depends: build-essential but it is not going to be installed 360s Depends: ninja-build but it is not going to be installed 360s Depends: libtorch-dev but it is not going to be installed 360s Depends: libtorch-test but it is not going to be installed 360s E: Unable to satisfy dependencies. Reached two conflicting assignments: 360s 1. python3-dev:ppc64el is selected for install because: 360s 1. satisfy:command-line:ppc64el=1 is selected for install 360s 2. satisfy:command-line:ppc64el Depends libtorch-dev 360s 3. libtorch-dev:ppc64el Depends python3-dev 360s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 360s but none of the choices are installable: 360s - python3-dev:ppc64el=3.14.2-1 is not selected for install 360s - python3-dev:ppc64el=3.13.9-3 is not selected for install 360s autopkgtest [14:11:28]: test 81_of_104__cpptest__mobile_memory_cleanup: preparing testbed 360s 80_of_104__cpptest__memory_overlapping_test FAIL badpkg 360s blame: pytorch 360s 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. 360s Reading package lists... 360s Building dependency tree... 360s Reading state information... 360s Solving dependencies... 360s Some packages could not be installed. This may mean that you have 360s requested an impossible situation or if you are using the unstable 360s distribution that some required packages have not yet been created 360s or been moved out of Incoming. 360s The following information may help to resolve the situation: 360s 360s The following packages have unmet dependencies: 360s satisfy:command-line : Depends: build-essential but it is not going to be installed 360s Depends: ninja-build but it is not going to be installed 360s Depends: libtorch-dev but it is not going to be installed 360s Depends: libtorch-test but it is not going to be installed 360s E: Unable to satisfy dependencies. Reached two conflicting assignments: 360s 1. python3-dev:ppc64el is selected for install because: 360s 1. satisfy:command-line:ppc64el=1 is selected for install 360s 2. satisfy:command-line:ppc64el Depends libtorch-dev 360s 3. libtorch-dev:ppc64el Depends python3-dev 360s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 360s but none of the choices are installable: 360s - python3-dev:ppc64el=3.14.2-1 is not selected for install 360s - python3-dev:ppc64el=3.13.9-3 is not selected for install 360s autopkgtest [14:11:28]: test 82_of_104__cpptest__native_test: preparing testbed 360s 81_of_104__cpptest__mobile_memory_cleanup FAIL badpkg 360s blame: pytorch 360s 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. 360s Reading package lists... 360s Building dependency tree... 360s Reading state information... 361s Solving dependencies... 361s Some packages could not be installed. This may mean that you have 361s requested an impossible situation or if you are using the unstable 361s distribution that some required packages have not yet been created 361s or been moved out of Incoming. 361s The following information may help to resolve the situation: 361s 361s The following packages have unmet dependencies: 361s satisfy:command-line : Depends: build-essential but it is not going to be installed 361s Depends: ninja-build but it is not going to be installed 361s Depends: libtorch-dev but it is not going to be installed 361s Depends: libtorch-test but it is not going to be installed 361s E: Unable to satisfy dependencies. Reached two conflicting assignments: 361s 1. python3-dev:ppc64el is selected for install because: 361s 1. satisfy:command-line:ppc64el=1 is selected for install 361s 2. satisfy:command-line:ppc64el Depends libtorch-dev 361s 3. libtorch-dev:ppc64el Depends python3-dev 361s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 361s but none of the choices are installable: 361s - python3-dev:ppc64el=3.14.2-1 is not selected for install 361s - python3-dev:ppc64el=3.13.9-3 is not selected for install 361s autopkgtest [14:11:29]: test 83_of_104__cpptest__op_allowlist_test: preparing testbed 361s 82_of_104__cpptest__native_test FAIL badpkg 361s blame: pytorch 361s 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. 361s Reading package lists... 361s Building dependency tree... 361s Reading state information... 361s Solving dependencies... 361s Some packages could not be installed. This may mean that you have 361s requested an impossible situation or if you are using the unstable 361s distribution that some required packages have not yet been created 361s or been moved out of Incoming. 361s The following information may help to resolve the situation: 361s 361s The following packages have unmet dependencies: 361s satisfy:command-line : Depends: build-essential but it is not going to be installed 361s Depends: ninja-build but it is not going to be installed 361s Depends: libtorch-dev but it is not going to be installed 361s Depends: libtorch-test but it is not going to be installed 361s E: Unable to satisfy dependencies. Reached two conflicting assignments: 361s 1. python3-dev:ppc64el is selected for install because: 361s 1. satisfy:command-line:ppc64el=1 is selected for install 361s 2. satisfy:command-line:ppc64el Depends libtorch-dev 361s 3. libtorch-dev:ppc64el Depends python3-dev 361s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 361s but none of the choices are installable: 361s - python3-dev:ppc64el=3.14.2-1 is not selected for install 361s - python3-dev:ppc64el=3.13.9-3 is not selected for install 361s autopkgtest [14:11:29]: test 84_of_104__cpptest__op_registration_test: preparing testbed 361s 83_of_104__cpptest__op_allowlist_test FAIL badpkg 361s blame: pytorch 361s 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. 361s Reading package lists... 361s Building dependency tree... 361s Reading state information... 362s Solving dependencies... 362s Some packages could not be installed. This may mean that you have 362s requested an impossible situation or if you are using the unstable 362s distribution that some required packages have not yet been created 362s or been moved out of Incoming. 362s The following information may help to resolve the situation: 362s 362s The following packages have unmet dependencies: 362s satisfy:command-line : Depends: build-essential but it is not going to be installed 362s Depends: ninja-build but it is not going to be installed 362s Depends: libtorch-dev but it is not going to be installed 362s Depends: libtorch-test but it is not going to be installed 362s E: Unable to satisfy dependencies. Reached two conflicting assignments: 362s 1. python3-dev:ppc64el is selected for install because: 362s 1. satisfy:command-line:ppc64el=1 is selected for install 362s 2. satisfy:command-line:ppc64el Depends libtorch-dev 362s 3. libtorch-dev:ppc64el Depends python3-dev 362s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 362s but none of the choices are installable: 362s - python3-dev:ppc64el=3.14.2-1 is not selected for install 362s - python3-dev:ppc64el=3.13.9-3 is not selected for install 362s 84_of_104__cpptest__op_registration_test FAIL badpkg 362s blame: pytorch 362s 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. 362s autopkgtest [14:11:30]: test 85_of_104__cpptest__operator_name_test: preparing testbed 362s Reading package lists... 362s Building dependency tree... 362s Reading state information... 362s Solving dependencies... 362s Some packages could not be installed. This may mean that you have 362s requested an impossible situation or if you are using the unstable 362s distribution that some required packages have not yet been created 362s or been moved out of Incoming. 362s The following information may help to resolve the situation: 362s 362s The following packages have unmet dependencies: 362s satisfy:command-line : Depends: build-essential but it is not going to be installed 362s Depends: ninja-build but it is not going to be installed 362s Depends: libtorch-dev but it is not going to be installed 362s Depends: libtorch-test but it is not going to be installed 362s E: Unable to satisfy dependencies. Reached two conflicting assignments: 362s 1. python3-dev:ppc64el is selected for install because: 362s 1. satisfy:command-line:ppc64el=1 is selected for install 362s 2. satisfy:command-line:ppc64el Depends libtorch-dev 362s 3. libtorch-dev:ppc64el Depends python3-dev 362s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 362s but none of the choices are installable: 362s - python3-dev:ppc64el=3.14.2-1 is not selected for install 362s - python3-dev:ppc64el=3.13.9-3 is not selected for install 362s autopkgtest [14:11:30]: test 86_of_104__cpptest__operators_test: preparing testbed 362s 85_of_104__cpptest__operator_name_test FAIL badpkg 362s blame: pytorch 362s 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. 362s Reading package lists... 362s Building dependency tree... 362s Reading state information... 363s Solving dependencies... 363s Some packages could not be installed. This may mean that you have 363s requested an impossible situation or if you are using the unstable 363s distribution that some required packages have not yet been created 363s or been moved out of Incoming. 363s The following information may help to resolve the situation: 363s 363s The following packages have unmet dependencies: 363s satisfy:command-line : Depends: build-essential but it is not going to be installed 363s Depends: ninja-build but it is not going to be installed 363s Depends: libtorch-dev but it is not going to be installed 363s Depends: libtorch-test but it is not going to be installed 363s E: Unable to satisfy dependencies. Reached two conflicting assignments: 363s 1. python3-dev:ppc64el is selected for install because: 363s 1. satisfy:command-line:ppc64el=1 is selected for install 363s 2. satisfy:command-line:ppc64el Depends libtorch-dev 363s 3. libtorch-dev:ppc64el Depends python3-dev 363s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 363s but none of the choices are installable: 363s - python3-dev:ppc64el=3.14.2-1 is not selected for install 363s - python3-dev:ppc64el=3.13.9-3 is not selected for install 363s autopkgtest [14:11:31]: test 87_of_104__cpptest__packedtensoraccessor_test: preparing testbed 363s 86_of_104__cpptest__operators_test FAIL badpkg 363s blame: pytorch 363s 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 Reading package lists... 363s Building dependency tree... 363s Reading state information... 363s Solving dependencies... 363s Some packages could not be installed. This may mean that you have 363s requested an impossible situation or if you are using the unstable 363s distribution that some required packages have not yet been created 363s or been moved out of Incoming. 363s The following information may help to resolve the situation: 363s 363s The following packages have unmet dependencies: 363s satisfy:command-line : Depends: build-essential but it is not going to be installed 363s Depends: ninja-build but it is not going to be installed 363s Depends: libtorch-dev but it is not going to be installed 363s Depends: libtorch-test but it is not going to be installed 363s E: Unable to satisfy dependencies. Reached two conflicting assignments: 363s 1. python3-dev:ppc64el is selected for install because: 363s 1. satisfy:command-line:ppc64el=1 is selected for install 363s 2. satisfy:command-line:ppc64el Depends libtorch-dev 363s 3. libtorch-dev:ppc64el Depends python3-dev 363s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 363s but none of the choices are installable: 363s - python3-dev:ppc64el=3.14.2-1 is not selected for install 363s - python3-dev:ppc64el=3.13.9-3 is not selected for install 363s autopkgtest [14:11:31]: test 88_of_104__cpptest__pow_test: preparing testbed 363s 87_of_104__cpptest__packedtensoraccessor_test FAIL badpkg 363s blame: pytorch 363s 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 Reading package lists... 363s Building dependency tree... 363s Reading state information... 363s Solving dependencies... 363s Some packages could not be installed. This may mean that you have 363s requested an impossible situation or if you are using the unstable 363s distribution that some required packages have not yet been created 363s or been moved out of Incoming. 363s The following information may help to resolve the situation: 363s 363s The following packages have unmet dependencies: 364s satisfy:command-line : Depends: build-essential but it is not going to be installed 364s Depends: ninja-build but it is not going to be installed 364s Depends: libtorch-dev but it is not going to be installed 364s Depends: libtorch-test but it is not going to be installed 364s E: Unable to satisfy dependencies. Reached two conflicting assignments: 364s 1. python3-dev:ppc64el is selected for install because: 364s 1. satisfy:command-line:ppc64el=1 is selected for install 364s 2. satisfy:command-line:ppc64el Depends libtorch-dev 364s 3. libtorch-dev:ppc64el Depends python3-dev 364s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 364s but none of the choices are installable: 364s - python3-dev:ppc64el=3.14.2-1 is not selected for install 364s - python3-dev:ppc64el=3.13.9-3 is not selected for install 364s autopkgtest [14:11:32]: test 89_of_104__cpptest__quantized_test: preparing testbed 364s 88_of_104__cpptest__pow_test FAIL badpkg 364s blame: pytorch 364s 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. 364s Reading package lists... 364s Building dependency tree... 364s Reading state information... 364s Solving dependencies... 364s Some packages could not be installed. This may mean that you have 364s requested an impossible situation or if you are using the unstable 364s distribution that some required packages have not yet been created 364s or been moved out of Incoming. 364s The following information may help to resolve the situation: 364s 364s The following packages have unmet dependencies: 364s satisfy:command-line : Depends: build-essential but it is not going to be installed 364s Depends: ninja-build but it is not going to be installed 364s Depends: libtorch-dev but it is not going to be installed 364s Depends: libtorch-test but it is not going to be installed 364s E: Unable to satisfy dependencies. Reached two conflicting assignments: 364s 1. python3-dev:ppc64el is selected for install because: 364s 1. satisfy:command-line:ppc64el=1 is selected for install 364s 2. satisfy:command-line:ppc64el Depends libtorch-dev 364s 3. libtorch-dev:ppc64el Depends python3-dev 364s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 364s but none of the choices are installable: 364s - python3-dev:ppc64el=3.14.2-1 is not selected for install 364s - python3-dev:ppc64el=3.13.9-3 is not selected for install 364s 89_of_104__cpptest__quantized_test FAIL badpkg 364s blame: pytorch 364s 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. 364s autopkgtest [14:11:32]: test 90_of_104__cpptest__reduce_ops_test: preparing testbed 364s Reading package lists... 364s Building dependency tree... 364s Reading state information... 364s Solving dependencies... 364s Some packages could not be installed. This may mean that you have 364s requested an impossible situation or if you are using the unstable 364s distribution that some required packages have not yet been created 364s or been moved out of Incoming. 364s The following information may help to resolve the situation: 364s 364s The following packages have unmet dependencies: 365s satisfy:command-line : Depends: build-essential but it is not going to be installed 365s Depends: ninja-build but it is not going to be installed 365s Depends: libtorch-dev but it is not going to be installed 365s Depends: libtorch-test but it is not going to be installed 365s E: Unable to satisfy dependencies. Reached two conflicting assignments: 365s 1. python3-dev:ppc64el is selected for install because: 365s 1. satisfy:command-line:ppc64el=1 is selected for install 365s 2. satisfy:command-line:ppc64el Depends libtorch-dev 365s 3. libtorch-dev:ppc64el Depends python3-dev 365s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 365s but none of the choices are installable: 365s - python3-dev:ppc64el=3.14.2-1 is not selected for install 365s - python3-dev:ppc64el=3.13.9-3 is not selected for install 365s 90_of_104__cpptest__reduce_ops_test FAIL badpkg 365s blame: pytorch 365s 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. 365s autopkgtest [14:11:33]: test 91_of_104__cpptest__reportMemoryUsage_test: preparing testbed 365s Reading package lists... 365s Building dependency tree... 365s Reading state information... 365s Solving dependencies... 365s Some packages could not be installed. This may mean that you have 365s requested an impossible situation or if you are using the unstable 365s distribution that some required packages have not yet been created 365s or been moved out of Incoming. 365s The following information may help to resolve the situation: 365s 365s The following packages have unmet dependencies: 365s satisfy:command-line : Depends: build-essential but it is not going to be installed 365s Depends: ninja-build but it is not going to be installed 365s Depends: libtorch-dev but it is not going to be installed 365s Depends: libtorch-test but it is not going to be installed 365s E: Unable to satisfy dependencies. Reached two conflicting assignments: 365s 1. python3-dev:ppc64el is selected for install because: 365s 1. satisfy:command-line:ppc64el=1 is selected for install 365s 2. satisfy:command-line:ppc64el Depends libtorch-dev 365s 3. libtorch-dev:ppc64el Depends python3-dev 365s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 365s but none of the choices are installable: 365s - python3-dev:ppc64el=3.14.2-1 is not selected for install 365s - python3-dev:ppc64el=3.13.9-3 is not selected for install 365s 91_of_104__cpptest__reportMemoryUsage_test FAIL badpkg 365s blame: pytorch 365s 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. 365s autopkgtest [14:11:33]: test 92_of_104__cpptest__scalar_tensor_test: preparing testbed 365s Reading package lists... 365s Building dependency tree... 365s Reading state information... 365s Solving dependencies... 365s Some packages could not be installed. This may mean that you have 365s requested an impossible situation or if you are using the unstable 365s distribution that some required packages have not yet been created 365s or been moved out of Incoming. 365s The following information may help to resolve the situation: 365s 365s The following packages have unmet dependencies: 366s satisfy:command-line : Depends: build-essential but it is not going to be installed 366s Depends: ninja-build but it is not going to be installed 366s Depends: libtorch-dev but it is not going to be installed 366s Depends: libtorch-test but it is not going to be installed 366s E: Unable to satisfy dependencies. Reached two conflicting assignments: 366s 1. python3-dev:ppc64el is selected for install because: 366s 1. satisfy:command-line:ppc64el=1 is selected for install 366s 2. satisfy:command-line:ppc64el Depends libtorch-dev 366s 3. libtorch-dev:ppc64el Depends python3-dev 366s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 366s but none of the choices are installable: 366s - python3-dev:ppc64el=3.14.2-1 is not selected for install 366s - python3-dev:ppc64el=3.13.9-3 is not selected for install 366s 92_of_104__cpptest__scalar_tensor_test FAIL badpkg 366s blame: pytorch 366s 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. 366s autopkgtest [14:11:34]: test 93_of_104__cpptest__scalar_test: preparing testbed 366s Reading package lists... 366s Building dependency tree... 366s Reading state information... 366s Solving dependencies... 366s Some packages could not be installed. This may mean that you have 366s requested an impossible situation or if you are using the unstable 366s distribution that some required packages have not yet been created 366s or been moved out of Incoming. 366s The following information may help to resolve the situation: 366s 366s The following packages have unmet dependencies: 366s satisfy:command-line : Depends: build-essential but it is not going to be installed 366s Depends: ninja-build but it is not going to be installed 366s Depends: libtorch-dev but it is not going to be installed 366s Depends: libtorch-test but it is not going to be installed 366s E: Unable to satisfy dependencies. Reached two conflicting assignments: 366s 1. python3-dev:ppc64el is selected for install because: 366s 1. satisfy:command-line:ppc64el=1 is selected for install 366s 2. satisfy:command-line:ppc64el Depends libtorch-dev 366s 3. libtorch-dev:ppc64el Depends python3-dev 366s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 366s but none of the choices are installable: 366s - python3-dev:ppc64el=3.14.2-1 is not selected for install 366s - python3-dev:ppc64el=3.13.9-3 is not selected for install 366s autopkgtest [14:11:34]: test 94_of_104__cpptest__stride_properties_test: preparing testbed 366s 93_of_104__cpptest__scalar_test FAIL badpkg 366s blame: pytorch 366s 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. 366s Reading package lists... 366s Building dependency tree... 366s Reading state information... 366s Solving dependencies... 366s Some packages could not be installed. This may mean that you have 366s requested an impossible situation or if you are using the unstable 366s distribution that some required packages have not yet been created 366s or been moved out of Incoming. 366s The following information may help to resolve the situation: 366s 366s The following packages have unmet dependencies: 366s satisfy:command-line : Depends: build-essential but it is not going to be installed 366s Depends: ninja-build but it is not going to be installed 366s Depends: libtorch-dev but it is not going to be installed 366s Depends: libtorch-test but it is not going to be installed 366s E: Unable to satisfy dependencies. Reached two conflicting assignments: 366s 1. python3-dev:ppc64el is selected for install because: 366s 1. satisfy:command-line:ppc64el=1 is selected for install 366s 2. satisfy:command-line:ppc64el Depends libtorch-dev 366s 3. libtorch-dev:ppc64el Depends python3-dev 366s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 366s but none of the choices are installable: 366s - python3-dev:ppc64el=3.14.2-1 is not selected for install 366s - python3-dev:ppc64el=3.13.9-3 is not selected for install 367s autopkgtest [14:11:35]: test 95_of_104__cpptest__tensor_iterator_test: preparing testbed 367s 94_of_104__cpptest__stride_properties_test FAIL badpkg 367s blame: pytorch 367s 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. 367s Reading package lists... 367s Building dependency tree... 367s Reading state information... 367s Solving dependencies... 367s Some packages could not be installed. This may mean that you have 367s requested an impossible situation or if you are using the unstable 367s distribution that some required packages have not yet been created 367s or been moved out of Incoming. 367s The following information may help to resolve the situation: 367s 367s The following packages have unmet dependencies: 367s satisfy:command-line : Depends: build-essential but it is not going to be installed 367s Depends: ninja-build but it is not going to be installed 367s Depends: libtorch-dev but it is not going to be installed 367s Depends: libtorch-test but it is not going to be installed 367s E: Unable to satisfy dependencies. Reached two conflicting assignments: 367s 1. python3-dev:ppc64el is selected for install because: 367s 1. satisfy:command-line:ppc64el=1 is selected for install 367s 2. satisfy:command-line:ppc64el Depends libtorch-dev 367s 3. libtorch-dev:ppc64el Depends python3-dev 367s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 367s but none of the choices are installable: 367s - python3-dev:ppc64el=3.14.2-1 is not selected for install 367s - python3-dev:ppc64el=3.13.9-3 is not selected for install 367s 95_of_104__cpptest__tensor_iterator_test FAIL badpkg 367s blame: pytorch 367s 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. 367s autopkgtest [14:11:35]: test 96_of_104__cpptest__test_parallel: preparing testbed 367s Reading package lists... 367s Building dependency tree... 367s Reading state information... 367s Solving dependencies... 367s Some packages could not be installed. This may mean that you have 367s requested an impossible situation or if you are using the unstable 367s distribution that some required packages have not yet been created 367s or been moved out of Incoming. 367s The following information may help to resolve the situation: 367s 367s The following packages have unmet dependencies: 367s satisfy:command-line : Depends: build-essential but it is not going to be installed 367s Depends: ninja-build but it is not going to be installed 367s Depends: libtorch-dev but it is not going to be installed 367s Depends: libtorch-test but it is not going to be installed 367s E: Unable to satisfy dependencies. Reached two conflicting assignments: 367s 1. python3-dev:ppc64el is selected for install because: 367s 1. satisfy:command-line:ppc64el=1 is selected for install 367s 2. satisfy:command-line:ppc64el Depends libtorch-dev 367s 3. libtorch-dev:ppc64el Depends python3-dev 367s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 367s but none of the choices are installable: 367s - python3-dev:ppc64el=3.14.2-1 is not selected for install 367s - python3-dev:ppc64el=3.13.9-3 is not selected for install 368s autopkgtest [14:11:35]: test 97_of_104__cpptest__thread_init_test: preparing testbed 368s 96_of_104__cpptest__test_parallel FAIL badpkg 368s blame: pytorch 368s 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. 368s Reading package lists... 368s Building dependency tree... 368s Reading state information... 368s Solving dependencies... 368s Some packages could not be installed. This may mean that you have 368s requested an impossible situation or if you are using the unstable 368s distribution that some required packages have not yet been created 368s or been moved out of Incoming. 368s The following information may help to resolve the situation: 368s 368s The following packages have unmet dependencies: 368s satisfy:command-line : Depends: build-essential but it is not going to be installed 368s Depends: ninja-build but it is not going to be installed 368s Depends: libtorch-dev but it is not going to be installed 368s Depends: libtorch-test but it is not going to be installed 368s E: Unable to satisfy dependencies. Reached two conflicting assignments: 368s 1. python3-dev:ppc64el is selected for install because: 368s 1. satisfy:command-line:ppc64el=1 is selected for install 368s 2. satisfy:command-line:ppc64el Depends libtorch-dev 368s 3. libtorch-dev:ppc64el Depends python3-dev 368s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 368s but none of the choices are installable: 368s - python3-dev:ppc64el=3.14.2-1 is not selected for install 368s - python3-dev:ppc64el=3.13.9-3 is not selected for install 368s autopkgtest [14:11:36]: test 98_of_104__cpptest__type_ptr_test: preparing testbed 368s 97_of_104__cpptest__thread_init_test FAIL badpkg 368s blame: pytorch 368s 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. 368s Reading package lists... 368s Building dependency tree... 368s Reading state information... 368s Solving dependencies... 368s Some packages could not be installed. This may mean that you have 368s requested an impossible situation or if you are using the unstable 368s distribution that some required packages have not yet been created 368s or been moved out of Incoming. 368s The following information may help to resolve the situation: 368s 368s The following packages have unmet dependencies: 368s satisfy:command-line : Depends: build-essential but it is not going to be installed 368s Depends: ninja-build but it is not going to be installed 368s Depends: libtorch-dev but it is not going to be installed 368s Depends: libtorch-test but it is not going to be installed 368s E: Unable to satisfy dependencies. Reached two conflicting assignments: 368s 1. python3-dev:ppc64el is selected for install because: 368s 1. satisfy:command-line:ppc64el=1 is selected for install 368s 2. satisfy:command-line:ppc64el Depends libtorch-dev 368s 3. libtorch-dev:ppc64el Depends python3-dev 368s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 368s but none of the choices are installable: 368s - python3-dev:ppc64el=3.14.2-1 is not selected for install 368s - python3-dev:ppc64el=3.13.9-3 is not selected for install 368s 98_of_104__cpptest__type_ptr_test FAIL badpkg 368s blame: pytorch 368s 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. 368s autopkgtest [14:11:36]: test 99_of_104__cpptest__type_test: preparing testbed 369s Reading package lists... 369s Building dependency tree... 369s Reading state information... 369s Solving dependencies... 369s Some packages could not be installed. This may mean that you have 369s requested an impossible situation or if you are using the unstable 369s distribution that some required packages have not yet been created 369s or been moved out of Incoming. 369s The following information may help to resolve the situation: 369s 369s The following packages have unmet dependencies: 369s satisfy:command-line : Depends: build-essential but it is not going to be installed 369s Depends: ninja-build but it is not going to be installed 369s Depends: libtorch-dev but it is not going to be installed 369s Depends: libtorch-test but it is not going to be installed 369s E: Unable to satisfy dependencies. Reached two conflicting assignments: 369s 1. python3-dev:ppc64el is selected for install because: 369s 1. satisfy:command-line:ppc64el=1 is selected for install 369s 2. satisfy:command-line:ppc64el Depends libtorch-dev 369s 3. libtorch-dev:ppc64el Depends python3-dev 369s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 369s but none of the choices are installable: 369s - python3-dev:ppc64el=3.14.2-1 is not selected for install 369s - python3-dev:ppc64el=3.13.9-3 is not selected for install 369s autopkgtest [14:11:37]: test 100_of_104__cpptest__undefined_tensor_test: preparing testbed 369s 99_of_104__cpptest__type_test FAIL badpkg 369s blame: pytorch 369s 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. 369s Reading package lists... 369s Building dependency tree... 369s Reading state information... 369s Solving dependencies... 369s Some packages could not be installed. This may mean that you have 369s requested an impossible situation or if you are using the unstable 369s distribution that some required packages have not yet been created 369s or been moved out of Incoming. 369s The following information may help to resolve the situation: 369s 369s The following packages have unmet dependencies: 369s satisfy:command-line : Depends: build-essential but it is not going to be installed 369s Depends: ninja-build but it is not going to be installed 369s Depends: libtorch-dev but it is not going to be installed 369s Depends: libtorch-test but it is not going to be installed 369s E: Unable to satisfy dependencies. Reached two conflicting assignments: 369s 1. python3-dev:ppc64el is selected for install because: 369s 1. satisfy:command-line:ppc64el=1 is selected for install 369s 2. satisfy:command-line:ppc64el Depends libtorch-dev 369s 3. libtorch-dev:ppc64el Depends python3-dev 369s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 369s but none of the choices are installable: 369s - python3-dev:ppc64el=3.14.2-1 is not selected for install 369s - python3-dev:ppc64el=3.13.9-3 is not selected for install 369s autopkgtest [14:11:37]: test 101_of_104__cpptest__verify_api_visibility: preparing testbed 369s 100_of_104__cpptest__undefined_tensor_test FAIL badpkg 369s blame: pytorch 369s 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. 370s Reading package lists... 370s Building dependency tree... 370s Reading state information... 370s Solving dependencies... 370s Some packages could not be installed. This may mean that you have 370s requested an impossible situation or if you are using the unstable 370s distribution that some required packages have not yet been created 370s or been moved out of Incoming. 370s The following information may help to resolve the situation: 370s 370s The following packages have unmet dependencies: 370s satisfy:command-line : Depends: build-essential but it is not going to be installed 370s Depends: ninja-build but it is not going to be installed 370s Depends: libtorch-dev but it is not going to be installed 370s Depends: libtorch-test but it is not going to be installed 370s E: Unable to satisfy dependencies. Reached two conflicting assignments: 370s 1. python3-dev:ppc64el is selected for install because: 370s 1. satisfy:command-line:ppc64el=1 is selected for install 370s 2. satisfy:command-line:ppc64el Depends libtorch-dev 370s 3. libtorch-dev:ppc64el Depends python3-dev 370s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 370s but none of the choices are installable: 370s - python3-dev:ppc64el=3.14.2-1 is not selected for install 370s - python3-dev:ppc64el=3.13.9-3 is not selected for install 370s 101_of_104__cpptest__verify_api_visibility FAIL badpkg 370s blame: pytorch 370s 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. 370s autopkgtest [14:11:38]: test 102_of_104__cpptest__weakref_test: preparing testbed 370s Reading package lists... 370s Building dependency tree... 370s Reading state information... 370s Solving dependencies... 370s Some packages could not be installed. This may mean that you have 370s requested an impossible situation or if you are using the unstable 370s distribution that some required packages have not yet been created 370s or been moved out of Incoming. 370s The following information may help to resolve the situation: 370s 370s The following packages have unmet dependencies: 370s satisfy:command-line : Depends: build-essential but it is not going to be installed 370s Depends: ninja-build but it is not going to be installed 370s Depends: libtorch-dev but it is not going to be installed 370s Depends: libtorch-test but it is not going to be installed 370s E: Unable to satisfy dependencies. Reached two conflicting assignments: 370s 1. python3-dev:ppc64el is selected for install because: 370s 1. satisfy:command-line:ppc64el=1 is selected for install 370s 2. satisfy:command-line:ppc64el Depends libtorch-dev 370s 3. libtorch-dev:ppc64el Depends python3-dev 370s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 370s but none of the choices are installable: 370s - python3-dev:ppc64el=3.14.2-1 is not selected for install 370s - python3-dev:ppc64el=3.13.9-3 is not selected for install 370s 102_of_104__cpptest__weakref_test FAIL badpkg 370s blame: pytorch 370s 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. 370s autopkgtest [14:11:38]: test 103_of_104__cpptest__wrapdim_test: preparing testbed 371s Reading package lists... 371s Building dependency tree... 371s Reading state information... 371s Solving dependencies... 371s Some packages could not be installed. This may mean that you have 371s requested an impossible situation or if you are using the unstable 371s distribution that some required packages have not yet been created 371s or been moved out of Incoming. 371s The following information may help to resolve the situation: 371s 371s The following packages have unmet dependencies: 371s satisfy:command-line : Depends: build-essential but it is not going to be installed 371s Depends: ninja-build but it is not going to be installed 371s Depends: libtorch-dev but it is not going to be installed 371s Depends: libtorch-test but it is not going to be installed 371s E: Unable to satisfy dependencies. Reached two conflicting assignments: 371s 1. python3-dev:ppc64el is selected for install because: 371s 1. satisfy:command-line:ppc64el=1 is selected for install 371s 2. satisfy:command-line:ppc64el Depends libtorch-dev 371s 3. libtorch-dev:ppc64el Depends python3-dev 371s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 371s but none of the choices are installable: 371s - python3-dev:ppc64el=3.14.2-1 is not selected for install 371s - python3-dev:ppc64el=3.13.9-3 is not selected for install 371s 103_of_104__cpptest__wrapdim_test FAIL badpkg 371s blame: pytorch 371s 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. 371s autopkgtest [14:11:39]: test 104_of_104__cpptest__xla_tensor_test: preparing testbed 371s Reading package lists... 371s Building dependency tree... 371s Reading state information... 371s Solving dependencies... 371s Some packages could not be installed. This may mean that you have 371s requested an impossible situation or if you are using the unstable 371s distribution that some required packages have not yet been created 371s or been moved out of Incoming. 371s The following information may help to resolve the situation: 371s 371s The following packages have unmet dependencies: 371s satisfy:command-line : Depends: build-essential but it is not going to be installed 371s Depends: ninja-build but it is not going to be installed 371s Depends: libtorch-dev but it is not going to be installed 371s Depends: libtorch-test but it is not going to be installed 371s E: Unable to satisfy dependencies. Reached two conflicting assignments: 371s 1. python3-dev:ppc64el is selected for install because: 371s 1. satisfy:command-line:ppc64el=1 is selected for install 371s 2. satisfy:command-line:ppc64el Depends libtorch-dev 371s 3. libtorch-dev:ppc64el Depends python3-dev 371s 2. python3-dev:ppc64el is available in versions 3.14.2-1, 3.13.9-3 371s but none of the choices are installable: 371s - python3-dev:ppc64el=3.14.2-1 is not selected for install 371s - python3-dev:ppc64el=3.13.9-3 is not selected for install 371s 104_of_104__cpptest__xla_tensor_test FAIL badpkg 371s blame: pytorch 371s 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. 371s autopkgtest [14:11:39]: @@@@@@@@@@@@@@@@@@@@ summary 371s py_import_and_version FAIL badpkg 371s blame: pytorch 371s 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. 371s py_blas_openblas FAIL badpkg 371s blame: pytorch 371s 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. 371s py_blas_blis FAIL badpkg 371s blame: pytorch 371s 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. 371s py_sequential FAIL badpkg 371s blame: pytorch 371s 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. 371s show_dangling_symlink_if_any FAIL badpkg 371s blame: pytorch 371s 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. 371s real_train_mnist FAIL badpkg 371s blame: pytorch 371s 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. 371s 1_of_104__cpptest__CppSignature_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 2_of_104__cpptest__Dict_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 3_of_104__cpptest__Dimname_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 4_of_104__cpptest__IListRef_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 5_of_104__cpptest__KernelFunction_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 6_of_104__cpptest__List_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 7_of_104__cpptest__MaybeOwned_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 8_of_104__cpptest__NamedTensor_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 9_of_104__cpptest__StorageUtils_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 10_of_104__cpptest__apply_utils_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 11_of_104__cpptest__atest FAIL badpkg 371s blame: pytorch 371s 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. 371s 12_of_104__cpptest__backend_fallback_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 13_of_104__cpptest__basic FAIL badpkg 371s blame: pytorch 371s 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. 371s 14_of_104__cpptest__broadcast_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 15_of_104__cpptest__c10_Bitset_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 16_of_104__cpptest__c10_CompileTimeFunctionPointer_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 17_of_104__cpptest__c10_ConstexprCrc_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 18_of_104__cpptest__c10_DeadlockDetection_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 19_of_104__cpptest__c10_DeviceGuard_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 20_of_104__cpptest__c10_Device_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 21_of_104__cpptest__c10_DispatchKeySet_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 22_of_104__cpptest__c10_Half_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 23_of_104__cpptest__c10_InlineDeviceGuard_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 24_of_104__cpptest__c10_InlineStreamGuard_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 25_of_104__cpptest__c10_LeftRight_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 26_of_104__cpptest__c10_Metaprogramming_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 27_of_104__cpptest__c10_NetworkFlow_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 28_of_104__cpptest__c10_Scalar_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 29_of_104__cpptest__c10_SizesAndStrides_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 30_of_104__cpptest__c10_StreamGuard_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 31_of_104__cpptest__c10_SymInt_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 32_of_104__cpptest__c10_Synchronized_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 33_of_104__cpptest__c10_ThreadLocal_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 34_of_104__cpptest__c10_TypeIndex_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 35_of_104__cpptest__c10_TypeList_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 36_of_104__cpptest__c10_TypeTraits_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 37_of_104__cpptest__c10_accumulate_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 38_of_104__cpptest__c10_bfloat16_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 39_of_104__cpptest__c10_bit_cast_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 40_of_104__cpptest__c10_complex_math_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 41_of_104__cpptest__c10_complex_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 42_of_104__cpptest__c10_cow_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 43_of_104__cpptest__c10_exception_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 44_of_104__cpptest__c10_flags_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 45_of_104__cpptest__c10_generic_math_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 46_of_104__cpptest__c10_intrusive_ptr_benchmark FAIL badpkg 371s blame: pytorch 371s 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. 371s 47_of_104__cpptest__c10_intrusive_ptr_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 48_of_104__cpptest__c10_irange_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 49_of_104__cpptest__c10_lazy_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 50_of_104__cpptest__c10_logging_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 51_of_104__cpptest__c10_optional_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 52_of_104__cpptest__c10_ordered_preserving_dict_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 53_of_104__cpptest__c10_registry_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 54_of_104__cpptest__c10_small_vector_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 55_of_104__cpptest__c10_ssize_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 56_of_104__cpptest__c10_string_util_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 57_of_104__cpptest__c10_string_view_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 58_of_104__cpptest__c10_tempfile_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 59_of_104__cpptest__c10_typeid_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 60_of_104__cpptest__cpu_allocator_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 61_of_104__cpptest__cpu_generator_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 62_of_104__cpptest__cpu_profiling_allocator_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 63_of_104__cpptest__cpu_rng_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 64_of_104__cpptest__dispatch_key_set_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 65_of_104__cpptest__dlconvertor_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 66_of_104__cpptest__extension_backend_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 67_of_104__cpptest__half_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 68_of_104__cpptest__inline_container_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 69_of_104__cpptest__ivalue_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 70_of_104__cpptest__kernel_function_legacy_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 71_of_104__cpptest__kernel_function_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 72_of_104__cpptest__kernel_lambda_legacy_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 73_of_104__cpptest__kernel_lambda_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 74_of_104__cpptest__kernel_stackbased_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 75_of_104__cpptest__lazy_tensor_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 76_of_104__cpptest__legacy_vmap_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 77_of_104__cpptest__make_boxed_from_unboxed_functor_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 78_of_104__cpptest__math_kernel_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 79_of_104__cpptest__memory_format_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 80_of_104__cpptest__memory_overlapping_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 81_of_104__cpptest__mobile_memory_cleanup FAIL badpkg 371s blame: pytorch 371s 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. 371s 82_of_104__cpptest__native_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 83_of_104__cpptest__op_allowlist_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 84_of_104__cpptest__op_registration_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 85_of_104__cpptest__operator_name_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 86_of_104__cpptest__operators_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 87_of_104__cpptest__packedtensoraccessor_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 88_of_104__cpptest__pow_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 89_of_104__cpptest__quantized_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 90_of_104__cpptest__reduce_ops_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 91_of_104__cpptest__reportMemoryUsage_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 92_of_104__cpptest__scalar_tensor_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 93_of_104__cpptest__scalar_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 94_of_104__cpptest__stride_properties_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 95_of_104__cpptest__tensor_iterator_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 96_of_104__cpptest__test_parallel FAIL badpkg 371s blame: pytorch 371s 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. 371s 97_of_104__cpptest__thread_init_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 98_of_104__cpptest__type_ptr_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 99_of_104__cpptest__type_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 100_of_104__cpptest__undefined_tensor_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 101_of_104__cpptest__verify_api_visibility FAIL badpkg 371s blame: pytorch 371s 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. 371s 102_of_104__cpptest__weakref_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 103_of_104__cpptest__wrapdim_test FAIL badpkg 371s blame: pytorch 371s 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. 371s 104_of_104__cpptest__xla_tensor_test FAIL badpkg 371s blame: pytorch 371s 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.