0s autopkgtest [16:24:59]: starting date and time: 2025-11-17 16:24:59+0000 0s autopkgtest [16:24:59]: git checkout: 508d4a25 a-v-ssh wait_for_ssh: demote "ssh connection failed" to a debug message 0s autopkgtest [16:24:59]: host juju-7f2275-prod-proposed-migration-environment-9; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.raq4f7bf/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,localhost,localdomain,internal,login.ubuntu.com,archive.ubuntu.com,ports.ubuntu.com,security.ubuntu.com,ddebs.ubuntu.com,changelogs.ubuntu.com,keyserver.ubuntu.com,launchpadlibrarian.net,launchpadcontent.net,launchpad.net,keystone.ps5.canonical.com,objectstorage.prodstack5.canonical.com,radosgw.ps5.canonical.com\n" >> /etc/environment' --apt-pocket=proposed=src:nodejs,src:node-body-parser --apt-upgrade node-telegram-bot-api --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 '--env=ADT_TEST_TRIGGERS=nodejs/20.19.5+dfsg+~cs20.19.24-1 node-body-parser/2.2.0+~1.19.6-3' -- lxd -r lxd-armhf-10.145.243.207 lxd-armhf-10.145.243.207:autopkgtest/ubuntu/resolute/armhf 25s autopkgtest [16:25:24]: testbed dpkg architecture: armhf 27s autopkgtest [16:25:26]: testbed apt version: 3.1.11 31s autopkgtest [16:25:30]: @@@@@@@@@@@@@@@@@@@@ test bed setup 33s autopkgtest [16:25:32]: testbed release detected to be: None 41s autopkgtest [16:25:40]: updating testbed package index (apt update) 44s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [87.8 kB] 44s Get:2 http://ftpmaster.internal/ubuntu resolute InRelease [87.8 kB] 44s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 44s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 44s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [839 kB] 45s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [81.5 kB] 45s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [22.9 kB] 45s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [9848 B] 45s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main armhf Packages [138 kB] 45s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/restricted armhf Packages [940 B] 45s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/universe armhf Packages [515 kB] 45s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse armhf Packages [9684 B] 45s Get:13 http://ftpmaster.internal/ubuntu resolute/universe Sources [21.3 MB] 48s Get:14 http://ftpmaster.internal/ubuntu resolute/main Sources [1416 kB] 49s Get:15 http://ftpmaster.internal/ubuntu resolute/main armhf Packages [1369 kB] 49s Get:16 http://ftpmaster.internal/ubuntu resolute/universe armhf Packages [15.2 MB] 52s Fetched 41.1 MB in 8s (5118 kB/s) 53s Reading package lists... 59s autopkgtest [16:25:58]: upgrading testbed (apt dist-upgrade and autopurge) 61s Reading package lists... 61s Building dependency tree... 61s Reading state information... 62s Calculating upgrade... 62s The following packages will be upgraded: 62s usbutils 62s 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 62s Need to get 77.7 kB of archives. 62s After this operation, 0 B of additional disk space will be used. 62s Get:1 http://ftpmaster.internal/ubuntu resolute/main armhf usbutils armhf 1:019-1 [77.7 kB] 63s Fetched 77.7 kB in 0s (272 kB/s) 63s (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 ... 65904 files and directories currently installed.) 63s Preparing to unpack .../usbutils_1%3a019-1_armhf.deb ... 63s Unpacking usbutils (1:019-1) over (1:018-2) ... 63s Setting up usbutils (1:019-1) ... 63s Processing triggers for man-db (2.13.1-1) ... 67s Reading package lists... 67s Building dependency tree... 67s Reading state information... 67s Solving dependencies... 68s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 70s autopkgtest [16:26:09]: rebooting testbed after setup commands that affected boot 112s autopkgtest [16:26:51]: testbed running kernel: Linux 6.8.0-86-generic #87~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 29 09:26:46 UTC 2 139s autopkgtest [16:27:18]: @@@@@@@@@@@@@@@@@@@@ apt-source node-telegram-bot-api 151s Get:1 http://ftpmaster.internal/ubuntu resolute/universe node-telegram-bot-api 2.0.1-3 (dsc) [2308 B] 151s Get:2 http://ftpmaster.internal/ubuntu resolute/universe node-telegram-bot-api 2.0.1-3 (tar) [2810 kB] 151s Get:3 http://ftpmaster.internal/ubuntu resolute/universe node-telegram-bot-api 2.0.1-3 (diff) [3968 B] 151s gpgv: Signature made Fri Nov 4 13:56:49 2022 UTC 151s gpgv: using RSA key 00DFE58B8B555779D1005EC9F6D74CA7C999EEE9 151s gpgv: Can't check signature: No public key 151s dpkg-source: warning: cannot verify inline signature for ./node-telegram-bot-api_2.0.1-3.dsc: no acceptable signature found 151s autopkgtest [16:27:30]: testing package node-telegram-bot-api version 2.0.1-3 153s autopkgtest [16:27:32]: build not needed 157s autopkgtest [16:27:36]: test command1: preparing testbed 159s Reading package lists... 159s Building dependency tree... 159s Reading state information... 159s Solving dependencies... 159s Some packages could not be installed. This may mean that you have 159s requested an impossible situation or if you are using the unstable 159s distribution that some required packages have not yet been created 159s or been moved out of Incoming. 159s The following information may help to resolve the situation: 159s 159s The following packages have unmet dependencies: 160s satisfy:command-line : Depends: node-telegram-bot-api but it is not going to be installed 160s Depends: nodejs but it is not going to be installed 160s E: Unable to satisfy dependencies. Reached two conflicting decisions: 160s 1. node-body-parser:armhf is selected for install because: 160s 1. satisfy:command-line:armhf=1 is selected for install 160s 2. satisfy:command-line:armhf Depends node-telegram-bot-api 160s 3. node-telegram-bot-api:armhf Depends node-body-parser 160s 2. node-body-parser:armhf is available in versions 2.2.0+~1.19.6-3, 1.20.3+~1.19.5-3 160s but none of the choices are installable: 160s - node-body-parser:armhf=2.2.0+~1.19.6-3 is not selected for install because: 160s 1. satisfy:command-line:armhf=1 is selected for install as above 160s 1-2. node-telegram-bot-api:armhf is selected for install as above 160s 3. node-telegram-bot-api:armhf Depends node-express 160s 4. node-express:armhf is available in version 4.21.2+~cs8.36.27-3 160s 5. node-body-parser:armhf=2.2.0+~1.19.6-3 Breaks node-express (< 5) 160s - node-body-parser:armhf=1.20.3+~1.19.5-3 is not selected for install 160s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 163s Reading package lists... 164s Building dependency tree... 164s Reading state information... 164s Solving dependencies... 164s Some packages could not be installed. This may mean that you have 164s requested an impossible situation or if you are using the unstable 164s distribution that some required packages have not yet been created 164s or been moved out of Incoming. 164s The following information may help to resolve the situation: 164s 164s The following packages have unmet dependencies: 165s satisfy:command-line : Depends: node-telegram-bot-api but it is not going to be installed 165s Depends: nodejs but it is not going to be installed 165s autopkgtest [16:27:44]: test pkg-js-autopkgtest-require: preparing testbed 165s E: Unable to satisfy dependencies. Reached two conflicting decisions: 165s 1. node-body-parser:armhf is selected for install because: 165s 1. satisfy:command-line:armhf=1 is selected for install 165s 2. satisfy:command-line:armhf Depends node-telegram-bot-api 165s 3. node-telegram-bot-api:armhf Depends node-body-parser 165s 2. node-body-parser:armhf is available in versions 2.2.0+~1.19.6-3, 1.20.3+~1.19.5-3 165s but none of the choices are installable: 165s - node-body-parser:armhf=2.2.0+~1.19.6-3 is not selected for install because: 165s 1. satisfy:command-line:armhf=1 is selected for install as above 165s 1-2. node-telegram-bot-api:armhf is selected for install as above 165s 3. node-telegram-bot-api:armhf Depends node-express 165s 4. node-express:armhf is available in version 4.21.2+~cs8.36.27-3 165s 5. node-body-parser:armhf=2.2.0+~1.19.6-3 Breaks node-express (< 5) 165s - node-body-parser:armhf=1.20.3+~1.19.5-3 is not selected for install 165s command1 FAIL badpkg 165s blame: node-telegram-bot-api 165s 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. 167s Reading package lists... 167s Building dependency tree... 167s Reading state information... 167s Solving dependencies... 167s Some packages could not be installed. This may mean that you have 167s requested an impossible situation or if you are using the unstable 167s distribution that some required packages have not yet been created 167s or been moved out of Incoming. 167s The following information may help to resolve the situation: 167s 167s The following packages have unmet dependencies: 168s satisfy:command-line : Depends: node-telegram-bot-api but it is not going to be installed 168s Depends: nodejs but it is not going to be installed 168s Depends: pkg-js-autopkgtest but it is not going to be installed 168s E: Unable to satisfy dependencies. Reached two conflicting decisions: 168s 1. node-body-parser:armhf is selected for install because: 168s 1. satisfy:command-line:armhf=1 is selected for install 168s 2. satisfy:command-line:armhf Depends node-telegram-bot-api 168s 3. node-telegram-bot-api:armhf Depends node-body-parser 168s 2. node-body-parser:armhf is available in versions 2.2.0+~1.19.6-3, 1.20.3+~1.19.5-3 168s but none of the choices are installable: 168s - node-body-parser:armhf=2.2.0+~1.19.6-3 is not selected for install because: 168s 1. satisfy:command-line:armhf=1 is selected for install as above 168s 1-2. node-telegram-bot-api:armhf is selected for install as above 168s 3. node-telegram-bot-api:armhf Depends node-express 168s 4. node-express:armhf is available in version 4.21.2+~cs8.36.27-3 168s 5. node-body-parser:armhf=2.2.0+~1.19.6-3 Breaks node-express (< 5) 168s - node-body-parser:armhf=1.20.3+~1.19.5-3 is not selected for install 168s autopkgtest [16:27:47]: test pkg-js-autopkgtest: preparing testbed 168s pkg-js-autopkgtest-require FAIL badpkg 168s blame: node-telegram-bot-api 168s 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. 192s autopkgtest [16:28:11]: testbed dpkg architecture: armhf 194s autopkgtest [16:28:13]: testbed apt version: 3.1.11 199s autopkgtest [16:28:18]: @@@@@@@@@@@@@@@@@@@@ test bed setup 201s autopkgtest [16:28:20]: testbed release detected to be: resolute 210s autopkgtest [16:28:29]: updating testbed package index (apt update) 212s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [87.8 kB] 212s Get:2 http://ftpmaster.internal/ubuntu resolute InRelease [87.8 kB] 212s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 213s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 213s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [22.9 kB] 213s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [9848 B] 213s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [839 kB] 213s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [81.5 kB] 213s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main armhf Packages [138 kB] 213s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/restricted armhf Packages [940 B] 213s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/universe armhf Packages [515 kB] 213s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse armhf Packages [9684 B] 213s Get:13 http://ftpmaster.internal/ubuntu resolute/main Sources [1416 kB] 214s Get:14 http://ftpmaster.internal/ubuntu resolute/universe Sources [21.3 MB] 216s Get:15 http://ftpmaster.internal/ubuntu resolute/main armhf Packages [1369 kB] 216s Get:16 http://ftpmaster.internal/ubuntu resolute/universe armhf Packages [15.2 MB] 220s Fetched 41.1 MB in 8s (5394 kB/s) 221s Reading package lists... 227s autopkgtest [16:28:46]: upgrading testbed (apt dist-upgrade and autopurge) 228s Reading package lists... 229s Building dependency tree... 229s Reading state information... 230s Calculating upgrade... 230s The following packages will be upgraded: 230s usbutils 232s 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 232s Need to get 77.7 kB of archives. 232s After this operation, 0 B of additional disk space will be used. 232s Get:1 http://ftpmaster.internal/ubuntu resolute/main armhf usbutils armhf 1:019-1 [77.7 kB] 233s Fetched 77.7 kB in 2s (45.2 kB/s) 233s (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 ... 65904 files and directories currently installed.) 233s Preparing to unpack .../usbutils_1%3a019-1_armhf.deb ... 233s Unpacking usbutils (1:019-1) over (1:018-2) ... 233s Setting up usbutils (1:019-1) ... 233s Processing triggers for man-db (2.13.1-1) ... 237s Reading package lists... 237s Building dependency tree... 237s Reading state information... 237s Solving dependencies... 238s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 239s autopkgtest [16:28:58]: rebooting testbed after setup commands that affected boot 305s Reading package lists... 305s Building dependency tree... 305s Reading state information... 306s Solving dependencies... 306s Some packages could not be installed. This may mean that you have 306s requested an impossible situation or if you are using the unstable 306s distribution that some required packages have not yet been created 306s or been moved out of Incoming. 306s The following information may help to resolve the situation: 306s 306s The following packages have unmet dependencies: 306s satisfy:command-line : Depends: node-telegram-bot-api but it is not going to be installed 306s Depends: debhelper-compat (= 13) 306s Depends: dh-sequence-nodejs 306s Depends: node-axios but it is not going to be installed 306s Depends: node-bluebird but it is not going to be installed 306s Depends: node-body-parser but it is not going to be installed 306s Depends: node-express but it is not going to be installed 306s Depends: node-extend but it is not going to be installed 306s Depends: build-essential but it is not going to be installed 306s Depends: pkg-js-autopkgtest but it is not going to be installed 306s E: Unable to satisfy dependencies. Reached two conflicting decisions: 306s 1. node-body-parser:armhf is selected for install because: 306s 1. satisfy:command-line:armhf=1 is selected for install 306s 2. satisfy:command-line:armhf Depends node-body-parser 306s 2. node-body-parser:armhf is available in versions 2.2.0+~1.19.6-3, 1.20.3+~1.19.5-3 306s but none of the choices are installable: 306s - node-body-parser:armhf=2.2.0+~1.19.6-3 is not selected for install because: 306s 1. satisfy:command-line:armhf=1 is selected for install as above 306s 2. satisfy:command-line:armhf Depends node-express 306s 3. node-express:armhf is available in version 4.21.2+~cs8.36.27-3 306s 4. node-body-parser:armhf=2.2.0+~1.19.6-3 Breaks node-express (< 5) 306s - node-body-parser:armhf=1.20.3+~1.19.5-3 is not selected for install 306s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 310s Reading package lists... 310s Building dependency tree... 310s Reading state information... 310s Solving dependencies... 310s Some packages could not be installed. This may mean that you have 310s requested an impossible situation or if you are using the unstable 310s distribution that some required packages have not yet been created 310s or been moved out of Incoming. 310s The following information may help to resolve the situation: 310s 310s The following packages have unmet dependencies: 311s satisfy:command-line : Depends: node-telegram-bot-api but it is not going to be installed 311s Depends: debhelper-compat (= 13) 311s Depends: dh-sequence-nodejs 311s Depends: node-axios but it is not going to be installed 311s Depends: node-bluebird but it is not going to be installed 311s Depends: node-body-parser but it is not going to be installed 311s Depends: node-express but it is not going to be installed 311s Depends: node-extend but it is not going to be installed 311s Depends: build-essential but it is not going to be installed 311s Depends: pkg-js-autopkgtest but it is not going to be installed 311s E: Unable to satisfy dependencies. Reached two conflicting decisions: 311s 1. node-body-parser:armhf is selected for install because: 311s 1. satisfy:command-line:armhf=1 is selected for install 311s 2. satisfy:command-line:armhf Depends node-body-parser 311s 2. node-body-parser:armhf is available in versions 2.2.0+~1.19.6-3, 1.20.3+~1.19.5-3 311s but none of the choices are installable: 311s - node-body-parser:armhf=2.2.0+~1.19.6-3 is not selected for install because: 311s 1. satisfy:command-line:armhf=1 is selected for install as above 311s 2. satisfy:command-line:armhf Depends node-express 311s 3. node-express:armhf is available in version 4.21.2+~cs8.36.27-3 311s 4. node-body-parser:armhf=2.2.0+~1.19.6-3 Breaks node-express (< 5) 311s - node-body-parser:armhf=1.20.3+~1.19.5-3 is not selected for install 311s pkg-js-autopkgtest FAIL badpkg 311s blame: node-telegram-bot-api 311s 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. 311s autopkgtest [16:30:10]: @@@@@@@@@@@@@@@@@@@@ summary 311s command1 FAIL badpkg 311s blame: node-telegram-bot-api 311s 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. 311s pkg-js-autopkgtest-require FAIL badpkg 311s blame: node-telegram-bot-api 311s 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. 311s pkg-js-autopkgtest FAIL badpkg 311s blame: node-telegram-bot-api 311s 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.