Skip to content

[ci] run UI E2E tests on ubuntu-24.04 (Playwright deps unavailable on ubuntu-26.04) - #1823

Draft
xiangfu0 wants to merge 1 commit into
masterfrom
cs_gjy7snIsW9/fix/e2e-runner-ubuntu-24.04
Draft

xiangfu0 wants to merge 1 commit into
masterfrom
cs_gjy7snIsW9/fix/e2e-runner-ubuntu-24.04

Conversation

@xiangfu0

@xiangfu0 xiangfu0 commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

Issue(s)

TE UI - E2E Tests fails on every non-draft PR before any test runs, whatever the change. For example, #1818 and #1820 only touch pom.xml, and this job sparse-checks-out only thirdeye-ui/.

Description

.github/workflows/fe-e2e.yaml: runs-on: ubuntu-latest → runs-on: ubuntu-24.04 (one line). No test, dependency or frontend changes.

Evidence from job 125148282103 (#1818) and run 41406063517 (#1820), both identical:

  • "Set up job" reports Image: ubuntu-26.04: ubuntu-latest now lands on the 26.04 image.
  • The Install Playwright Browsers step (npx playwright install --with-deps, @playwright/test ^1.49.1) fails with:
    E: Package 'libicu74' has no installation candidate, E: Unable to locate package libvpx9, E: Package 'libxml2' has no installation candidate, E: Unable to locate package libx264-164, then Failed to install browsers. Those are Ubuntu 24.04 package names, which this Playwright version installs.
  • Run local server and Run Playwright tests are then skipped.
  • ubuntu-24.04 is a supported GitHub-hosted runner label (actions/runner-images README).

Not changed: gyp ERR! ... ValueError: invalid mode: 'rU' during npm ci. Node 14's bundled node-gyp 5.1.1 cannot run on Python ≥ 3.11, but the optional native builds that fail are non-fatal: Install dependencies succeeds (2,689 packages). Fixing that means a Node/toolchain upgrade, a separate frontend change.

How to test

This PR's own TE UI - E2E Tests run is the validation: the Playwright browser install should succeed on 24.04 and the existing E2E suite should run against the configured E2E backend (secrets E2E_TOKEN / E2E_PROXY). Results will be reported in a comment. Run backend tests on this PR fails at Testcontainers Docker discovery until #1820 is merged; that is unrelated.

ubuntu-latest now resolves to ubuntu-26.04, where 'npx playwright install
--with-deps' (Playwright 1.49) fails before any test runs: it installs the
Ubuntu 24.04 package set (libicu74, libvpx9, libx264-164, libxml2), which
is not available on 26.04.
@intentlab-ai

intentlab-ai Bot commented Nov 2, 2026

Copy link
Copy Markdown

Code Review

✅ Passed

Reviewed bd7fbd9

@intentlab-ai

intentlab-ai Bot commented Nov 2, 2026

Copy link
Copy Markdown

PR Readiness Review

✅ Passed

Reviewed bd7fbd9

xiangfu0 commented Nov 2, 2026

Copy link
Copy Markdown
Contributor Author

E2E validation result for this PR: run https://github.com/startreedata/thirdeye/actions/runs/41407038977 (runner image ubuntu24/20261025.353).

What this change fixes (verified):

  • Install Playwright Browsers now succeeds: the 24.04 packages installed. Previously it failed on ubuntu-26.04 with libicu74 / libvpx9 / libxml2 / libx264-164 unavailable.
  • Run local server and Wait for server to be ready succeed, and the existing suite runs: Running 38 tests using 1 worker.

What is still failing (not caused or fixed by this PR): 27 failed, 1 passed, 3 skipped, 7 did not run (32.6 min).

  • Every failure is a timeout waiting for the app's first render or API response. For example alert-details.spec.ts:126: after goto("http://localhost:7004/#access_token=''"), the wait for h4:has-text('StarTree ThirdEye') times out at 10 s. Others time out in waitForURL / waitForResponse.
  • This most likely means the dev server's backend proxy/auth (TE_DEV_PROXY_SERVER = secret E2E_PROXY, VERCEL_ACCESS_TOKEN = secret E2E_TOKEN) is unreachable or no longer valid. That is an inference: the job uploads no Playwright traces, the backgrounded dev server's output isn't captured, and the secret values were not inspected.
  • Baseline: across all 31 retained runs of this workflow (2026-04-16 → today) there are 0 successful runs.

So this PR is the necessary runner fix, but on its own it does not make E2E green. Returning it to draft. Next step for repository owners: confirm or refresh the E2E backend and token behind those secrets, then re-run. No tests were disabled or changed.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant