Closed
Conversation
Print test thread count and available parallelism at startup to help debug CI performance issues. Also add periodic progress output for CI environments (no TTY) to show test completion status. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Add timing information to identify which test files are taking the longest to complete, helping diagnose CI performance bottlenecks. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Switch from m8a.12xlarge (48 AMD cores) to c7i.4xlarge (16 Intel cores) for better single-thread performance. The sqlite tests are bottlenecked by large files running sequentially, so faster cores matter more than core count. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This reverts commit d6ce63e.
github-actions
bot
added
development-process
Contributor
Author
|
closing in favour of #20511 |
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.
Which issue does this PR close?
Rationale for this change
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?