Files
hyperframes/packages
Miguel Ángel 856ac34c53 test(engine): time the bun --eval spawn in resolveHeadlessShellPath tests (#4078)
These tests spawn a bun process to check platform-specific chrome
binary resolution, and have hit the default test timeout on Windows
CI runners before. The log only ever shows the bare timeout, with no
way to tell whether the spawn itself was slow or something else in
the test body stalled. Wrapping each spawn in console.time/
console.timeEnd costs nothing when the test is fast and names the
slow step the next time it isn't. No behavior change.
2026-09-18 10:07:58 -04:00
..
2026-09-17 23:55:00 -07:00
2026-09-17 23:55:00 -07:00
2026-09-17 23:55:00 -07:00
2026-09-17 23:55:00 -07:00
2026-09-17 23:55:00 -07:00
2026-09-17 23:55:00 -07:00
2026-09-17 23:55:00 -07:00