Repository navigation
chore(ci): refresh the Test Core shard-timings dataset - #22923
Merged
objectstack-fleet[bot] merged 2 commits intoOct 12, 2026
Merged
Conversation
Regenerated by .github/workflows/shard-timings-refresh.yml from the test-core-run-summary artifacts of 12 accumulated run(s) (38195222269 38192273698 38186537664 38178693315 38174616574 38170438819 38166241661 38162059938 38157849210 38153696467 38149530770 38145479058), newest 38195222269 at eab7236. Generated, never hand-edited.
objectstack-fleet
Bot
deleted the
claude/shard-timings-refresh-38195222269
branch
October 12, 2026 03:58
This was referenced Oct 12, 2026
This was referenced Oct 12, 2026
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.
Refreshes
scripts/test-shard-timings.json, the balancing input for the Test Coreshard split. Opened automatically by
.github/workflows/shard-timings-refresh.yml.Every byte came out of
scripts/measure-test-shard-timings.mjs; nothing here washand-edited, and no bound, timeout or matrix entry was touched.
Source
Measured across 12 accumulated run(s) of the HOURLY
schedulerun of CI onmain— the full-battery run (#16467). Apushrun onmainis affected-only andis not a measurement of the workspace, so no push run feeds this file.
No single green run measures the whole workspace either — turbo's cache is namespaced
per shard and only main pushes write it, so a
package whose inputs have not changed is a HIT and the generator refuses hits rather
than recording a replay as a duration. Runs are therefore accumulated, each fenced by
its own
--rungroup, until every package has been EXECUTED by at least thegenerator's minimum number of them, and each weight is the median of those executions.
https://github.com/objectstack-ai/objectstack/actions/runs/38195222269
https://github.com/objectstack-ai/objectstack/actions/runs/38192273698
https://github.com/objectstack-ai/objectstack/actions/runs/38186537664
https://github.com/objectstack-ai/objectstack/actions/runs/38178693315
https://github.com/objectstack-ai/objectstack/actions/runs/38174616574
https://github.com/objectstack-ai/objectstack/actions/runs/38170438819
https://github.com/objectstack-ai/objectstack/actions/runs/38166241661
https://github.com/objectstack-ai/objectstack/actions/runs/38162059938
https://github.com/objectstack-ai/objectstack/actions/runs/38157849210
https://github.com/objectstack-ai/objectstack/actions/runs/38153696467
https://github.com/objectstack-ai/objectstack/actions/runs/38149530770
https://github.com/objectstack-ai/objectstack/actions/runs/38145479058
Newest run in the set:
38195222269, commiteab7236ff70d2c4217706e932d14a64ca25e8d2e— the date this refresh carries.Every run above had all six
Test Core (N/6)jobs concludesuccesswith its sixrun-summary artifacts still retained; runs that were cancelled, failed or had lost
their artifacts were rejected by name in the log before any of these were used.
All 72 package weights were measured in these runs; nothing was carried.
because a weekly lane cannot know which cards a given run ought to retire. If this is
the first refresh to land, retire those two by hand as part of merging it.
Sample depth, run-to-run spread and suite-duration ceilings
Every one of the 72 weights rests on at least 3 executed runs; none is provisional.
Test Corecheck (scripts/check-test-suite-ceilings.mjs) grades every executed package against it -- until then it reads NOT MEASURED. Every later refresh HOLDS these numbers and a ceiling rises only by a ruling, so review the ceiling column below before merging.Every package carries a ceiling.
Each package's executed runs in this refresh (minimum 3), the spread of its readings in seconds, and the suite-duration ceiling
Test Coregrades it against: its slowest executed run x 1.25 when first set, then held by every refresh -- a ceiling is raised only by a ruling.@objectstack/example-embed-objectql@objectstack/example-crm@objectstack/verify@objectstack/service-realtime@objectstack/service-job@objectstack/trigger-record-change@objectstack/cloud-connection@objectstack/service-i18n@objectstack/plugin-approvals@objectstack/http-conformance@objectstack/client-react@objectstack/connector-mcp@objectstack/trigger-api@objectstack/connector-openapi@objectstack/service-knowledge@objectstack/platform-objects@objectstack/runtime@objectstack/client@objectstack/plugin-auth@objectstack/service-package@objectstack/downstream-contract@objectstack/connector-rest@objectstack/service-cluster@objectstack/driver-mongodb@objectstack/knowledge-memory@objectstack/metadata-core@objectstack/service-analytics@objectstack/hono@objectstack/plugin-pinyin-search@objectstack/service-cache@objectstack/driver-sqlite-wasm@objectstack/embedder-openai@objectstack/service-queuecreate-objectstack@objectstack/metadata@objectstack/observability@objectstack/service-sms@objectstack/plugin-webhooks@objectstack/objectql@objectstack/service-datasource@objectstack/rest@objectstack/plugin-sharing@objectstack/driver-turso@objectstack/service-storage@objectstack/metadata-protocol@objectstack/formula@objectstack/lint@objectstack/example-todo@objectstack/plugin-security@objectstack/service-settings@objectstack/plugin-dev@objectstack/trigger-schedule@objectstack/core@objectstack/vitest-filter-preflight@objectstack/driver-memory@objectstack/knowledge-ragflow@objectstack/example-showcase@objectstack/mcp@objectstack/service-cluster-redis@objectstack/plugin-hono-server@objectstack/sdui-parser@objectstack/service-messaging@objectstack/types@objectstack/service-automation@objectstack/organizations@objectstack/plugin-audit@objectstack/plugin-email@objectstack/cli@objectstack/driver-sql@objectstack/connector-slack@objectstack/spec@objectstack/metadata-fsMeasured per-shard suite time on the newest run in the set
Predicted bins, before and after
No checks will start on this PR by themselves
It was opened with the Actions
GITHUB_TOKEN, and GitHub's recursion guard means aPR opened that way triggers no workflow runs. Push any commit to the branch, or close
and reopen the PR, to start CI.
Refs #16464, #16173, #16222.