0s autopkgtest [09:34:18]: starting date and time: 2024-12-03 09:34:18+0000
  0s autopkgtest [09:34:18]: git checkout: be626eda Fix armhf LXD image generation for plucky
  0s autopkgtest [09:34:18]: host juju-7f2275-prod-proposed-migration-environment-2; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.d0_i8q85/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:openmpi,src:scalapack,src:scotch --apt-upgrade mumps --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 '--env=ADT_TEST_TRIGGERS=openmpi/5.0.6-3 scalapack/2.2.1-7 scotch/7.0.5-1ubuntu2' -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-2@bos03-arm64-40.secgroup --name adt-plucky-arm64-mumps-20241203-093418-juju-7f2275-prod-proposed-migration-environment-2-5cda5757-4077-4c70-b8e8-22624094f225 --image adt/ubuntu-plucky-arm64-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-2 --net-id=net_prod-proposed-migration -e TERM=linux -e ''"'"'http_proxy=http://squid.internal:3128'"'"'' -e ''"'"'https_proxy=http://squid.internal:3128'"'"'' -e ''"'"'no_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'"'"'' --mirror=http://ftpmaster.internal/ubuntu/
134s autopkgtest [09:36:32]: testbed dpkg architecture: arm64
134s autopkgtest [09:36:32]: testbed apt version: 2.9.14ubuntu1
135s autopkgtest [09:36:33]: @@@@@@@@@@@@@@@@@@@@ test bed setup
135s autopkgtest [09:36:33]: testbed release detected to be: None
136s autopkgtest [09:36:34]: updating testbed package index (apt update)
136s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB]
136s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease
136s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease
136s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease
136s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B]
136s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [781 kB]
137s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [15.1 kB]
137s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [65.3 kB]
137s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main arm64 Packages [145 kB]
137s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted arm64 Packages [58.2 kB]
137s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe arm64 Packages [669 kB]
137s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse arm64 Packages [21.3 kB]
137s Fetched 1838 kB in 1s (1918 kB/s)
138s Reading package lists...
138s Reading package lists...
139s Building dependency tree...
139s Reading state information...
139s Calculating upgrade...
140s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
140s Reading package lists...
140s Building dependency tree...
140s Reading state information...
141s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
141s autopkgtest [09:36:39]: upgrading testbed (apt dist-upgrade and autopurge)
141s Reading package lists...
141s Building dependency tree...
141s Reading state information...
142s Calculating upgrade...Starting pkgProblemResolver with broken count: 0
142s Starting 2 pkgProblemResolver with broken count: 0
142s Done
143s Entering ResolveByKeep
143s 
143s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
144s Reading package lists...
144s Building dependency tree...
144s Reading state information...
144s Starting pkgProblemResolver with broken count: 0
144s Starting 2 pkgProblemResolver with broken count: 0
144s Done
145s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
148s autopkgtest [09:36:46]: testbed running kernel: Linux 6.11.0-8-generic #8-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 16 14:19:41 UTC 2024
148s autopkgtest [09:36:46]: @@@@@@@@@@@@@@@@@@@@ apt-source mumps
162s Get:1 http://ftpmaster.internal/ubuntu plucky/universe mumps 5.6.2-2.1build3 (dsc) [3292 B]
162s Get:2 http://ftpmaster.internal/ubuntu plucky/universe mumps 5.6.2-2.1build3 (tar) [4341 kB]
162s Get:3 http://ftpmaster.internal/ubuntu plucky/universe mumps 5.6.2-2.1build3 (diff) [22.3 kB]
163s gpgv: Signature made Wed Jul 31 19:55:05 2024 UTC
163s gpgv:                using RSA key 883FEC247A03BE63B70FD5F920FB053CAF9559CF
163s gpgv:                issuer "eeickmeyer@ubuntu.com"
163s gpgv: Can't check signature: No public key
163s dpkg-source: warning: cannot verify inline signature for ./mumps_5.6.2-2.1build3.dsc: no acceptable signature found
163s autopkgtest [09:37:01]: testing package mumps version 5.6.2-2.1build3
167s autopkgtest [09:37:05]: build not needed
173s autopkgtest [09:37:11]: test mumps-examples-serial: preparing testbed
173s Reading package lists...
173s Building dependency tree...
173s Reading state information...
174s Starting pkgProblemResolver with broken count: 1
174s Starting 2 pkgProblemResolver with broken count: 1
174s Investigating (0) libopenmpi40:arm64 < none -> 5.0.6-3 @un puN Ib >
174s Broken libopenmpi40:arm64 Breaks on libopenmpi3:arm64 < none @un H > (< 5.0.6-3)
174s   Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring
174s   Considering libopenmpi3t64:arm64 8 as a solution to libopenmpi40:arm64 10
174s Broken libopenmpi40:arm64 Breaks on libopenmpi3t64:arm64 < none -> 5.0.5-6 @un puN > (< 5.0.6-3)
174s   Considering libopenmpi3t64:arm64 8 as a solution to libopenmpi40:arm64 10
174s   Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring
174s Done
174s Some packages could not be installed. This may mean that you have
174s requested an impossible situation or if you are using the unstable
174s distribution that some required packages have not yet been created
174s or been moved out of Incoming.
174s The following information may help to resolve the situation:
174s 
174s The following packages have unmet dependencies:
174s  libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3)
174s                 Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed
174s E: Unable to correct problems, you have held broken packages.
174s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed
175s Reading package lists...
175s Building dependency tree...
175s Reading state information...
175s Starting pkgProblemResolver with broken count: 4
176s Starting 2 pkgProblemResolver with broken count: 4
176s Investigating (0) libmumps-5.6t64:arm64 < none -> 5.6.2-2.1build3 @un puN Ib >
176s Broken libmumps-5.6t64:arm64 Depends on libopenmpi3t64:arm64 < none @un pH > (>= 4.1.6)
176s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-5.6t64:arm64 0
176s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-5.6t64:arm64 0
176s Investigating (0) libmumps-64pord-5.6t64:arm64 < none -> 5.6.2-2.1build3 @un puN Ib >
176s Broken libmumps-64pord-5.6t64:arm64 Depends on libopenmpi3t64:arm64 < none @un pH > (>= 4.1.6)
176s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-64pord-5.6t64:arm64 0
176s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-64pord-5.6t64:arm64 0
176s Investigating (0) libmumps-64pord-ptscotch-5.6t64:arm64 < none -> 5.6.2-2.1build3 @un puN Ib >
176s Broken libmumps-64pord-ptscotch-5.6t64:arm64 Depends on libopenmpi3t64:arm64 < none @un pH > (>= 4.1.6)
176s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-64pord-ptscotch-5.6t64:arm64 0
176s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-64pord-ptscotch-5.6t64:arm64 0
176s Investigating (0) libmumps-ptscotch-5.6t64:arm64 < none -> 5.6.2-2.1build3 @un puN Ib >
176s Broken libmumps-ptscotch-5.6t64:arm64 Depends on libopenmpi3t64:arm64 < none @un pH > (>= 4.1.6)
176s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-ptscotch-5.6t64:arm64 0
176s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-ptscotch-5.6t64:arm64 0
176s Done
176s Some packages could not be installed. This may mean that you have
176s requested an impossible situation or if you are using the unstable
176s distribution that some required packages have not yet been created
176s or been moved out of Incoming.
176s The following information may help to resolve the situation:
176s 
176s The following packages have unmet dependencies:
176s  libmumps-5.6t64 : Depends: libopenmpi3t64 (>= 4.1.6) but it is not installable
176s  libmumps-64pord-5.6t64 : Depends: libopenmpi3t64 (>= 4.1.6) but it is not installable
176s  libmumps-64pord-ptscotch-5.6t64 : Depends: libopenmpi3t64 (>= 4.1.6) but it is not installable
176s  libmumps-ptscotch-5.6t64 : Depends: libopenmpi3t64 (>= 4.1.6) but it is not installable
176s E: Unable to correct problems, you have held broken packages.
176s mumps-examples-serial FAIL badpkg
176s blame: mumps
176s 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.
176s autopkgtest [09:37:14]: test mumps-examples-mpi: preparing testbed
176s Reading package lists...
176s Building dependency tree...
176s Reading state information...
177s Starting pkgProblemResolver with broken count: 4
177s Starting 2 pkgProblemResolver with broken count: 4
177s Investigating (0) libmumps-5.6t64:arm64 < none -> 5.6.2-2.1build3 @un puN Ib >
177s Broken libmumps-5.6t64:arm64 Depends on libopenmpi3t64:arm64 < none @un pH > (>= 4.1.6)
177s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-5.6t64:arm64 0
177s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-5.6t64:arm64 0
177s Investigating (0) libmumps-64pord-5.6t64:arm64 < none -> 5.6.2-2.1build3 @un puN Ib >
177s Broken libmumps-64pord-5.6t64:arm64 Depends on libopenmpi3t64:arm64 < none @un pH > (>= 4.1.6)
177s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-64pord-5.6t64:arm64 0
177s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-64pord-5.6t64:arm64 0
177s Investigating (0) libmumps-64pord-ptscotch-5.6t64:arm64 < none -> 5.6.2-2.1build3 @un puN Ib >
177s Broken libmumps-64pord-ptscotch-5.6t64:arm64 Depends on libopenmpi3t64:arm64 < none @un pH > (>= 4.1.6)
177s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-64pord-ptscotch-5.6t64:arm64 0
177s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-64pord-ptscotch-5.6t64:arm64 0
177s Investigating (0) libmumps-ptscotch-5.6t64:arm64 < none -> 5.6.2-2.1build3 @un puN Ib >
177s Broken libmumps-ptscotch-5.6t64:arm64 Depends on libopenmpi3t64:arm64 < none @un pH > (>= 4.1.6)
177s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-ptscotch-5.6t64:arm64 0
177s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-ptscotch-5.6t64:arm64 0
177s Done
177s Some packages could not be installed. This may mean that you have
177s requested an impossible situation or if you are using the unstable
177s distribution that some required packages have not yet been created
177s or been moved out of Incoming.
177s The following information may help to resolve the situation:
177s 
177s The following packages have unmet dependencies:
177s  libmumps-5.6t64 : Depends: libopenmpi3t64 (>= 4.1.6) but it is not installable
177s  libmumps-64pord-5.6t64 : Depends: libopenmpi3t64 (>= 4.1.6) but it is not installable
177s  libmumps-64pord-ptscotch-5.6t64 : Depends: libopenmpi3t64 (>= 4.1.6) but it is not installable
177s  libmumps-ptscotch-5.6t64 : Depends: libopenmpi3t64 (>= 4.1.6) but it is not installable
177s E: Unable to correct problems, you have held broken packages.
177s autopkgtest [09:37:15]: test mumps64-examples-serial: preparing testbed
177s mumps-examples-mpi   FAIL badpkg
177s blame: mumps
177s 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.
178s Reading package lists...
178s Building dependency tree...
178s Reading state information...
178s Starting pkgProblemResolver with broken count: 4
178s Starting 2 pkgProblemResolver with broken count: 4
178s Investigating (0) libmumps-5.6t64:arm64 < none -> 5.6.2-2.1build3 @un puN Ib >
178s Broken libmumps-5.6t64:arm64 Depends on libopenmpi3t64:arm64 < none @un pH > (>= 4.1.6)
178s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-5.6t64:arm64 0
178s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-5.6t64:arm64 0
178s Investigating (0) libmumps-64pord-5.6t64:arm64 < none -> 5.6.2-2.1build3 @un puN Ib >
178s Broken libmumps-64pord-5.6t64:arm64 Depends on libopenmpi3t64:arm64 < none @un pH > (>= 4.1.6)
178s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-64pord-5.6t64:arm64 0
178s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-64pord-5.6t64:arm64 0
178s Investigating (0) libmumps-64pord-ptscotch-5.6t64:arm64 < none -> 5.6.2-2.1build3 @un puN Ib >
178s Broken libmumps-64pord-ptscotch-5.6t64:arm64 Depends on libopenmpi3t64:arm64 < none @un pH > (>= 4.1.6)
178s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-64pord-ptscotch-5.6t64:arm64 0
178s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-64pord-ptscotch-5.6t64:arm64 0
178s Investigating (0) libmumps-ptscotch-5.6t64:arm64 < none -> 5.6.2-2.1build3 @un puN Ib >
178s Broken libmumps-ptscotch-5.6t64:arm64 Depends on libopenmpi3t64:arm64 < none @un pH > (>= 4.1.6)
178s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-ptscotch-5.6t64:arm64 0
178s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-ptscotch-5.6t64:arm64 0
178s Done
178s Some packages could not be installed. This may mean that you have
178s requested an impossible situation or if you are using the unstable
178s distribution that some required packages have not yet been created
178s or been moved out of Incoming.
178s The following information may help to resolve the situation:
178s 
178s The following packages have unmet dependencies:
179s  libmumps-5.6t64 : Depends: libopenmpi3t64 (>= 4.1.6) but it is not installable
179s  libmumps-64pord-5.6t64 : Depends: libopenmpi3t64 (>= 4.1.6) but it is not installable
179s  libmumps-64pord-ptscotch-5.6t64 : Depends: libopenmpi3t64 (>= 4.1.6) but it is not installable
179s  libmumps-ptscotch-5.6t64 : Depends: libopenmpi3t64 (>= 4.1.6) but it is not installable
179s E: Unable to correct problems, you have held broken packages.
179s autopkgtest [09:37:17]: test mumps64-examples-mpi: preparing testbed
179s mumps64-examples-serial FAIL badpkg
179s blame: mumps
179s 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.
179s Reading package lists...
179s Building dependency tree...
179s Reading state information...
180s Starting pkgProblemResolver with broken count: 4
180s Starting 2 pkgProblemResolver with broken count: 4
180s Investigating (0) libmumps-5.6t64:arm64 < none -> 5.6.2-2.1build3 @un puN Ib >
180s Broken libmumps-5.6t64:arm64 Depends on libopenmpi3t64:arm64 < none @un pH > (>= 4.1.6)
180s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-5.6t64:arm64 0
180s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-5.6t64:arm64 0
180s Investigating (0) libmumps-64pord-5.6t64:arm64 < none -> 5.6.2-2.1build3 @un puN Ib >
180s Broken libmumps-64pord-5.6t64:arm64 Depends on libopenmpi3t64:arm64 < none @un pH > (>= 4.1.6)
180s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-64pord-5.6t64:arm64 0
180s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-64pord-5.6t64:arm64 0
180s Investigating (0) libmumps-64pord-ptscotch-5.6t64:arm64 < none -> 5.6.2-2.1build3 @un puN Ib >
180s Broken libmumps-64pord-ptscotch-5.6t64:arm64 Depends on libopenmpi3t64:arm64 < none @un pH > (>= 4.1.6)
180s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-64pord-ptscotch-5.6t64:arm64 0
180s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-64pord-ptscotch-5.6t64:arm64 0
180s Investigating (0) libmumps-ptscotch-5.6t64:arm64 < none -> 5.6.2-2.1build3 @un puN Ib >
180s Broken libmumps-ptscotch-5.6t64:arm64 Depends on libopenmpi3t64:arm64 < none @un pH > (>= 4.1.6)
180s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-ptscotch-5.6t64:arm64 0
180s   Considering libopenmpi3t64:arm64 0 as a solution to libmumps-ptscotch-5.6t64:arm64 0
180s Done
180s Some packages could not be installed. This may mean that you have
180s requested an impossible situation or if you are using the unstable
180s distribution that some required packages have not yet been created
180s or been moved out of Incoming.
180s The following information may help to resolve the situation:
180s 
180s The following packages have unmet dependencies:
180s  libmumps-5.6t64 : Depends: libopenmpi3t64 (>= 4.1.6) but it is not installable
180s  libmumps-64pord-5.6t64 : Depends: libopenmpi3t64 (>= 4.1.6) but it is not installable
180s  libmumps-64pord-ptscotch-5.6t64 : Depends: libopenmpi3t64 (>= 4.1.6) but it is not installable
180s  libmumps-ptscotch-5.6t64 : Depends: libopenmpi3t64 (>= 4.1.6) but it is not installable
180s E: Unable to correct problems, you have held broken packages.
180s autopkgtest [09:37:18]: @@@@@@@@@@@@@@@@@@@@ summary
180s mumps-examples-serial FAIL badpkg
180s blame: mumps
180s 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.
180s mumps-examples-mpi   FAIL badpkg
180s blame: mumps
180s 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.
180s mumps64-examples-serial FAIL badpkg
180s blame: mumps
180s 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.
180s mumps64-examples-mpi FAIL badpkg
180s blame: mumps
180s 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.
180s mumps64-examples-mpi FAIL badpkg
180s blame: mumps
180s 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.
193s nova [W] Using flock in prodstack6-arm64
193s flock: timeout while waiting to get lock
193s Creating nova instance adt-plucky-arm64-mumps-20241203-093418-juju-7f2275-prod-proposed-migration-environment-2-5cda5757-4077-4c70-b8e8-22624094f225 from image adt/ubuntu-plucky-arm64-server-20241203.img (UUID b9293590-1195-42ea-ba16-5ab4b1e94eab)...