-
cleanup(testing): drop sub-default timeout overrides on release e2e setup hooks (#36009)
发布于
2026-06-16 15:14:50 +00:00 Current Behavior
The
e2e/releasejest project sets a120000mstestTimeout
(e2e/release/jest.config.cts), which Jest applies to any setup hook
without an explicit timeout. Ten release suites instead hardcoded a
60000ms timeout on theirnewProject-basedbeforeEach/beforeAll
setup, half the suite default. Under CI load that setup (newProject
plus@nx/workspace:npm-packagegenerators plus git tagging) can run
past 60s, so the hook times out and the suite fails intermittently.
These surface as recurring high-risk flaky tasks on the Nx Cloud
dashboard (version-plans, version-plans-check,
version-plans-only-touched, conventional-commits-config, among others),
and a CI run on this branch reproduced it in thefirst-release
beforeAll, wherenewProjectalone took 58s.Expected Behavior
The setup hooks drop the explicit per-hook timeout and inherit the
suite's120000ms default, giving the heavy setup enough headroom and
removing the artificial sub-default cap. The60000values were
copy-paste boilerplate carried in by each suite's introducing PR, not a
deliberate limit, and this matches the common e2e idiom where setup
hooks omit a per-hook timeout and rely on the file default.
下载附件