Skip to content

Nightly TFE Tests #1112

Nightly TFE Tests

Nightly TFE Tests #1112

Triggered via schedule March 19, 2026 07:19
Status Failure
Total duration 29m 5s
Artifacts 3

nightly-tfe-test.yml

on: schedule
Matrix: tests
tests-summarize
2s
tests-summarize
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 18 warnings
tests (5, 2)
Process completed with exit code 1.
tests (5, 1)
Process completed with exit code 1.
tests-summarize
Process completed with exit code 1.
slack-notify
Missing input! The webhook type must be 'incoming-webhook' or 'webhook-trigger'.
instance
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hashicorp-forge/terraform-cloud-action/apply@ceddc497db955594f0b0d5f0bee29c41f60d6d33. 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/
tests (5, 4)
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/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, dawidd6/action-download-artifact@09f2f74827fd3a8607589e5ad7f9398816f540fe, hashicorp-forge/go-test-split-action@796beedbdb3d1bea14cad2d3057bab5c5cf15fe5, hashicorp-forge/terraform-cloud-action/outputs@ceddc497db955594f0b0d5f0bee29c41f60d6d33. 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/
tests (5, 4)
Failed to use junit splitting strategy (falling back to naive strategy): Error: ENOENT: no such file or directory, open './ci-summary-provider.xml'
tests (5, 4)
no artifacts found
tests (5, 3)
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/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, dawidd6/action-download-artifact@09f2f74827fd3a8607589e5ad7f9398816f540fe, hashicorp-forge/go-test-split-action@796beedbdb3d1bea14cad2d3057bab5c5cf15fe5, hashicorp-forge/terraform-cloud-action/outputs@ceddc497db955594f0b0d5f0bee29c41f60d6d33. 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/
tests (5, 3)
Failed to use junit splitting strategy (falling back to naive strategy): Error: ENOENT: no such file or directory, open './ci-summary-provider.xml'
tests (5, 3)
no artifacts found
tests (5, 0)
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/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, dawidd6/action-download-artifact@09f2f74827fd3a8607589e5ad7f9398816f540fe, hashicorp-forge/go-test-split-action@796beedbdb3d1bea14cad2d3057bab5c5cf15fe5, hashicorp-forge/terraform-cloud-action/outputs@ceddc497db955594f0b0d5f0bee29c41f60d6d33. 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/
tests (5, 0)
Failed to use junit splitting strategy (falling back to naive strategy): Error: ENOENT: no such file or directory, open './ci-summary-provider.xml'
tests (5, 0)
no artifacts found
tests (5, 2)
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, dawidd6/action-download-artifact@09f2f74827fd3a8607589e5ad7f9398816f540fe, hashicorp-forge/go-test-split-action@796beedbdb3d1bea14cad2d3057bab5c5cf15fe5, hashicorp-forge/terraform-cloud-action/outputs@ceddc497db955594f0b0d5f0bee29c41f60d6d33. 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/
tests (5, 2)
Failed to use junit splitting strategy (falling back to naive strategy): Error: ENOENT: no such file or directory, open './ci-summary-provider.xml'
tests (5, 2)
no artifacts found
tests (5, 1)
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, dawidd6/action-download-artifact@09f2f74827fd3a8607589e5ad7f9398816f540fe, hashicorp-forge/go-test-split-action@796beedbdb3d1bea14cad2d3057bab5c5cf15fe5, hashicorp-forge/terraform-cloud-action/outputs@ceddc497db955594f0b0d5f0bee29c41f60d6d33. 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/
tests (5, 1)
Failed to use junit splitting strategy (falling back to naive strategy): Error: ENOENT: no such file or directory, open './ci-summary-provider.xml'
tests (5, 1)
no artifacts found
slack-notify
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: slackapi/slack-github-action@91efab103c0de0a537f72a35f6b8cda0ee76bf0a. 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/
cleanup
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, hashicorp-forge/terraform-cloud-action/destroy@ceddc497db955594f0b0d5f0bee29c41f60d6d33. 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/

Artifacts

Produced during runtime
Name Size Digest
junit-test-summary-0 Expired
3.12 KB
sha256:31c9ab82cee939e2287921b70fcf96614c64eba13ef072b177bd95671f0ad7b2
junit-test-summary-3 Expired
3.4 KB
sha256:371ea39e32d2737f728cfed9e5d2561d79fff4d87b539364ebb7418f9d1eed65
junit-test-summary-4 Expired
3.15 KB
sha256:e820b0192eb5ce18474de2f355c8394a220501430226396f83e2e394963a1bb9