mengw15 opened a new pull request, #7717: URL: https://github.com/apache/texera/pull/7717
### What changes were proposed in this PR? The `build / frontend (macos-latest)` leg failed 6 times between 08-14 and 08-17, each time on a **pure timeout in a different spec** — never a failed assertion (details and per-failure table in #7713). The leg's own wall time swings ~2x run to run (9m17s–16m52s), and the same test that runs in ~400ms on ubuntu has been observed at 11s+ inside a `beforeEach` on a loaded macOS runner — while Vitest's default limits (5s test / 10s hook) are fixed absolute values that don't scale with runner load. Nothing in the frontend test setup changed in that window; the margin is simply thin enough that ordinary macOS runner variance crosses it. - Set `testTimeout: 20000` and `hookTimeout: 30000` in `frontend/vitest.config.ts` (which previously set neither, inheriting the 5s/10s defaults) — roughly 4x/3x the worst observed times. Both are needed: 4 of the 6 failures hit the test timeout, 2 hit the hook timeout. - The cost is that a genuinely hung test reports 15–20s later, negligible against a 9–17 minute leg and strictly cheaper than re-running CI and eroding the signal a red leg carries. - `vitest.browser.config.ts` (the browser-mode leg) deliberately keeps the defaults — no timeout failures have been observed there. - Deliberately **not** making the individual specs cheaper: some are expensive on purpose (`hub-search-result` / `search` stand up real child components to work around the coverage-attribution loss in #7458; undoing that would revert #7627 / #7535). ### Any related issues, documentation, discussions? Closes #7713. ### How was this PR tested? - Config-only change with no executable code; the frontend CI legs themselves exercise it by loading `vitest.config.ts` for the full 202-spec / 4704-test suite. - Type-checked the edited config against Vitest's `InlineConfig` typings (`tsc --noEmit` passes — the option names and types are validated), and `prettier --check` passes, so `format:ci` is unaffected. - No spec sets a per-test timeout override (verified by grep), so the global raise applies uniformly. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (claude-opus-4-8) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
