0s autopkgtest [12:49:39]: starting date and time: 2025-11-17 12:49:39+0000 0s autopkgtest [12:49:39]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [12:49:39]: host juju-7f2275-prod-proposed-migration-environment-20; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.gx0b3vuu/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:fenics-basix,src:python3-defaults --apt-upgrade fenics --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 '--env=ADT_TEST_TRIGGERS=fenics-basix/0.9.0-4 python3-defaults/3.13.7-2' -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest-ppc64el --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-20@bos03-ppc64el-3.secgroup --name adt-resolute-ppc64el-fenics-20251117-124939-juju-7f2275-prod-proposed-migration-environment-20-895cd50d-f617-4e33-a624-b400c5e6c458 --image adt/ubuntu-resolute-ppc64el-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-20 --net-id=net_prod-proposed-migration-ppc64el -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 3s Creating nova instance adt-resolute-ppc64el-fenics-20251117-124939-juju-7f2275-prod-proposed-migration-environment-20-895cd50d-f617-4e33-a624-b400c5e6c458 from image adt/ubuntu-resolute-ppc64el-server-20251117.img (UUID c6f5b741-c77a-45db-84cb-f00b40e77676)... 55s autopkgtest [12:50:34]: testbed dpkg architecture: ppc64el 55s autopkgtest [12:50:34]: testbed apt version: 3.1.11 56s autopkgtest [12:50:35]: @@@@@@@@@@@@@@@@@@@@ test bed setup 56s autopkgtest [12:50:35]: testbed release detected to be: None 57s autopkgtest [12:50:36]: updating testbed package index (apt update) 57s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [87.8 kB] 57s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 58s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 58s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 58s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [9848 B] 58s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [81.1 kB] 58s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [22.9 kB] 58s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [868 kB] 60s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el Packages [140 kB] 60s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/restricted ppc64el Packages [940 B] 60s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/universe ppc64el Packages [562 kB] 61s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse ppc64el Packages [11.0 kB] 61s Fetched 1784 kB in 4s (436 kB/s) 62s Reading package lists... 62s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 63s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 63s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 63s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 63s Reading package lists... 64s Reading package lists... 64s Building dependency tree... 64s Reading state information... 64s Calculating upgrade... 64s The following packages will be upgraded: 64s libpython3-stdlib python3 python3-minimal usbutils 64s 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 64s Need to get 154 kB of archives. 64s After this operation, 0 B of additional disk space will be used. 64s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el python3-minimal ppc64el 3.13.7-2 [27.8 kB] 64s Get:2 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el python3 ppc64el 3.13.7-2 [23.9 kB] 64s Get:3 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el libpython3-stdlib ppc64el 3.13.7-2 [10.6 kB] 64s Get:4 http://ftpmaster.internal/ubuntu resolute/main ppc64el usbutils ppc64el 1:019-1 [91.5 kB] 65s dpkg-preconfigure: unable to re-open stdin: No such file or directory 65s Fetched 154 kB in 1s (271 kB/s) 65s (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 ... 81022 files and directories currently installed.) 65s Preparing to unpack .../python3-minimal_3.13.7-2_ppc64el.deb ... 65s Unpacking python3-minimal (3.13.7-2) over (3.13.7-1) ... 65s Setting up python3-minimal (3.13.7-2) ... 65s (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 ... 81022 files and directories currently installed.) 65s Preparing to unpack .../python3_3.13.7-2_ppc64el.deb ... 65s running python pre-rtupdate hooks for python3.13... 65s Unpacking python3 (3.13.7-2) over (3.13.7-1) ... 65s Preparing to unpack .../libpython3-stdlib_3.13.7-2_ppc64el.deb ... 65s Unpacking libpython3-stdlib:ppc64el (3.13.7-2) over (3.13.7-1) ... 65s Preparing to unpack .../usbutils_1%3a019-1_ppc64el.deb ... 65s Unpacking usbutils (1:019-1) over (1:018-2) ... 66s Setting up usbutils (1:019-1) ... 66s Setting up libpython3-stdlib:ppc64el (3.13.7-2) ... 66s Setting up python3 (3.13.7-2) ... 66s running python rtupdate hooks for python3.13... 66s running python post-rtupdate hooks for python3.13... 66s Processing triggers for man-db (2.13.1-1) ... 67s autopkgtest [12:50:46]: upgrading testbed (apt dist-upgrade and autopurge) 67s Reading package lists... 67s Building dependency tree... 67s Reading state information... 67s Calculating upgrade... 68s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 68s Reading package lists... 68s Building dependency tree... 68s Reading state information... 68s Solving dependencies... 68s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 71s autopkgtest [12:50:50]: testbed running kernel: Linux 6.17.0-5-generic #5-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 22 10:02:41 UTC 2025 71s autopkgtest [12:50:50]: @@@@@@@@@@@@@@@@@@@@ apt-source fenics 73s Get:1 http://ftpmaster.internal/ubuntu resolute/universe fenics 2:0.9.0.3 (dsc) [1917 B] 73s Get:2 http://ftpmaster.internal/ubuntu resolute/universe fenics 2:0.9.0.3 (tar) [5964 B] 73s gpgv: Signature made Mon May 5 12:44:30 2025 UTC 73s gpgv: using RSA key 23C9A93E585819E9126D0A36573EF1E4BD5A01FA 73s gpgv: Can't check signature: No public key 73s dpkg-source: warning: cannot verify inline signature for ./fenics_0.9.0.3.dsc: no acceptable signature found 73s autopkgtest [12:50:52]: testing package fenics version 2:0.9.0.3 73s autopkgtest [12:50:52]: build not needed 73s autopkgtest [12:50:52]: test test-fenics: preparing testbed 74s Reading package lists... 74s Building dependency tree... 74s Reading state information... 74s Solving dependencies... 74s Some packages could not be installed. This may mean that you have 74s requested an impossible situation or if you are using the unstable 74s distribution that some required packages have not yet been created 74s or been moved out of Incoming. 74s The following information may help to resolve the situation: 74s 74s The following packages have unmet dependencies: 74s satisfy:command-line : Depends: fenics but it is not going to be installed 74s Depends: fenicsx but it is not going to be installed 74s Depends: debhelper-compat (= 13) 74s Depends: build-essential but it is not going to be installed 74s Depends: python3-dolfinx-mpc but it is not going to be installed 74s Depends: python3-adios4dolfinx but it is not going to be installed 74s Depends: python3-scifem but it is not going to be installed 74s Depends: python3-all but it is not going to be installed 74s E: Unable to satisfy dependencies. Reached two conflicting decisions: 74s 1. python3-basix:ppc64el is selected for install because: 74s 1. satisfy:command-line:ppc64el=1 is selected for install 74s 2. satisfy:command-line:ppc64el Depends fenicsx 74s 3. fenicsx:ppc64el Depends python3-basix (>= 0.9~) 74s 2. python3-basix:ppc64el is available in versions 0.9.0-4, 0.9.0-2build2 74s but none of the choices are installable: 74s - python3-basix:ppc64el=0.9.0-4 is not selected for install because: 74s 1. satisfy:command-line:ppc64el=1 is selected for install as above 74s 2. satisfy:command-line:ppc64el Depends python3-dolfinx-mpc 74s 3. python3-dolfinx-mpc:ppc64el is available in version 0.9.1-2 74s 4. python3-basix:ppc64el=0.9.0-4 Breaks python3-dolfinx-mpc (< 0.9.3-2~) 74s - python3-basix:ppc64el=0.9.0-2build2 is not selected for install 74s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 74s Reading package lists... 75s Building dependency tree... 75s Reading state information... 75s Solving dependencies... 75s Some packages could not be installed. This may mean that you have 75s requested an impossible situation or if you are using the unstable 75s distribution that some required packages have not yet been created 75s or been moved out of Incoming. 75s The following information may help to resolve the situation: 75s 75s The following packages have unmet dependencies: 75s satisfy:command-line : Depends: fenics but it is not going to be installed 75s Depends: fenicsx but it is not going to be installed 75s Depends: debhelper-compat (= 13) 75s Depends: build-essential but it is not going to be installed 75s Depends: python3-dolfinx-mpc but it is not going to be installed 75s Depends: python3-adios4dolfinx but it is not going to be installed 75s Depends: python3-scifem but it is not going to be installed 75s Depends: python3-all but it is not going to be installed 75s E: Unable to satisfy dependencies. Reached two conflicting decisions: 75s 1. python3-basix:ppc64el is selected for install because: 75s 1. satisfy:command-line:ppc64el=1 is selected for install 75s 2. satisfy:command-line:ppc64el Depends fenicsx 75s 3. fenicsx:ppc64el Depends python3-basix (>= 0.9~) 75s 2. python3-basix:ppc64el is available in versions 0.9.0-4, 0.9.0-2build2 75s but none of the choices are installable: 75s - python3-basix:ppc64el=0.9.0-4 is not selected for install because: 75s 1. satisfy:command-line:ppc64el=1 is selected for install as above 75s 2. satisfy:command-line:ppc64el Depends python3-dolfinx-mpc 75s 3. python3-dolfinx-mpc:ppc64el is available in version 0.9.1-2 75s 4. python3-basix:ppc64el=0.9.0-4 Breaks python3-dolfinx-mpc (< 0.9.3-2~) 75s - python3-basix:ppc64el=0.9.0-2build2 is not selected for install 75s autopkgtest [12:50:54]: test test-fenicsx: preparing testbed 75s test-fenics FAIL badpkg 75s blame: fenics 75s badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. 75s Reading package lists... 75s Building dependency tree... 75s Reading state information... 75s Solving dependencies... 75s Some packages could not be installed. This may mean that you have 75s requested an impossible situation or if you are using the unstable 75s distribution that some required packages have not yet been created 75s or been moved out of Incoming. 75s The following information may help to resolve the situation: 75s 75s The following packages have unmet dependencies: 75s satisfy:command-line : Depends: fenics but it is not going to be installed 75s Depends: fenicsx but it is not going to be installed 75s Depends: debhelper-compat (= 13) 75s Depends: build-essential but it is not going to be installed 75s Depends: python3-dolfinx-mpc but it is not going to be installed 75s Depends: python3-adios4dolfinx but it is not going to be installed 75s Depends: python3-scifem but it is not going to be installed 75s Depends: python3-all but it is not going to be installed 75s E: Unable to satisfy dependencies. Reached two conflicting decisions: 75s 1. python3-basix:ppc64el is selected for install because: 75s 1. satisfy:command-line:ppc64el=1 is selected for install 75s 2. satisfy:command-line:ppc64el Depends fenicsx 75s 3. fenicsx:ppc64el Depends python3-basix (>= 0.9~) 75s 2. python3-basix:ppc64el is available in versions 0.9.0-4, 0.9.0-2build2 75s but none of the choices are installable: 75s - python3-basix:ppc64el=0.9.0-4 is not selected for install because: 75s 1. satisfy:command-line:ppc64el=1 is selected for install as above 75s 2. satisfy:command-line:ppc64el Depends python3-dolfinx-mpc 75s 3. python3-dolfinx-mpc:ppc64el is available in version 0.9.1-2 75s 4. python3-basix:ppc64el=0.9.0-4 Breaks python3-dolfinx-mpc (< 0.9.3-2~) 75s - python3-basix:ppc64el=0.9.0-2build2 is not selected for install 75s autopkgtest [12:50:54]: @@@@@@@@@@@@@@@@@@@@ summary 75s test-fenics FAIL badpkg 75s blame: fenics 75s badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. 75s test-fenicsx FAIL badpkg 75s blame: fenics 75s badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. 75s test-fenicsx FAIL badpkg 75s blame: fenics 75s badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.