fix(ci): raise the e2e jest timeout for cold CI runners - #549
Merged
Conversation
The advisory E2E jest job has timed out twice on feedback-flow's first test (default 5s) under cold CI load while the same suite passes locally and on re-run (#542). Give each e2e test 20s so cold-start renders stop flaking the job.
RonenMars
marked this pull request as ready for review
August 4, 2026 15:24
RonenMars
added a commit
that referenced
this pull request
Aug 4, 2026
<!-- CURSOR_AGENT_PR_BODY_BEGIN --> ## Summary The advisory `E2E jest` job has flaked twice on cold CI with the same failure: `feedback-flow › shows all entry points` exceeding Jest's default 5s per-test timeout. Local isolation passes, and a single CI re-run goes green — documented in #542 with the instruction to raise the timeout on recurrence rather than delete the job. `test:e2e` now passes `--testTimeout=20000` so cold-start renders on CI runners stop tipping the default. ## Test plan - [x] `npm run test:e2e` — 7 suites / 60 tests pass locally with the new timeout - [x] `E2E jest` green on the previous run of this change without a re-run (feedback-flow suite still ~18s on CI; 20s per-test margin holds) - [ ] After merge, #542 can be closed if the next few PR runs stay green <!-- CURSOR_AGENT_PR_BODY_END --> <div><a href="https://cursor.com/agents/bc-81427069-eace-4d04-983d-af1299c47c6f?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a href="https://cursor.com/background-agent?bcId=bc-81427069-eace-4d04-983d-af1299c47c6f&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> </div> Co-authored-by: Cursor Agent <cursoragent@cursor.com>
![https://cursor.com/assets/images/open-in-web-dark.png"><source](https://cursor.com/assets/images/open-in-web-dark.png"><source){kind=link}
![https://cursor.com/assets/images/open-in-web-light.png"><img](https://cursor.com/assets/images/open-in-web-light.png"><img){kind=link}
![https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a](https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a){kind=link}
![https://cursor.com/assets/images/open-in-cursor-dark.png"><source](https://cursor.com/assets/images/open-in-cursor-dark.png"><source){kind=link}
![https://cursor.com/assets/images/open-in-cursor-light.png"><img](https://cursor.com/assets/images/open-in-cursor-light.png"><img){kind=link}
![https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> </div](https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> </div){kind=link}
RonenMars
added a commit
that referenced
this pull request
Aug 4, 2026
<!-- CURSOR_AGENT_PR_BODY_BEGIN --> ## Summary The advisory `E2E jest` job has flaked twice on cold CI with the same failure: `feedback-flow › shows all entry points` exceeding Jest's default 5s per-test timeout. Local isolation passes, and a single CI re-run goes green — documented in #542 with the instruction to raise the timeout on recurrence rather than delete the job. `test:e2e` now passes `--testTimeout=20000` so cold-start renders on CI runners stop tipping the default. ## Test plan - [x] `npm run test:e2e` — 7 suites / 60 tests pass locally with the new timeout - [x] `E2E jest` green on the previous run of this change without a re-run (feedback-flow suite still ~18s on CI; 20s per-test margin holds) - [ ] After merge, #542 can be closed if the next few PR runs stay green <!-- CURSOR_AGENT_PR_BODY_END --> <div><a href="https://cursor.com/agents/bc-81427069-eace-4d04-983d-af1299c47c6f?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a href="https://cursor.com/background-agent?bcId=bc-81427069-eace-4d04-983d-af1299c47c6f&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> </div> Co-authored-by: Cursor Agent <cursoragent@cursor.com>
RonenMars
added a commit
that referenced
this pull request
Aug 4, 2026
<!-- CURSOR_AGENT_PR_BODY_BEGIN --> ## Summary The advisory `E2E jest` job has flaked twice on cold CI with the same failure: `feedback-flow › shows all entry points` exceeding Jest's default 5s per-test timeout. Local isolation passes, and a single CI re-run goes green — documented in #542 with the instruction to raise the timeout on recurrence rather than delete the job. `test:e2e` now passes `--testTimeout=20000` so cold-start renders on CI runners stop tipping the default. ## Test plan - [x] `npm run test:e2e` — 7 suites / 60 tests pass locally with the new timeout - [x] `E2E jest` green on the previous run of this change without a re-run (feedback-flow suite still ~18s on CI; 20s per-test margin holds) - [ ] After merge, #542 can be closed if the next few PR runs stay green <!-- CURSOR_AGENT_PR_BODY_END --> <div><a href="https://cursor.com/agents/bc-81427069-eace-4d04-983d-af1299c47c6f?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a href="https://cursor.com/background-agent?bcId=bc-81427069-eace-4d04-983d-af1299c47c6f&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> </div> Co-authored-by: Cursor Agent <cursoragent@cursor.com>
RonenMars
added a commit
that referenced
this pull request
Aug 4, 2026
<!-- CURSOR_AGENT_PR_BODY_BEGIN --> ## Summary The advisory `E2E jest` job has flaked twice on cold CI with the same failure: `feedback-flow › shows all entry points` exceeding Jest's default 5s per-test timeout. Local isolation passes, and a single CI re-run goes green — documented in #542 with the instruction to raise the timeout on recurrence rather than delete the job. `test:e2e` now passes `--testTimeout=20000` so cold-start renders on CI runners stop tipping the default. ## Test plan - [x] `npm run test:e2e` — 7 suites / 60 tests pass locally with the new timeout - [x] `E2E jest` green on the previous run of this change without a re-run (feedback-flow suite still ~18s on CI; 20s per-test margin holds) - [ ] After merge, #542 can be closed if the next few PR runs stay green <!-- CURSOR_AGENT_PR_BODY_END --> <div><a href="https://cursor.com/agents/bc-81427069-eace-4d04-983d-af1299c47c6f?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a href="https://cursor.com/background-agent?bcId=bc-81427069-eace-4d04-983d-af1299c47c6f&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> </div> Co-authored-by: Cursor Agent <cursoragent@cursor.com>
RonenMars
added a commit
that referenced
this pull request
Aug 4, 2026
The advisory `E2E jest` job has flaked twice on cold CI with the same failure: `feedback-flow › shows all entry points` exceeding Jest's default 5s per-test timeout. Local isolation passes, and a single CI re-run goes green — documented in #542 with the instruction to raise the timeout on recurrence rather than delete the job. `test:e2e` now passes `--testTimeout=20000` so cold-start renders on CI runners stop tipping the default. - [x] `npm run test:e2e` — 7 suites / 60 tests pass locally with the new timeout - [x] `E2E jest` green on the previous run of this change without a re-run (feedback-flow suite still ~18s on CI; 20s per-test margin holds) - [ ] After merge, #542 can be closed if the next few PR runs stay green
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The advisory
E2E jestjob has flaked twice on cold CI with the same failure:feedback-flow › shows all entry pointsexceeding Jest's default 5s per-test timeout. Local isolation passes, and a single CI re-run goes green — documented in #542 with the instruction to raise the timeout on recurrence rather than delete the job.test:e2enow passes--testTimeout=20000so cold-start renders on CI runners stop tipping the default.Test plan
npm run test:e2e— 7 suites / 60 tests pass locally with the new timeoutE2E jestgreen on the previous run of this change without a re-run (feedback-flow suite still ~18s on CI; 20s per-test margin holds)