fix: ExternalTaskSensor check_existence ignored in deferrable mode (Airflow < 3.0) #25356
eladkalci-amd-arm.yml
on: pull_request
Matrix: Build CI images / build-ci-images
Matrix: Airflow CTL tests / distributions-tests
Basic tests
/
Breeze unit tests
1m 9s
Basic tests
/
Breeze integration tests
1m 15s
Basic tests
/
Scripts tests
24s
Basic tests
/
React UI tests
1m 31s
Basic tests
/
Check translation completeness
25s
Basic tests
/
Static checks: basic checks only
0s
Basic tests
/
Test git clone on Windows
21s
Basic tests
/
Upgrade checks
0s
Basic tests
/
Test Airflow release commands
0s
Basic tests
/
Test Airflow standalone commands
26s
Go SDK tests
42s
Platform: ARM
0s
Platform: AMD
4s
Verify release calendar
0s
Matrix: Generate constraints / generate-constraints-matrix
Matrix: MySQL tests: core / tests
Matrix: MySQL tests: providers / tests
Matrix: Non-DB tests: core / tests
Matrix: Non-DB tests: providers / tests
Matrix: Postgres tests: core / tests
Matrix: Postgres tests: providers / tests
Matrix: Sqlite tests: core / tests
Matrix: Sqlite tests: providers / tests
Matrix: Task SDK tests / distributions-tests
Matrix: Low dep tests:core / tests
Matrix: Low dep tests: providers / tests
Matrix: Additional CI image checks / Push Early Image Cache / push-ci-image-cache
Waiting for pending jobs
Matrix: Additional CI image checks / Push Early Image Cache / push-prod-image-cache
Waiting for pending jobs
Matrix: CI image checks / Build documentation
Matrix: CI image checks / MyPy checks
Matrix: provider distributions tests / prepare-install-verify-provider-distributions
Matrix: provider distributions tests / providers-compatibility-tests-matrix
Matrix: Helm tests / tests-helm
Matrix: Integration and System Tests / tests-core-integration
Matrix: Integration and System Tests / tests-providers-integration
Matrix: Special tests / Latest Boto test: core / tests
Matrix: Special tests / Latest Boto test: providers / tests
Matrix: Special tests / Latest SQLAlchemy test: providers / tests
Matrix: Special tests / Latest SQLAlchemy test: core / tests
Matrix: Special tests / Min SQLAlchemy test: providers / tests
Matrix: Special tests / Min SQLAlchemy test: core / tests
Matrix: Special tests / Pendulum2 test: core / tests
Matrix: Special tests / Pendulum2 test: providers / tests
Matrix: Special tests / Quarantined test: core / tests
Matrix: Special tests / Quarantined test: providers / tests
Matrix: tests-special / tests-system-core / tests
Additional CI image checks
/
Check that image builds quickly
10m 32s
CI image checks
/
Static checks
21m 1s
CI image checks
/
Test Python API client
4m 58s
Helm tests
/
Release Helm
1m 46s
Integration and System Tests
/
System Tests
5m 13s
Build PROD images
/
Build Airflow and provider distributions
3m 47s
CI image checks
/
Publish documentation and validate versions
4m 47s
Summarize warnings
0s
Matrix: Build PROD images / build-prod-images
Matrix: Kubernetes tests / tests-kubernetes
Additional PROD image tests
/
...
/
Build Airflow and provider distributions
Additional PROD image tests
/
...
/
Build Airflow and provider distributions
Additional PROD image tests
/
Test examples of PROD image building
3m 21s
Additional PROD image tests
/
Docker Compose quick start with PROD image verifying
3m 51s
Additional PROD image tests
/
Task SDK integration tests with PROD image
3m 42s
Additional PROD image tests
/
...
/
Regular e2e test
10m 38s
Additional PROD image tests
/
...
/
Remote logging e2e test
5m 41s
Additional PROD image tests
/
...
/
Elasticsearch remote logging e2e test
5m 3s
Additional PROD image tests
/
...
/
XCom object storage backend e2e test
5m 10s
Additional PROD image tests
/
...
/
Chromium UI e2e tests
17m 52s
Additional PROD image tests
/
...
/
Firefox UI e2e tests
40m 21s
Additional PROD image tests
/
...
/
WebKit UI e2e tests
17m 9s
Additional PROD image tests
/
Airflow CTL integration tests with PROD image
5m 38s
Matrix: Additional PROD image tests / PROD image extra checks (main) / pip-image / build-prod-images
Waiting for pending jobs
Matrix: Additional PROD image tests / PROD image extra checks (release) / pip-image / build-prod-images
Waiting for pending jobs
Matrix: Finalize tests / dependency-upgrade-summary
Waiting for pending jobs
Matrix: finalize-tests / push-buildx-cache-to-github-registry / push-ci-image-cache
Waiting for pending jobs
Matrix: finalize-tests / push-buildx-cache-to-github-registry / push-prod-image-cache
Waiting for pending jobs
Notify Slack
0s
Annotations
16 errors, 56 warnings, and 3 notices
|
provider distributions tests / Compat 2.11.1:P3.10:
Process completed with exit code 1.
|
|
provider distributions tests / Compat 3.0.6:P3.10:
Process completed with exit code 1.
|
|
provider distributions tests / Compat 3.1.8:P3.10:
Process completed with exit code 1.
|
|
[chromium] › tests/e2e/specs/task-instances.spec.ts:137:3 › Task Instances Page › verify task details display correctly:
airflow-core/src/airflow/ui/tests/e2e/pages/TaskInstancesPage.ts#L40
1) [chromium] › tests/e2e/specs/task-instances.spec.ts:137:3 › Task Instances Page › verify task details display correctly
TimeoutError: locator.waitFor: Timeout 10000ms exceeded.
Call log:
- waiting for locator('table, div[role="table"]') to be visible
at ../pages/TaskInstancesPage.ts:40
38 | await this.navigateTo(TaskInstancesPage.taskInstancesUrl);
39 | await this.page.waitForURL(/.*task_instances/, { timeout: 15_000 });
> 40 | await this.taskInstancesTable.waitFor({ state: "visible", timeout: 10_000 });
| ^
41 |
42 | const dataLink = this.taskInstancesTable.locator("a[href*='/dags/']").first();
43 | const noDataMessage = this.page.locator('text="No Task Instances found"');
at TaskInstancesPage.navigate (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/TaskInstancesPage.ts:40:35)
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/task-instances.spec.ts:138:5
|
|
Special tests / Latest Boto test: providers / All-prov:LatestBoto-Postgres:14:3.10:-amazon,celer...standard
Process completed with exit code 1.
|
|
Special tests / Pendulum2 test: providers / All-prov:Pendulum2-Postgres:14:3.10:-amazon,celer...standard
Process completed with exit code 1.
|
|
[firefox] › tests/e2e/specs/dag-calendar-tab.spec.ts:133:3 › DAG Calendar Tab › failed filter shows only failed runs:
airflow-core/src/airflow/ui/tests/e2e/specs/dag-calendar-tab.spec.ts#L0
4) [firefox] › tests/e2e/specs/dag-calendar-tab.spec.ts:133:3 › DAG Calendar Tab › failed filter shows only failed runs
Test timeout of 60000ms exceeded.
|
|
[firefox] › tests/e2e/specs/requiredAction.spec.ts:43:3 › Verify Required Action page › Verify the actions list/table is displayed (or empty state if none):
airflow-core/src/airflow/ui/tests/e2e/pages/RequiredActionsPage.ts#L271
3) [firefox] › tests/e2e/specs/requiredAction.spec.ts:43:3 › Verify Required Action page › Verify the actions list/table is displayed (or empty state if none)
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timeout 30000ms exceeded while waiting on the predicate
at ../pages/RequiredActionsPage.ts:271
269 |
270 | await expect(stateBadge).toContainText(options.expectedState, { timeout: 5000 });
> 271 | }).toPass({ timeout: options.timeout ?? 120_000 });
| ^
272 | }
273 | }
274 |
at RequiredActionsPage.waitForTaskState (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/RequiredActionsPage.ts:271:8)
at RequiredActionsPage.verifyFinalTaskStates (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/RequiredActionsPage.ts:239:18)
at RequiredActionsPage.runHITLFlow (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/RequiredActionsPage.ts:223:5)
at RequiredActionsPage.runHITLFlowWithRejection (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/RequiredActionsPage.ts:65:5)
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/requiredAction.spec.ts:38:5
|
|
[firefox] › tests/e2e/specs/requiredAction.spec.ts:43:3 › Verify Required Action page › Verify the actions list/table is displayed (or empty state if none):
airflow-core/src/airflow/ui/tests/e2e/pages/RequiredActionsPage.ts#L271
3) [firefox] › tests/e2e/specs/requiredAction.spec.ts:43:3 › Verify Required Action page › Verify the actions list/table is displayed (or empty state if none)
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: Test timeout of 30000ms exceeded
at ../pages/RequiredActionsPage.ts:271
269 |
270 | await expect(stateBadge).toContainText(options.expectedState, { timeout: 5000 });
> 271 | }).toPass({ timeout: options.timeout ?? 120_000 });
| ^
272 | }
273 | }
274 |
at RequiredActionsPage.waitForTaskState (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/RequiredActionsPage.ts:271:8)
at RequiredActionsPage.verifyFinalTaskStates (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/RequiredActionsPage.ts:240:18)
at RequiredActionsPage.runHITLFlow (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/RequiredActionsPage.ts:223:5)
at RequiredActionsPage.runHITLFlowWithRejection (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/RequiredActionsPage.ts:65:5)
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/requiredAction.spec.ts:38:5
|
|
[firefox] › tests/e2e/specs/requiredAction.spec.ts:43:3 › Verify Required Action page › Verify the actions list/table is displayed (or empty state if none):
airflow-core/src/airflow/ui/tests/e2e/pages/RequiredActionsPage.ts#L271
3) [firefox] › tests/e2e/specs/requiredAction.spec.ts:43:3 › Verify Required Action page › Verify the actions list/table is displayed (or empty state if none)
Error: expect(locator).toBeVisible() failed
Locator: getByTestId('grid-manual__2026-03-29T08:38:59.729410+00:00-wait_for_multiple_options')
Expected: visible
Timeout: 5000ms
Error: element(s) not found
Call log:
- Expect "toBeVisible" with timeout 5000ms
- waiting for getByTestId('grid-manual__2026-03-29T08:38:59.729410+00:00-wait_for_multiple_options')
Call Log:
- Timeout 120000ms exceeded while waiting on the predicate
at ../pages/RequiredActionsPage.ts:271
269 |
270 | await expect(stateBadge).toContainText(options.expectedState, { timeout: 5000 });
> 271 | }).toPass({ timeout: options.timeout ?? 120_000 });
| ^
272 | }
273 | }
274 |
at RequiredActionsPage.waitForTaskState (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/RequiredActionsPage.ts:271:8)
at RequiredActionsPage.handleWaitForMultipleOptionsTask (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/RequiredActionsPage.ts:173:16)
at RequiredActionsPage.runHITLFlow (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/RequiredActionsPage.ts:213:5)
at RequiredActionsPage.runHITLFlowWithApproval (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/RequiredActionsPage.ts:61:5)
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/requiredAction.spec.ts:37:5
|
|
[firefox] › tests/e2e/specs/dag-code-tab.spec.ts:46:3 › DAG Code Tab › Verify line numbers are displayed:
airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts#L42
2) [firefox] › tests/e2e/specs/dag-code-tab.spec.ts:46:3 › DAG Code Tab › Verify line numbers are displayed
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: Test timeout of 60000ms exceeded
at ../pages/DagCodePage.ts:42
40 | await this.navigateTo(`/dags/${dagId}/code`);
41 | await expect(this.editorContainer).toBeVisible({ timeout: 5000 });
> 42 | }).toPass({ intervals: [2000], timeout: 60_000 });
| ^
43 | await this.waitForCodeReady();
44 | }
45 |
at DagCodePage.navigateToCodeTab (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts:42:8)
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/dag-code-tab.spec.ts:31:20
|
|
[firefox] › tests/e2e/specs/dag-code-tab.spec.ts:46:3 › DAG Code Tab › Verify line numbers are displayed:
airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts#L42
2) [firefox] › tests/e2e/specs/dag-code-tab.spec.ts:46:3 › DAG Code Tab › Verify line numbers are displayed
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: Test timeout of 60000ms exceeded
at ../pages/DagCodePage.ts:42
40 | await this.navigateTo(`/dags/${dagId}/code`);
41 | await expect(this.editorContainer).toBeVisible({ timeout: 5000 });
> 42 | }).toPass({ intervals: [2000], timeout: 60_000 });
| ^
43 | await this.waitForCodeReady();
44 | }
45 |
at DagCodePage.navigateToCodeTab (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts:42:8)
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/dag-code-tab.spec.ts:31:20
|
|
[firefox] › tests/e2e/specs/dag-code-tab.spec.ts:46:3 › DAG Code Tab › Verify line numbers are displayed:
airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts#L42
2) [firefox] › tests/e2e/specs/dag-code-tab.spec.ts:46:3 › DAG Code Tab › Verify line numbers are displayed
Error: expect(locator).toBeVisible() failed
Locator: locator('[role="code"]')
Expected: visible
Timeout: 5000ms
Error: element(s) not found
Call log:
- Expect "toBeVisible" with timeout 5000ms
- waiting for locator('[role="code"]')
Call Log:
- Test timeout of 60000ms exceeded
at ../pages/DagCodePage.ts:42
40 | await this.navigateTo(`/dags/${dagId}/code`);
41 | await expect(this.editorContainer).toBeVisible({ timeout: 5000 });
> 42 | }).toPass({ intervals: [2000], timeout: 60_000 });
| ^
43 | await this.waitForCodeReady();
44 | }
45 |
at DagCodePage.navigateToCodeTab (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts:42:8)
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/dag-code-tab.spec.ts:31:20
|
|
[firefox] › tests/e2e/specs/dag-code-tab.spec.ts:42:3 › DAG Code Tab › Verify code is scrollable for long files:
airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts#L42
1) [firefox] › tests/e2e/specs/dag-code-tab.spec.ts:42:3 › DAG Code Tab › Verify code is scrollable for long files
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: Test timeout of 60000ms exceeded
at ../pages/DagCodePage.ts:42
40 | await this.navigateTo(`/dags/${dagId}/code`);
41 | await expect(this.editorContainer).toBeVisible({ timeout: 5000 });
> 42 | }).toPass({ intervals: [2000], timeout: 60_000 });
| ^
43 | await this.waitForCodeReady();
44 | }
45 |
at DagCodePage.navigateToCodeTab (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts:42:8)
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/dag-code-tab.spec.ts:31:20
|
|
[firefox] › tests/e2e/specs/dag-code-tab.spec.ts:42:3 › DAG Code Tab › Verify code is scrollable for long files:
airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts#L42
1) [firefox] › tests/e2e/specs/dag-code-tab.spec.ts:42:3 › DAG Code Tab › Verify code is scrollable for long files
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: Test timeout of 60000ms exceeded
at ../pages/DagCodePage.ts:42
40 | await this.navigateTo(`/dags/${dagId}/code`);
41 | await expect(this.editorContainer).toBeVisible({ timeout: 5000 });
> 42 | }).toPass({ intervals: [2000], timeout: 60_000 });
| ^
43 | await this.waitForCodeReady();
44 | }
45 |
at DagCodePage.navigateToCodeTab (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts:42:8)
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/dag-code-tab.spec.ts:31:20
|
|
[firefox] › tests/e2e/specs/dag-code-tab.spec.ts:42:3 › DAG Code Tab › Verify code is scrollable for long files:
airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts#L42
1) [firefox] › tests/e2e/specs/dag-code-tab.spec.ts:42:3 › DAG Code Tab › Verify code is scrollable for long files
Error: expect(locator).toBeVisible() failed
Locator: locator('[role="code"]')
Expected: visible
Timeout: 5000ms
Error: element(s) not found
Call log:
- Expect "toBeVisible" with timeout 5000ms
- waiting for locator('[role="code"]')
Call Log:
- Test timeout of 60000ms exceeded
at ../pages/DagCodePage.ts:42
40 | await this.navigateTo(`/dags/${dagId}/code`);
41 | await expect(this.editorContainer).toBeVisible({ timeout: 5000 });
> 42 | }).toPass({ intervals: [2000], timeout: 60_000 });
| ^
43 | await this.waitForCodeReady();
44 | }
45 |
at DagCodePage.navigateToCodeTab (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts:42:8)
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/dag-code-tab.spec.ts:31:20
|
|
Basic tests / React UI tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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/
|
|
Build CI images / Build CI linux/amd64 image 3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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/
|
|
Integration and System Tests / Integration core redis
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Integration and System Tests / Integration: providers redis
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Integration and System Tests / Integration core kerberos
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Integration and System Tests / Integration: providers mongo
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Non-DB tests: core / Non-DB-core::3.10:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Integration and System Tests / Integration: providers ydb
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Integration and System Tests / Integration: providers drill
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Integration and System Tests / Integration: providers elasticsearch
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Integration and System Tests / Integration: providers pinot
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Integration and System Tests / Integration: providers trino
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Integration and System Tests / Integration: providers tinkerpop
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Integration and System Tests / Integration: providers qdrant
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Special tests / System test: / System-core:SystemTest:14:3.10:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Integration and System Tests / Integration: providers celery
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Special tests / Quarantined test: core / Qrnt-core:Postgres:14:3.10:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Non-DB tests: core / Non-DB-core::3.10:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Special tests / Quarantined test: core / Qrnt-core:Postgres:14:3.10:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Integration and System Tests / Integration: providers cassandra
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Integration and System Tests / Integration: providers kafka
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Integration and System Tests / System Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Special tests / System test: / System-core:SystemTest:14:3.10:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Special tests / Quarantined test: providers / Qrnt-prov:Postgres:14:3.10:-amazon,celer...standard
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Integration and System Tests / Integration core otel
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Low dep tests: providers / All-prov:LowestDeps:14:3.10:mysql...samba
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Low dep tests: providers / All-prov:LowestDeps:14:3.10:asana...exasol
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Low dep tests: providers / All-prov:LowestDeps:14:3.10:fab...mongo
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Non-DB tests: providers / Non-DB-prov::3.10:-amazon,celer...standard
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Low dep tests: providers / All-prov:LowestDeps:14:3.10:airbyte...arangodb
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
CI image checks / Static checks
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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/
|
|
Build PROD images / Build PROD Regular image 3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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/
|
|
Special tests / Latest SQLAlchemy test: core / DB-core:LatestSQLAlchemy-Postgres:14:3.10:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Special tests / Pendulum2 test: core / All-core:Pendulum2-Postgres:14:3.10:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Special tests / Min SQLAlchemy test: core / DB-core:MinSQLAlchemy-Postgres:14:3.10:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Low dep tests:core / All-core:LowestDeps:14:3.10:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Sqlite tests: core / DB-core:Sqlite:3.10:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Sqlite tests: core / DB-core:Sqlite:3.10:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Special tests / Latest Boto test: core / All-core:LatestBoto-Postgres:14:3.10:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Low dep tests:core / All-core:LowestDeps:14:3.10:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Postgres tests: core / DB-core:Postgres:14:3.10:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Special tests / Min SQLAlchemy test: core / DB-core:MinSQLAlchemy-Postgres:14:3.10:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Special tests / Latest SQLAlchemy test: core / DB-core:LatestSQLAlchemy-Postgres:14:3.10:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Special tests / Latest Boto test: core / All-core:LatestBoto-Postgres:14:3.10:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Special tests / Pendulum2 test: core / All-core:Pendulum2-Postgres:14:3.10:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
MySQL tests: core / DB-core:MySQL:8.0:3.10:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Postgres tests: core / DB-core:Postgres:14:3.10:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
MySQL tests: core / DB-core:MySQL:8.0:3.10:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Low dep tests: providers / All-prov:LowestDeps:14:3.10:segment...zendesk
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
MySQL tests: providers / DB-prov:MySQL:8.0:3.10:-amazon,celer...standard
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Special tests / Latest SQLAlchemy test: providers / DB-prov:LatestSQLAlchemy-Postgres:14:3.10:-amazon,celer...standard
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Special tests / Min SQLAlchemy test: providers / DB-prov:MinSQLAlchemy-Postgres:14:3.10:-amazon,celer...standard
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Postgres tests: providers / DB-prov:Postgres:14:3.10:-amazon,celer...standard
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Special tests / Latest Boto test: providers / All-prov:LatestBoto-Postgres:14:3.10:-amazon,celer...standard
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Sqlite tests: providers / DB-prov:Sqlite:3.10:-amazon,celer...standard
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Special tests / Pendulum2 test: providers / All-prov:Pendulum2-Postgres:14:3.10:-amazon,celer...standard
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
🎭 Playwright Run Summary
1 skipped
87 passed (13.2m)
|
|
🎭 Playwright Run Summary
1 flaky
[chromium] › tests/e2e/specs/task-instances.spec.ts:137:3 › Task Instances Page › verify task details display correctly
1 skipped
86 passed (13.7m)
|
|
🎭 Playwright Run Summary
3 failed
[firefox] › tests/e2e/specs/dag-code-tab.spec.ts:42:3 › DAG Code Tab › Verify code is scrollable for long files
[firefox] › tests/e2e/specs/dag-code-tab.spec.ts:46:3 › DAG Code Tab › Verify line numbers are displayed
[firefox] › tests/e2e/specs/requiredAction.spec.ts:43:3 › Verify Required Action page › Verify the actions list/table is displayed (or empty state if none)
7 flaky
[firefox] › tests/e2e/specs/dag-calendar-tab.spec.ts:133:3 › DAG Calendar Tab › failed filter shows only failed runs
[firefox] › tests/e2e/specs/dag-code-tab.spec.ts:34:3 › DAG Code Tab › Verify DAG source code is displayed
[firefox] › tests/e2e/specs/dag-code-tab.spec.ts:38:3 › DAG Code Tab › Verify syntax highlighting is applied
[firefox] › tests/e2e/specs/dags-list.spec.ts:31:3 › Dag Trigger Workflow › should successfully trigger a Dag run
[firefox] › tests/e2e/specs/task-instances.spec.ts:132:3 › Task Instances Page › verify task instances table displays data
[firefox] › tests/e2e/specs/task-instances.spec.ts:137:3 › Task Instances Page › verify task details display correctly
[firefox] › tests/e2e/specs/xcoms.spec.ts:92:3 › XComs Page › verify filtering by key pattern ──
1 skipped
77 passed (35.8m)
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
Helm artifacts
Expired
|
479 KB |
sha256:a66acb93df442586c5e5f8dd7a694f9fcc5a524604e544d6615906a194f15afc
|
|
|
airflow-docs
Expired
|
306 MB |
sha256:39fdb2628d9b57090d2dca507a1f667a5e8786d288bec5f82f4a75d8d84860a3
|
|
|
airflow-logs-providers--amazon,celer...standard-All-LatestBoto-Postgres-postgres-14-3.10
Expired
|
647 Bytes |
sha256:31de3b7905c8771719a8dc9c892a8c480dab0c228acdd92055e1ad543047bcf7
|
|
|
airflow-logs-providers--amazon,celer...standard-All-Pendulum2-Postgres-postgres-14-3.10
Expired
|
635 Bytes |
sha256:a46e3044014a2eb229885c60f1ae408bcb36ca4057f6a17a66792b5895b24cf2
|
|
|
cache-prek-v9-linux_amd64-python3.10.20-uv0.10.12-85d69a8464bb09f130ebd8d14d64ead3f2f18d79e8e26aa6ba2489811c14d65d-64394_merge
Expired
|
257 MB |
sha256:26bb1457320c19287d6d8344ec97064697655a998de133d10dd278c081c213d9
|
|
|
cache-ui-node-modules-v1-Linux--64394_merge
Expired
|
49.8 MB |
sha256:3842665f18b8405e2208a60e0a7ae0b8283c8d6f9af1bfa1a75c4e78fc7dcc80
|
|
|
ci-image-save-v3-linux_amd64-3.10-64394_merge
Expired
|
2.09 GB |
sha256:15f3ee88cb44a9a60f71012780e3ac9647df72321e4f1c5bb87471e656507bd7
|
|
|
constraints-3.10
Expired
|
13.2 KB |
sha256:e6563e2baff3304e42f5ec012ecdb101358fd0ed8dd28dbd748d071b885574bb
|
|
|
container-logs-providers--amazon,celer...standard-All-LatestBoto-Postgres-postgres-14-3.10
Expired
|
1.5 KB |
sha256:c63e6239038828aecbdb05d4d528eb8cfcd90f1de689d3a9c15f24ea02cb9193
|
|
|
container-logs-providers--amazon,celer...standard-All-Pendulum2-Postgres-postgres-14-3.10
Expired
|
1.49 KB |
sha256:1ae95c2729d7a83f9f8e437d7ffbf21feef444c38f8d8ee88caa9c35eff056c1
|
|
|
e2e-test-logs-basic
Expired
|
276 KB |
sha256:520647e4799d95b03d4cbb7bac132f5671c632670e67cd1fee0d514713acf169
|
|
|
e2e-test-logs-remote_log
Expired
|
21.8 KB |
sha256:38bd42773a926949e641506141933f01ba51ca6d44d95a696d79df0214a2b87d
|
|
|
e2e-test-logs-remote_log_elasticsearch
Expired
|
29.2 KB |
sha256:1edbe9185e03b35f976123f6cc0e112d94d066d68ce528d34ef0f5fce330d4ce
|
|
|
e2e-test-logs-xcom_object_storage
Expired
|
30.2 KB |
sha256:c8c3be35eec3e33144aa9b2a202d25cc8c45b7ebf673e33e8128b47b5f0f6ac6
|
|
|
playwright-report-chromium
Expired
|
2.93 MB |
sha256:cabcddae99927a9291ab550d2458e175cb290e45b7f2f7159cd1827c95cf65e9
|
|
|
playwright-report-firefox
Expired
|
333 MB |
sha256:4c13c8190763e8c4541e60f8937661e3831420eadcdb4b7a9e17ed04265c42b0
|
|
|
playwright-report-webkit
Expired
|
329 KB |
sha256:2df3eea30a9acef650b26fac84b2417824d2162850b8c2d48bfd8f67fb27614b
|
|
|
prod-image-save-v3-linux_amd64-3.10-64394_merge
Expired
|
627 MB |
sha256:9b6f9a65b9248211fa241ef4c8084b478898492925a47dbc7eb1abadbf68fcc1
|
|
|
prod-packages
Expired
|
8.19 MB |
sha256:991b0c0b0b063b94c162a0483888d6dfedf1d6e317e1ec0f29aa4e18284c198d
|
|
|
test-warnings-core-API...CLI-All-LatestBoto-Postgres-postgres-14-3.10
Expired
|
55.8 KB |
sha256:9d020855efd9796eaf104108a0e36091d5ef2f054cbafad6a8b1cce47661fde7
|
|
|
test-warnings-core-API...CLI-All-LowestDeps-sqlite-14-3.10
Expired
|
35 KB |
sha256:3457bee9f58131dd4ef24b9a96a314a83d6ae913de3c463084defb0cef626106
|
|
|
test-warnings-core-API...CLI-All-Pendulum2-Postgres-postgres-14-3.10
Expired
|
55.6 KB |
sha256:9e002bc693b6fb9735bfdc3c897e24c07c5057f25433994f72c7b562505440b3
|
|
|
test-warnings-core-API...CLI-DB-LatestSQLAlchemy-Postgres-postgres-14-3.10
Expired
|
54.3 KB |
sha256:f2a9a5185a3b2752ec8420b9e686e812a53646130bd8af2d69c809ab728872e7
|
|
|
test-warnings-core-API...CLI-DB-MinSQLAlchemy-Postgres-postgres-14-3.10
Expired
|
54.3 KB |
sha256:607102dbb9bd0812440a0f508d0874fa19cf19e15b7bf96e0333f2837169431e
|
|
|
test-warnings-core-API...CLI-DB-MySQL-mysql-8.0-3.10
Expired
|
57.9 KB |
sha256:ab35bb0940399d0409beccf028e9a965a256b95b23b05f7e6fa3a9f900d32550
|
|
|
test-warnings-core-API...CLI-DB-Postgres-postgres-14-3.10
Expired
|
54.3 KB |
sha256:f1349d0704e40f2533c79a60d7cb049e08aec6fe37106609404176530907bb92
|
|
|
test-warnings-core-API...CLI-DB-Sqlite-sqlite--3.10
Expired
|
54.4 KB |
sha256:3289e155db533c3b6486b1cd8b666699ceec4e2f3fb69bbf7482cf90b3a51cc4
|
|
|
test-warnings-core-API...CLI-Non-DB--sqlite--3.10
Expired
|
4.91 KB |
sha256:0115d0c2ffc7e4fc81a700b59b50aa54653766ed975b7fe027427df5837f5cff
|
|
|
test-warnings-core-API...CLI-Quarantined-Postgres-postgres-14-3.10
Expired
|
468 Bytes |
sha256:61e4271b8efed5acf23fdf91d24f88c94aa33aa870c32dce073c4a236e3694dc
|
|
|
test-warnings-core-Core...Serialization-All-LatestBoto-Postgres-postgres-14-3.10
Expired
|
9.81 KB |
sha256:bd80e290d28dcda4f009050bef2db215250c12f462fea102615fd8753b8408ab
|
|
|
test-warnings-core-Core...Serialization-All-LowestDeps-sqlite-14-3.10
Expired
|
9.54 KB |
sha256:6afc29d98320e058ed066d391dba3b393cf6fbcdddb2a04c50715268e08e0d46
|
|
|
test-warnings-core-Core...Serialization-All-Pendulum2-Postgres-postgres-14-3.10
Expired
|
17.2 KB |
sha256:4916f85265014506faf6bebd720215e7c7f0e30d4e598cf0950aef24fcdbe367
|
|
|
test-warnings-core-Core...Serialization-DB-LatestSQLAlchemy-Postgres-postgres-14-3.10
Expired
|
8.27 KB |
sha256:539b1fc2a5579d4aec4983fef898e0261afdfd549a75a8615ea13880b467c35e
|
|
|
test-warnings-core-Core...Serialization-DB-MinSQLAlchemy-Postgres-postgres-14-3.10
Expired
|
8.29 KB |
sha256:415e3e6039272719640ce2b17d5497ba93bb054ff7e09e57a89ed49fbef6f142
|
|
|
test-warnings-core-Core...Serialization-DB-MySQL-mysql-8.0-3.10
Expired
|
10.7 KB |
sha256:2959e364ea2e7579568a33ff24c576fb9ee417c6a31c3aaec9b091591793b758
|
|
|
test-warnings-core-Core...Serialization-DB-Postgres-postgres-14-3.10
Expired
|
8.26 KB |
sha256:fa02efff28bc41d728160831cb1bc9fa99b5666185425b3f08cf13033aac9e29
|
|
|
test-warnings-core-Core...Serialization-DB-Sqlite-sqlite--3.10
Expired
|
8.47 KB |
sha256:28f9da742ebf2f75446509a9ec9b50bef35db980fbf30c77a0aadeef1365b156
|
|
|
test-warnings-core-Core...Serialization-Non-DB--sqlite--3.10
Expired
|
2.38 KB |
sha256:9d3410df778b9396b4c905b994574795d01a6e68a1ccd3ac8e195ebe1885fab2
|
|
|
test-warnings-core-Core...Serialization-Quarantined-Postgres-postgres-14-3.10
Expired
|
468 Bytes |
sha256:8747a44788fb36b4e18227a5b6545bfa6e299e0e17ce7da6644a9d66e94df09c
|
|
|
test-warnings-integration-providers-cassandra
Expired
|
815 Bytes |
sha256:d2a8ca1426d8ce54fbec1a25df9b5c7dc6b698ea3a89e4c566e201a141e96d70
|
|
|
test-warnings-integration-providers-qdrant
Expired
|
629 Bytes |
sha256:be8db16b4367d326b420d7c531638322da4e69082319be73f9ada1ef13208aad
|
|
|
test-warnings-integration-providers-trino
Expired
|
512 Bytes |
sha256:ddaf0a3146fe5191bbd54cb8ac808507ca30d961221ba85b15747368a5db18fe
|
|
|
test-warnings-providers--amazon,celer...standard-DB-LatestSQLAlchemy-Postgres-postgres-14-3.10
Expired
|
17.8 KB |
sha256:f02087d484610cc1547275149b86b186084ead49e3051a0218852a17ab3d9ac6
|
|
|
test-warnings-providers--amazon,celer...standard-DB-MinSQLAlchemy-Postgres-postgres-14-3.10
Expired
|
17.8 KB |
sha256:53d4c11599f88420d2c642e95764b6a684cd0701e4423baa340381bdc6c5d0c6
|
|
|
test-warnings-providers--amazon,celer...standard-DB-MySQL-mysql-8.0-3.10
Expired
|
17.9 KB |
sha256:db8a1dfd54e6bb152e54fc57c27428b9580005075614f56662369f38ae09fd95
|
|
|
test-warnings-providers--amazon,celer...standard-DB-Postgres-postgres-14-3.10
Expired
|
17.8 KB |
sha256:1054c51c60562586af7fdce925c8f76cd43993ea9870b7be08aa150a0223319e
|
|
|
test-warnings-providers--amazon,celer...standard-DB-Sqlite-sqlite--3.10
Expired
|
18 KB |
sha256:a079f6c218e75e30e8837ca2adb0d35879fbfa57d2c36f6e865c5687d719160f
|
|
|
test-warnings-providers--amazon,celer...standard-Non-DB--sqlite--3.10
Expired
|
29.2 KB |
sha256:5bdb44c107c25a1c1f30a6325ad579852a49125fa77318b277894e9e7bd59451
|
|
|
test-warnings-providers-airbyte...arangodb-All-LowestDeps-sqlite-14-3.10
Expired
|
19.5 KB |
sha256:4028841701b1ee94f9ed5f97b0ff41fdd79859934b781b2f5edff594dfd7d602
|
|
|
test-warnings-providers-asana...exasol-All-LowestDeps-sqlite-14-3.10
Expired
|
16.6 KB |
sha256:281f34a1f5e0f89c9aae81010ef8d8103b349e6c4b89df60e8e0e5194447a5e9
|
|
|
test-warnings-providers-fab...mongo-All-LowestDeps-sqlite-14-3.10
Expired
|
13.8 KB |
sha256:a6e1494f6fcd6fbbe745c2c361d9b32eee512dd2b72d692547df8d16ec1e61cb
|
|
|
test-warnings-providers-mysql...samba-All-LowestDeps-sqlite-14-3.10
Expired
|
3.2 KB |
sha256:c997a2d5d3c87e523a34dcbb52f28663343223d2c41148e3a73b3d18114ee421
|
|
|
test-warnings-providers-segment...zendesk-All-LowestDeps-sqlite-14-3.10
Expired
|
11.9 KB |
sha256:9bd03ba9d36977dd0a051dd800865830e0f6a745ea4338166b365513cf3cc8a5
|
|