test: stealth-webdriver launch gets parallel-load headroom (120s)

Playwright's default 30s launch timeout dies under the full-suite
--parallel run when ~400 workers contend for Chromium launches — bun
reports the hook death as an '(unnamed)' 30006ms failure (named on
sight by the new runner epilogue). Both launch sites get explicit 120s
timeouts; the runner's external wall-clock still bounds the ceiling.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Garry Tan 2026-08-15 11:20:05 -07:00
parent 98dec67233
commit ec8cedca6f
No known key found for this signature in database
GPG Key ID: C1F69E85C74EFE1D
1 changed files with 6 additions and 1 deletions

View File

@ -5,7 +5,11 @@ import { applyStealth, STEALTH_LAUNCH_ARGS } from '../src/stealth';
let browser: Browser;
beforeAll(async () => {
browser = await chromium.launch({ headless: true, args: STEALTH_LAUNCH_ARGS });
// Playwright's default launch timeout is 30s — under the full-suite
// --parallel run, ~400 workers contend and a cold Chromium launch can
// stall past it (observed: hook death reported as an '(unnamed)' test at
// 30006ms). The runner's external wall-clock still bounds the ceiling.
browser = await chromium.launch({ headless: true, args: STEALTH_LAUNCH_ARGS, timeout: 120_000 });
});
afterAll(async () => {
@ -292,6 +296,7 @@ describe('applyStealth — persistent context (headed + handoff parity)', () =>
const ctx = await chromium.launchPersistentContext(userDataDir, {
headless: true,
args: STEALTH_LAUNCH_ARGS,
timeout: 120_000, // same parallel-load headroom as the top-level launch
});
try {
await applyStealth(ctx);