Skip to content

Conversation

rmunn
Copy link
Collaborator

@rmunn rmunn commented Jun 16, 2025

At least one project took 23 minutes 3 seconds to do an hg merge operation, so Chorus's default 15 minute timeout is too low.

Fixes #357.

At least one project took 23 minutes 3 seconds to do an hg merge
operation, so Chorus's default 15 minute timeout is too low.
@rmunn rmunn self-assigned this Jun 16, 2025
@rmunn
Copy link
Collaborator Author

rmunn commented Jun 16, 2025

This has been "tested in production" before creating the PR: I fixed a stuck Send/Receive project by editing the /usr/share/lfmerge/7000072/environ file and adding export CHORUS_LOCAL_TIMEOUT_SECONDS=3600 there. This made the project able to Send/Receive again. So this PR simply makes that change permanent, rather than having a change that will be reverted the next time LfMerge gets deployed to production.

@rmunn rmunn requested a review from megahirt June 16, 2025 05:41
Copy link

Test Results

    2 files  ±0    21 suites  ±0   4m 54s ⏱️ -3s
315 tests ±0  293 ✔️ ±0  22 💤 ±0  0 ±0 
318 runs  ±0  296 ✔️ ±0  22 💤 ±0  0 ±0 

Results for commit 7453a74. ± Comparison against base commit 92c8c96.

Copy link
Contributor

@megahirt megahirt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Increase Chorus timeout by setting env var
3 participants