Deadlines endpoints #25355
imrichardwuci-amd-arm.yml
on: pull_request
Matrix: Build CI images / build-ci-images
Matrix: Airflow CTL tests / distributions-tests
Basic tests
/
Breeze unit tests
1m 2s
Basic tests
/
Breeze integration tests
1m 18s
Basic tests
/
Scripts tests
26s
Basic tests
/
React UI tests
1m 28s
Basic tests
/
Check translation completeness
29s
Basic tests
/
Static checks: basic checks only
0s
Basic tests
/
Test git clone on Windows
19s
Basic tests
/
Upgrade checks
0s
Basic tests
/
Test Airflow release commands
0s
Basic tests
/
Test Airflow standalone commands
26s
Go SDK tests
37s
Platform: ARM
0s
Platform: AMD
4s
Verify release calendar
0s
Matrix: Generate constraints / generate-constraints-matrix
Matrix: MySQL tests: core / tests
Matrix: MySQL tests: providers / tests
Matrix: Non-DB tests: core / tests
Matrix: Non-DB tests: providers / tests
Matrix: Postgres tests: core / tests
Matrix: Postgres tests: providers / tests
Matrix: Sqlite tests: core / tests
Matrix: Sqlite tests: providers / tests
Matrix: Task SDK tests / distributions-tests
Matrix: Low dep tests:core / tests
Matrix: Low dep tests: providers / tests
Matrix: Additional CI image checks / Push Early Image Cache / push-ci-image-cache
Waiting for pending jobs
Matrix: Additional CI image checks / Push Early Image Cache / push-prod-image-cache
Waiting for pending jobs
Matrix: CI image checks / Build documentation
Matrix: CI image checks / MyPy checks
Matrix: provider distributions tests / prepare-install-verify-provider-distributions
Matrix: provider distributions tests / providers-compatibility-tests-matrix
Matrix: Helm tests / tests-helm
Matrix: Integration and System Tests / tests-core-integration
Matrix: Integration and System Tests / tests-providers-integration
Matrix: Special tests / Latest Boto test: core / tests
Matrix: Special tests / Latest Boto test: providers / tests
Matrix: Special tests / Latest SQLAlchemy test: providers / tests
Matrix: Special tests / Latest SQLAlchemy test: core / tests
Matrix: Special tests / Min SQLAlchemy test: providers / tests
Matrix: Special tests / Min SQLAlchemy test: core / tests
Matrix: Special tests / Pendulum2 test: core / tests
Matrix: Special tests / Pendulum2 test: providers / tests
Matrix: Special tests / Quarantined test: core / tests
Matrix: Special tests / Quarantined test: providers / tests
Matrix: tests-special / tests-system-core / tests
Additional CI image checks
/
Check that image builds quickly
11m 14s
CI image checks
/
Static checks
22m 58s
CI image checks
/
Test Python API client
5m 41s
Helm tests
/
Release Helm
1m 41s
Integration and System Tests
/
System Tests
5m 22s
Build PROD images
/
Build Airflow and provider distributions
3m 55s
CI image checks
/
Publish documentation and validate versions
6m 9s
Summarize warnings
Matrix: Build PROD images / build-prod-images
Matrix: Kubernetes tests / tests-kubernetes
Additional PROD image tests
/
...
/
Build Airflow and provider distributions
Additional PROD image tests
/
...
/
Build Airflow and provider distributions
Additional PROD image tests
/
Test examples of PROD image building
2m 38s
Additional PROD image tests
/
Docker Compose quick start with PROD image verifying
3m 45s
Additional PROD image tests
/
Task SDK integration tests with PROD image
3m 31s
Additional PROD image tests
/
...
/
Regular e2e test
10m 10s
Additional PROD image tests
/
...
/
Remote logging e2e test
5m 6s
Additional PROD image tests
/
...
/
Elasticsearch remote logging e2e test
4m 32s
Additional PROD image tests
/
...
/
XCom object storage backend e2e test
5m 4s
Additional PROD image tests
/
...
/
Chromium UI e2e tests
15m 9s
Additional PROD image tests
/
...
/
Firefox UI e2e tests
31m 4s
Additional PROD image tests
/
...
/
WebKit UI e2e tests
42m 20s
Additional PROD image tests
/
Airflow CTL integration tests with PROD image
5m 42s
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
Annotations
24 errors, 56 warnings, and 3 notices
|
provider distributions tests / Compat 2.11.1:P3.10:
Process completed with exit code 1.
|
|
provider distributions tests / Compat 3.1.8:P3.10:
Process completed with exit code 1.
|
|
provider distributions tests / Compat 3.0.6:P3.10:
Process completed with exit code 1.
|
|
[chromium] › tests/e2e/specs/dag-calendar-tab.spec.ts:124:3 › DAG Calendar Tab › verify hover shows correct run states:
airflow-core/src/airflow/ui/tests/e2e/pages/DagCalendarTab.ts#L73
1) [chromium] › tests/e2e/specs/dag-calendar-tab.spec.ts:124:3 › DAG Calendar Tab › verify hover shows correct run states
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:127:20
|
|
Special tests / Pendulum2 test: providers / All-prov:Pendulum2-Postgres:14:3.10:-amazon,celer...standard
Process completed with exit code 1.
|
|
Special tests / Latest Boto test: providers / All-prov:LatestBoto-Postgres:14:3.10:-amazon,celer...standard
Process completed with exit code 1.
|
|
[firefox] › tests/e2e/specs/requiredAction.spec.ts:43:3 › Verify Required Action page › Verify the actions list/table is displayed (or empty state if none):
airflow-core/src/airflow/ui/tests/e2e/specs/requiredAction.spec.ts#L29
4) [firefox] › tests/e2e/specs/requiredAction.spec.ts:43:3 › Verify Required Action page › Verify the actions list/table is displayed (or empty state if none)
"beforeAll" hook timeout of 400000ms exceeded.
27 | test.describe.configure({ mode: "serial" });
28 |
> 29 | test.beforeAll(async ({ browser }) => {
| ^
30 | test.setTimeout(400_000);
31 |
32 | const context = await browser.newContext({ storageState: AUTH_FILE });
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/requiredAction.spec.ts:29:8
|
|
[firefox] › tests/e2e/specs/home-dashboard.spec.ts:65:3 › Dashboard Metrics Display › should navigate to filtered DAGs list when clicking stats cards:
airflow-core/src/airflow/ui/tests/e2e/specs/home-dashboard.spec.ts#L69
3) [firefox] › tests/e2e/specs/home-dashboard.spec.ts:65:3 › Dashboard Metrics Display › should navigate to filtered DAGs list when clicking stats cards
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: locator.click: Test timeout of 30000ms exceeded.
Call log:
- waiting for locator('a[href*="paused=false"]')
67 | await homePage.waitForDashboardLoad();
68 |
> 69 | await homePage.activeDagsCard.click();
| ^
70 | await expect(homePage.page).toHaveURL(/paused=false/);
71 |
72 | await homePage.navigate();
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/home-dashboard.spec.ts:69:35
|
|
[firefox] › tests/e2e/specs/home-dashboard.spec.ts:65:3 › Dashboard Metrics Display › should navigate to filtered DAGs list when clicking stats cards:
airflow-core/src/airflow/ui/tests/e2e/specs/home-dashboard.spec.ts#L0
3) [firefox] › tests/e2e/specs/home-dashboard.spec.ts:65:3 › Dashboard Metrics Display › should navigate to filtered DAGs list when clicking stats cards
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Test timeout of 30000ms exceeded.
|
|
[firefox] › tests/e2e/specs/home-dashboard.spec.ts:65:3 › Dashboard Metrics Display › should navigate to filtered DAGs list when clicking stats cards:
airflow-core/src/airflow/ui/tests/e2e/pages/BasePage.ts#L56
3) [firefox] › tests/e2e/specs/home-dashboard.spec.ts:65:3 › Dashboard Metrics Display › should navigate to filtered DAGs list when clicking stats cards
Error: page.goto: Test timeout of 30000ms exceeded.
Call log:
- navigating to "http://localhost:8080/", waiting until "domcontentloaded"
at ../pages/BasePage.ts:56
54 |
55 | public async navigateTo(path: string): Promise<void> {
> 56 | await this.page.goto(path, {
| ^
57 | waitUntil: "domcontentloaded",
58 | });
59 | }
at HomePage.navigateTo (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/BasePage.ts:56:21)
at HomePage.navigate (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/HomePage.ts:116:16)
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/home-dashboard.spec.ts:66:20
|
|
[firefox] › tests/e2e/specs/home-dashboard.spec.ts:65:3 › Dashboard Metrics Display › should navigate to filtered DAGs list when clicking stats cards:
airflow-core/src/airflow/ui/tests/e2e/specs/home-dashboard.spec.ts#L0
3) [firefox] › tests/e2e/specs/home-dashboard.spec.ts:65:3 › Dashboard Metrics Display › should navigate to filtered DAGs list when clicking stats cards
Test timeout of 30000ms exceeded.
|
|
[firefox] › tests/e2e/specs/events-page.spec.ts:126:3 › Events with Generated Data › verify filter by DAG ID:
airflow-core/src/airflow/ui/tests/e2e/specs/events-page.spec.ts#L145
2) [firefox] › tests/e2e/specs/events-page.spec.ts:126:3 › Events with Generated Data › verify filter by DAG ID
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timeout 20000ms exceeded while waiting on the predicate
143 | expect(dagIdText?.toLowerCase()).toContain(testDagId.toLowerCase());
144 | }
> 145 | }).toPass({ timeout: 20_000 });
| ^
146 | });
147 | });
148 |
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/events-page.spec.ts:145:8
|
|
[firefox] › tests/e2e/specs/events-page.spec.ts:126:3 › Events with Generated Data › verify filter by DAG ID:
airflow-core/src/airflow/ui/tests/e2e/specs/events-page.spec.ts#L145
2) [firefox] › tests/e2e/specs/events-page.spec.ts:126:3 › Events with Generated Data › verify filter by DAG ID
Error: expect(received).toContain(expected) // indexOf
Expected substring: "example_bash_operator"
Received string: ""
Call Log:
- Timeout 20000ms exceeded while waiting on the predicate
143 | expect(dagIdText?.toLowerCase()).toContain(testDagId.toLowerCase());
144 | }
> 145 | }).toPass({ timeout: 20_000 });
| ^
146 | });
147 | });
148 |
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/events-page.spec.ts:145:8
|
|
[firefox] › tests/e2e/specs/dag-code-tab.spec.ts:42:3 › DAG Code Tab › Verify code is scrollable for long files:
airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts#L42
1) [firefox] › tests/e2e/specs/dag-code-tab.spec.ts:42:3 › DAG Code Tab › Verify code is scrollable for long files
Error: expect(locator).toBeVisible() failed
Locator: locator('[role="code"]')
Expected: visible
Timeout: 5000ms
Error: element(s) not found
Call log:
- Expect "toBeVisible" with timeout 5000ms
- waiting for locator('[role="code"]')
Call Log:
- Test timeout of 60000ms exceeded
at ../pages/DagCodePage.ts:42
40 | await this.navigateTo(`/dags/${dagId}/code`);
41 | await expect(this.editorContainer).toBeVisible({ timeout: 5000 });
> 42 | }).toPass({ intervals: [2000], timeout: 60_000 });
| ^
43 | await this.waitForCodeReady();
44 | }
45 |
at DagCodePage.navigateToCodeTab (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts:42:8)
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/dag-code-tab.spec.ts:31:20
|
|
[webkit] › tests/e2e/specs/dag-code-tab.spec.ts:42:3 › DAG Code Tab › Verify code is scrollable for long files:
airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts#L42
4) [webkit] › tests/e2e/specs/dag-code-tab.spec.ts:42:3 › DAG Code Tab › Verify code is scrollable for long files
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: Test timeout of 60000ms exceeded
at ../pages/DagCodePage.ts:42
40 | await this.navigateTo(`/dags/${dagId}/code`);
41 | await expect(this.editorContainer).toBeVisible({ timeout: 5000 });
> 42 | }).toPass({ intervals: [2000], timeout: 60_000 });
| ^
43 | await this.waitForCodeReady();
44 | }
45 |
at DagCodePage.navigateToCodeTab (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts:42:8)
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/dag-code-tab.spec.ts:31:20
|
|
[webkit] › tests/e2e/specs/dag-code-tab.spec.ts:42:3 › DAG Code Tab › Verify code is scrollable for long files:
airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts#L42
4) [webkit] › tests/e2e/specs/dag-code-tab.spec.ts:42:3 › DAG Code Tab › Verify code is scrollable for long files
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: Test timeout of 60000ms exceeded
at ../pages/DagCodePage.ts:42
40 | await this.navigateTo(`/dags/${dagId}/code`);
41 | await expect(this.editorContainer).toBeVisible({ timeout: 5000 });
> 42 | }).toPass({ intervals: [2000], timeout: 60_000 });
| ^
43 | await this.waitForCodeReady();
44 | }
45 |
at DagCodePage.navigateToCodeTab (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts:42:8)
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/dag-code-tab.spec.ts:31:20
|
|
[webkit] › tests/e2e/specs/dag-code-tab.spec.ts:42:3 › DAG Code Tab › Verify code is scrollable for long files:
airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts#L42
4) [webkit] › tests/e2e/specs/dag-code-tab.spec.ts:42:3 › DAG Code Tab › Verify code is scrollable for long files
Error: expect(locator).toBeVisible() failed
Locator: locator('[role="code"]')
Expected: visible
Received: hidden
Timeout: 5000ms
Call log:
- Expect "toBeVisible" with timeout 5000ms
- waiting for locator('[role="code"]')
- locator resolved to <div role="code" data-uri="inmemory://model/1" class="monaco-editor no-minimap-shadow enable-user-select mac showUnused showDeprecated vs">…</div>
- unexpected value "hidden"
Call Log:
- Test timeout of 60000ms exceeded
at ../pages/DagCodePage.ts:42
40 | await this.navigateTo(`/dags/${dagId}/code`);
41 | await expect(this.editorContainer).toBeVisible({ timeout: 5000 });
> 42 | }).toPass({ intervals: [2000], timeout: 60_000 });
| ^
43 | await this.waitForCodeReady();
44 | }
45 |
at DagCodePage.navigateToCodeTab (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts:42:8)
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/dag-code-tab.spec.ts:31:20
|
|
[webkit] › tests/e2e/specs/dag-code-tab.spec.ts:38:3 › DAG Code Tab › Verify syntax highlighting is applied:
airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts#L42
3) [webkit] › tests/e2e/specs/dag-code-tab.spec.ts:38:3 › DAG Code Tab › Verify syntax highlighting is applied
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: Test timeout of 60000ms exceeded
at ../pages/DagCodePage.ts:42
40 | await this.navigateTo(`/dags/${dagId}/code`);
41 | await expect(this.editorContainer).toBeVisible({ timeout: 5000 });
> 42 | }).toPass({ intervals: [2000], timeout: 60_000 });
| ^
43 | await this.waitForCodeReady();
44 | }
45 |
at DagCodePage.navigateToCodeTab (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts:42:8)
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/dag-code-tab.spec.ts:31:20
|
|
[webkit] › tests/e2e/specs/dag-code-tab.spec.ts:38:3 › DAG Code Tab › Verify syntax highlighting is applied:
airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts#L42
3) [webkit] › tests/e2e/specs/dag-code-tab.spec.ts:38:3 › DAG Code Tab › Verify syntax highlighting is applied
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: Test timeout of 60000ms exceeded
at ../pages/DagCodePage.ts:42
40 | await this.navigateTo(`/dags/${dagId}/code`);
41 | await expect(this.editorContainer).toBeVisible({ timeout: 5000 });
> 42 | }).toPass({ intervals: [2000], timeout: 60_000 });
| ^
43 | await this.waitForCodeReady();
44 | }
45 |
at DagCodePage.navigateToCodeTab (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts:42:8)
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/dag-code-tab.spec.ts:31:20
|
|
[webkit] › tests/e2e/specs/dag-code-tab.spec.ts:38:3 › DAG Code Tab › Verify syntax highlighting is applied:
airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts#L42
3) [webkit] › tests/e2e/specs/dag-code-tab.spec.ts:38:3 › DAG Code Tab › Verify syntax highlighting is applied
Error: expect(locator).toBeVisible() failed
Locator: locator('[role="code"]')
Expected: visible
Timeout: 5000ms
Error: element(s) not found
Call log:
- Expect "toBeVisible" with timeout 5000ms
- waiting for locator('[role="code"]')
Call Log:
- Test timeout of 60000ms exceeded
at ../pages/DagCodePage.ts:42
40 | await this.navigateTo(`/dags/${dagId}/code`);
41 | await expect(this.editorContainer).toBeVisible({ timeout: 5000 });
> 42 | }).toPass({ intervals: [2000], timeout: 60_000 });
| ^
43 | await this.waitForCodeReady();
44 | }
45 |
at DagCodePage.navigateToCodeTab (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts:42:8)
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/dag-code-tab.spec.ts:31:20
|
|
[webkit] › tests/e2e/specs/dag-code-tab.spec.ts:34:3 › DAG Code Tab › Verify DAG source code is displayed:
airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts#L42
2) [webkit] › tests/e2e/specs/dag-code-tab.spec.ts:34:3 › DAG Code Tab › Verify DAG source code is displayed
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: Test timeout of 60000ms exceeded
at ../pages/DagCodePage.ts:42
40 | await this.navigateTo(`/dags/${dagId}/code`);
41 | await expect(this.editorContainer).toBeVisible({ timeout: 5000 });
> 42 | }).toPass({ intervals: [2000], timeout: 60_000 });
| ^
43 | await this.waitForCodeReady();
44 | }
45 |
at DagCodePage.navigateToCodeTab (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts:42:8)
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/dag-code-tab.spec.ts:31:20
|
|
[webkit] › tests/e2e/specs/dag-code-tab.spec.ts:34:3 › DAG Code Tab › Verify DAG source code is displayed:
airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts#L42
2) [webkit] › tests/e2e/specs/dag-code-tab.spec.ts:34:3 › DAG Code Tab › Verify DAG source code is displayed
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: Test timeout of 60000ms exceeded
at ../pages/DagCodePage.ts:42
40 | await this.navigateTo(`/dags/${dagId}/code`);
41 | await expect(this.editorContainer).toBeVisible({ timeout: 5000 });
> 42 | }).toPass({ intervals: [2000], timeout: 60_000 });
| ^
43 | await this.waitForCodeReady();
44 | }
45 |
at DagCodePage.navigateToCodeTab (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts:42:8)
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/dag-code-tab.spec.ts:31:20
|
|
[webkit] › tests/e2e/specs/dag-code-tab.spec.ts:34:3 › DAG Code Tab › Verify DAG source code is displayed:
airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts#L42
2) [webkit] › tests/e2e/specs/dag-code-tab.spec.ts:34:3 › DAG Code Tab › Verify DAG source code is displayed
Error: expect(locator).toBeVisible() failed
Locator: locator('[role="code"]')
Expected: visible
Timeout: 5000ms
Error: element(s) not found
Call log:
- Expect "toBeVisible" with timeout 5000ms
- waiting for locator('[role="code"]')
Call Log:
- Test timeout of 60000ms exceeded
at ../pages/DagCodePage.ts:42
40 | await this.navigateTo(`/dags/${dagId}/code`);
41 | await expect(this.editorContainer).toBeVisible({ timeout: 5000 });
> 42 | }).toPass({ intervals: [2000], timeout: 60_000 });
| ^
43 | await this.waitForCodeReady();
44 | }
45 |
at DagCodePage.navigateToCodeTab (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/DagCodePage.ts:42:8)
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/dag-code-tab.spec.ts:31:20
|
|
[webkit] › tests/e2e/specs/backfill.spec.ts:89:7 › Backfill › Backfill creation and validation › verify backfill with 'Missing and Errored Runs' behavior:
airflow-core/src/airflow/ui/tests/e2e/pages/BackfillPage.ts#L280
1) [webkit] › tests/e2e/specs/backfill.spec.ts:89:7 › Backfill › Backfill creation and validation › verify backfill with 'Missing and Errored Runs' behavior
Error: Backfill row with dates 2020-03-01T00:00:00Z ~ 2020-03-04T00:00:00Z not found in table
expect(received).toBeTruthy()
Received: false
Call Log:
- Test timeout of 120000ms exceeded
at ../pages/BackfillPage.ts:280
278 | let foundColumnMap: Map<string, number> | undefined;
279 |
> 280 | await expect
| ^
281 | .poll(
282 | async () => {
283 | try {
at BackfillPage.findBackfillRowByDateRange (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/BackfillPage.ts:280:5)
at BackfillPage.getBackfillDetailsByDateRange (/home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/pages/BackfillPage.ts:343:32)
at /home/runner/work/airflow/airflow/airflow-core/src/airflow/ui/tests/e2e/specs/backfill.spec.ts:94:25
|
|
Basic tests / React UI tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build CI images / Build CI linux/amd64 image 3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Integration and System Tests / Integration: providers redis
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Integration and System Tests / Integration: 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 pinot
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Integration and System Tests / Integration: providers elasticsearch
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Integration and System Tests / Integration: providers trino
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Integration and System Tests / Integration core kerberos
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Integration and System Tests / Integration: providers 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/
|
|
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/
|
|
Non-DB tests: core / Non-DB-core::3.10:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Integration and System Tests / Integration 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/
|
|
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/
|
|
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.10:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Integration and System Tests / Integration: providers drill
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Special tests / Quarantined test: core / Qrnt-core:Postgres:14:3.10:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Integration and System Tests / Integration: providers qdrant
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Special tests / System test: / System-core:SystemTest:14:3.10: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 / 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/
|
|
Integration and System Tests / Integration: providers tinkerpop
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Special tests / Quarantined test: providers / Qrnt-prov:Postgres:14:3.10:-amazon,celer...standard
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Integration and System Tests / Integration: providers ydb
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Integration and System Tests / Integration 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/
|
|
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/
|
|
Low dep tests: providers / All-prov:LowestDeps:14:3.10:mysql...samba
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Low dep tests: providers / All-prov:LowestDeps:14:3.10:asana...exasol
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Non-DB tests: providers / Non-DB-prov::3.10:-amazon,celer...standard
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Low dep tests: providers / All-prov:LowestDeps:14:3.10: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:airbyte...arangodb
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
CI image checks / Static checks
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build PROD images / Build PROD Regular image 3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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/
|
|
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/
|
|
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/
|
|
Special tests / Latest SQLAlchemy test: core / DB-core:LatestSQLAlchemy-Postgres:14:3.10:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Special tests / Pendulum2 test: core / All-core:Pendulum2-Postgres:14:3.10:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Special tests / 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 Boto test: core / All-core:LatestBoto-Postgres:14:3.10:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Low dep tests:core / All-core:LowestDeps:14:3.10:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Sqlite tests: core / DB-core:Sqlite:3.10:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Special tests / Latest SQLAlchemy test: core / DB-core:LatestSQLAlchemy-Postgres:14:3.10:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Postgres tests: core / DB-core:Postgres:14:3.10:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Special tests / Min SQLAlchemy test: core / DB-core:MinSQLAlchemy-Postgres:14:3.10:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Special tests / Pendulum2 test: core / All-core:Pendulum2-Postgres:14:3.10:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MySQL tests: core / DB-core:MySQL:8.0:3.10:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Postgres tests: core / DB-core:Postgres:14:3.10:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MySQL tests: core / DB-core:MySQL:8.0:3.10:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Low dep tests: providers / All-prov:LowestDeps:14:3.10:segment...zendesk
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Sqlite tests: providers / DB-prov:Sqlite:3.10:-amazon,celer...standard
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Special tests / 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/
|
|
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/
|
|
MySQL tests: providers / DB-prov:MySQL:8.0:3.10:-amazon,celer...standard
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Special tests / 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/
|
|
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/
|
|
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/
|
|
🎭 Playwright Run Summary
1 flaky
[chromium] › tests/e2e/specs/dag-calendar-tab.spec.ts:124:3 › DAG Calendar Tab › verify hover shows correct run states
1 skipped
86 passed (10.7m)
|
|
🎭 Playwright Run Summary
4 flaky
[firefox] › tests/e2e/specs/dag-code-tab.spec.ts:42:3 › DAG Code Tab › Verify code is scrollable for long files
[firefox] › tests/e2e/specs/events-page.spec.ts:126:3 › Events with Generated Data › verify filter by DAG ID
[firefox] › tests/e2e/specs/home-dashboard.spec.ts:65:3 › Dashboard Metrics Display › should navigate to filtered DAGs list when clicking stats cards
[firefox] › tests/e2e/specs/requiredAction.spec.ts:43:3 › Verify Required Action page › Verify the actions list/table is displayed (or empty state if none)
1 skipped
83 passed (26.5m)
|
|
🎭 Playwright Run Summary
14 failed
[webkit] › tests/e2e/specs/backfill.spec.ts:89:7 › Backfill › Backfill creation and validation › verify backfill with 'Missing and Errored Runs' behavior
[webkit] › tests/e2e/specs/dag-code-tab.spec.ts:34:3 › DAG Code Tab › Verify DAG source code is displayed
[webkit] › tests/e2e/specs/dag-code-tab.spec.ts:38:3 › DAG Code Tab › Verify syntax highlighting is applied
[webkit] › tests/e2e/specs/dag-code-tab.spec.ts:42:3 › DAG Code Tab › Verify code is scrollable for long files
[webkit] › tests/e2e/specs/dags-list.spec.ts:31:3 › Dag Trigger Workflow › should successfully trigger a Dag run
[webkit] › tests/e2e/specs/dags-list.spec.ts:166:3 › Dags Status Filtering › should display status filter buttons
[webkit] › tests/e2e/specs/events-page.spec.ts:31:3 › Events Page › verify events page displays correctly
[webkit] › tests/e2e/specs/home-dashboard.spec.ts:65:3 › Dashboard Metrics Display › should navigate to filtered DAGs list when clicking stats cards
[webkit] › tests/e2e/specs/home-dashboard.spec.ts:79:3 › Dashboard Metrics Display › should display welcome heading on dashboard
[webkit] › tests/e2e/specs/home-dashboard.spec.ts:115:3 › Dashboard Metrics Display › should display historical metrics section with recent runs
[webkit] › tests/e2e/specs/requiredAction.spec.ts:43:3 › Verify Required Action page › Verify the actions list/table is displayed (or empty state if none)
[webkit] › tests/e2e/specs/task-instances.spec.ts:142:3 › Task Instances Page › verify filtering by failed state
[webkit] › tests/e2e/specs/xcoms.spec.ts:68:3 › XComs Page › verify XComs table renders ────────
[webkit] › tests/e2e/specs/xcoms.spec.ts:88:3 › XComs Page › verify expand/collapse functionality
7 flaky
[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-audit-log.spec.ts:78:3 › DAG Audit Log › verify audit log entries display valid data
[webkit] › tests/e2e/specs/dags-list.spec.ts:51:3 › Dag Details Tab › should successfully verify details tab
[webkit] › tests/e2e/specs/dags-list.spec.ts:74:3 › Dags List Display › should display Dag links correctly
[webkit] › tests/e2e/specs/events-page.spec.ts:39:3 › Events Page › verify search input is visible
[webkit] › tests/e2e/specs/events-page.spec.ts:94:3 › Events with Generated Data › verify audit log entries display valid data
[webkit] › tests/e2e/specs/home-dashboard.spec.ts:54:3 › Dashboard Metrics Display › should display health status badges
1 skipped
11 did not run
55 passed (38.3m)
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
Helm artifacts
Expired
|
479 KB |
sha256:8db3fa3e413b53ac44764cf0f880fd236d8c51d516123b34ae5c4526f75d26a7
|
|
|
airflow-docs
Expired
|
305 MB |
sha256:36783accdac0ce701b6223e2da3c146aa75c6e34a1057289a3a7b06722aa4c47
|
|
|
airflow-logs-providers--amazon,celer...standard-All-LatestBoto-Postgres-postgres-14-3.10
Expired
|
644 Bytes |
sha256:d0b8ea8932d39deabe0284d3d116abe764a67e764192ced294cd19102f28b0f5
|
|
|
airflow-logs-providers--amazon,celer...standard-All-Pendulum2-Postgres-postgres-14-3.10
Expired
|
653 Bytes |
sha256:d9e13ea5bd76a8afbe0207e3bdd2d1c4d595cc4acf2998e4f8b19360e6b8d903
|
|
|
cache-prek-v9-linux_amd64-python3.10.20-uv0.10.12-85d69a8464bb09f130ebd8d14d64ead3f2f18d79e8e26aa6ba2489811c14d65d-62583_merge
Expired
|
257 MB |
sha256:e00d6fda5a8970f02eaadb5c4d92574d1d430ccdaf02bfde6eb2024ee8c9438d
|
|
|
cache-ui-node-modules-v1-Linux--62583_merge
Expired
|
49.8 MB |
sha256:6162faa05b01838c89e90ef5302477378893c25cd282ba07079dd3eabea870b9
|
|
|
ci-image-save-v3-linux_amd64-3.10-62583_merge
Expired
|
2.09 GB |
sha256:63c9ceefd0c0457f186963d21b8d422b66fc3b75dff54f13004002abf7efb756
|
|
|
constraints-3.10
Expired
|
13.2 KB |
sha256:c8eab8dacb9003b0f5f1f4bbc4b5c1c1071af9e707cd8eb262dd5231b3e85f14
|
|
|
container-logs-providers--amazon,celer...standard-All-LatestBoto-Postgres-postgres-14-3.10
Expired
|
1.49 KB |
sha256:41c24058aa0c64b6f7dce129bcca9960f3c888064f71ecaba4f9dd306f0b1c28
|
|
|
container-logs-providers--amazon,celer...standard-All-Pendulum2-Postgres-postgres-14-3.10
Expired
|
1.5 KB |
sha256:f3ba32193979526543f4d876c4b28003ee79d9b2099f8672a37e97d7633bd55e
|
|
|
e2e-test-logs-basic
Expired
|
278 KB |
sha256:3ee115a31b81f18c6abcedea7111e0c7c48be479d24ba02a96bd35201d186cbe
|
|
|
e2e-test-logs-remote_log
Expired
|
22.2 KB |
sha256:02b3c7458283cebf1ca5082eea82377d6107f2d911d46ba5fd7a434e99c9e037
|
|
|
e2e-test-logs-remote_log_elasticsearch
Expired
|
28.2 KB |
sha256:f88d58286090ae7d08be20d712d8a7695cb6c973178335fb24023a0faa79a252
|
|
|
e2e-test-logs-xcom_object_storage
Expired
|
30.4 KB |
sha256:6ade794f058668df188e261be9e417002f5a2ced836d0c6f971f493c50bd7557
|
|
|
playwright-report-chromium
Expired
|
6.84 MB |
sha256:75a0261994175eb6f217912270e01b31311c343835905699198d4b8e4861822f
|
|
|
playwright-report-firefox
Expired
|
210 MB |
sha256:7ec350acfbf80b9170554284056baa5cf451e39ca51bdf5bd853ac7f469c235b
|
|
|
playwright-report-webkit
Expired
|
68.9 MB |
sha256:b51d44b53754ba8f7a280512f81d02b22384487c06568ae1fac400d3144e69b2
|
|
|
prod-image-save-v3-linux_amd64-3.10-62583_merge
Expired
|
627 MB |
sha256:43306b4d5fd62aa670c666536d5b6e99b70a8aca0e0c3ae13eb85bbcd4627075
|
|
|
prod-packages
Expired
|
8.19 MB |
sha256:71f0887f91cd7790fdd7b3980f5763e73a1da8a6768a0a26301ee8393a794bd6
|
|
|
test-warnings-core-API...CLI-All-LatestBoto-Postgres-postgres-14-3.10
Expired
|
56.1 KB |
sha256:2d47584d9338cc44c79f40f41c8e6185bc43332b6743a245917aab6b81dd7fef
|
|
|
test-warnings-core-API...CLI-All-LowestDeps-sqlite-14-3.10
Expired
|
35.3 KB |
sha256:6672369fe4ec64f0d503db0171d7c36214658575aaaa5651737f931bb560e460
|
|
|
test-warnings-core-API...CLI-All-Pendulum2-Postgres-postgres-14-3.10
Expired
|
56 KB |
sha256:6737c994241dfaf4c12afd482a7ef927f6c3ebae9edc5417dfa3648704ae3c6f
|
|
|
test-warnings-core-API...CLI-DB-LatestSQLAlchemy-Postgres-postgres-14-3.10
Expired
|
54.7 KB |
sha256:8c0bee028f4ea9a2e32eed547b1a057da487bb9508d7ed4f79c431203297c6b9
|
|
|
test-warnings-core-API...CLI-DB-MinSQLAlchemy-Postgres-postgres-14-3.10
Expired
|
54.7 KB |
sha256:a815946a1ad2610c66bfe2d2b03621f3d55a600373ab5e90ea923d94efb6aa10
|
|
|
test-warnings-core-API...CLI-DB-MySQL-mysql-8.0-3.10
Expired
|
58.2 KB |
sha256:1e438ed7c700b024795cfc5e817964010b8b189c5a51f36b5df86ddae75ca113
|
|
|
test-warnings-core-API...CLI-DB-Postgres-postgres-14-3.10
Expired
|
54.7 KB |
sha256:1c4dbb27fa5d3e0d904c3139b6dd1e34c9d11c3591321b7226db6500a734a12c
|
|
|
test-warnings-core-API...CLI-DB-Sqlite-sqlite--3.10
Expired
|
54.8 KB |
sha256:e04fb5a78827d341355c9324f64d8ac3c5d6a72c482c2814c225ffa950128f48
|
|
|
test-warnings-core-API...CLI-Non-DB--sqlite--3.10
Expired
|
4.88 KB |
sha256:dfa3d690ff93b06500f7dd9c001eb3ec024116f3caee4eaac0105998f4baf8e7
|
|
|
test-warnings-core-API...CLI-Quarantined-Postgres-postgres-14-3.10
Expired
|
468 Bytes |
sha256:126e5f0042fd0c9fad5b2c65351a241e0f542a40c7fa4315306fa28b90e0974b
|
|
|
test-warnings-core-Core...Serialization-All-LatestBoto-Postgres-postgres-14-3.10
Expired
|
9.8 KB |
sha256:4c3ec96e3b00c9924942a1531e5403cf29b1868f526b24fcdb4471ac73803c29
|
|
|
test-warnings-core-Core...Serialization-All-LowestDeps-sqlite-14-3.10
Expired
|
9.54 KB |
sha256:29f9b5e8f64b8df671cb2fcf24e13e85c95dc999aece42826f5205dca1be8b1b
|
|
|
test-warnings-core-Core...Serialization-All-Pendulum2-Postgres-postgres-14-3.10
Expired
|
17.2 KB |
sha256:a4885873bf8c4b73f737c62b37f026dfcf9bf7f9ed4ca043fe7effd298489626
|
|
|
test-warnings-core-Core...Serialization-DB-LatestSQLAlchemy-Postgres-postgres-14-3.10
Expired
|
8.29 KB |
sha256:cd191f075937d7d549a2572e654ba04fcc92fe3dba8fbf010469156ead350c21
|
|
|
test-warnings-core-Core...Serialization-DB-MinSQLAlchemy-Postgres-postgres-14-3.10
Expired
|
8.29 KB |
sha256:f314489ea4e7c212151146a5ccaacd610baa6ddc0648961669e820c0bef9d18a
|
|
|
test-warnings-core-Core...Serialization-DB-MySQL-mysql-8.0-3.10
Expired
|
10.7 KB |
sha256:2a611eded83f640f0c773ef33048318249b1aeea94e3dfc90dbbe4be2d7be639
|
|
|
test-warnings-core-Core...Serialization-DB-Postgres-postgres-14-3.10
Expired
|
8.27 KB |
sha256:734104f664763da94614eacb95bc24e3868dbf892d9538f7d4d04eb4daa969a6
|
|
|
test-warnings-core-Core...Serialization-DB-Sqlite-sqlite--3.10
Expired
|
8.46 KB |
sha256:662d33489eded6192241025924feaf4ac23b29e3f0da1f7ac0c3edd9cbe24375
|
|
|
test-warnings-core-Core...Serialization-Non-DB--sqlite--3.10
Expired
|
2.39 KB |
sha256:d912035e8540cb6f60cd943957cc0f2197d12bcc5de439b7b4c998e702d0007f
|
|
|
test-warnings-core-Core...Serialization-Quarantined-Postgres-postgres-14-3.10
Expired
|
468 Bytes |
sha256:498e01bf465fa16a6800360b934932a1c8bf18782cc35805613799f06132c8fd
|
|
|
test-warnings-integration-providers-cassandra
Expired
|
815 Bytes |
sha256:3a233d823f16a97b68642139d39cf05b55df6bd93aa1b75165a4e7f72c9cacf2
|
|
|
test-warnings-integration-providers-qdrant
Expired
|
629 Bytes |
sha256:5840fa8f572721373f610dd5e4ed4e6b74db020c5c30e37524bfc2dd1de9aba5
|
|
|
test-warnings-integration-providers-trino
Expired
|
511 Bytes |
sha256:5a61d7eca3951ae479e9e427eef822d295a772a592c94400a3746d5e1092eedf
|
|
|
test-warnings-providers--amazon,celer...standard-DB-LatestSQLAlchemy-Postgres-postgres-14-3.10
Expired
|
17.8 KB |
sha256:8b9210c70dd859bccd5bf76f2669bfb2e767beeb92c4d5ed58d5fb611f41f67f
|
|
|
test-warnings-providers--amazon,celer...standard-DB-MinSQLAlchemy-Postgres-postgres-14-3.10
Expired
|
17.8 KB |
sha256:07b94e21f37c8add1bccaf9be16c7b78b6c7eaa8acf6e1ef316ae5e3a8cd2de8
|
|
|
test-warnings-providers--amazon,celer...standard-DB-MySQL-mysql-8.0-3.10
Expired
|
17.9 KB |
sha256:d489b1a93932c1a6d93f66d8dcc6b9141365eb3bb9a90b4cca6835cfea392ff4
|
|
|
test-warnings-providers--amazon,celer...standard-DB-Postgres-postgres-14-3.10
Expired
|
17.8 KB |
sha256:0c98489514df6885549f47eb38eebf3911ca9683700373384e1e83f398680ac8
|
|
|
test-warnings-providers--amazon,celer...standard-DB-Sqlite-sqlite--3.10
Expired
|
18 KB |
sha256:73d32a184569a2137b0f28b5aa2d4f0383eebbcba349347a9fd436154147029f
|
|
|
test-warnings-providers--amazon,celer...standard-Non-DB--sqlite--3.10
Expired
|
30.3 KB |
sha256:453435bf83950d09140ceac9628a3ee561f05efdb04f569dcbf2097ff6d39449
|
|
|
test-warnings-providers-airbyte...arangodb-All-LowestDeps-sqlite-14-3.10
Expired
|
19.4 KB |
sha256:af64f50fd16cfe2abfc2ad55d5ca4ffa49b3d340f7fc811a8b9a5ba1f774c836
|
|
|
test-warnings-providers-asana...exasol-All-LowestDeps-sqlite-14-3.10
Expired
|
16.6 KB |
sha256:f191044942b4c274da823d2632969cb25223b3349a15fa8041a63906d327010f
|
|
|
test-warnings-providers-fab...mongo-All-LowestDeps-sqlite-14-3.10
Expired
|
13.8 KB |
sha256:bca9b748ad487158fcedc8ec6485431a2c98311e536880d2c3c2d4e49664f4a0
|
|
|
test-warnings-providers-mysql...samba-All-LowestDeps-sqlite-14-3.10
Expired
|
2.38 KB |
sha256:52cb43a5786de7a74d59a45fdd806d8fb898a77bff5015440de6f03842e6c255
|
|
|
test-warnings-providers-segment...zendesk-All-LowestDeps-sqlite-14-3.10
Expired
|
11.9 KB |
sha256:5922aa906bc9c12620bf2f6e0fffbadba202de98a41d8d5c6c72f92bf71603f9
|
|