Skip to content

[2/7] Telemetry Infrastructure: CircuitBreaker and FeatureFlagCache #987

[2/7] Telemetry Infrastructure: CircuitBreaker and FeatureFlagCache

[2/7] Telemetry Infrastructure: CircuitBreaker and FeatureFlagCache #987

Triggered via pull request April 17, 2026 13:12
Status Failure
Total duration 11d 7h 24m 20s
Artifacts

main.yml

on: pull_request
Matrix: unit-test
coverage
0s
coverage
Fit to window
Zoom out
Zoom in

Deployment protection rules

Reviewers, timers, and other rules protecting deployments in this run
Event Environments Comment
vikrantpuppala
deleted by vikrantpuppala Apr 28, 2026
azure-prod

Required reviewers protection rule deleted.

Annotations

16 errors and 8 warnings
unit-test (20)
Process completed with exit code 1.
unit-test (20): tests/unit/telemetry/DatabricksTelemetryExporter.test.ts#L330
Argument of type 'unknown' is not assignable to parameter of type 'string'.
unit-test (20): tests/unit/telemetry/DatabricksTelemetryExporter.test.ts#L311
Argument of type 'unknown' is not assignable to parameter of type 'string'.
unit-test (16)
The strategy configuration was canceled because "unit-test._20" failed
unit-test (16)
The operation was canceled.
unit-test (16): tests/unit/telemetry/DatabricksTelemetryExporter.test.ts#L330
Argument of type 'unknown' is not assignable to parameter of type 'string'.
unit-test (16): tests/unit/telemetry/DatabricksTelemetryExporter.test.ts#L311
Argument of type 'unknown' is not assignable to parameter of type 'string'.
unit-test (18)
The strategy configuration was canceled because "unit-test._20" failed
unit-test (18)
Process completed with exit code 1.
unit-test (18): tests/unit/telemetry/DatabricksTelemetryExporter.test.ts#L330
Argument of type 'unknown' is not assignable to parameter of type 'string'.
unit-test (18): tests/unit/telemetry/DatabricksTelemetryExporter.test.ts#L311
Argument of type 'unknown' is not assignable to parameter of type 'string'.
unit-test (14)
The strategy configuration was canceled because "unit-test._20" failed
unit-test (14)
The operation was canceled.
unit-test (14): tests/unit/telemetry/DatabricksTelemetryExporter.test.ts#L330
Argument of type 'unknown' is not assignable to parameter of type 'string'.
unit-test (14): tests/unit/telemetry/DatabricksTelemetryExporter.test.ts#L311
Argument of type 'unknown' is not assignable to parameter of type 'string'.
e2e-test
The deployment was rejected or didn't satisfy other protection rules.
lint
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/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. 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/
lint: tests/e2e/protocol_versions.test.ts#L329
Unexpected unnamed function
lint: tests/e2e/protocol_versions.test.ts#L44
Unexpected unnamed function
lint: tests/e2e/protocol_versions.test.ts#L33
Unexpected unnamed function
unit-test (20)
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/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. 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/
unit-test (16)
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/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. 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/
unit-test (18)
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/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. 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/
unit-test (14)
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/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, actions/setup-python@7f4fc3e22c37d6ff65e88745f38bd3157c663f7c. 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/