Repository navigation
Conversation
When a green push to main publishes e2e-timings, each file's time is averaged half and half with the timings that run packed by, so one noisy run moves the plan only halfway. New specs keep their own time, deleted ones drop out, and without usable previous timings the run's own are written.
HMarzban
marked this pull request as ready for review
November 22, 2026 15:40
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.
Summary
Shard timings are averaged across runs. This follow-up is stacked on #186 (base: its branch) and is meant to land with it.
One run's per-file times are noisy. In #186's run,
mobile-bar.spec.tstook 263 s against 116 s in the run its timings came from, so shard 1 carried 1,017 s of tests against 879 s planned and was the slowest job, at 7m23s.smoothTimingsinscripts/e2e-shards.tsis a pure exponential moving average: half weight to the newest run, half to the previous average. A new spec keeps its own time, and a deleted spec is dropped.main) passes the timings this run packed by (needs.changes.outputs.timings) as the previous ones. No second download is needed, and a PR still never writes timings. Without usable previous timings it writes the run's own, as before.e2e-shards.test.tscovers the average: a table of cases plus the weight.ci-workflow.test.tspins that the publish step reads the timings the run packed by.Verification
bun test tests/unit/cipasses 176 tests, and actionlint is clean.mobile-barat 130.6 s averaged with a previous 50 s gives 90.3 s. A file missing from the report is dropped. An empty previous file writes the run's own timings, byte for byte the same as without a previous file.mainpublishes, so it first takes effect after this merges.Deploy: none.
🤖 Generated with Claude Code