0s autopkgtest [11:41:53]: starting date and time: 2024-06-29 11:41:53+0000 0s autopkgtest [11:41:53]: git checkout: 85adf9a1 setup-testbed: prevent /tmp from getting a tmpfs mount 0s autopkgtest [11:41:53]: host juju-7f2275-prod-proposed-migration-environment-9; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.n6oisgzr/out --timeout-copy=6000 --setup-commands 'ln -s /dev/null /etc/systemd/system/bluetooth.service; printf "http_proxy=http://squid.internal:3128\nhttps_proxy=http://squid.internal:3128\nno_proxy=127.0.0.1,127.0.1.1,login.ubuntu.com,localhost,localdomain,novalocal,internal,archive.ubuntu.com,ports.ubuntu.com,security.ubuntu.com,ddebs.ubuntu.com,changelogs.ubuntu.com,keyserver.ubuntu.com,launchpadlibrarian.net,launchpadcontent.net,launchpad.net,10.24.0.0/24,keystone.ps5.canonical.com,objectstorage.prodstack5.canonical.com\n" >> /etc/environment' --apt-pocket=proposed=src:fenics --apt-upgrade fenics --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 --env=ADT_TEST_TRIGGERS=fenics/2:0.8.0.1build1 -- lxd -r lxd-armhf-10.145.243.183 lxd-armhf-10.145.243.183:autopkgtest/ubuntu/oracular/armhf 25s autopkgtest [11:42:18]: testbed dpkg architecture: armhf 27s autopkgtest [11:42:20]: testbed apt version: 2.9.5 27s autopkgtest [11:42:20]: @@@@@@@@@@@@@@@@@@@@ test bed setup 35s Get:1 http://ftpmaster.internal/ubuntu oracular-proposed InRelease [110 kB] 35s Get:2 http://ftpmaster.internal/ubuntu oracular-proposed/multiverse Sources [2576 B] 35s Get:3 http://ftpmaster.internal/ubuntu oracular-proposed/main Sources [53.6 kB] 35s Get:4 http://ftpmaster.internal/ubuntu oracular-proposed/restricted Sources [7052 B] 35s Get:5 http://ftpmaster.internal/ubuntu oracular-proposed/universe Sources [370 kB] 36s Get:6 http://ftpmaster.internal/ubuntu oracular-proposed/main armhf Packages [77.5 kB] 36s Get:7 http://ftpmaster.internal/ubuntu oracular-proposed/restricted armhf Packages [1368 B] 36s Get:8 http://ftpmaster.internal/ubuntu oracular-proposed/universe armhf Packages [312 kB] 36s Get:9 http://ftpmaster.internal/ubuntu oracular-proposed/multiverse armhf Packages [1768 B] 36s Fetched 936 kB in 1s (1181 kB/s) 36s Reading package lists... 54s tee: /proc/self/fd/2: Permission denied 75s Hit:1 http://ftpmaster.internal/ubuntu oracular-proposed InRelease 75s Hit:2 http://ftpmaster.internal/ubuntu oracular InRelease 75s Hit:3 http://ftpmaster.internal/ubuntu oracular-updates InRelease 75s Hit:4 http://ftpmaster.internal/ubuntu oracular-security InRelease 76s Reading package lists... 76s Reading package lists... 76s Building dependency tree... 76s Reading state information... 77s Calculating upgrade... 77s The following packages will be upgraded: 77s dracut-install 77s 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 77s Need to get 35.3 kB of archives. 77s After this operation, 1024 B of additional disk space will be used. 77s Get:1 http://ftpmaster.internal/ubuntu oracular/main armhf dracut-install armhf 102-3ubuntu3 [35.3 kB] 78s Fetched 35.3 kB in 0s (161 kB/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 ... 58374 files and directories currently installed.) 78s Preparing to unpack .../dracut-install_102-3ubuntu3_armhf.deb ... 78s Unpacking dracut-install (102-3ubuntu3) over (102-3ubuntu2) ... 78s Setting up dracut-install (102-3ubuntu3) ... 78s Reading package lists... 78s Building dependency tree... 78s Reading state information... 79s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 81s autopkgtest [11:43:14]: rebooting testbed after setup commands that affected boot 123s autopkgtest [11:43:56]: testbed running kernel: Linux 6.5.0-41-generic #41~22.04.2-Ubuntu SMP PREEMPT_DYNAMIC Mon Jun 3 16:28:24 UTC 2 150s autopkgtest [11:44:23]: @@@@@@@@@@@@@@@@@@@@ apt-source fenics 164s Get:1 http://ftpmaster.internal/ubuntu oracular-proposed/universe fenics 2:0.8.0.1build1 (dsc) [1865 B] 164s Get:2 http://ftpmaster.internal/ubuntu oracular-proposed/universe fenics 2:0.8.0.1build1 (tar) [5792 B] 164s gpgv: Signature made Wed May 29 15:21:24 2024 UTC 164s gpgv: using RSA key 92978A6E195E4921825F7FF0F34F09744E9F5DD9 164s gpgv: Can't check signature: No public key 164s dpkg-source: warning: cannot verify inline signature for ./fenics_0.8.0.1build1.dsc: no acceptable signature found 164s autopkgtest [11:44:37]: testing package fenics version 2:0.8.0.1build1 167s autopkgtest [11:44:40]: build not needed 169s autopkgtest [11:44:42]: test test-fenics: preparing testbed 185s Reading package lists... 185s Building dependency tree... 185s Reading state information... 185s Starting pkgProblemResolver with broken count: 2 185s Starting 2 pkgProblemResolver with broken count: 2 185s Investigating (0) python3-pusimp:armhf < none -> 0.1.1-1 @un puN Ib > 185s Broken python3-pusimp:armhf Breaks on python3-dolfin:armhf < none -> 2019.2.0~legacy20240219.1c52e83-3ubuntu1 @un puN > (< 2019.2.0~legacy20240219.1c52e83-6) 185s Considering python3-dolfin:armhf 5 as a solution to python3-pusimp:armhf 4 185s Re-Instated python3-dolfin:armhf 185s Investigating (0) fenicsx:armhf < none -> 2:0.8.0.1build1 @un puN Ib > 185s Broken fenicsx:armhf Depends on python3-dolfinx:armhf < none | 1:0.8.0-10 @un uH > (>= 1:0.8~) 185s Considering python3-dolfinx:armhf 1 as a solution to fenicsx:armhf 0 185s Re-Instated python3-dolfinx:armhf 185s Broken fenicsx:armhf Depends on dolfinx-doc:armhf < none @un H > (>= 1:0.8~) 185s Broken fenicsx:armhf Depends on basix-doc:armhf < none | 0.8.0-7 @un uH > (>= 0.8~) 185s Considering basix-doc:armhf 0 as a solution to fenicsx:armhf 0 185s Re-Instated basix-doc:armhf 185s Broken fenicsx:armhf Depends on python-ufl-doc:armhf < none | 2024.1.0-1 @un uH > (>= 2024.1~) 185s Considering python-ufl-doc:armhf 0 as a solution to fenicsx:armhf 0 185s Re-Instated python-ufl-doc:armhf 185s Done 185s Some packages could not be installed. This may mean that you have 185s requested an impossible situation or if you are using the unstable 185s distribution that some required packages have not yet been created 185s or been moved out of Incoming. 185s The following information may help to resolve the situation: 185s 185s The following packages have unmet dependencies: 186s fenicsx : Depends: dolfinx-doc (>= 1:0.8~) but it is not installable 186s python3-pusimp : Breaks: python3-dolfin (< 2019.2.0~legacy20240219.1c52e83-6) but 2019.2.0~legacy20240219.1c52e83-3ubuntu1 is to be installed 186s E: Unable to correct problems, you have held broken packages. 186s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from oracular-proposed 192s Reading package lists... 192s Building dependency tree... 192s Reading state information... 192s Starting pkgProblemResolver with broken count: 2 192s Starting 2 pkgProblemResolver with broken count: 2 192s Investigating (0) python3-pusimp:armhf < none -> 0.1.1-1 @un puN Ib > 192s Broken python3-pusimp:armhf Breaks on python3-dolfin:armhf < none -> 2019.2.0~legacy20240219.1c52e83-3ubuntu1 @un puN > (< 2019.2.0~legacy20240219.1c52e83-6) 192s Considering python3-dolfin:armhf 5 as a solution to python3-pusimp:armhf 4 192s Re-Instated python3-dolfin:armhf 192s Investigating (0) fenicsx:armhf < none -> 2:0.8.0.1build1 @un puN Ib > 192s Broken fenicsx:armhf Depends on python3-dolfinx:armhf < none | 1:0.8.0-10 @un uH > (>= 1:0.8~) 192s Considering python3-dolfinx:armhf 1 as a solution to fenicsx:armhf 0 192s Re-Instated python3-dolfinx:armhf 192s Broken fenicsx:armhf Depends on dolfinx-doc:armhf < none @un H > (>= 1:0.8~) 192s Broken fenicsx:armhf Depends on basix-doc:armhf < none | 0.8.0-7 @un uH > (>= 0.8~) 192s Considering basix-doc:armhf 0 as a solution to fenicsx:armhf 0 192s Re-Instated basix-doc:armhf 192s Broken fenicsx:armhf Depends on python-ufl-doc:armhf < none | 2024.1.0-1 @un uH > (>= 2024.1~) 192s Considering python-ufl-doc:armhf 0 as a solution to fenicsx:armhf 0 192s Re-Instated python-ufl-doc:armhf 192s Done 192s Some packages could not be installed. This may mean that you have 192s requested an impossible situation or if you are using the unstable 192s distribution that some required packages have not yet been created 192s or been moved out of Incoming. 192s The following information may help to resolve the situation: 192s 192s The following packages have unmet dependencies: 193s fenicsx : Depends: dolfinx-doc (>= 1:0.8~) but it is not installable 193s python3-pusimp : Breaks: python3-dolfin (< 2019.2.0~legacy20240219.1c52e83-6) but 2019.2.0~legacy20240219.1c52e83-3ubuntu1 is to be installed 193s E: Unable to correct problems, you have held broken packages. 193s autopkgtest: WARNING: Test dependencies are unsatisfiable - calling apt install on test deps directly for further data about failing dependencies in test logs 195s test-fenics FAIL badpkg 195s blame: fenics 195s 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. 195s autopkgtest [11:45:08]: test test-fenicsx: preparing testbed 205s Reading package lists... 206s Building dependency tree... 206s Reading state information... 206s Starting pkgProblemResolver with broken count: 2 206s Starting 2 pkgProblemResolver with broken count: 2 206s Investigating (0) python3-pusimp:armhf < none -> 0.1.1-1 @un puN Ib > 206s Broken python3-pusimp:armhf Breaks on python3-dolfin:armhf < none -> 2019.2.0~legacy20240219.1c52e83-3ubuntu1 @un puN > (< 2019.2.0~legacy20240219.1c52e83-6) 206s Considering python3-dolfin:armhf 5 as a solution to python3-pusimp:armhf 4 206s Re-Instated python3-dolfin:armhf 206s Investigating (0) fenicsx:armhf < none -> 2:0.8.0.1build1 @un puN Ib > 206s Broken fenicsx:armhf Depends on python3-dolfinx:armhf < none | 1:0.8.0-10 @un uH > (>= 1:0.8~) 206s Considering python3-dolfinx:armhf 1 as a solution to fenicsx:armhf 0 206s Re-Instated python3-dolfinx:armhf 206s Broken fenicsx:armhf Depends on dolfinx-doc:armhf < none @un H > (>= 1:0.8~) 206s Broken fenicsx:armhf Depends on basix-doc:armhf < none | 0.8.0-7 @un uH > (>= 0.8~) 206s Considering basix-doc:armhf 0 as a solution to fenicsx:armhf 0 206s Re-Instated basix-doc:armhf 206s Broken fenicsx:armhf Depends on python-ufl-doc:armhf < none | 2024.1.0-1 @un uH > (>= 2024.1~) 206s Considering python-ufl-doc:armhf 0 as a solution to fenicsx:armhf 0 206s Re-Instated python-ufl-doc:armhf 206s Done 206s Some packages could not be installed. This may mean that you have 206s requested an impossible situation or if you are using the unstable 206s distribution that some required packages have not yet been created 206s or been moved out of Incoming. 206s The following information may help to resolve the situation: 206s 206s The following packages have unmet dependencies: 207s fenicsx : Depends: dolfinx-doc (>= 1:0.8~) but it is not installable 207s python3-pusimp : Breaks: python3-dolfin (< 2019.2.0~legacy20240219.1c52e83-6) but 2019.2.0~legacy20240219.1c52e83-3ubuntu1 is to be installed 207s E: Unable to correct problems, you have held broken packages. 207s autopkgtest: WARNING: Test dependencies are unsatisfiable - calling apt install on test deps directly for further data about failing dependencies in test logs 209s test-fenicsx FAIL badpkg 209s blame: fenics 209s 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. 209s autopkgtest [11:45:22]: @@@@@@@@@@@@@@@@@@@@ summary 209s test-fenics FAIL badpkg 209s blame: fenics 209s 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. 209s test-fenicsx FAIL badpkg 209s blame: fenics 209s 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.