test(node): Increase cron integration test timeout to 60s#21704
Open
JPeer264 wants to merge 1 commit into
Open
test(node): Increase cron integration test timeout to 60s#21704JPeer264 wants to merge 1 commit into
JPeer264 wants to merge 1 commit into
Conversation
The cron test spawns a child process with `-r ts-node/register` which compiles the scenario on the fly. Under CI load, ts-node compilation can exceed the previous 30s test timeout before the cron ticks and envelopes arrive. Doubling the timeout gives sufficient headroom. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
andreiborza
approved these changes
Jun 23, 2026
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.
closes #21623
closes #21667
In the previous PR the
setTimeoutand this timeout have both been increased., so it could be that that was the reason for the timeout, everything just got delayed.If this is getting flaky one more time then there might be another issue somewhere.