Repository navigation
chore(ci): refresh the Test Core shard-timings dataset - #24467
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
Regenerated by .github/workflows/shard-timings-refresh.yml from the test-core-run-summary artifacts of 7 accumulated run(s) (39202368342 39197429467 39192681060 39188268133 39184708096 39178996284 39174682274), newest 39202368342 at 725a5b1. Generated, never hand-edited.
This was referenced Oct 19, 2026
This branch has not been deployed
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.
Regression readings: NOT MEASURED -- the diff refused (exit 1)
What the seat landing this PR does
File nothing from this refresh's readings: no rise and no file was judged. The refusal above
is a defect in this lane, and that is the one card to file.
Source
Measured across 7 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/39202368342
https://github.com/objectstack-ai/objectstack/actions/runs/39197429467
https://github.com/objectstack-ai/objectstack/actions/runs/39192681060
https://github.com/objectstack-ai/objectstack/actions/runs/39188268133
https://github.com/objectstack-ai/objectstack/actions/runs/39184708096
https://github.com/objectstack-ai/objectstack/actions/runs/39178996284
https://github.com/objectstack-ai/objectstack/actions/runs/39174682274
Newest run in the set:
39202368342, commit725a5b1311ecc051edafcd8122ad47dfe1ccfbf8— 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 75 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 75 weights rests on at least 3 executed runs; none is provisional.
Suite-duration ceilings: 72 held unchanged (a refresh never moves one; a raise is a ruling), 3 new (@objectstack/connector-imap, @objectstack/service-mailbox, @objectstack/service-print), each new one its slowest executed run in this window x 1.25.
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/service-package@objectstack/example-embed-objectql@objectstack/service-automation@objectstack/knowledge-memory@objectstack/plugin-email@objectstack/connector-slack@objectstack/embedder-openai@objectstack/downstream-contract@objectstack/rest@objectstack/example-showcase@objectstack/observability@objectstack/knowledge-ragflow@objectstack/service-knowledge@objectstack/plugin-webhooks@objectstack/driver-mongodb@objectstack/plugin-auth@objectstack/sdui-parser@objectstack/service-i18n@objectstack/service-storage@objectstack/http-conformance@objectstack/runtime@objectstack/service-datasource@objectstack/connector-openapi@objectstack/plugin-pinyin-search@objectstack/example-todo@objectstack/example-crm@objectstack/plugin-approvals@objectstack/service-sms@objectstack/service-realtime@objectstack/metadata-fs@objectstack/client@objectstack/driver-sqlite-wasm@objectstack/cloud-connection@objectstack/plugin-security@objectstack/service-cluster-redis@objectstack/lint@objectstack/metadata-protocol@objectstack/driver-memory@objectstack/plugin-sharing@objectstack/service-cache@objectstack/formula@objectstack/service-analytics@objectstack/service-print@objectstack/service-settings@objectstack/platform-objects@objectstack/verify@objectstack/driver-sql@objectstack/plugin-audit@objectstack/service-cluster@objectstack/organizations@objectstack/trigger-api@objectstack/service-messaging@objectstack/plugin-dev@objectstack/spec@objectstack/driver-turso@objectstack/client-react@objectstack/connector-rest@objectstack/types@objectstack/hono@objectstack/vitest-filter-preflight@objectstack/connector-mcp@objectstack/trigger-schedule@objectstack/service-mailbox@objectstack/metadata@objectstack/service-queue@objectstack/metadata-core@objectstack/core@objectstack/service-jobcreate-objectstack@objectstack/plugin-hono-server@objectstack/mcp@objectstack/connector-imap@objectstack/objectql@objectstack/trigger-record-change@objectstack/cliMeasured 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.