Skip to content

hostagent: gate Ready on raw-TCP SSH banner probe #11637

hostagent: gate Ready on raw-TCP SSH banner probe

hostagent: gate Ready on raw-TCP SSH banner probe #11637

Triggered via pull request June 4, 2026 06:05
Status Failure
Total duration 38m 43s
Artifacts 4

test.yml

on: pull_request
Lints
2m 8s
Lints
Vulncheck
37s
Vulncheck
Windows tests (WSL2)
11m 26s
Windows tests (WSL2)
Windows tests (QEMU)
16m 7s
Windows tests (QEMU)
Integration tests (QEMU, macOS host)
19m 41s
Integration tests (QEMU, macOS host)
Integration tests (BATS)
18m 3s
Integration tests (BATS)
Colima tests (QEMU, Linux host)
5m 49s
Colima tests (QEMU, Linux host)
VMNet tests (QEMU)
21m 16s
VMNet tests (QEMU)
gomodjail (experimental; failures shall not block merging PRs)
11m 17s
gomodjail (experimental; failures shall not block merging PRs)
Cross-compile (NetBSD, DragonFlyBSD)
1m 41s
Cross-compile (NetBSD, DragonFlyBSD)
Smoke tests (QEMU, old Linux host)
5m 44s
Smoke tests (QEMU, old Linux host)
Matrix: Lint Go
Matrix: Integration tests (QEMU, Linux host)
Matrix: Unit tests
Matrix: Upgrade tests (QEMU, macOS host)
Matrix: Integration tests (vz)
Fit to window
Zoom out
Zoom in

Annotations

2 errors, 7 warnings, and 4 notices
Integration tests (vz) (default.yaml)
Process completed with exit code 1.
Integration tests (QEMU, Linux host) (docker.yaml)
Final attempt failed. Child_process exited with error code 1
Vulncheck
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.1, actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Vulncheck
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>05hUhagAAAAB3kMTFZqMdQYXIna9jLer2UEhMMzBFREdFMDExNwBFZGdl
Vulncheck
Failed to restore: Cache service responded with 400
Lints
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ls-lint/action@02e380fe8733d499cbfc9e22276de5085508a5bd. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
VMNet tests (QEMU)
Attempt 1 failed. Reason: Child_process exited with error code 1
Integration tests (QEMU, Linux host) (docker.yaml)
Attempt 2 failed. Reason: Child_process exited with error code 1
Integration tests (QEMU, Linux host) (docker.yaml)
Attempt 1 failed. Reason: Child_process exited with error code 1
Lint Go (windows-2025)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026
Windows tests (WSL2)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026
Windows tests (QEMU)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026

Artifacts

Produced during runtime
Name Size Digest
failure-logs-qemu-linux-docker_yaml
113 KB
sha256:bfa501170562041c4759796fc316480890d0684ef2cbbeb9b002fe2e4f918147
failure-logs-upgrade
41 KB
sha256:75fcf53a6eddf6f68ac16babfbf73a12129755a91d33ae10868bf21d7c643ad6
failure-logs-vmnet
53 KB
sha256:ae4584aaa57a34532c86e20c237c89a6a76364a3e7673a18fdb50fdcfeaa5df1
failure-logs-vz-default_yaml
208 KB
sha256:bccb9fffadbf188e2dd5287d943685d782ee4439a705d87ec1ed27df5912d0fd