0s autopkgtest [16:36:29]: starting date and time: 2025-11-17 16:36:29+0000 0s autopkgtest [16:36:29]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [16:36:29]: host juju-7f2275-prod-proposed-migration-environment-15; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.zd98fapn/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:node-body-parser --apt-upgrade node-telegram-bot-api --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 '--env=ADT_TEST_TRIGGERS=node-body-parser/2.2.0+~1.19.6-3' -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest-s390x --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-15@bos03-s390x-5.secgroup --name adt-resolute-s390x-node-telegram-bot-api-20251117-163629-juju-7f2275-prod-proposed-migration-environment-15-18edd002-609c-4bcd-9cd6-4bad165b7dd2 --image adt/ubuntu-resolute-s390x-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-15 --net-id=net_prod-proposed-migration-s390x -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 4s Creating nova instance adt-resolute-s390x-node-telegram-bot-api-20251117-163629-juju-7f2275-prod-proposed-migration-environment-15-18edd002-609c-4bcd-9cd6-4bad165b7dd2 from image adt/ubuntu-resolute-s390x-server-20251117.img (UUID a3a3e3b9-e6ba-478c-a5e9-fce6f0982a95)... 49s autopkgtest [16:37:18]: testbed dpkg architecture: s390x 49s autopkgtest [16:37:18]: testbed apt version: 3.1.11 50s autopkgtest [16:37:19]: @@@@@@@@@@@@@@@@@@@@ test bed setup 50s autopkgtest [16:37:19]: testbed release detected to be: None 50s autopkgtest [16:37:19]: updating testbed package index (apt update) 51s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [87.8 kB] 51s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 51s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 51s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 51s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [22.9 kB] 51s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [839 kB] 52s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [81.5 kB] 52s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [9848 B] 52s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main s390x Packages [138 kB] 52s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/restricted s390x Packages [940 B] 52s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/universe s390x Packages [531 kB] 52s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse s390x Packages [10.6 kB] 52s Fetched 1722 kB in 2s (974 kB/s) 53s Reading package lists... 54s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 54s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 54s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 54s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 54s Reading package lists... 54s Reading package lists... 55s Building dependency tree... 55s Reading state information... 55s Calculating upgrade... 55s The following packages will be upgraded: 55s usbutils 55s 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 55s Need to get 85.6 kB of archives. 55s After this operation, 4096 B disk space will be freed. 55s Get:1 http://ftpmaster.internal/ubuntu resolute/main s390x usbutils s390x 1:019-1 [85.6 kB] 55s dpkg-preconfigure: unable to re-open stdin: No such file or directory 55s Fetched 85.6 kB in 0s (319 kB/s) 55s (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 ... 61309 files and directories currently installed.) 55s Preparing to unpack .../usbutils_1%3a019-1_s390x.deb ... 55s Unpacking usbutils (1:019-1) over (1:018-2) ... 55s Setting up usbutils (1:019-1) ... 55s Processing triggers for man-db (2.13.1-1) ... 56s autopkgtest [16:37:25]: upgrading testbed (apt dist-upgrade and autopurge) 56s Reading package lists... 56s Building dependency tree... 56s Reading state information... 56s Calculating upgrade... 57s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 57s Reading package lists... 57s Building dependency tree... 57s Reading state information... 57s Solving dependencies... 57s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 59s autopkgtest [16:37:28]: testbed running kernel: Linux 6.17.0-5-generic #5-Ubuntu SMP Mon Sep 22 08:56:47 UTC 2025 59s autopkgtest [16:37:28]: @@@@@@@@@@@@@@@@@@@@ apt-source node-telegram-bot-api 62s Get:1 http://ftpmaster.internal/ubuntu resolute/universe node-telegram-bot-api 2.0.1-3 (dsc) [2308 B] 62s Get:2 http://ftpmaster.internal/ubuntu resolute/universe node-telegram-bot-api 2.0.1-3 (tar) [2810 kB] 62s Get:3 http://ftpmaster.internal/ubuntu resolute/universe node-telegram-bot-api 2.0.1-3 (diff) [3968 B] 62s gpgv: Signature made Fri Nov 4 13:56:49 2022 UTC 62s gpgv: using RSA key 00DFE58B8B555779D1005EC9F6D74CA7C999EEE9 62s gpgv: Can't check signature: No public key 62s dpkg-source: warning: cannot verify inline signature for ./node-telegram-bot-api_2.0.1-3.dsc: no acceptable signature found 62s autopkgtest [16:37:31]: testing package node-telegram-bot-api version 2.0.1-3 63s autopkgtest [16:37:32]: build not needed 63s autopkgtest [16:37:32]: test command1: preparing testbed 64s Reading package lists... 64s Building dependency tree... 64s Reading state information... 64s Solving dependencies... 64s Some packages could not be installed. This may mean that you have 64s requested an impossible situation or if you are using the unstable 64s distribution that some required packages have not yet been created 64s or been moved out of Incoming. 64s The following information may help to resolve the situation: 64s 64s The following packages have unmet dependencies: 64s satisfy:command-line : Depends: node-telegram-bot-api but it is not going to be installed 64s Depends: nodejs but it is not going to be installed 64s E: Unable to satisfy dependencies. Reached two conflicting decisions: 64s 1. node-body-parser:s390x is selected for install because: 64s 1. satisfy:command-line:s390x=1 is selected for install 64s 2. satisfy:command-line:s390x Depends node-telegram-bot-api 64s 3. node-telegram-bot-api:s390x Depends node-body-parser 64s 2. node-body-parser:s390x is available in versions 2.2.0+~1.19.6-3, 1.20.3+~1.19.5-3 64s but none of the choices are installable: 64s - node-body-parser:s390x=2.2.0+~1.19.6-3 is not selected for install because: 64s 1. satisfy:command-line:s390x=1 is selected for install as above 64s 1-2. node-telegram-bot-api:s390x is selected for install as above 64s 3. node-telegram-bot-api:s390x Depends node-express 64s 4. node-express:s390x is available in version 4.21.2+~cs8.36.27-3 64s 5. node-body-parser:s390x=2.2.0+~1.19.6-3 Breaks node-express (< 5) 64s - node-body-parser:s390x=1.20.3+~1.19.5-3 is not selected for install 64s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 64s Reading package lists... 64s Building dependency tree... 64s Reading state information... 65s Solving dependencies... 65s Some packages could not be installed. This may mean that you have 65s requested an impossible situation or if you are using the unstable 65s distribution that some required packages have not yet been created 65s or been moved out of Incoming. 65s The following information may help to resolve the situation: 65s 65s The following packages have unmet dependencies: 65s satisfy:command-line : Depends: node-telegram-bot-api but it is not going to be installed 65s Depends: nodejs but it is not going to be installed 65s E: Unable to satisfy dependencies. Reached two conflicting decisions: 65s 1. node-body-parser:s390x is selected for install because: 65s 1. satisfy:command-line:s390x=1 is selected for install 65s 2. satisfy:command-line:s390x Depends node-telegram-bot-api 65s 3. node-telegram-bot-api:s390x Depends node-body-parser 65s 2. node-body-parser:s390x is available in versions 2.2.0+~1.19.6-3, 1.20.3+~1.19.5-3 65s but none of the choices are installable: 65s - node-body-parser:s390x=2.2.0+~1.19.6-3 is not selected for install because: 65s 1. satisfy:command-line:s390x=1 is selected for install as above 65s 1-2. node-telegram-bot-api:s390x is selected for install as above 65s 3. node-telegram-bot-api:s390x Depends node-express 65s 4. node-express:s390x is available in version 4.21.2+~cs8.36.27-3 65s 5. node-body-parser:s390x=2.2.0+~1.19.6-3 Breaks node-express (< 5) 65s - node-body-parser:s390x=1.20.3+~1.19.5-3 is not selected for install 65s autopkgtest [16:37:34]: test pkg-js-autopkgtest-require: preparing testbed 65s command1 FAIL badpkg 65s blame: node-telegram-bot-api 65s 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. 65s Reading package lists... 65s Building dependency tree... 65s Reading state information... 65s Solving dependencies... 65s Some packages could not be installed. This may mean that you have 65s requested an impossible situation or if you are using the unstable 65s distribution that some required packages have not yet been created 65s or been moved out of Incoming. 65s The following information may help to resolve the situation: 65s 65s The following packages have unmet dependencies: 65s satisfy:command-line : Depends: node-telegram-bot-api but it is not going to be installed 65s Depends: nodejs but it is not going to be installed 65s Depends: pkg-js-autopkgtest but it is not going to be installed 65s E: Unable to satisfy dependencies. Reached two conflicting decisions: 65s 1. node-body-parser:s390x is selected for install because: 65s 1. satisfy:command-line:s390x=1 is selected for install 65s 2. satisfy:command-line:s390x Depends node-telegram-bot-api 65s 3. node-telegram-bot-api:s390x Depends node-body-parser 65s 2. node-body-parser:s390x is available in versions 2.2.0+~1.19.6-3, 1.20.3+~1.19.5-3 65s but none of the choices are installable: 65s - node-body-parser:s390x=2.2.0+~1.19.6-3 is not selected for install because: 65s 1. satisfy:command-line:s390x=1 is selected for install as above 65s 1-2. node-telegram-bot-api:s390x is selected for install as above 65s 3. node-telegram-bot-api:s390x Depends node-express 65s 4. node-express:s390x is available in version 4.21.2+~cs8.36.27-3 65s 5. node-body-parser:s390x=2.2.0+~1.19.6-3 Breaks node-express (< 5) 65s - node-body-parser:s390x=1.20.3+~1.19.5-3 is not selected for install 65s autopkgtest [16:37:34]: test pkg-js-autopkgtest: preparing testbed 65s pkg-js-autopkgtest-require FAIL badpkg 65s blame: node-telegram-bot-api 65s 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. 86s Creating nova instance adt-resolute-s390x-node-telegram-bot-api-20251117-163629-juju-7f2275-prod-proposed-migration-environment-15-18edd002-609c-4bcd-9cd6-4bad165b7dd2 from image adt/ubuntu-resolute-s390x-server-20251117.img (UUID a3a3e3b9-e6ba-478c-a5e9-fce6f0982a95)... 121s autopkgtest [16:38:30]: testbed dpkg architecture: s390x 121s autopkgtest [16:38:30]: testbed apt version: 3.1.11 121s autopkgtest [16:38:30]: @@@@@@@@@@@@@@@@@@@@ test bed setup 122s autopkgtest [16:38:31]: testbed release detected to be: resolute 122s autopkgtest [16:38:31]: updating testbed package index (apt update) 123s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [87.8 kB] 123s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 123s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 123s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 123s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [22.9 kB] 123s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [81.5 kB] 123s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [839 kB] 123s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [9848 B] 123s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main s390x Packages [138 kB] 123s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/restricted s390x Packages [940 B] 123s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/universe s390x Packages [531 kB] 124s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse s390x Packages [10.6 kB] 124s Fetched 1722 kB in 1s (1545 kB/s) 124s Reading package lists... 125s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 125s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 125s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 125s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 126s Reading package lists... 126s Reading package lists... 126s Building dependency tree... 126s Reading state information... 126s Calculating upgrade... 126s The following packages will be upgraded: 126s usbutils 126s 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 126s Need to get 85.6 kB of archives. 126s After this operation, 4096 B disk space will be freed. 126s Get:1 http://ftpmaster.internal/ubuntu resolute/main s390x usbutils s390x 1:019-1 [85.6 kB] 127s dpkg-preconfigure: unable to re-open stdin: No such file or directory 127s Fetched 85.6 kB in 0s (240 kB/s) 127s (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 ... 61309 files and directories currently installed.) 127s Preparing to unpack .../usbutils_1%3a019-1_s390x.deb ... 127s Unpacking usbutils (1:019-1) over (1:018-2) ... 127s Setting up usbutils (1:019-1) ... 127s Processing triggers for man-db (2.13.1-1) ... 128s autopkgtest [16:38:37]: upgrading testbed (apt dist-upgrade and autopurge) 128s Reading package lists... 128s Building dependency tree... 128s Reading state information... 129s Calculating upgrade... 129s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 129s Reading package lists... 129s Building dependency tree... 129s Reading state information... 129s Solving dependencies... 129s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 132s Reading package lists... 132s Building dependency tree... 132s Reading state information... 132s Solving dependencies... 132s Some packages could not be installed. This may mean that you have 132s requested an impossible situation or if you are using the unstable 132s distribution that some required packages have not yet been created 132s or been moved out of Incoming. 132s The following information may help to resolve the situation: 132s 132s The following packages have unmet dependencies: 132s satisfy:command-line : Depends: node-telegram-bot-api but it is not going to be installed 132s Depends: debhelper-compat (= 13) 132s Depends: dh-sequence-nodejs 132s Depends: node-axios but it is not going to be installed 132s Depends: node-bluebird but it is not going to be installed 132s Depends: node-body-parser but it is not going to be installed 132s Depends: node-express but it is not going to be installed 132s Depends: node-extend but it is not going to be installed 132s Depends: build-essential but it is not going to be installed 132s Depends: pkg-js-autopkgtest but it is not going to be installed 132s E: Unable to satisfy dependencies. Reached two conflicting decisions: 132s 1. node-body-parser:s390x is selected for install because: 132s 1. satisfy:command-line:s390x=1 is selected for install 132s 2. satisfy:command-line:s390x Depends node-body-parser 132s 2. node-body-parser:s390x is available in versions 2.2.0+~1.19.6-3, 1.20.3+~1.19.5-3 132s but none of the choices are installable: 132s - node-body-parser:s390x=2.2.0+~1.19.6-3 is not selected for install because: 132s 1. satisfy:command-line:s390x=1 is selected for install as above 132s 2. satisfy:command-line:s390x Depends node-express 132s 3. node-express:s390x is available in version 4.21.2+~cs8.36.27-3 132s 4. node-body-parser:s390x=2.2.0+~1.19.6-3 Breaks node-express (< 5) 132s - node-body-parser:s390x=1.20.3+~1.19.5-3 is not selected for install 132s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 133s Reading package lists... 133s Building dependency tree... 133s Reading state information... 133s Solving dependencies... 133s Some packages could not be installed. This may mean that you have 133s requested an impossible situation or if you are using the unstable 133s distribution that some required packages have not yet been created 133s or been moved out of Incoming. 133s The following information may help to resolve the situation: 133s 133s The following packages have unmet dependencies: 133s satisfy:command-line : Depends: node-telegram-bot-api but it is not going to be installed 133s Depends: debhelper-compat (= 13) 133s Depends: dh-sequence-nodejs 133s Depends: node-axios but it is not going to be installed 133s Depends: node-bluebird but it is not going to be installed 133s Depends: node-body-parser but it is not going to be installed 133s Depends: node-express but it is not going to be installed 133s Depends: node-extend but it is not going to be installed 133s Depends: build-essential but it is not going to be installed 133s Depends: pkg-js-autopkgtest but it is not going to be installed 133s E: Unable to satisfy dependencies. Reached two conflicting decisions: 133s 1. node-body-parser:s390x is selected for install because: 133s 1. satisfy:command-line:s390x=1 is selected for install 133s 2. satisfy:command-line:s390x Depends node-body-parser 133s 2. node-body-parser:s390x is available in versions 2.2.0+~1.19.6-3, 1.20.3+~1.19.5-3 133s but none of the choices are installable: 133s - node-body-parser:s390x=2.2.0+~1.19.6-3 is not selected for install because: 133s 1. satisfy:command-line:s390x=1 is selected for install as above 133s 2. satisfy:command-line:s390x Depends node-express 133s 3. node-express:s390x is available in version 4.21.2+~cs8.36.27-3 133s 4. node-body-parser:s390x=2.2.0+~1.19.6-3 Breaks node-express (< 5) 133s - node-body-parser:s390x=1.20.3+~1.19.5-3 is not selected for install 133s pkg-js-autopkgtest FAIL badpkg 133s blame: node-telegram-bot-api 133s 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. 133s autopkgtest [16:38:42]: @@@@@@@@@@@@@@@@@@@@ summary 133s command1 FAIL badpkg 133s blame: node-telegram-bot-api 133s 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. 133s pkg-js-autopkgtest-require FAIL badpkg 133s blame: node-telegram-bot-api 133s 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. 133s pkg-js-autopkgtest FAIL badpkg 133s blame: node-telegram-bot-api 133s 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.