Retire julia-ci.yml — its three callers have moved to TestShards - #22
Merged
Conversation
This was a third hand-written copy of the sharded-test vertical: a plan job driven by each
repo's `test/ci/plan_shards.jl`, a `CI_CASES` env protocol, a coverage upload, a timing
recorder, and a gate. The other two copies were the fleet's in-repo CI.yml files and
TestShards.jl itself; the first is gone from every repository and the second is a published
package now, so this one has nothing left to be the third of.
Its callers, all migrated today:
QAtlasHub/DataVault.jl -> TestShards directly
QAtlasHub/ParamIO.jl -> TestShards directly
QAtlasHub/AbstractQAtlas.jl -> TestShards directly, twice, one call per Julia version
The last of those is why TestShards grew `artifact-prefix` and `record-timings`: two calls in
one run collided on artifact names, and would have raced to record measurements of two DIFFERENT
Julia versions into one timing history — the first failing loudly on an upload, the second not
failing at all.
Verified before deleting: no workflow in QAtlasHub, lab-sotashimozono or sotashimozono still
references it. The remaining search hits were the word "julia-ci" inside the comments of the
very PRs that removed it.
What this file did well is not lost — the exactly-once gate, the merged coverage and the timing
history all live in TestShards, and unlike here they are tested.
Refs QAtlasHub/TestShards.jl#13, #47.
Co-Authored-By: Claude Opus 5 (1M context) <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.
This was a third hand-written copy of the sharded-test vertical: a plan job driven by each repo's
test/ci/plan_shards.jl, aCI_CASESenv protocol, a coverage upload, a timing recorder, and a gate.The other two copies were the fleet's in-repo
CI.ymlfiles and TestShards.jl itself. The first is gone from every repository and the second is a published package now, so this one has nothing left to be the third of.Its callers, all migrated today
QAtlasHub/DataVault.jlQAtlasHub/ParamIO.jlQAtlasHub/AbstractQAtlas.jlThe last of those is why TestShards grew
artifact-prefixandrecord-timings. Two calls in one run collided on artifact names, and would have raced to record measurements of two different Julia versions into one timing history — the first failing loudly on an upload, the second not failing at all.Verified before deleting
No workflow in
QAtlasHub,lab-sotashimozonoorsotashimozonostill references it. The remaining code-search hits were the word "julia-ci" inside the comments of the very PRs that removed it — the index lags, so I read the live files.What this file did well is not lost: the exactly-once gate, the merged coverage and the timing history all live in TestShards, and unlike here they are tested.
Refs QAtlasHub/TestShards.jl#13, #47.
🤖 Generated with Claude Code