0s autopkgtest [19:50:14]: starting date and time: 2025-09-04 19:50:14+0000 0s autopkgtest [19:50:14]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [19:50:14]: host juju-7f2275-prod-proposed-migration-environment-2; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.nj5s9cth/out --timeout-copy=6000 -a i386 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:build-essential --apt-upgrade ruby3.3 --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 --env=ADT_TEST_TRIGGERS=build-essential/12.12ubuntu2 -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest-cpu2-ram4-disk20-amd64 --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-2@sto01-1.secgroup --name adt-questing-i386-ruby3.3-20250904-195013-juju-7f2275-prod-proposed-migration-environment-2-4e5c6f83-1770-4a9b-bd5c-1f86eb62c1e9 --image adt/ubuntu-questing-amd64-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-2 --net-id=net_prod-autopkgtest-workers-amd64 -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 3s Creating nova instance adt-questing-i386-ruby3.3-20250904-195013-juju-7f2275-prod-proposed-migration-environment-2-4e5c6f83-1770-4a9b-bd5c-1f86eb62c1e9 from image adt/ubuntu-questing-amd64-server-20250904.img (UUID ad84c7a7-c39c-42a3-aa38-d5a0dd25b14d)... 44s autopkgtest [19:50:58]: testbed dpkg architecture: amd64 44s autopkgtest [19:50:58]: testbed apt version: 3.1.5ubuntu1 45s autopkgtest [19:50:59]: @@@@@@@@@@@@@@@@@@@@ test bed setup 45s autopkgtest [19:50:59]: testbed release detected to be: None 45s autopkgtest [19:50:59]: updating testbed package index (apt update) 45s Get:1 http://ftpmaster.internal/ubuntu questing-proposed InRelease [265 kB] 45s Hit:2 http://ftpmaster.internal/ubuntu questing InRelease 46s Hit:3 http://ftpmaster.internal/ubuntu questing-updates InRelease 46s Hit:4 http://ftpmaster.internal/ubuntu questing-security InRelease 46s Get:5 http://ftpmaster.internal/ubuntu questing-proposed/multiverse Sources [14.1 kB] 46s Get:6 http://ftpmaster.internal/ubuntu questing-proposed/main Sources [59.4 kB] 46s Get:7 http://ftpmaster.internal/ubuntu questing-proposed/restricted Sources [3848 B] 46s Get:8 http://ftpmaster.internal/ubuntu questing-proposed/universe Sources [234 kB] 46s Get:9 http://ftpmaster.internal/ubuntu questing-proposed/main i386 Packages [80.7 kB] 46s Get:10 http://ftpmaster.internal/ubuntu questing-proposed/main amd64 Packages [116 kB] 46s Get:11 http://ftpmaster.internal/ubuntu questing-proposed/main amd64 c-n-f Metadata [4048 B] 46s Get:12 http://ftpmaster.internal/ubuntu questing-proposed/restricted amd64 Packages [20.7 kB] 46s Get:13 http://ftpmaster.internal/ubuntu questing-proposed/restricted i386 Packages [2448 B] 46s Get:14 http://ftpmaster.internal/ubuntu questing-proposed/restricted amd64 c-n-f Metadata [120 B] 46s Get:15 http://ftpmaster.internal/ubuntu questing-proposed/universe i386 Packages [141 kB] 46s Get:16 http://ftpmaster.internal/ubuntu questing-proposed/universe amd64 Packages [229 kB] 46s Get:17 http://ftpmaster.internal/ubuntu questing-proposed/universe amd64 c-n-f Metadata [8728 B] 46s Get:18 http://ftpmaster.internal/ubuntu questing-proposed/multiverse i386 Packages [2480 B] 46s Get:19 http://ftpmaster.internal/ubuntu questing-proposed/multiverse amd64 Packages [5468 B] 46s Get:20 http://ftpmaster.internal/ubuntu questing-proposed/multiverse amd64 c-n-f Metadata [572 B] 47s Fetched 1188 kB in 1s (1471 kB/s) 48s Reading package lists... 48s autopkgtest [19:51:02]: upgrading testbed (apt dist-upgrade and autopurge) 48s Reading package lists... 48s Building dependency tree... 48s Reading state information... 49s Calculating upgrade... 49s The following packages will be upgraded: 49s bpftrace cron cron-daemon-common cryptsetup-bin dash libbrotli1 49s libcryptsetup12 49s 7 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 49s Need to get 3064 kB of archives. 49s After this operation, 225 kB of additional disk space will be used. 49s Get:1 http://ftpmaster.internal/ubuntu questing/main amd64 dash amd64 0.5.12-12ubuntu2 [98.7 kB] 49s Get:2 http://ftpmaster.internal/ubuntu questing/main amd64 cron amd64 3.0pl1-196ubuntu2 [89.1 kB] 49s Get:3 http://ftpmaster.internal/ubuntu questing/main amd64 libcryptsetup12 amd64 2:2.8.0-1ubuntu2 [293 kB] 49s Get:4 http://ftpmaster.internal/ubuntu questing/main amd64 cron-daemon-common all 3.0pl1-196ubuntu2 [15.3 kB] 49s Get:5 http://ftpmaster.internal/ubuntu questing/main amd64 bpftrace amd64 0.23.5-1ubuntu1 [1999 kB] 49s Get:6 http://ftpmaster.internal/ubuntu questing/main amd64 cryptsetup-bin amd64 2:2.8.0-1ubuntu2 [232 kB] 49s Get:7 http://ftpmaster.internal/ubuntu questing/main amd64 libbrotli1 amd64 1.1.0-2build5 [337 kB] 49s Preconfiguring packages ... 50s Fetched 3064 kB in 1s (4675 kB/s) 50s (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 ... 121119 files and directories currently installed.) 50s Preparing to unpack .../dash_0.5.12-12ubuntu2_amd64.deb ... 50s Unpacking dash (0.5.12-12ubuntu2) over (0.5.12-12ubuntu1) ... 50s Setting up dash (0.5.12-12ubuntu2) ... 50s (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 ... 121119 files and directories currently installed.) 50s Preparing to unpack .../0-cron_3.0pl1-196ubuntu2_amd64.deb ... 50s Unpacking cron (3.0pl1-196ubuntu2) over (3.0pl1-196ubuntu1) ... 50s Preparing to unpack .../1-libcryptsetup12_2%3a2.8.0-1ubuntu2_amd64.deb ... 50s Unpacking libcryptsetup12:amd64 (2:2.8.0-1ubuntu2) over (2:2.8.0-1ubuntu1) ... 50s Preparing to unpack .../2-cron-daemon-common_3.0pl1-196ubuntu2_all.deb ... 50s Unpacking cron-daemon-common (3.0pl1-196ubuntu2) over (3.0pl1-196ubuntu1) ... 50s Preparing to unpack .../3-bpftrace_0.23.5-1ubuntu1_amd64.deb ... 50s Unpacking bpftrace (0.23.5-1ubuntu1) over (0.23.2-1ubuntu2) ... 50s Preparing to unpack .../4-cryptsetup-bin_2%3a2.8.0-1ubuntu2_amd64.deb ... 50s Unpacking cryptsetup-bin (2:2.8.0-1ubuntu2) over (2:2.8.0-1ubuntu1) ... 50s Preparing to unpack .../5-libbrotli1_1.1.0-2build5_amd64.deb ... 50s Unpacking libbrotli1:amd64 (1.1.0-2build5) over (1.1.0-2build4) ... 50s Setting up bpftrace (0.23.5-1ubuntu1) ... 50s Setting up libbrotli1:amd64 (1.1.0-2build5) ... 50s Setting up libcryptsetup12:amd64 (2:2.8.0-1ubuntu2) ... 50s Setting up cron-daemon-common (3.0pl1-196ubuntu2) ... 50s Setting up cryptsetup-bin (2:2.8.0-1ubuntu2) ... 50s Setting up cron (3.0pl1-196ubuntu2) ... 51s Processing triggers for debianutils (5.23.2) ... 51s Processing triggers for libc-bin (2.42-0ubuntu1) ... 51s Processing triggers for man-db (2.13.1-1) ... 52s Reading package lists... 52s Building dependency tree... 52s Reading state information... 52s Solving dependencies... 52s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 52s autopkgtest [19:51:06]: rebooting testbed after setup commands that affected boot 80s autopkgtest [19:51:34]: testbed running kernel: Linux 6.16.0-16-generic #16-Ubuntu SMP PREEMPT_DYNAMIC Sat Aug 16 17:05:34 UTC 2025 82s autopkgtest [19:51:36]: @@@@@@@@@@@@@@@@@@@@ apt-source ruby3.3 89s Get:1 http://ftpmaster.internal/ubuntu questing/main ruby3.3 3.3.8-2ubuntu1 (dsc) [2711 B] 89s Get:2 http://ftpmaster.internal/ubuntu questing/main ruby3.3 3.3.8-2ubuntu1 (tar) [14.5 MB] 89s Get:3 http://ftpmaster.internal/ubuntu questing/main ruby3.3 3.3.8-2ubuntu1 (diff) [67.5 kB] 89s gpgv: Signature made Wed Jun 11 17:12:36 2025 UTC 89s gpgv: using RSA key 439884E6862A429C290DF63B033C4CA276024834 89s gpgv: issuer "athos.ribeiro@canonical.com" 89s gpgv: Can't check signature: No public key 89s dpkg-source: warning: cannot verify inline signature for ./ruby3.3_3.3.8-2ubuntu1.dsc: no acceptable signature found 90s autopkgtest [19:51:44]: testing package ruby3.3 version 3.3.8-2ubuntu1 91s autopkgtest [19:51:45]: build not needed 98s autopkgtest [19:51:52]: test run-all: preparing testbed 98s Reading package lists... 98s Building dependency tree... 98s Reading state information... 98s Solving dependencies... 98s Some packages could not be installed. This may mean that you have 98s requested an impossible situation or if you are using the unstable 98s distribution that some required packages have not yet been created 98s or been moved out of Incoming. 98s The following information may help to resolve the situation: 98s 98s The following packages have unmet dependencies: 98s satisfy:command-line : Depends: ruby3.3:i386 98s Depends: libruby3.3:i386 98s Depends: ruby3.3-dev:i386 98s Depends: ruby3.3-doc but it is not going to be installed 98s Depends: libffi-dev but it is not going to be installed 98s Depends: pkg-config (>= 1.8.0-7~) 98s Depends: build-essential:amd64 98s Depends: crossbuild-essential-i386:amd64 98s Depends: libc-dev:i386 98s Depends: libstdc++-dev:i386 98s E: Unable to satisfy dependencies. Reached two conflicting decisions: 98s 1. libruby3.3:i386=3.3.8-2ubuntu1 is selected for install because: 98s 1. satisfy:command-line:amd64=1 is selected for install 98s 2. satisfy:command-line:amd64 Depends libruby3.3:i386 98s 2. libruby3.3:i386 Depends ruby-ruby2-keywords:i386 (>= 0.0.5-1~) 98s but none of the choices are installable: 98s [no choices] 98s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from questing-proposed 98s Reading package lists... 99s Building dependency tree... 99s Reading state information... 99s Solving dependencies... 99s Some packages could not be installed. This may mean that you have 99s requested an impossible situation or if you are using the unstable 99s distribution that some required packages have not yet been created 99s or been moved out of Incoming. 99s The following information may help to resolve the situation: 99s 99s The following packages have unmet dependencies: 99s satisfy:command-line : Depends: ruby3.3:i386 99s Depends: libruby3.3:i386 99s Depends: ruby3.3-dev:i386 99s Depends: ruby3.3-doc but it is not going to be installed 99s Depends: libffi-dev but it is not going to be installed 99s Depends: pkg-config (>= 1.8.0-7~) 99s Depends: build-essential:amd64 99s Depends: crossbuild-essential-i386:amd64 99s Depends: libc-dev:i386 99s Depends: libstdc++-dev:i386 99s autopkgtest [19:51:53]: test bundled-gems: preparing testbed 99s E: Unable to satisfy dependencies. Reached two conflicting decisions: 99s 1. libruby3.3:i386=3.3.8-2ubuntu1 is selected for install because: 99s 1. satisfy:command-line:amd64=1 is selected for install 99s 2. satisfy:command-line:amd64 Depends libruby3.3:i386 99s 2. libruby3.3:i386 Depends ruby-ruby2-keywords:i386 (>= 0.0.5-1~) 99s but none of the choices are installable: 99s [no choices] 99s run-all FAIL badpkg 99s blame: ruby3.3 99s 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. 99s Reading package lists... 99s Building dependency tree... 99s Reading state information... 99s Solving dependencies... 99s Some packages could not be installed. This may mean that you have 99s requested an impossible situation or if you are using the unstable 99s distribution that some required packages have not yet been created 99s or been moved out of Incoming. 99s The following information may help to resolve the situation: 99s 99s The following packages have unmet dependencies: 99s satisfy:command-line : Depends: ruby3.3:i386 99s Depends: libruby3.3:i386 99s Depends: ruby3.3-dev:i386 99s Depends: ruby3.3-doc but it is not going to be installed 99s Depends: libffi-dev but it is not going to be installed 99s Depends: pkg-config (>= 1.8.0-7~) 99s Depends: build-essential:amd64 99s Depends: crossbuild-essential-i386:amd64 99s Depends: libc-dev:i386 99s Depends: libstdc++-dev:i386 99s E: Unable to satisfy dependencies. Reached two conflicting decisions: 99s 1. libruby3.3:i386=3.3.8-2ubuntu1 is selected for install because: 99s 1. satisfy:command-line:amd64=1 is selected for install 99s 2. satisfy:command-line:amd64 Depends libruby3.3:i386 99s 2. libruby3.3:i386 Depends ruby-ruby2-keywords:i386 (>= 0.0.5-1~) 99s but none of the choices are installable: 99s [no choices] 99s bundled-gems FAIL badpkg 99s blame: ruby3.3 99s autopkgtest [19:51:53]: test builtin-extensions: preparing testbed 99s 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. 99s Reading package lists... 100s Building dependency tree... 100s Reading state information... 100s Solving dependencies... 100s Some packages could not be installed. This may mean that you have 100s requested an impossible situation or if you are using the unstable 100s distribution that some required packages have not yet been created 100s or been moved out of Incoming. 100s The following information may help to resolve the situation: 100s 100s The following packages have unmet dependencies: 100s satisfy:command-line : Depends: ruby3.3:i386 100s Depends: libruby3.3:i386 100s Depends: ruby3.3-dev:i386 100s Depends: ruby3.3-doc but it is not going to be installed 100s Depends: libffi-dev but it is not going to be installed 100s Depends: pkg-config (>= 1.8.0-7~) 100s Depends: build-essential:amd64 100s Depends: crossbuild-essential-i386:amd64 100s Depends: libc-dev:i386 100s Depends: libstdc++-dev:i386 100s E: Unable to satisfy dependencies. Reached two conflicting decisions: 100s 1. libruby3.3:i386=3.3.8-2ubuntu1 is selected for install because: 100s 1. satisfy:command-line:amd64=1 is selected for install 100s 2. satisfy:command-line:amd64 Depends libruby3.3:i386 100s 2. libruby3.3:i386 Depends ruby-ruby2-keywords:i386 (>= 0.0.5-1~) 100s but none of the choices are installable: 100s [no choices] 100s autopkgtest [19:51:54]: test rubyconfig: preparing testbed 100s builtin-extensions FAIL badpkg 100s blame: ruby3.3 100s 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. 100s Reading package lists... 100s Building dependency tree... 100s Reading state information... 100s Solving dependencies... 100s Some packages could not be installed. This may mean that you have 100s requested an impossible situation or if you are using the unstable 100s distribution that some required packages have not yet been created 100s or been moved out of Incoming. 100s The following information may help to resolve the situation: 100s 100s The following packages have unmet dependencies: 100s satisfy:command-line : Depends: ruby3.3:i386 100s Depends: libruby3.3:i386 100s Depends: ruby3.3-dev:i386 100s Depends: ruby3.3-doc but it is not going to be installed 100s Depends: libffi-dev but it is not going to be installed 100s Depends: pkg-config (>= 1.8.0-7~) 100s Depends: build-essential:amd64 100s Depends: crossbuild-essential-i386:amd64 100s Depends: libc-dev:i386 100s Depends: libstdc++-dev:i386 100s E: Unable to satisfy dependencies. Reached two conflicting decisions: 100s 1. libruby3.3:i386=3.3.8-2ubuntu1 is selected for install because: 100s 1. satisfy:command-line:amd64=1 is selected for install 100s 2. satisfy:command-line:amd64 Depends libruby3.3:i386 100s 2. libruby3.3:i386 Depends ruby-ruby2-keywords:i386 (>= 0.0.5-1~) 100s but none of the choices are installable: 100s [no choices] 100s autopkgtest [19:51:54]: test pkg-config: preparing testbed 100s rubyconfig FAIL badpkg 100s blame: ruby3.3 100s 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. 101s Reading package lists... 101s Building dependency tree... 101s Reading state information... 101s Solving dependencies... 101s Some packages could not be installed. This may mean that you have 101s requested an impossible situation or if you are using the unstable 101s distribution that some required packages have not yet been created 101s or been moved out of Incoming. 101s The following information may help to resolve the situation: 101s 101s The following packages have unmet dependencies: 101s satisfy:command-line : Depends: ruby3.3:i386 101s Depends: libruby3.3:i386 101s Depends: ruby3.3-dev:i386 101s Depends: ruby3.3-doc but it is not going to be installed 101s Depends: libffi-dev but it is not going to be installed 101s Depends: pkg-config (>= 1.8.0-7~) 101s Depends: build-essential:amd64 101s Depends: crossbuild-essential-i386:amd64 101s Depends: libc-dev:i386 101s Depends: libstdc++-dev:i386 101s E: Unable to satisfy dependencies. Reached two conflicting decisions: 101s 1. libruby3.3:i386=3.3.8-2ubuntu1 is selected for install because: 101s 1. satisfy:command-line:amd64=1 is selected for install 101s 2. satisfy:command-line:amd64 Depends libruby3.3:i386 101s 2. libruby3.3:i386 Depends ruby-ruby2-keywords:i386 (>= 0.0.5-1~) 101s but none of the choices are installable: 101s [no choices] 101s pkg-config FAIL badpkg 101s blame: ruby3.3 101s 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. 101s autopkgtest [19:51:55]: @@@@@@@@@@@@@@@@@@@@ summary 101s run-all FAIL badpkg 101s blame: ruby3.3 101s 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. 101s bundled-gems FAIL badpkg 101s blame: ruby3.3 101s 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. 101s builtin-extensions FAIL badpkg 101s blame: ruby3.3 101s 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. 101s rubyconfig FAIL badpkg 101s blame: ruby3.3 101s 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. 101s pkg-config FAIL badpkg 101s blame: ruby3.3 101s 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.