ci: shard behavior tests by measured duration - #70
Closed
ruby-dlee wants to merge 10 commits into
Closed
Conversation
Owner
Author
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
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.
Intent
Refresh PR 56 onto current main without rewriting its gate-tracked history, preserve its behavior-test sharding work, fix all current-head CI defects, and get the existing PR fully green without merging it.
What Changed
Risk Assessment
✅ Low: The follow-up accurately refreshes the shard inventory, load table, and indivisible-test floor, while the full change remains well-bounded and preserves the sharding and merge-history requirements.
Testing
Pipeline
Updates from git push no-mistakes
✅ **intent** - passed
✅ No issues found.
✅ **Rebase** - passed
✅ No issues found.
🔧 **Review** - 1 issue found → auto-fixed ✅
docs/ci-behavior-shards.md:21- The documented “checked-in plan” is stale after the teardown split and current-main refresh. The actual 87-test plan has loads of 475500/436053/436051/436048/436056/436296/436222/436053 ms, while this table totals only 84 tests; line 38 also names the removedfm-teardown.test.sh. Refresh the assignment table and floor description so the operational documentation matches the committed inventory.🔧 Fix: Refresh current behavior shard plan documentation
✅ Re-checked - no issues remain.
⏭️ **Test** - skipped
Step was skipped.
✅ **Document** - passed
✅ No issues found.
✅ **Lint** - passed
✅ No issues found.
✅ **Push** - passed
✅ No issues found.