Tests #240
ci-amd-arm.yml
on: schedule
Matrix: Build CI images / build-ci-images
Matrix: Airflow CTL tests / distributions-tests
Basic tests
/
Breeze unit tests
58s
Basic tests
/
Breeze integration tests
1m 13s
Basic tests
/
Scripts tests
18s
Basic tests
/
React UI tests
1m 18s
Basic tests
/
Check translation completeness
27s
Basic tests
/
Static checks: basic checks only
0s
Basic tests
/
Test git clone on Windows
32s
Basic tests
/
Upgrade checks
Basic tests
/
Test Airflow release commands
Basic tests
/
Test Airflow standalone commands
27s
Go SDK tests
37s
Platform: ARM
2s
Platform: AMD
0s
Verify release calendar
Matrix: Generate constraints / generate-constraints-matrix
Matrix: MySQL tests: core / tests
Waiting for pending jobs
Matrix: MySQL tests: providers / tests
Waiting for pending jobs
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
9m 21s
CI image checks
/
Static checks
19m 9s
CI image checks
/
Test Python API client
4m 45s
Helm tests
/
Release Helm
1m 39s
Integration and System Tests
/
System Tests
4m 59s
Build PROD images
/
Build Airflow and provider distributions
3m 31s
CI image checks
/
Publish documentation and validate versions
5m 4s
Summarize warnings
0s
Matrix: Build PROD images / build-prod-images
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 18s
Additional PROD image tests
/
Docker Compose quick start with PROD image verifying
3m 40s
Additional PROD image tests
/
Task SDK integration tests with PROD image
4m 3s
Additional PROD image tests
/
...
/
Regular e2e test
2m 3s
Additional PROD image tests
/
...
/
Remote logging e2e test
1m 59s
Additional PROD image tests
/
...
/
Elasticsearch remote logging e2e test
2m 4s
Additional PROD image tests
/
...
/
XCom object storage backend e2e test
1m 57s
Additional PROD image tests
/
...
/
Chromium UI e2e tests
15m 50s
Additional PROD image tests
/
...
/
Firefox UI e2e tests
14m 37s
Additional PROD image tests
/
...
/
WebKit UI e2e tests
17m 32s
Additional PROD image tests
/
Airflow CTL integration tests with PROD image
5m 15s
Matrix: Kubernetes tests / tests-kubernetes
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
26s
Annotations
62 errors, 155 warnings, and 3 notices
|
Helm tests / Release Helm
Process completed with exit code 1.
|
|
provider distributions tests / Providers wheel tests
Process completed with exit code 1.
|
|
Additional PROD image tests / Remote logging tests with PROD image / Remote logging e2e test
No files were found with the provided path: ./airflow-e2e-tests/logs.zip. No artifacts will be uploaded.
|
|
Additional PROD image tests / Remote logging tests with PROD image / Remote logging e2e test
Process completed with exit code 12.
|
|
Additional PROD image tests / Remote logging tests with PROD image / Remote logging e2e test
Process completed with exit code 3.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.12-v1.32.8-false
Process completed with exit code 1.
|
|
Additional PROD image tests / Test e2e integration tests with PROD image / Regular e2e test
No files were found with the provided path: ./airflow-e2e-tests/logs.zip. No artifacts will be uploaded.
|
|
Additional PROD image tests / Test e2e integration tests with PROD image / Regular e2e test
Process completed with exit code 12.
|
|
Additional PROD image tests / Test e2e integration tests with PROD image / Regular e2e test
Process completed with exit code 3.
|
|
Additional PROD image tests / Elasticsearch remote logging tests with PROD image / Elasticsearch remote logging e2e test
No files were found with the provided path: ./airflow-e2e-tests/logs.zip. No artifacts will be uploaded.
|
|
Additional PROD image tests / Elasticsearch remote logging tests with PROD image / Elasticsearch remote logging e2e test
Process completed with exit code 12.
|
|
Additional PROD image tests / Elasticsearch remote logging tests with PROD image / Elasticsearch remote logging e2e test
Process completed with exit code 3.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.13-v1.33.4-true
Process completed with exit code 1.
|
|
Additional PROD image tests / XCom object storage backend tests with PROD image / XCom object storage backend e2e test
No files were found with the provided path: ./airflow-e2e-tests/logs.zip. No artifacts will be uploaded.
|
|
Additional PROD image tests / XCom object storage backend tests with PROD image / XCom object storage backend e2e test
Process completed with exit code 12.
|
|
Additional PROD image tests / XCom object storage backend tests with PROD image / XCom object storage backend e2e test
Process completed with exit code 3.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.11-v1.31.12-true
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.12-v1.32.8-true
Process completed with exit code 1.
|
|
[chromium] › 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
2) [chromium] › 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-25T12:20:09.446975+00:00-wait_for_input')
Expected: visible
Timeout: 5000ms
Error: element(s) not found
Call log:
- Expect "toBeVisible" with timeout 5000ms
- waiting for getByTestId('grid-manual__2026-03-25T12:20:09.446975+00:00-wait_for_input')
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.handleWaitForInputTask (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/RequiredActionsPage.ts:147:16)
at RequiredActionsPage.runHITLFlow (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/RequiredActionsPage.ts:211: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
|
|
[chromium] › 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/pages/DagCalendarTab.ts#L73
1) [chromium] › tests/e2e/specs/dag-calendar-tab.spec.ts:133:3 › DAG Calendar Tab › failed filter shows only failed runs
Error: expect(locator).toBeVisible() failed
Locator: getByTestId('calendar-tooltip')
Expected: visible
Timeout: 20000ms
Error: element(s) not found
Call log:
- Expect "toBeVisible" with timeout 20000ms
- waiting for getByTestId('calendar-tooltip')
at ../pages/DagCalendarTab.ts:73
71 |
72 | await cell.hover();
> 73 | await expect(this.tooltip).toBeVisible({ timeout: 20_000 });
| ^
74 |
75 | const text = ((await this.tooltip.textContent()) ?? "").toLowerCase();
76 |
at DagCalendarTab.getManualRunStates (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/DagCalendarTab.ts:73:34)
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/dag-calendar-tab.spec.ts:136:25
|
|
Additional PROD image tests / WebKit UI e2e tests with PROD image / WebKit UI e2e tests
Process completed with exit code 1.
|
|
[webkit] › 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/pages/DagCalendarTab.ts#L73
3) [webkit] › tests/e2e/specs/dag-calendar-tab.spec.ts:133:3 › DAG Calendar Tab › failed filter shows only failed runs
Error: expect(locator).toBeVisible() failed
Locator: getByTestId('calendar-tooltip')
Expected: visible
Timeout: 20000ms
Error: element(s) not found
Call log:
- Expect "toBeVisible" with timeout 20000ms
- waiting for getByTestId('calendar-tooltip')
at ../pages/DagCalendarTab.ts:73
71 |
72 | await cell.hover();
> 73 | await expect(this.tooltip).toBeVisible({ timeout: 20_000 });
| ^
74 |
75 | const text = ((await this.tooltip.textContent()) ?? "").toLowerCase();
76 |
at DagCalendarTab.getManualRunStates (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/DagCalendarTab.ts:73:34)
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/dag-calendar-tab.spec.ts:136:25
|
|
[webkit] › tests/e2e/specs/dag-calendar-tab.spec.ts:104:3 › DAG Calendar Tab › verify active cells appear for DAG runs:
airflow-core/src/airflow/ui/tests/e2e/specs/dag-calendar-tab.spec.ts#L40
2) [webkit] › tests/e2e/specs/dag-calendar-tab.spec.ts:104:3 › DAG Calendar Tab › verify active cells appear for DAG runs
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
TimeoutError: apiRequestContext.get: Timeout 10000ms exceeded.
Call log:
- → GET http://localhost:8080/api/v2/dags/example_bash_operator
- user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.0 Safari/605.1.15
- accept: */*
- accept-encoding: gzip,deflate,br
- cookie: session=8d68830b-7903-409f-892b-88be17472956.NrysN9AeFfiqIrQ5ZLdnh9TRhhk; _token=***
38 | .poll(
39 | async () => {
> 40 | const response = await page.request.get(`/api/v2/dags/${dagId}`);
| ^
41 |
42 | return response.ok();
43 | },
at Object.expect.poll.intervals (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/dag-calendar-tab.spec.ts:40:47)
|
|
[webkit] › tests/e2e/specs/dag-calendar-tab.spec.ts:104:3 › DAG Calendar Tab › verify active cells appear for DAG runs:
airflow-core/src/airflow/ui/tests/e2e/specs/dag-calendar-tab.spec.ts#L40
2) [webkit] › tests/e2e/specs/dag-calendar-tab.spec.ts:104:3 › DAG Calendar Tab › verify active cells appear for DAG runs
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
TimeoutError: apiRequestContext.get: Timeout 10000ms exceeded.
Call log:
- → GET http://localhost:8080/api/v2/dags/example_bash_operator
- user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.0 Safari/605.1.15
- accept: */*
- accept-encoding: gzip,deflate,br
- cookie: session=8d68830b-7903-409f-892b-88be17472956.NrysN9AeFfiqIrQ5ZLdnh9TRhhk; _token=***
38 | .poll(
39 | async () => {
> 40 | const response = await page.request.get(`/api/v2/dags/${dagId}`);
| ^
41 |
42 | return response.ok();
43 | },
at Object.expect.poll.intervals (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/dag-calendar-tab.spec.ts:40:47)
|
|
[webkit] › tests/e2e/specs/dag-calendar-tab.spec.ts:104:3 › DAG Calendar Tab › verify active cells appear for DAG runs:
airflow-core/src/airflow/ui/tests/e2e/pages/DagCalendarTab.ts#L119
2) [webkit] › tests/e2e/specs/dag-calendar-tab.spec.ts:104:3 › DAG Calendar Tab › verify active cells appear for DAG runs
Error: locator.waitFor: Test timeout of 60000ms exceeded.
Call log:
- waiting for getByTestId('calendar-loading-overlay') to be hidden
116 × locator resolved to visible <div class="css-14812xn" data-testid="calendar-loading-overlay">…</div>
at ../pages/DagCalendarTab.ts:119
117 |
118 | if (await overlay.isVisible().catch(() => false)) {
> 119 | await overlay.waitFor({ state: "hidden", timeout: 120_000 });
| ^
120 | }
121 |
122 | await this.page.getByTestId("calendar-grid").waitFor({ state: "visible", timeout: 120_000 });
at DagCalendarTab.waitForCalendarReady (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/DagCalendarTab.ts:119:21)
at DagCalendarTab.navigateToCalendar (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/DagCalendarTab.ts:90:5)
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/dag-calendar-tab.spec.ts:96:5
|
|
[webkit] › tests/e2e/specs/dag-calendar-tab.spec.ts:104:3 › DAG Calendar Tab › verify active cells appear for DAG runs:
airflow-core/src/airflow/ui/tests/e2e/specs/dag-calendar-tab.spec.ts#L93
2) [webkit] › tests/e2e/specs/dag-calendar-tab.spec.ts:104:3 › DAG Calendar Tab › verify active cells appear for DAG runs
Test timeout of 60000ms exceeded while running "beforeEach" hook.
91 | });
92 |
> 93 | test.beforeEach(async ({ page }) => {
| ^
94 | test.setTimeout(60_000);
95 | calendar = new DagCalendarTab(page);
96 | await calendar.navigateToCalendar(dagId);
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/dag-calendar-tab.spec.ts:93:8
|
|
[webkit] › tests/e2e/specs/backfill.spec.ts:89:7 › Backfill › Backfill creation and validation › verify backfill with 'All Runs' behavior:
airflow-core/src/airflow/ui/tests/e2e/pages/BackfillPage.ts#L172
1) [webkit] › tests/e2e/specs/backfill.spec.ts:89:7 › Backfill › Backfill creation and validation › verify backfill with 'All Runs' behavior
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: No runs matching: dag=example_bash_operator, from=2020-02-01T00:00:00Z, to=2020-02-03T00:00:00Z, reprocess=none
at ../pages/BackfillPage.ts:172
170 | await this.page.keyboard.press("Escape");
171 |
> 172 | throw new Error(
| ^
173 | `No runs matching: dag=${dagName}, from=${fromDate}, to=${toDate}, reprocess=${reprocessBehavior}`,
174 | );
175 | }
at BackfillPage.createBackfill (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/BackfillPage.ts:172:13)
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/backfill.spec.ts:67:28
|
|
[webkit] › tests/e2e/specs/backfill.spec.ts:89:7 › Backfill › Backfill creation and validation › verify backfill with 'All Runs' behavior:
airflow-core/src/airflow/ui/tests/e2e/pages/BackfillPage.ts#L172
1) [webkit] › tests/e2e/specs/backfill.spec.ts:89:7 › Backfill › Backfill creation and validation › verify backfill with 'All Runs' behavior
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: No runs matching: dag=example_bash_operator, from=2020-02-01T00:00:00Z, to=2020-02-03T00:00:00Z, reprocess=none
at ../pages/BackfillPage.ts:172
170 | await this.page.keyboard.press("Escape");
171 |
> 172 | throw new Error(
| ^
173 | `No runs matching: dag=${dagName}, from=${fromDate}, to=${toDate}, reprocess=${reprocessBehavior}`,
174 | );
175 | }
at BackfillPage.createBackfill (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/BackfillPage.ts:172:13)
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/backfill.spec.ts:67:28
|
|
[webkit] › tests/e2e/specs/backfill.spec.ts:89:7 › Backfill › Backfill creation and validation › verify backfill with 'All Runs' behavior:
airflow-core/src/airflow/ui/tests/e2e/pages/BackfillPage.ts#L462
1) [webkit] › tests/e2e/specs/backfill.spec.ts:89:7 › Backfill › Backfill creation and validation › verify backfill with 'All Runs' behavior
Error: Backfill 3 did not complete within 120000ms
expect(received).toBeTruthy()
Received: false
Call Log:
- Timeout 120000ms exceeded while waiting on the predicate
at ../pages/BackfillPage.ts:462
460 |
461 | public async waitForBackfillComplete(backfillId: number, timeout: number = 120_000): Promise<void> {
> 462 | await expect
| ^
463 | .poll(
464 | async () => {
465 | try {
at BackfillPage.waitForBackfillComplete (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/BackfillPage.ts:462:5)
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/backfill.spec.ts:73:9
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.14-v1.34.0-true
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.10-v1.35.0-false
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.10-v1.30.13-true
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.10-v1.30.13-false
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.10-v1.30.13-true
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.11-v1.31.12-false
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.14-v1.34.0-true
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.13-v1.33.4-false
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.13-v1.33.4-true
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.10-v1.30.13-false
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.11-v1.31.12-false
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.10-v1.35.0-true
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.10-v1.35.0-true
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.11-v1.31.12-true
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.12-v1.32.8-true
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.14-v1.34.0-false
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.12-v1.32.8-false
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.13-v1.33.4-false
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.14-v1.34.0-false
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:LocalExecutor-3.10-v1.30.13-true
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.10-v1.35.0-false
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:LocalExecutor-3.12-v1.32.8-true
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:LocalExecutor-3.11-v1.31.12-true
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:LocalExecutor-3.13-v1.33.4-true
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:LocalExecutor-3.14-v1.34.0-true
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:LocalExecutor-3.10-v1.35.0-true
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:LocalExecutor-3.10-v1.30.13-false
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:LocalExecutor-3.11-v1.31.12-false
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:LocalExecutor-3.12-v1.32.8-false
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:LocalExecutor-3.13-v1.33.4-false
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:LocalExecutor-3.14-v1.34.0-false
Process completed with exit code 1.
|
|
Kubernetes tests / K8S System:LocalExecutor-3.10-v1.35.0-false
Process completed with exit code 1.
|
|
Notify Slack
Missing input! A token must be provided to use the method decided.
|
|
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/arm64 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/
|
|
Build CI images / Build CI linux/arm64 image 3.11
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/arm64 image 3.12
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/arm64 image 3.13
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. 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/arm64 image 3.14
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 / 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/
|
|
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/
|
|
Non-DB tests: providers / Non-DB-prov::3.13:-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 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/
|
|
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/
|
|
Postgres tests: core / DB-core:Postgres:18:3.14: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: providers / Non-DB-prov::3.11:-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: core / DB-core:Postgres:15:3.11: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:17:3.13: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:18:3.14: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/
|
|
Non-DB tests: core / Non-DB-core::3.14: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/
|
|
Postgres tests: core / DB-core:Postgres:16:3.12: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: providers / Non-DB-prov::3.12:-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: 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/
|
|
Non-DB tests: core / Non-DB-core::3.14: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 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/
|
|
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/
|
|
Non-DB tests: providers / Non-DB-prov::3.14:-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/
|
|
Non-DB tests: core / Non-DB-core::3.11: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/
|
|
Postgres tests: core / DB-core:Postgres:15:3.11: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/
|
|
Postgres tests: core / DB-core:Postgres:16:3.12: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/
|
|
Non-DB tests: core / Non-DB-core::3.12: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/
|
|
Non-DB tests: core / Non-DB-core::3.11: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 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/
|
|
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/
|
|
Non-DB tests: core / Non-DB-core::3.13: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 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/
|
|
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 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/
|
|
Non-DB tests: core / Non-DB-core::3.12: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:17:3.13: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 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/
|
|
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/
|
|
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/
|
|
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/
|
|
Build PROD images / Build PROD Regular image 3.13
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.11
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.12
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.14
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/
|
|
Postgres tests: providers / DB-prov:Postgres:17:3.13:-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: core / DB-core:Sqlite:3.12: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: providers / DB-prov:Postgres:16:3.12:-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/
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.12-v1.32.8-false
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Sqlite tests: core / DB-core:Sqlite:3.11: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/
|
|
Postgres tests: providers / DB-prov:Postgres:15:3.11:-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: 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/
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.13-v1.33.4-true
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.11-v1.31.12-true
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Non-DB tests: core / Non-DB-core::3.13: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/
|
|
Postgres tests: providers / DB-prov:Postgres:18:3.14:-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.12:-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/
|
|
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/
|
|
Sqlite tests: core / DB-core:Sqlite:3.11: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.13: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: providers / DB-prov:Sqlite:3.11:-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.13:-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/
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.12-v1.32.8-true
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Sqlite tests: providers / DB-prov:Sqlite:3.14:-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: core / DB-core:Sqlite:3.13: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.14: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.14: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.12: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. 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/
|
|
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/
|
|
Low dep tests:core / All-core:LowestDeps:14:3.14: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: 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/
|
|
Low dep tests:core / All-core:LowestDeps:14:3.12: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.14: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.12: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/
|
|
Low dep tests:core / All-core:LowestDeps:14:3.13: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.11: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: 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/
|
|
Low dep tests:core / All-core:LowestDeps:14:3.11: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/
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.14-v1.34.0-true
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.10-v1.35.0-false
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Low dep tests:core / All-core:LowestDeps:14:3.12: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/
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.10-v1.30.13-true
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Low dep tests: providers / All-prov:LowestDeps:14:3.11: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/
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.10-v1.30.13-false
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.10-v1.30.13-true
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.11-v1.31.12-false
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.14-v1.34.0-true
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Low dep tests:core / All-core:LowestDeps:14:3.13: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. 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/
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.13-v1.33.4-false
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.13-v1.33.4-true
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
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/
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.10-v1.30.13-false
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.11-v1.31.12-false
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Low dep tests: providers / All-prov:LowestDeps:14:3.13: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/
|
|
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/
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.10-v1.35.0-true
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Low dep tests: providers / All-prov:LowestDeps:14:3.11: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/
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.10-v1.35.0-true
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Low dep tests: providers / All-prov:LowestDeps:14:3.12: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/
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.11-v1.31.12-true
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.12-v1.32.8-true
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.14-v1.34.0-false
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
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/
|
|
Low dep tests: providers / All-prov:LowestDeps:14:3.12: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/
|
|
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/
|
|
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/
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.12-v1.32.8-false
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
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/
|
|
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/
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.13-v1.33.4-false
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Low dep tests: providers / All-prov:LowestDeps:14:3.13: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.13: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/
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.14-v1.34.0-false
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
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/
|
|
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/
|
|
Low dep tests: providers / All-prov:LowestDeps:14:3.12: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.13: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/
|
|
Kubernetes tests / K8S System:LocalExecutor-3.10-v1.30.13-true
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.10-v1.35.0-false
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Low dep tests: providers / All-prov:LowestDeps:14:3.11: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/
|
|
Kubernetes tests / K8S System:LocalExecutor-3.12-v1.32.8-true
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:LocalExecutor-3.11-v1.31.12-true
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Low dep tests: providers / All-prov:LowestDeps:14:3.12: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/
|
|
Kubernetes tests / K8S System:LocalExecutor-3.13-v1.33.4-true
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:LocalExecutor-3.14-v1.34.0-true
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Low dep tests: providers / All-prov:LowestDeps:14:3.13: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/
|
|
Kubernetes tests / K8S System:LocalExecutor-3.10-v1.35.0-true
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Low dep tests: providers / All-prov:LowestDeps:14:3.11: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/
|
|
Kubernetes tests / K8S System:LocalExecutor-3.10-v1.30.13-false
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:LocalExecutor-3.11-v1.31.12-false
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
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/
|
|
Kubernetes tests / K8S System:LocalExecutor-3.12-v1.32.8-false
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
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/
|
|
Kubernetes tests / K8S System:LocalExecutor-3.13-v1.33.4-false
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:LocalExecutor-3.14-v1.34.0-false
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:LocalExecutor-3.10-v1.35.0-false
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
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 / 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 / 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. 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/
|
|
Low dep tests: providers / All-prov:LowestDeps:14:3.11: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/
|
|
Low dep tests: providers / All-prov:LowestDeps:14:3.14: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/
|
|
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/
|
|
Low dep tests: providers / All-prov:LowestDeps:14:3.14: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/
|
|
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/
|
|
Low dep tests: providers / All-prov:LowestDeps:14:3.14: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/
|
|
Low dep tests: providers / All-prov:LowestDeps:14:3.14: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/
|
|
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/
|
|
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/
|
|
Low dep tests: providers / All-prov:LowestDeps:14:3.14: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/
|
|
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
2 flaky
[chromium] › tests/e2e/specs/dag-calendar-tab.spec.ts:133:3 › DAG Calendar Tab › failed filter shows only failed runs
[chromium] › tests/e2e/specs/requiredAction.spec.ts:43:3 › Verify Required Action page › Verify the actions list/table is displayed (or empty state if none)
1 skipped
85 passed (10.8m)
|
|
🎭 Playwright Run Summary
1 skipped
87 passed (10.0m)
|
|
🎭 Playwright Run Summary
2 failed
[webkit] › tests/e2e/specs/backfill.spec.ts:89:7 › Backfill › Backfill creation and validation › verify backfill with 'All Runs' behavior
[webkit] › tests/e2e/specs/dag-calendar-tab.spec.ts:104:3 › DAG Calendar Tab › verify active cells appear for DAG runs
1 flaky
[webkit] › tests/e2e/specs/dag-calendar-tab.spec.ts:133:3 › DAG Calendar Tab › failed filter shows only failed runs
1 skipped
7 did not run
77 passed (12.5m)
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
airflow-docs
Expired
|
305 MB |
sha256:89c7305dd1b7da8759b44aa557d1bd5d5bb9f1f2bb6a2b8730fc364fa0ec32cd
|
|
|
cache-prek-v9-linux_arm64-python3.10.20-uv0.10.12-5eafae0d5fc9c7705376e8a1f824871c161e52f826b4e73b086b46e7cf11b57b-main
Expired
|
248 MB |
sha256:88f25cdb6538a988ddbc4cf4b155c19a548116162a406ba5a401be4380db8158
|
|
|
cache-ui-node-modules-v1-Linux--main
Expired
|
49.8 MB |
sha256:2c8d4aec4d73ef0ca2c1a2b7f320c4d79cc50ec6d03f339a27d89d89d425dc35
|
|
|
ci-image-save-v3-linux_arm64-3.10-main
Expired
|
1.86 GB |
sha256:8bb7f0bb2f0913ba3a56c6b40a96446961fe2befe0d0a687fefc3dceedd3ebbd
|
|
|
ci-image-save-v3-linux_arm64-3.11-main
Expired
|
1.86 GB |
sha256:3fa1940dab0434b92e9e451b4e5a5e65f6ff3178d54da23bb874f42767d336c6
|
|
|
ci-image-save-v3-linux_arm64-3.11-main
Expired
|
1.86 GB |
sha256:3fa1940dab0434b92e9e451b4e5a5e65f6ff3178d54da23bb874f42767d336c6
|
|
|
ci-image-save-v3-linux_arm64-3.12-main
Expired
|
1.86 GB |
sha256:a8fb014312e2ffa9f46c0e11c83a36b940e560261e4f6b539c132e3aa31c6c22
|
|
|
ci-image-save-v3-linux_arm64-3.13-main
Expired
|
1.85 GB |
sha256:f8b4cd185ee36ecf42353a1283bd4fa8592b73505da3b6da47ed02fc1885254c
|
|
|
ci-image-save-v3-linux_arm64-3.14-main
Expired
|
1.84 GB |
sha256:f4456e0d392b000147c8d8415010463ded64625658cbef334c0cc8471dc9a544
|
|
|
constraints-3.10
Expired
|
12.5 KB |
sha256:791bd210b7e48effe954f13727f7f738fe8c6d5ed650c1ef3ea33e2f705392f0
|
|
|
constraints-3.11
Expired
|
12.4 KB |
sha256:1abd96f512e665b2db9d20b81749f55456c6d09db1b8395e70996e4d31160170
|
|
|
constraints-3.12
Expired
|
12.4 KB |
sha256:9976dfc321f079fe84a4d11bd97f9027f5046dab5e9c52b08473342f5639acd7
|
|
|
constraints-3.13
Expired
|
12.4 KB |
sha256:de28ee58855ce0ce6122e419ae6db54e9b866fe797728a35c80492ee4238476d
|
|
|
constraints-3.14
Expired
|
12.2 KB |
sha256:7d581c345acd2003c36e088296525cee3a575b57d4a1ed2887b4f4d1dfad8c40
|
|
|
playwright-report-chromium
Expired
|
132 MB |
sha256:d6311171135e729a129e230904bed64806b08393fd30cbbf114c26094005c191
|
|
|
playwright-report-firefox
Expired
|
327 KB |
sha256:ea316c02e46faabbb271dc09446b1c23ea7252d3e8d4ba59c870f45622cb8c20
|
|
|
playwright-report-webkit
Expired
|
15.7 MB |
sha256:f3f8e283f00a8742427fd9630f6535f7b91bcbf107f56c117bf5b8cdfd9645ea
|
|
|
prod-image-save-v3-linux_arm64-3.10-main
Expired
|
613 MB |
sha256:b1b788055ebe9289f5c22c1c2b120102ac2b368aff270016ec9babb66ea000cb
|
|
|
prod-image-save-v3-linux_arm64-3.11-main
Expired
|
616 MB |
sha256:d1e9955ac948687755f3c9f88b3e256f13d5941ba0423191e14258cb692bdb48
|
|
|
prod-image-save-v3-linux_arm64-3.12-main
Expired
|
612 MB |
sha256:98bb90cb6642432bbe9645aaf5c53ca06c6456081e2b0710cb5d989471433446
|
|
|
prod-image-save-v3-linux_arm64-3.13-main
Expired
|
605 MB |
sha256:b0d8e154bb755ca1bbf60f07ebb49ab4da5a600b7ba052b0d2ccc31572a31e8b
|
|
|
prod-image-save-v3-linux_arm64-3.14-main
Expired
|
528 MB |
sha256:71474a94b6aada2b854ffb62feade0f331d413da2166a29904b378b220254fc7
|
|
|
prod-packages
Expired
|
8.17 MB |
sha256:210983bd18d1face2713ac1d28d346de6857bbc04595271a42c3322cd61496a7
|
|
|
slack-state-tests-main
Expired
|
591 Bytes |
sha256:53a11da65cd6e75820b9bd7c88332b2087f8c2e55a3d0c532237371ade01611d
|
|
|
test-warnings-core-API...CLI-All-LatestBoto-Postgres-postgres-14-3.10
Expired
|
54 KB |
sha256:3b883be41268ae6015797d5544c459e2a06053355c28d7431a2ef13a1a9ca37a
|
|
|
test-warnings-core-API...CLI-All-LowestDeps-sqlite-14-3.10
Expired
|
34.8 KB |
sha256:dca3be8ccc66e0924cc8fd1cebac4e8d1a9708b58b914027f514ea61b10b5479
|
|
|
test-warnings-core-API...CLI-All-LowestDeps-sqlite-14-3.11
Expired
|
34.8 KB |
sha256:7f8939eb0efa8dad0b0db48d58d7b7bc2c339e255895bd921b3546d4e7dd91e2
|
|
|
test-warnings-core-API...CLI-All-LowestDeps-sqlite-14-3.12
Expired
|
58 KB |
sha256:5d1b79c2c3fdbe522e2cb70fc2622676cd38563df1399b6767b50b5eb8739397
|
|
|
test-warnings-core-API...CLI-All-LowestDeps-sqlite-14-3.13
Expired
|
66.7 KB |
sha256:9b029142af87d80436adcee6de5707be87deb325c5da665b8f0444b706c64367
|
|
|
test-warnings-core-API...CLI-All-LowestDeps-sqlite-14-3.14
Expired
|
35.1 KB |
sha256:dd23161c6fb325b0ba738227b2f3a6a8e3b0302609923d51b1ad8dbd0094f1db
|
|
|
test-warnings-core-API...CLI-All-Pendulum2-Postgres-postgres-14-3.10
Expired
|
53.9 KB |
sha256:dd483530b349a41a590cb89444662c108ffad38132c3b3588bb5c17cd718c158
|
|
|
test-warnings-core-API...CLI-DB-LatestSQLAlchemy-Postgres-postgres-14-3.10
Expired
|
52.6 KB |
sha256:09ffe63526aefa9a3688ea4171545eb33e7284f6b8592601f71b9cadce487185
|
|
|
test-warnings-core-API...CLI-DB-MinSQLAlchemy-Postgres-postgres-14-3.10
Expired
|
52.6 KB |
sha256:d69cbee4d719e687ede7dd1d3f1b0c658a57c6c4ec5d01459a0c66348b4a0732
|
|
|
test-warnings-core-API...CLI-DB-Postgres-postgres-14-3.10
Expired
|
52.6 KB |
sha256:c3975414e1743c63c2451400ea1d3235da005341bc5360923bd8843adc934faf
|
|
|
test-warnings-core-API...CLI-DB-Postgres-postgres-15-3.11
Expired
|
52.6 KB |
sha256:032dc426260dbd9415d536c98a1bd73470c3b46994ad3948ac58a38a9d42d60c
|
|
|
test-warnings-core-API...CLI-DB-Postgres-postgres-16-3.12
Expired
|
48.8 KB |
sha256:4c1701eaf7a528147b26cb2ca90f25e07a88c0f78fe6ba23259b7876676386a6
|
|
|
test-warnings-core-API...CLI-DB-Postgres-postgres-17-3.13
Expired
|
48.7 KB |
sha256:0b1b00374ab4474ccfe04d93a1c30caecf6697e17e1e280fc25235c8f72beb50
|
|
|
test-warnings-core-API...CLI-DB-Postgres-postgres-18-3.14
Expired
|
48.4 KB |
sha256:1977b2f910f88a34b9dbb25ffb78a26b29bd44409afd2e32b055b25d68c87c0e
|
|
|
test-warnings-core-API...CLI-DB-Sqlite-sqlite--3.10
Expired
|
52.7 KB |
sha256:c6b17d53a84fa35b7e7f2b9210b817a4b24ba3f9fd428177594e8a272ffeba06
|
|
|
test-warnings-core-API...CLI-DB-Sqlite-sqlite--3.11
Expired
|
52.7 KB |
sha256:f9054e88f26feb48d5872974e8c4e2e2fb39dc8c8f87729b200a03df4454eb94
|
|
|
test-warnings-core-API...CLI-DB-Sqlite-sqlite--3.12
Expired
|
48.9 KB |
sha256:c9bcdafeadb4386d976db3b072c8c4370f746318d6a87ec355f0a4bb1d5bfdd9
|
|
|
test-warnings-core-API...CLI-DB-Sqlite-sqlite--3.13
Expired
|
48.8 KB |
sha256:11a1d7c98051cfb32c8feaade39d9ae63cabb68b05121493856c54d76d2aa8bc
|
|
|
test-warnings-core-API...CLI-DB-Sqlite-sqlite--3.14
Expired
|
48.5 KB |
sha256:043c6085c51c1e92cd2a0bb1524c9d4086e82e163fef9fa4b2ec52229d8c7f2d
|
|
|
test-warnings-core-API...CLI-Non-DB--sqlite--3.10
Expired
|
4.37 KB |
sha256:fbc4ee18233e99ab03aa0720bd6debf477492656f7a19d0d63f5e433ac6e3adf
|
|
|
test-warnings-core-API...CLI-Non-DB--sqlite--3.11
Expired
|
4.37 KB |
sha256:c3213096a84d81d8d124a1d3ed09669f27af188d299a78be5e4bf2a9e587af76
|
|
|
test-warnings-core-API...CLI-Non-DB--sqlite--3.12
Expired
|
2.58 KB |
sha256:96af66bc77de61ccae388fed93af5b388afc9fa3803c0d77994266fb87bc2a87
|
|
|
test-warnings-core-API...CLI-Non-DB--sqlite--3.13
Expired
|
2.54 KB |
sha256:c6cd73528de8a999298380e37c0aefe77f8f8ba34737ffffd1dce5ec18e01027
|
|
|
test-warnings-core-API...CLI-Non-DB--sqlite--3.14
Expired
|
2.52 KB |
sha256:4514b07c94b3828678b8f6fe87452282e5d3ca89e9773ef841796eaca40021f3
|
|
|
test-warnings-core-API...CLI-Quarantined-Postgres-postgres-14-3.10
Expired
|
468 Bytes |
sha256:ca77827f868552aa420f2806c7ff4712e07869918b0149d06a731cb91fbcee8f
|
|
|
test-warnings-core-Core...Serialization-All-LatestBoto-Postgres-postgres-14-3.10
Expired
|
9.81 KB |
sha256:f06c1f4fbf13730d6c29f617af278f3052cc351f62aac967b484ec19ae37c979
|
|
|
test-warnings-core-Core...Serialization-All-LowestDeps-sqlite-14-3.10
Expired
|
9.52 KB |
sha256:8ff5c479651846e6d7d1fb28da4df29e51820a9346618cf33837e0cd9b71eca1
|
|
|
test-warnings-core-Core...Serialization-All-LowestDeps-sqlite-14-3.11
Expired
|
9.49 KB |
sha256:46f9ac17432803d373a20b6f45185ccbde0e6788af69f18369e5df092edebc4e
|
|
|
test-warnings-core-Core...Serialization-All-LowestDeps-sqlite-14-3.12
Expired
|
10.6 KB |
sha256:534bac7bc606b7b7cc16b9e95937640fea202ac6bc4c04478be2410c17673edc
|
|
|
test-warnings-core-Core...Serialization-All-LowestDeps-sqlite-14-3.13
Expired
|
10.7 KB |
sha256:74a6b943926bbbd6e60838fda35595071dbb135c5538f4bf9a2b111b41921cce
|
|
|
test-warnings-core-Core...Serialization-All-LowestDeps-sqlite-14-3.14
Expired
|
10.2 KB |
sha256:5721ceeb556951d5214c90d25058467f0647e4300b738f3d1c9f394cf9af2bbc
|
|
|
test-warnings-core-Core...Serialization-All-Pendulum2-Postgres-postgres-14-3.10
Expired
|
16.2 KB |
sha256:72cefab2e138d8767f68f177fb7167c5a7aad5b914fa8b88f6fcb43c6ecfcf4e
|
|
|
test-warnings-core-Core...Serialization-DB-LatestSQLAlchemy-Postgres-postgres-14-3.10
Expired
|
8.27 KB |
sha256:b9a95b914469943c5c0e499aaefb27a4800044beed3dc7343ec6133ad2309d32
|
|
|
test-warnings-core-Core...Serialization-DB-MinSQLAlchemy-Postgres-postgres-14-3.10
Expired
|
8.28 KB |
sha256:de15a2fe328f0078bc8d5394d42ec67c0ba891f5d870e0a324704a308f33f7ea
|
|
|
test-warnings-core-Core...Serialization-DB-Postgres-postgres-14-3.10
Expired
|
8.24 KB |
sha256:d0156c18a29ea1ec7b9710b563e0aebcaab8bcf03702e147aa377035e1e31495
|
|
|
test-warnings-core-Core...Serialization-DB-Postgres-postgres-15-3.11
Expired
|
8.26 KB |
sha256:43b54b487a85feef84e5ce3885b7dadb7dc9f3fc47d1881c5fdfa7f5eca7ae3f
|
|
|
test-warnings-core-Core...Serialization-DB-Postgres-postgres-16-3.12
Expired
|
9.21 KB |
sha256:e445ebe74e32bb26e4ff15f11939c5275c9a97d00f12fa8781be797dd480126f
|
|
|
test-warnings-core-Core...Serialization-DB-Postgres-postgres-17-3.13
Expired
|
9.2 KB |
sha256:c9f0adf7676389e6fbb4e9a651f170d2facaa2ab1ebb9a0529f6a9f86b8b1080
|
|
|
test-warnings-core-Core...Serialization-DB-Postgres-postgres-18-3.14
Expired
|
8.83 KB |
sha256:97e36e221a581695ab5b4e4865aded89a8bdbbe99b6936536876fdce1ff5b072
|
|
|
test-warnings-core-Core...Serialization-DB-Sqlite-sqlite--3.10
Expired
|
8.45 KB |
sha256:e4782467e1f35780cc50adc24b3a3c7a097f47bcecb6ffcafd2da3463faf1775
|
|
|
test-warnings-core-Core...Serialization-DB-Sqlite-sqlite--3.11
Expired
|
8.43 KB |
sha256:e841bc761832ec1c778c210d58babc6e1aa1ad559227047fe22e7b99fe010651
|
|
|
test-warnings-core-Core...Serialization-DB-Sqlite-sqlite--3.12
Expired
|
9.38 KB |
sha256:eda9e05ea15f8aef05fc360ebe252bed2f18a6045842f52d4b4b5eaadedfcb75
|
|
|
test-warnings-core-Core...Serialization-DB-Sqlite-sqlite--3.13
Expired
|
9.37 KB |
sha256:1af8cb756b1fd24e0ee3b7781382904fbbc0ddad52ba423210ec896f0b0519c6
|
|
|
test-warnings-core-Core...Serialization-DB-Sqlite-sqlite--3.14
Expired
|
8.73 KB |
sha256:eee396cee95ee6abf3cf2aae334b672f95376e2d18f881832e9c06e43baf6e78
|
|
|
test-warnings-core-Core...Serialization-Non-DB--sqlite--3.10
Expired
|
2.39 KB |
sha256:9ebf73ef8f261cec56bdc025b49cd811e31fe7bfaebb9d0a18a51069a2932b57
|
|
|
test-warnings-core-Core...Serialization-Non-DB--sqlite--3.11
Expired
|
2.39 KB |
sha256:96c542ed0040d6ebe452ae31739146942b24ccf15661ec19043a92d0a70e9571
|
|
|
test-warnings-core-Core...Serialization-Non-DB--sqlite--3.12
Expired
|
2.38 KB |
sha256:c1c0d5cf2b779c3974d2898df0d7c6113652a4a1f0770c9ea74efd3b20f5ff02
|
|
|
test-warnings-core-Core...Serialization-Non-DB--sqlite--3.13
Expired
|
2.36 KB |
sha256:85f8629e7cf399c4a8c15e48e082ba0cf5965b5f98208d58447f9400e84f69a1
|
|
|
test-warnings-core-Core...Serialization-Non-DB--sqlite--3.14
Expired
|
2.36 KB |
sha256:bd0413fd68d3e4d0042526a80a7b481f8ce61628bdc3718ab85082392694bacf
|
|
|
test-warnings-core-Core...Serialization-Quarantined-Postgres-postgres-14-3.10
Expired
|
468 Bytes |
sha256:1834952b96a79d14f9377f3aa5a45cd945f47881fb43a143bfaf83dc2c384595
|
|
|
test-warnings-integration-providers-cassandra
Expired
|
815 Bytes |
sha256:1c65b70e1cc52b48c3aa60eec57577609b4d3de972842f7679c7b1dfbe9ccd4a
|
|
|
test-warnings-integration-providers-qdrant
Expired
|
629 Bytes |
sha256:788c770a2ac1b03e7caa0406012f556d256d9e0e6b2a044bad8511a99eec918a
|
|
|
test-warnings-providers--amazon,celer...standard-All-LatestBoto-Postgres-postgres-14-3.10
Expired
|
43.6 KB |
sha256:a1cd9159f9077b9419a78230dd07ea82a7b3c53a52cf6bf1d480699c90b3c212
|
|
|
test-warnings-providers--amazon,celer...standard-All-Pendulum2-Postgres-postgres-14-3.10
Expired
|
44.1 KB |
sha256:1f0057ebf7ffba6444475214717eea51aa4e207cb3d098eda063d7e02bdf5d12
|
|
|
test-warnings-providers--amazon,celer...standard-DB-LatestSQLAlchemy-Postgres-postgres-14-3.10
Expired
|
17.5 KB |
sha256:7a7f5015eeaae5b36f18f2816cac9612bb6b8e301a2feb9de1c32974626377c5
|
|
|
test-warnings-providers--amazon,celer...standard-DB-MinSQLAlchemy-Postgres-postgres-14-3.10
Expired
|
17.5 KB |
sha256:2ab11f0860f4962d6bf366e1cfedcd9c3775e77f4a1e2f64533a2e5b2726ed67
|
|
|
test-warnings-providers--amazon,celer...standard-DB-Postgres-postgres-14-3.10
Expired
|
17.5 KB |
sha256:e04d76684e31931f3ab7d5c2dcbf6c95e729cf1cbc217177f5bf06d190c7438e
|
|
|
test-warnings-providers--amazon,celer...standard-DB-Postgres-postgres-15-3.11
Expired
|
17.5 KB |
sha256:0a08a4983c32d5b356a911000130e2601948d5efa7d74523fbcfe7cb3c9e35da
|
|
|
test-warnings-providers--amazon,celer...standard-DB-Postgres-postgres-16-3.12
Expired
|
18.2 KB |
sha256:9c4f87fb19b9772eb6db33cb2cca303cb54320f6cfd8e0cc3bf56684d8586132
|
|
|
test-warnings-providers--amazon,celer...standard-DB-Postgres-postgres-17-3.13
Expired
|
18.2 KB |
sha256:aa31e159d556b20c33f38f9624edec66d59ce5b15201332b4e9fe00f96aad79a
|
|
|
test-warnings-providers--amazon,celer...standard-DB-Postgres-postgres-18-3.14
Expired
|
16.9 KB |
sha256:daad541ce7ce7426e1151426a3fbd026b4beca0730a5975bf68a34be458c0cad
|
|
|
test-warnings-providers--amazon,celer...standard-DB-Sqlite-sqlite--3.10
Expired
|
17.6 KB |
sha256:fdb85e82edec6b6ea3e2d62e4943610d2ad444f7cc89d61c8ad6a3f797071323
|
|
|
test-warnings-providers--amazon,celer...standard-DB-Sqlite-sqlite--3.11
Expired
|
17.6 KB |
sha256:d6ac3814d940fdbcd765d17382fda38ad4311214e8228f922b6ed4e4e8d62f19
|
|
|
test-warnings-providers--amazon,celer...standard-DB-Sqlite-sqlite--3.12
Expired
|
17.9 KB |
sha256:edbf75fac8ea5617f5cdb954070d82dd846ac20ec75c0e953510f3cb1d417ec0
|
|
|
test-warnings-providers--amazon,celer...standard-DB-Sqlite-sqlite--3.13
Expired
|
17.9 KB |
sha256:96fb5be6214274bda6451a46f6b5a5e3ffed065835df7842fc3f57f4c1e528a7
|
|
|
test-warnings-providers--amazon,celer...standard-DB-Sqlite-sqlite--3.14
Expired
|
17 KB |
sha256:c712f9b247bf9c0443f49327873efc33f43b42b41040f2745a930a5ca93bea38
|
|
|
test-warnings-providers--amazon,celer...standard-Non-DB--sqlite--3.10
Expired
|
29.2 KB |
sha256:e48909cfabe44dd5b2ab5bdc0f8ef7a8236f317fbbf87b1f76aff86a01f804f7
|
|
|
test-warnings-providers--amazon,celer...standard-Non-DB--sqlite--3.11
Expired
|
29.3 KB |
sha256:b708e2ce7c0c1d08b171ca4943697996b43cbe620ee1329c7eae5b6823222c9f
|
|
|
test-warnings-providers--amazon,celer...standard-Non-DB--sqlite--3.12
Expired
|
29.5 KB |
sha256:6b94ca5b9115fb07082f7d494520183e594ea7ac0e80ebc991cb2e1e4c9fcb56
|
|
|
test-warnings-providers--amazon,celer...standard-Non-DB--sqlite--3.13
Expired
|
30.8 KB |
sha256:7184b703fdf615a116faac4b19ee2ec8d413a76daf4eda196e87e6705e86b712
|
|
|
test-warnings-providers--amazon,celer...standard-Non-DB--sqlite--3.14
Expired
|
27.5 KB |
sha256:4868899340436b6d7bddc5859b740919a1ce1d84a657b596eef442e1668d6a4f
|
|
|
test-warnings-providers-airbyte...arangodb-All-LowestDeps-sqlite-14-3.10
Expired
|
19.5 KB |
sha256:300ad69e5f157cc5753ae56851347045c5bf020dcf7f35ff1ac64eb971258934
|
|
|
test-warnings-providers-airbyte...arangodb-All-LowestDeps-sqlite-14-3.11
Expired
|
19.4 KB |
sha256:bfdf47b3eb2501b37021650b56ed600f9b63f1f87418512183a2218ce91d3c78
|
|
|
test-warnings-providers-airbyte...arangodb-All-LowestDeps-sqlite-14-3.12
Expired
|
19 KB |
sha256:6c1e6dc53d8a856c12520f0ea07672904a15526de157cb299b475d9d5aae6770
|
|
|
test-warnings-providers-airbyte...arangodb-All-LowestDeps-sqlite-14-3.13
Expired
|
19.5 KB |
sha256:a234f9711523d1d8af05eeaf6fcc24ab46af42cebaf7034e7c7cc68e7cc2d61c
|
|
|
test-warnings-providers-airbyte...arangodb-All-LowestDeps-sqlite-14-3.14
Expired
|
18.9 KB |
sha256:fff72f63db99d31be07b5f71d318cae18dc4d707f7098757241681fdea38cf9d
|
|
|
test-warnings-providers-asana...exasol-All-LowestDeps-sqlite-14-3.10
Expired
|
16.8 KB |
sha256:2cb6c36df915cb8ce33d1da9d509b013b651d5681cd81166b5706bcc43f47ff7
|
|
|
test-warnings-providers-asana...exasol-All-LowestDeps-sqlite-14-3.11
Expired
|
16.8 KB |
sha256:88a1c8b51261b2d24ab6c2171fca04eafce5f6b3b4a6467a2fab7af0d397a169
|
|
|
test-warnings-providers-asana...exasol-All-LowestDeps-sqlite-14-3.12
Expired
|
18.1 KB |
sha256:61aa0614084cb31cc3447d00c58ade6e3a330a12ff7f571b2f587ef3fd531703
|
|
|
test-warnings-providers-asana...exasol-All-LowestDeps-sqlite-14-3.13
Expired
|
18.1 KB |
sha256:507c68b1468d1cf79e4822576a4fcf63159870159d8f558d7389dd62ff104d93
|
|
|
test-warnings-providers-asana...exasol-All-LowestDeps-sqlite-14-3.14
Expired
|
16.8 KB |
sha256:b13e403ff75367641da4922bc2aa066af505a9512d229a123301159519aa06da
|
|
|
test-warnings-providers-fab...mongo-All-LowestDeps-sqlite-14-3.10
Expired
|
13.2 KB |
sha256:2aecb62df8866ec17727a23d2d42ce43fa2c0dd8a1184ef22108ebbdea07f19c
|
|
|
test-warnings-providers-fab...mongo-All-LowestDeps-sqlite-14-3.11
Expired
|
13.1 KB |
sha256:ed195e4e830e442710e06a52fe2a360aa45c82022e3cf9d601293c43c656f902
|
|
|
test-warnings-providers-fab...mongo-All-LowestDeps-sqlite-14-3.12
Expired
|
20.7 KB |
sha256:27a6966dcaeb6d5ff7d2e8a9b4f5882554b33583007dd02a13fa10e8f6f9a85d
|
|
|
test-warnings-providers-fab...mongo-All-LowestDeps-sqlite-14-3.13
Expired
|
23 KB |
sha256:68d41322f1aa4cbb61fc9a0353318a55a9ebf14ec5c1cddb205cf538748f2e1c
|
|
|
test-warnings-providers-fab...mongo-All-LowestDeps-sqlite-14-3.14
Expired
|
13.6 KB |
sha256:a37002a32a057419f5752795174766806879b74f6248f633bbc184ab6857edf8
|
|
|
test-warnings-providers-mysql...samba-All-LowestDeps-sqlite-14-3.10
Expired
|
3.2 KB |
sha256:87d9cc434426af16d9e85d2381fd825368f60026ff893d76e0c3a20d8c5dd5e7
|
|
|
test-warnings-providers-mysql...samba-All-LowestDeps-sqlite-14-3.11
Expired
|
3.19 KB |
sha256:05c4c8a411d0480ef65fa2c29aeafce066830867b1503b15e6e1f5b9b64ff9b5
|
|
|
test-warnings-providers-mysql...samba-All-LowestDeps-sqlite-14-3.12
Expired
|
3.64 KB |
sha256:96b03c3c04e458551b3ad9f2bdc033f57294e3951e57a1afbec8b073ba667b4e
|
|
|
test-warnings-providers-mysql...samba-All-LowestDeps-sqlite-14-3.13
Expired
|
3.67 KB |
sha256:373b434bb76d5f231dc20d998d7cdb0905d9a95c2265748f2b01fc055d9ccd4c
|
|
|
test-warnings-providers-mysql...samba-All-LowestDeps-sqlite-14-3.14
Expired
|
3.21 KB |
sha256:92bf468c37bc5cb7c316a1a23161e68b41ac41b7969f4e63b21e3e36a0f3980e
|
|
|
test-warnings-providers-segment...zendesk-All-LowestDeps-sqlite-14-3.10
Expired
|
11.9 KB |
sha256:2daeba9bfaa64bca7cbabe6132cce67202787847098d81f13c2b60e26a7b140d
|
|
|
test-warnings-providers-segment...zendesk-All-LowestDeps-sqlite-14-3.11
Expired
|
11.9 KB |
sha256:29e043cae9c13245e3d9e66ae3306a917081861065ee87353ea5a6ff870e555d
|
|
|
test-warnings-providers-segment...zendesk-All-LowestDeps-sqlite-14-3.12
Expired
|
11.7 KB |
sha256:07af7cedaf5653f158dd7dfa29a6f780e234980ba846c3e86f2c076d62ef7cfb
|
|
|
test-warnings-providers-segment...zendesk-All-LowestDeps-sqlite-14-3.13
Expired
|
11.9 KB |
sha256:a9fb2c67b778541f2c4bbc68d36b26c79c56bafb461d8b3fe9285376d88714fa
|
|
|
test-warnings-providers-segment...zendesk-All-LowestDeps-sqlite-14-3.14
Expired
|
11.2 KB |
sha256:9590777bd56fc7b717aa38aa33cbbd99ed96f01c523a47a2530b4d13032049a1
|
|