fix: increase create-expert E2E timeout to 600s#597
Merged
Conversation
420s was still insufficient for the "modify existing perstack.toml" test in CI. The multi-delegation workflow (planner → definition-writer → expert-tester) can take over 7 minutes under CI load. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
1 participant
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
LLM_TIMEOUTfrom 420s to 600s for the create-expert E2E testsContext
The previous bump from 300s → 420s (#594) was not enough. The
changeset-release/mainCI run (#22215783403) timed out at exactly 420s.Test plan
🤖 Generated with Claude Code