build(deps): bump google.golang.org/grpc from 1.70.0 to 1.79.3 in /troubleshoot #82
Triggered via pull request
March 19, 2026 01:42
Status
Cancelled
Total duration
2d 0h 0m 45s
Artifacts
–
go-tests.yml
on: pull_request
get-go-version
/
Determine Go toolchain version
6s
conditional-skip
/
Check whether to skip build and tests
24s
noop
4s
Matrix: lint-32bit / lint
Matrix: lint / lint
check-go-mod
/
check-go-mod
0s
check-generated-protobuf
1d 0h
check-codegen
0s
lint-enums
0s
lint-container-test-deps
0s
lint-consul-retry
0s
go-test-32bit
/
go-test
go-test-api
/
go-test
go-test-api-backwards-compatibility
/
go-test
go-test-envoyextensions
/
go-test
go-test-race
/
go-test
go-test-sdk
/
go-test
go-test-sdk-backwards-compatibility
/
go-test
go-test-testing-deployer
/
go-test
go-test-troubleshoot
/
go-test
Matrix: go-test-ce / go-test
Waiting for pending jobs
Matrix: go-test-enterprise / go-test
Waiting for pending jobs
go-tests-success
0s
Annotations
24 errors and 3 warnings
|
lint-enums
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
check-generated-protobuf
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
lint-32bit / lint envoyextensions
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
lint-32bit / lint test/integration/consul-container
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
lint / lint test/integration/consul-container
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
dev-build / build
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
lint-32bit / lint troubleshoot
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
lint-32bit / lint sdk
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
lint-32bit / lint test-integ
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
lint / lint troubleshoot
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
lint / lint sdk
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
lint / lint
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
lint / lint envoyextensions
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
check-go-mod / check-go-mod
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
check-codegen
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
lint-consul-retry
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
lint-32bit / lint
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
lint / lint testing/deployer
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
lint-32bit / lint testing/deployer
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
lint-container-test-deps
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
lint / lint test-integ
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
lint-32bit / lint api
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
lint / lint api
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
go-tests-success
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
get-go-version / Determine Go toolchain version
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@0ad4b8fadaa221de15dcec353f45205ec38ea70b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
conditional-skip / Check whether to skip build and tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@0ad4b8fadaa221de15dcec353f45205ec38ea70b, tj-actions/changed-files@2f7c5bfce28377bc069a65ba478de0a74aa0ca32. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Setup
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@0ad4b8fadaa221de15dcec353f45205ec38ea70b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|