0s autopkgtest [12:50:17]: starting date and time: 2026-02-03 12:50:17+0000 0s autopkgtest [12:50:17]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [12:50:17]: host juju-7f2275-prod-proposed-migration-environment-20; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work._iu5qxls/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:libyaml --apt-upgrade ruby3.3 --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 --env=ADT_TEST_TRIGGERS=libyaml/0.2.5-2build3 -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest-cpu2-ram4-disk20-amd64 --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-20@sto01-12.secgroup --name adt-resolute-i386-ruby3.3-20260203-125017-juju-7f2275-prod-proposed-migration-environment-20-a6f2ebba-e4c8-42d1-93ce-6b375e647053 --image adt/ubuntu-resolute-amd64-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-20 --net-id=net_prod-autopkgtest-workers-amd64 -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 4s Creating nova instance adt-resolute-i386-ruby3.3-20260203-125017-juju-7f2275-prod-proposed-migration-environment-20-a6f2ebba-e4c8-42d1-93ce-6b375e647053 from image adt/ubuntu-resolute-amd64-server-20260203.img (UUID 74b0e1d0-93d1-4a18-9efb-95495079a2d9)... 90s autopkgtest [12:51:47]: testbed dpkg architecture: amd64 90s autopkgtest [12:51:47]: testbed apt version: 3.1.14 91s autopkgtest [12:51:48]: @@@@@@@@@@@@@@@@@@@@ test bed setup 91s autopkgtest [12:51:48]: testbed release detected to be: None 92s autopkgtest [12:51:49]: updating testbed package index (apt update) 92s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 92s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 92s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 92s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 92s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [5260 B] 92s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [1317 kB] 93s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [27.9 kB] 93s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [243 kB] 93s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main i386 Packages [233 kB] 93s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 Packages [299 kB] 93s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 c-n-f Metadata [8072 B] 93s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 Packages [32.9 kB] 93s Get:13 http://ftpmaster.internal/ubuntu resolute-proposed/restricted i386 Packages [3692 B] 93s Get:14 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 c-n-f Metadata [336 B] 93s Get:15 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 Packages [1156 kB] 93s Get:16 http://ftpmaster.internal/ubuntu resolute-proposed/universe i386 Packages [443 kB] 93s Get:17 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 c-n-f Metadata [28.7 kB] 93s Get:18 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 Packages [24.7 kB] 93s Get:19 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse i386 Packages [3972 B] 93s Get:20 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 c-n-f Metadata [1060 B] 94s Fetched 3952 kB in 1s (2821 kB/s) 95s Reading package lists... 96s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 96s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 96s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 96s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 97s Reading package lists... 97s Reading package lists... 98s Building dependency tree... 98s Reading state information... 98s Calculating upgrade... 98s The following packages will be upgraded: 98s firmware-sof-signed libyaml-0-2 powermgmt-base 98s 3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 98s Need to get 1756 kB of archives. 98s After this operation, 8192 B disk space will be freed. 98s Get:1 http://ftpmaster.internal/ubuntu resolute/main amd64 firmware-sof-signed all 2025.05.1-1build1 [1696 kB] 98s Get:2 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 libyaml-0-2 amd64 0.2.5-2build3 [52.6 kB] 98s Get:3 http://ftpmaster.internal/ubuntu resolute/main amd64 powermgmt-base all 1.38ubuntu2 [7878 B] 99s dpkg-preconfigure: unable to re-open stdin: No such file or directory 99s Fetched 1756 kB in 0s (5203 kB/s) 99s (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 ... 83957 files and directories currently installed.) 99s Preparing to unpack .../firmware-sof-signed_2025.05.1-1build1_all.deb ... 99s Unpacking firmware-sof-signed (2025.05.1-1build1) over (2025.05.1-1) ... 99s Preparing to unpack .../libyaml-0-2_0.2.5-2build3_amd64.deb ... 99s Unpacking libyaml-0-2:amd64 (0.2.5-2build3) over (0.2.5-2build2) ... 99s Preparing to unpack .../powermgmt-base_1.38ubuntu2_all.deb ... 99s Unpacking powermgmt-base (1.38ubuntu2) over (1.38ubuntu1) ... 100s Setting up powermgmt-base (1.38ubuntu2) ... 100s Setting up libyaml-0-2:amd64 (0.2.5-2build3) ... 100s Setting up firmware-sof-signed (2025.05.1-1build1) ... 100s Processing triggers for man-db (2.13.1-1) ... 100s Processing triggers for libc-bin (2.42-2ubuntu4) ... 100s autopkgtest [12:51:57]: upgrading testbed (apt dist-upgrade and autopurge) 101s Reading package lists... 101s Building dependency tree... 101s Reading state information... 101s Calculating upgrade... 101s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 101s Reading package lists... 102s Building dependency tree... 102s Reading state information... 102s Solving dependencies... 102s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 104s autopkgtest [12:52:01]: testbed running kernel: Linux 6.18.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 12 16:49:02 UTC 2026 105s autopkgtest [12:52:02]: @@@@@@@@@@@@@@@@@@@@ apt-source ruby3.3 108s Get:1 http://ftpmaster.internal/ubuntu resolute/main ruby3.3 3.3.8-2ubuntu2 (dsc) [2540 B] 108s Get:2 http://ftpmaster.internal/ubuntu resolute/main ruby3.3 3.3.8-2ubuntu2 (tar) [14.5 MB] 108s Get:3 http://ftpmaster.internal/ubuntu resolute/main ruby3.3 3.3.8-2ubuntu2 (diff) [68.6 kB] 108s gpgv: Signature made Wed Sep 10 16:25:19 2025 UTC 108s gpgv: using RSA key B35EBCD35C6717BC0ADEB08AEC873ACED468723C 108s gpgv: issuer "nishit.majithia@canonical.com" 108s gpgv: Can't check signature: No public key 108s dpkg-source: warning: cannot verify inline signature for ./ruby3.3_3.3.8-2ubuntu2.dsc: no acceptable signature found 110s autopkgtest [12:52:07]: testing package ruby3.3 version 3.3.8-2ubuntu2 110s autopkgtest [12:52:07]: build not needed 115s autopkgtest [12:52:12]: test run-all: preparing testbed 115s Reading package lists... 115s Building dependency tree... 115s Reading state information... 116s Solving dependencies... 116s Some packages could not be installed. This may mean that you have 116s requested an impossible situation or if you are using the unstable 116s distribution that some required packages have not yet been created 116s or been moved out of Incoming. 116s The following information may help to resolve the situation: 116s 116s The following packages have unmet dependencies: 116s satisfy:command-line : Depends: ruby3.3:i386 116s Depends: libruby3.3:i386 116s Depends: ruby3.3-dev:i386 116s Depends: ruby3.3-doc but it is not going to be installed 116s Depends: libffi-dev but it is not going to be installed 116s Depends: pkg-config (>= 1.8.0-7~) 116s Depends: build-essential:amd64 116s Depends: crossbuild-essential-i386:amd64 116s Depends: libc-dev:i386 116s Depends: libstdc++-dev:i386 116s E: Unable to satisfy dependencies. Reached two conflicting assignments: 116s 1. satisfy:command-line:amd64=1 is selected for install 116s 2. satisfy:command-line:amd64 Depends ruby3.3-dev:i386 116s but none of the choices are installable: 116s - ruby3.3-dev:i386=3.3.8-2ubuntu2 is not selected for install 116s - ruby3.3-dev:i386=3.3.8-2ubuntu3 is not selected for install 116s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 116s Reading package lists... 116s Building dependency tree... 116s Reading state information... 117s Solving dependencies... 117s Some packages could not be installed. This may mean that you have 117s requested an impossible situation or if you are using the unstable 117s distribution that some required packages have not yet been created 117s or been moved out of Incoming. 117s The following information may help to resolve the situation: 117s 117s The following packages have unmet dependencies: 117s satisfy:command-line : Depends: ruby3.3:i386 117s Depends: libruby3.3:i386 117s Depends: ruby3.3-dev:i386 117s Depends: ruby3.3-doc but it is not going to be installed 117s Depends: libffi-dev but it is not going to be installed 117s Depends: pkg-config (>= 1.8.0-7~) 117s Depends: build-essential:amd64 117s Depends: crossbuild-essential-i386:amd64 117s Depends: libc-dev:i386 117s Depends: libstdc++-dev:i386 117s E: Unable to satisfy dependencies. Reached two conflicting assignments: 117s 1. satisfy:command-line:amd64=1 is selected for install 117s 2. satisfy:command-line:amd64 Depends libruby3.3:i386 117s but none of the choices are installable: 117s - libruby3.3:i386=3.3.8-2ubuntu3 is not selected for install 117s - libruby3.3:i386=3.3.8-2ubuntu2 is not selected for install 117s run-all FAIL badpkg 117s blame: ruby3.3 117s 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. 117s autopkgtest [12:52:14]: test bundled-gems: preparing testbed 117s Reading package lists... 117s Building dependency tree... 117s Reading state information... 117s Solving dependencies... 117s Some packages could not be installed. This may mean that you have 117s requested an impossible situation or if you are using the unstable 117s distribution that some required packages have not yet been created 117s or been moved out of Incoming. 117s The following information may help to resolve the situation: 117s 117s The following packages have unmet dependencies: 117s satisfy:command-line : Depends: ruby3.3:i386 117s Depends: libruby3.3:i386 117s Depends: ruby3.3-dev:i386 117s Depends: ruby3.3-doc but it is not going to be installed 117s Depends: libffi-dev but it is not going to be installed 117s Depends: pkg-config (>= 1.8.0-7~) 117s Depends: build-essential:amd64 117s Depends: crossbuild-essential-i386:amd64 117s Depends: libc-dev:i386 117s Depends: libstdc++-dev:i386 117s E: Unable to satisfy dependencies. Reached two conflicting assignments: 117s 1. satisfy:command-line:amd64=1 is selected for install 117s 2. satisfy:command-line:amd64 Depends libruby3.3:i386 117s but none of the choices are installable: 117s - libruby3.3:i386=3.3.8-2ubuntu3 is not selected for install 117s - libruby3.3:i386=3.3.8-2ubuntu2 is not selected for install 117s bundled-gems FAIL badpkg 117s blame: ruby3.3 117s 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. 117s autopkgtest [12:52:14]: test builtin-extensions: preparing testbed 118s Reading package lists... 118s Building dependency tree... 118s Reading state information... 118s Solving dependencies... 118s Some packages could not be installed. This may mean that you have 118s requested an impossible situation or if you are using the unstable 118s distribution that some required packages have not yet been created 118s or been moved out of Incoming. 118s The following information may help to resolve the situation: 118s 118s The following packages have unmet dependencies: 118s satisfy:command-line : Depends: ruby3.3:i386 118s Depends: libruby3.3:i386 118s Depends: ruby3.3-dev:i386 118s Depends: ruby3.3-doc but it is not going to be installed 118s Depends: libffi-dev but it is not going to be installed 118s Depends: pkg-config (>= 1.8.0-7~) 118s Depends: build-essential:amd64 118s Depends: crossbuild-essential-i386:amd64 118s Depends: libc-dev:i386 118s Depends: libstdc++-dev:i386 118s E: Unable to satisfy dependencies. Reached two conflicting assignments: 118s 1. satisfy:command-line:amd64=1 is selected for install 118s 2. satisfy:command-line:amd64 Depends libruby3.3:i386 118s but none of the choices are installable: 118s - libruby3.3:i386=3.3.8-2ubuntu3 is not selected for install 118s - libruby3.3:i386=3.3.8-2ubuntu2 is not selected for install 118s autopkgtest [12:52:15]: test rubyconfig: preparing testbed 118s builtin-extensions FAIL badpkg 118s blame: ruby3.3 118s 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. 118s Reading package lists... 119s Building dependency tree... 119s Reading state information... 119s Solving dependencies... 119s Some packages could not be installed. This may mean that you have 119s requested an impossible situation or if you are using the unstable 119s distribution that some required packages have not yet been created 119s or been moved out of Incoming. 119s The following information may help to resolve the situation: 119s 119s The following packages have unmet dependencies: 119s satisfy:command-line : Depends: ruby3.3:i386 119s Depends: libruby3.3:i386 119s Depends: ruby3.3-dev:i386 119s Depends: ruby3.3-doc but it is not going to be installed 119s Depends: libffi-dev but it is not going to be installed 119s Depends: pkg-config (>= 1.8.0-7~) 119s Depends: build-essential:amd64 119s Depends: crossbuild-essential-i386:amd64 119s Depends: libc-dev:i386 119s Depends: libstdc++-dev:i386 119s E: Unable to satisfy dependencies. Reached two conflicting assignments: 119s 1. satisfy:command-line:amd64=1 is selected for install 119s 2. satisfy:command-line:amd64 Depends libruby3.3:i386 119s but none of the choices are installable: 119s - libruby3.3:i386=3.3.8-2ubuntu3 is not selected for install 119s - libruby3.3:i386=3.3.8-2ubuntu2 is not selected for install 119s autopkgtest [12:52:16]: test pkg-config: preparing testbed 119s rubyconfig FAIL badpkg 119s blame: ruby3.3 119s 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. 119s Reading package lists... 119s Building dependency tree... 119s Reading state information... 120s Solving dependencies... 120s Some packages could not be installed. This may mean that you have 120s requested an impossible situation or if you are using the unstable 120s distribution that some required packages have not yet been created 120s or been moved out of Incoming. 120s The following information may help to resolve the situation: 120s 120s The following packages have unmet dependencies: 120s satisfy:command-line : Depends: ruby3.3:i386 120s Depends: libruby3.3:i386 120s Depends: ruby3.3-dev:i386 120s Depends: ruby3.3-doc but it is not going to be installed 120s Depends: libffi-dev but it is not going to be installed 120s Depends: pkg-config (>= 1.8.0-7~) 120s Depends: build-essential:amd64 120s Depends: crossbuild-essential-i386:amd64 120s Depends: libc-dev:i386 120s Depends: libstdc++-dev:i386 120s E: Unable to satisfy dependencies. Reached two conflicting assignments: 120s 1. satisfy:command-line:amd64=1 is selected for install 120s 2. satisfy:command-line:amd64 Depends libruby3.3:i386 120s but none of the choices are installable: 120s - libruby3.3:i386=3.3.8-2ubuntu3 is not selected for install 120s - libruby3.3:i386=3.3.8-2ubuntu2 is not selected for install 120s autopkgtest [12:52:17]: @@@@@@@@@@@@@@@@@@@@ summary 120s run-all FAIL badpkg 120s blame: ruby3.3 120s 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. 120s bundled-gems FAIL badpkg 120s blame: ruby3.3 120s 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. 120s builtin-extensions FAIL badpkg 120s blame: ruby3.3 120s 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. 120s rubyconfig FAIL badpkg 120s blame: ruby3.3 120s 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. 120s pkg-config FAIL badpkg 120s blame: ruby3.3 120s 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. 120s pkg-config FAIL badpkg 120s blame: ruby3.3 120s 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.