NGTS: Various further updates and fixes #959
SgtCoDFishtests.yaml
on: pull_request
verify
2m 35s
test
36s
ark-test-e2e
1m 55s
ngts-test-e2e
0s
test-e2e
0s
Annotations
15 errors and 3 warnings
|
test
Process completed with exit code 2.
|
|
test:
pkg/client/client_ngts_test.go#L359
not enough arguments in call to NewNGTSClient
|
|
test:
pkg/client/client_ngts_test.go#L293
not enough arguments in call to NewNGTSClient
|
|
test:
pkg/client/client_ngts_test.go#L231
not enough arguments in call to NewNGTSClient
|
|
test:
pkg/client/client_ngts_test.go#L176
not enough arguments in call to NewNGTSClient
|
|
test:
pkg/client/client_ngts_test.go#L105
not enough arguments in call to NewNGTSClient
|
|
test:
pkg/agent/config.go#L973
not enough arguments in call to client.NewNGTSClient
|
|
ark-test-e2e
Process completed with exit code 2.
|
|
ark-test-e2e:
pkg/agent/config.go#L973
not enough arguments in call to client.NewNGTSClient
|
|
verify
Process completed with exit code 2.
|
|
verify:
pkg/client/client_ngts_test.go#L359
not enough arguments in call to NewNGTSClient
|
|
verify:
pkg/client/client_ngts_test.go#L293
not enough arguments in call to NewNGTSClient
|
|
verify:
pkg/client/client_ngts_test.go#L231
not enough arguments in call to NewNGTSClient
|
|
verify:
pkg/client/client_ngts_test.go#L176
not enough arguments in call to NewNGTSClient
|
|
verify:
pkg/client/client_ngts_test.go#L105
not enough arguments in call to NewNGTSClient
|
|
test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
ark-test-e2e
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
verify
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|