0s autopkgtest [13:25:43]: starting date and time: 2026-02-02 13:25:43+0000 0s autopkgtest [13:25:43]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [13:25:43]: host juju-7f2275-prod-proposed-migration-environment-15; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.mbzasw1l/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:scifem --apt-upgrade fenics --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 --env=ADT_TEST_TRIGGERS=scifem/0.16.1-1build2 -- 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-132543-juju-7f2275-prod-proposed-migration-environment-15-a8848e42-8fbf-43dc-ac5d-dd58283e3fa4 --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/ 4s Creating nova instance adt-resolute-i386-fenics-20260202-132543-juju-7f2275-prod-proposed-migration-environment-15-a8848e42-8fbf-43dc-ac5d-dd58283e3fa4 from image adt/ubuntu-resolute-amd64-server-20260202.img (UUID 54e94ad2-f1e5-466e-b281-ee6f460760b3)... 73s autopkgtest [13:26:56]: testbed dpkg architecture: amd64 73s autopkgtest [13:26:56]: testbed apt version: 3.1.14 74s autopkgtest [13:26:57]: @@@@@@@@@@@@@@@@@@@@ test bed setup 74s autopkgtest [13:26:57]: testbed release detected to be: None 74s autopkgtest [13:26:57]: updating testbed package index (apt update) 75s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 75s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 75s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 75s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 75s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [1266 kB] 75s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [102 kB] 75s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [27.9 kB] 75s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [2816 B] 75s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 Packages [120 kB] 75s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/main i386 Packages [102 kB] 75s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 c-n-f Metadata [3536 B] 75s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/restricted i386 Packages [3692 B] 75s Get:13 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 Packages [12.3 kB] 75s Get:14 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 c-n-f Metadata [336 B] 75s Get:15 http://ftpmaster.internal/ubuntu resolute-proposed/universe i386 Packages [405 kB] 75s Get:16 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 Packages [1078 kB] 76s Get:17 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 c-n-f Metadata [27.1 kB] 76s Get:18 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse i386 Packages [3632 B] 76s Get:19 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 Packages [24.7 kB] 76s Get:20 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 c-n-f Metadata [1060 B] 76s Fetched 3304 kB in 1s (3002 kB/s) 77s Reading package lists... 77s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 78s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 78s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 78s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 78s Reading package lists... 78s Reading package lists... 78s Building dependency tree... 78s Reading state information... 79s Calculating upgrade... 79s The following packages will be upgraded: 79s libgpg-error-l10n libgpg-error0 pci.ids 79s 3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 79s Need to get 391 kB of archives. 79s After this operation, 12.3 kB of additional disk space will be used. 79s Get:1 http://ftpmaster.internal/ubuntu resolute/main amd64 libgpg-error-l10n all 1.58-2 [9244 B] 79s Get:2 http://ftpmaster.internal/ubuntu resolute/main amd64 libgpg-error0 amd64 1.58-2 [83.3 kB] 79s Get:3 http://ftpmaster.internal/ubuntu resolute/main amd64 pci.ids all 0.0~2026.01.31-1 [299 kB] 79s dpkg-preconfigure: unable to re-open stdin: No such file or directory 79s Fetched 391 kB in 0s (24.6 MB/s) 79s (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.) 79s Preparing to unpack .../libgpg-error-l10n_1.58-2_all.deb ... 79s Unpacking libgpg-error-l10n (1.58-2) over (1.58-1build1) ... 79s Preparing to unpack .../libgpg-error0_1.58-2_amd64.deb ... 79s Unpacking libgpg-error0:amd64 (1.58-2) over (1.58-1build1) ... 79s Preparing to unpack .../pci.ids_0.0~2026.01.31-1_all.deb ... 79s Unpacking pci.ids (0.0~2026.01.31-1) over (0.0~2025.12.16-1) ... 79s Setting up pci.ids (0.0~2026.01.31-1) ... 79s Setting up libgpg-error0:amd64 (1.58-2) ... 79s Setting up libgpg-error-l10n (1.58-2) ... 79s Processing triggers for libc-bin (2.42-2ubuntu4) ... 79s autopkgtest [13:27:02]: upgrading testbed (apt dist-upgrade and autopurge) 80s Reading package lists... 80s Building dependency tree... 80s Reading state information... 80s Calculating upgrade... 80s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 80s Reading package lists... 80s Building dependency tree... 80s Reading state information... 80s Solving dependencies... 81s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 83s autopkgtest [13:27:06]: testbed running kernel: Linux 6.18.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 12 16:49:02 UTC 2026 83s autopkgtest [13:27:06]: @@@@@@@@@@@@@@@@@@@@ apt-source fenics 84s Get:1 http://ftpmaster.internal/ubuntu resolute/universe fenics 2:0.10.0.1 (dsc) [1921 B] 84s Get:2 http://ftpmaster.internal/ubuntu resolute/universe fenics 2:0.10.0.1 (tar) [6020 B] 84s gpgv: Signature made Mon Dec 22 12:00:08 2025 UTC 84s gpgv: using RSA key 23C9A93E585819E9126D0A36573EF1E4BD5A01FA 84s gpgv: Can't check signature: No public key 84s dpkg-source: warning: cannot verify inline signature for ./fenics_0.10.0.1.dsc: no acceptable signature found 84s autopkgtest [13:27:07]: testing package fenics version 2:0.10.0.1 84s autopkgtest [13:27:07]: build not needed 85s autopkgtest [13:27:08]: test test-fenics: preparing testbed 85s 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: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 86s Reading package lists... 86s Building dependency tree... 86s Reading state information... 86s Solving dependencies... 86s Some packages could not be installed. This may mean that you have 86s requested an impossible situation or if you are using the unstable 86s distribution that some required packages have not yet been created 86s or been moved out of Incoming. 86s The following information may help to resolve the situation: 86s 86s The following packages have unmet dependencies: 86s satisfy:command-line : Depends: fenics:i386 but it is not installable 86s Depends: fenicsx but it is not going to be installed 86s Depends: debhelper-compat (= 13) 86s Depends: python3-dolfinx-mpc but it is not going to be installed 86s Depends: python3-adios4dolfinx but it is not going to be installed 86s Depends: python3-scifem but it is not going to be installed 86s Depends: python3-all but it is not going to be installed 86s Depends: build-essential:amd64 86s Depends: crossbuild-essential-i386:amd64 86s Depends: libc-dev:i386 86s Depends: libstdc++-dev:i386 86s E: Unable to satisfy dependencies. Reached two conflicting assignments: 86s 1. satisfy:command-line:amd64=1 is selected for install 86s 2. satisfy:command-line:amd64 Depends fenics:i386 86s but none of the choices are installable: 86s [no choices] 86s autopkgtest [13:27:09]: test test-fenicsx: preparing testbed 86s test-fenics FAIL badpkg 86s blame: fenics 86s 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. 86s Reading package lists... 86s Building dependency tree... 86s Reading state information... 86s Solving dependencies... 86s Some packages could not be installed. This may mean that you have 86s requested an impossible situation or if you are using the unstable 86s distribution that some required packages have not yet been created 86s or been moved out of Incoming. 86s The following information may help to resolve the situation: 86s 86s The following packages have unmet dependencies: 86s satisfy:command-line : Depends: fenics:i386 but it is not installable 86s Depends: fenicsx but it is not going to be installed 86s Depends: debhelper-compat (= 13) 86s Depends: python3-dolfinx-mpc but it is not going to be installed 86s Depends: python3-adios4dolfinx but it is not going to be installed 86s Depends: python3-scifem but it is not going to be installed 86s Depends: python3-all but it is not going to be installed 86s Depends: build-essential:amd64 86s Depends: crossbuild-essential-i386:amd64 86s Depends: libc-dev:i386 86s Depends: libstdc++-dev:i386 86s E: Unable to satisfy dependencies. Reached two conflicting assignments: 86s 1. satisfy:command-line:amd64=1 is selected for install 86s 2. satisfy:command-line:amd64 Depends fenics:i386 86s but none of the choices are installable: 86s [no choices] 87s test-fenicsx FAIL badpkg 87s blame: fenics 87s 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. 87s autopkgtest [13:27:10]: @@@@@@@@@@@@@@@@@@@@ summary 87s test-fenics FAIL badpkg 87s blame: fenics 87s 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. 87s test-fenicsx FAIL badpkg 87s blame: fenics 87s 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.