0s autopkgtest [13:18:10]: starting date and time: 2026-02-02 13:18:10+0000 0s autopkgtest [13:18:10]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [13:18:10]: host juju-7f2275-prod-proposed-migration-environment-15; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.nqasca1v/out --timeout-copy=6000 --needs-internet=try -a i386 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:dolfinx-mpc --apt-upgrade fenics --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 --env=ADT_TEST_TRIGGERS=dolfinx-mpc/0.10.1-1build1 -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest-cpu2-ram4-disk20-amd64 --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-15@sto01-11.secgroup --name adt-resolute-i386-fenics-20260202-131810-juju-7f2275-prod-proposed-migration-environment-15-74cd0f4a-f042-4bfb-a115-97942335a495 --image adt/ubuntu-resolute-amd64-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-15 --net-id=net_prod-autopkgtest-workers-amd64 -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 3s Creating nova instance adt-resolute-i386-fenics-20260202-131810-juju-7f2275-prod-proposed-migration-environment-15-74cd0f4a-f042-4bfb-a115-97942335a495 from image adt/ubuntu-resolute-amd64-server-20260202.img (UUID 54e94ad2-f1e5-466e-b281-ee6f460760b3)... 72s autopkgtest [13:19:22]: testbed dpkg architecture: amd64 72s autopkgtest [13:19:22]: testbed apt version: 3.1.14 72s autopkgtest [13:19:22]: @@@@@@@@@@@@@@@@@@@@ test bed setup 72s autopkgtest [13:19:22]: testbed release detected to be: None 73s autopkgtest [13:19:23]: updating testbed package index (apt update) 73s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 73s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 73s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 73s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 73s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [99.2 kB] 73s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [2816 B] 73s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [27.3 kB] 74s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [1241 kB] 74s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main i386 Packages [95.3 kB] 74s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 Packages [113 kB] 74s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 c-n-f Metadata [3536 B] 74s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/restricted i386 Packages [3692 B] 74s Get:13 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 Packages [12.3 kB] 74s Get:14 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 c-n-f Metadata [336 B] 74s Get:15 http://ftpmaster.internal/ubuntu resolute-proposed/universe i386 Packages [401 kB] 74s Get:16 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 Packages [1065 kB] 74s Get:17 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 c-n-f Metadata [27.3 kB] 74s Get:18 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 Packages [24.4 kB] 74s Get:19 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse i386 Packages [3632 B] 74s Get:20 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 c-n-f Metadata [1060 B] 75s Fetched 3245 kB in 1s (3709 kB/s) 75s Reading package lists... 76s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 76s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 76s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 76s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 77s Reading package lists... 77s Reading package lists... 77s Building dependency tree... 77s Reading state information... 77s Calculating upgrade... 77s The following packages will be upgraded: 77s libgpg-error-l10n libgpg-error0 pci.ids 77s 3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 77s Need to get 391 kB of archives. 77s After this operation, 12.3 kB of additional disk space will be used. 77s Get:1 http://ftpmaster.internal/ubuntu resolute/main amd64 libgpg-error-l10n all 1.58-2 [9244 B] 77s Get:2 http://ftpmaster.internal/ubuntu resolute/main amd64 libgpg-error0 amd64 1.58-2 [83.3 kB] 77s Get:3 http://ftpmaster.internal/ubuntu resolute/main amd64 pci.ids all 0.0~2026.01.31-1 [299 kB] 77s dpkg-preconfigure: unable to re-open stdin: No such file or directory 77s Fetched 391 kB in 0s (26.7 MB/s) 78s (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 ... 83956 files and directories currently installed.) 78s Preparing to unpack .../libgpg-error-l10n_1.58-2_all.deb ... 78s Unpacking libgpg-error-l10n (1.58-2) over (1.58-1build1) ... 78s Preparing to unpack .../libgpg-error0_1.58-2_amd64.deb ... 78s Unpacking libgpg-error0:amd64 (1.58-2) over (1.58-1build1) ... 78s Preparing to unpack .../pci.ids_0.0~2026.01.31-1_all.deb ... 78s Unpacking pci.ids (0.0~2026.01.31-1) over (0.0~2025.12.16-1) ... 78s Setting up pci.ids (0.0~2026.01.31-1) ... 78s Setting up libgpg-error0:amd64 (1.58-2) ... 78s Setting up libgpg-error-l10n (1.58-2) ... 78s Processing triggers for libc-bin (2.42-2ubuntu4) ... 78s autopkgtest [13:19:28]: upgrading testbed (apt dist-upgrade and autopurge) 78s Reading package lists... 78s Building dependency tree... 78s Reading state information... 78s Calculating upgrade... 78s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 79s Reading package lists... 79s Building dependency tree... 79s Reading state information... 79s Solving dependencies... 79s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 81s autopkgtest [13:19:31]: testbed running kernel: Linux 6.18.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 12 16:49:02 UTC 2026 81s autopkgtest [13:19:31]: @@@@@@@@@@@@@@@@@@@@ apt-source fenics 83s Get:1 http://ftpmaster.internal/ubuntu resolute/universe fenics 2:0.10.0.1 (dsc) [1921 B] 83s Get:2 http://ftpmaster.internal/ubuntu resolute/universe fenics 2:0.10.0.1 (tar) [6020 B] 83s gpgv: Signature made Mon Dec 22 12:00:08 2025 UTC 83s gpgv: using RSA key 23C9A93E585819E9126D0A36573EF1E4BD5A01FA 83s gpgv: Can't check signature: No public key 83s dpkg-source: warning: cannot verify inline signature for ./fenics_0.10.0.1.dsc: no acceptable signature found 83s autopkgtest [13:19:33]: testing package fenics version 2:0.10.0.1 83s autopkgtest [13:19:33]: build not needed 83s autopkgtest [13:19:33]: test test-fenics: preparing testbed 83s Reading package lists... 83s Building dependency tree... 83s Reading state information... 83s Solving dependencies... 83s Some packages could not be installed. This may mean that you have 83s requested an impossible situation or if you are using the unstable 83s distribution that some required packages have not yet been created 83s or been moved out of Incoming. 83s The following information may help to resolve the situation: 83s 83s The following packages have unmet dependencies: 84s satisfy:command-line : Depends: fenics:i386 but it is not installable 84s Depends: fenicsx but it is not going to be installed 84s Depends: debhelper-compat (= 13) 84s Depends: python3-dolfinx-mpc but it is not going to be installed 84s Depends: python3-adios4dolfinx but it is not going to be installed 84s Depends: python3-scifem but it is not going to be installed 84s Depends: python3-all but it is not going to be installed 84s Depends: build-essential:amd64 84s Depends: crossbuild-essential-i386:amd64 84s Depends: libc-dev:i386 84s Depends: libstdc++-dev:i386 84s E: Unable to satisfy dependencies. Reached two conflicting assignments: 84s 1. satisfy:command-line:amd64=1 is selected for install 84s 2. satisfy:command-line:amd64 Depends fenics:i386 84s but none of the choices are installable: 84s [no choices] 84s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 84s Reading package lists... 84s Building dependency tree... 84s Reading state information... 84s Solving dependencies... 84s Some packages could not be installed. This may mean that you have 84s requested an impossible situation or if you are using the unstable 84s distribution that some required packages have not yet been created 84s or been moved out of Incoming. 84s The following information may help to resolve the situation: 84s 84s The following packages have unmet dependencies: 84s satisfy:command-line : Depends: fenics:i386 but it is not installable 84s Depends: fenicsx but it is not going to be installed 84s Depends: debhelper-compat (= 13) 84s Depends: python3-dolfinx-mpc but it is not going to be installed 84s Depends: python3-adios4dolfinx but it is not going to be installed 84s Depends: python3-scifem but it is not going to be installed 84s Depends: python3-all but it is not going to be installed 84s Depends: build-essential:amd64 84s Depends: crossbuild-essential-i386:amd64 84s Depends: libc-dev:i386 84s Depends: libstdc++-dev:i386 84s E: Unable to satisfy dependencies. Reached two conflicting assignments: 84s 1. satisfy:command-line:amd64=1 is selected for install 84s 2. satisfy:command-line:amd64 Depends fenics:i386 84s but none of the choices are installable: 84s [no choices] 84s autopkgtest [13:19:34]: test test-fenicsx: preparing testbed 84s test-fenics FAIL badpkg 84s blame: fenics 84s badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. 84s Reading package lists... 85s Building dependency tree... 85s Reading state information... 85s Solving dependencies... 85s Some packages could not be installed. This may mean that you have 85s requested an impossible situation or if you are using the unstable 85s distribution that some required packages have not yet been created 85s or been moved out of Incoming. 85s The following information may help to resolve the situation: 85s 85s The following packages have unmet dependencies: 85s satisfy:command-line : Depends: fenics:i386 but it is not installable 85s Depends: fenicsx but it is not going to be installed 85s Depends: debhelper-compat (= 13) 85s Depends: python3-dolfinx-mpc but it is not going to be installed 85s Depends: python3-adios4dolfinx but it is not going to be installed 85s Depends: python3-scifem but it is not going to be installed 85s Depends: python3-all but it is not going to be installed 85s Depends: build-essential:amd64 85s Depends: crossbuild-essential-i386:amd64 85s Depends: libc-dev:i386 85s Depends: libstdc++-dev:i386 85s E: Unable to satisfy dependencies. Reached two conflicting assignments: 85s 1. satisfy:command-line:amd64=1 is selected for install 85s 2. satisfy:command-line:amd64 Depends fenics:i386 85s but none of the choices are installable: 85s [no choices] 85s autopkgtest [13:19:35]: @@@@@@@@@@@@@@@@@@@@ summary 85s test-fenics FAIL badpkg 85s blame: fenics 85s badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. 85s test-fenicsx FAIL badpkg 85s blame: fenics 85s badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. 85s test-fenicsx FAIL badpkg 85s blame: fenics 85s badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.