Skip to content

chore(ci): refresh the Test Core shard-timings dataset - #22965

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
claude/shard-timings-refresh-38206660804
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
claude/shard-timings-refresh-38206660804

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Refreshes scripts/test-shard-timings.json, the balancing input for the Test Core
shard split. Opened automatically by .github/workflows/shard-timings-refresh.yml.
Every byte came out of scripts/measure-test-shard-timings.mjs; nothing here was
hand-edited, and no bound, timeout or matrix entry was touched.

Source

Measured across 13 accumulated run(s) of the HOURLY schedule run of CI on
main — the full-battery run (#16467). A push run on main is affected-only and
is 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 --run group, until every package has been EXECUTED by at least the
generator's minimum number of them, and each weight is the median of those executions.

All 72 package weights were measured in these runs; nothing was carried.

⚠️ This PR references #16173 and #16222 but does NOT carry a closing keyword for them,
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.

Suite-duration ceilings: 72 held unchanged (a refresh never moves one; a raise is a ruling), 0 new, each new one its slowest executed run in this window x 1.25.

Every package carries a ceiling.

⚠️ 1 package(s) ran OVER their held ceiling in this window (marked in the table): the brake fired on main. This refresh does not raise them; that takes a ruling.

Each package's executed runs in this refresh (minimum 3), the spread of its readings in seconds, and the suite-duration ceiling Test Core grades 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.

package runs min s median s max s max/min ceiling s
@objectstack/example-embed-objectql 13 6.91 24.11 41.20 5.96× 51.51
@objectstack/example-crm 12 14.02 34.07 55.06 3.93× 68.83
@objectstack/knowledge-memory 13 1.44 2.87 5.11 3.55× 6.39
@objectstack/cloud-connection 12 50.11 99.60 172.11 3.43× 163.89 held; this window: 215.14; ⚠ a window run is OVER its held ceiling
@objectstack/plugin-approvals 11 70.14 145.12 232.48 3.31× 290.60
@objectstack/service-realtime 13 7.33 14.46 22.14 3.02× 27.68
@objectstack/verify 12 120.87 230.44 335.17 2.77× 418.97
@objectstack/service-job 10 13.34 22.27 36.25 2.72× 45.32
@objectstack/trigger-record-change 9 32.75 68.97 87.30 2.67× 109.12
@objectstack/connector-mcp 11 18.94 27.20 49.57 2.62× 54.85 held; this window: 61.97
@objectstack/service-i18n 13 15.29 23.52 39.56 2.59× 49.45
@objectstack/downstream-contract 13 8.54 11.87 21.15 2.48× 22.71 held; this window: 26.44
@objectstack/client-react 12 5.57 8.90 12.98 2.33× 16.23
@objectstack/plugin-webhooks 10 37.28 51.50 86.43 2.32× 108.05
@objectstack/service-datasource 9 44.62 60.73 103.14 2.31× 128.93
@objectstack/trigger-api 13 14.69 23.82 33.69 2.29× 42.12
@objectstack/connector-openapi 11 21.58 43.95 49.25 2.28× 61.57
@objectstack/service-storage 10 72.31 121.00 164.06 2.27× 208.28 held; this window: 205.08
@objectstack/service-knowledge 10 17.29 22.43 38.86 2.25× 48.58
@objectstack/http-conformance 12 53.78 75.82 119.68 2.23× 149.61
@objectstack/plugin-auth 12 218.12 445.89 480.35 2.20× 600.45
@objectstack/runtime 10 335.18 461.07 730.47 2.18× 913.09
@objectstack/service-cluster 13 10.93 13.46 23.50 2.15× 28.46 held; this window: 29.38
@objectstack/service-package 11 12.38 18.10 26.32 2.13× 32.90
@objectstack/platform-objects 8 49.40 84.44 104.50 2.12× 135.03 held; this window: 130.63
@objectstack/connector-rest 11 23.21 30.63 48.65 2.10× 60.82
@objectstack/example-showcase 11 74.52 142.92 153.63 2.06× 192.05
@objectstack/client 11 67.22 118.45 138.35 2.06× 179.74 held; this window: 172.94
@objectstack/driver-mongodb 8 62.05 83.62 127.16 2.05× 158.96
@objectstack/metadata-core 13 15.17 22.90 30.72 2.02× 38.66 held; this window: 38.41
@objectstack/service-analytics 10 175.18 262.37 352.43 2.01× 440.54
@objectstack/hono 12 18.29 29.62 36.62 2.00× 45.99 held; this window: 45.77
@objectstack/observability 6 1.80 2.69 3.58 1.99× 4.24 held; this window: 4.49
@objectstack/plugin-pinyin-search 7 25.27 41.22 49.89 1.97× 62.37
@objectstack/service-cache 13 1.51 2.19 2.95 1.95× 3.69
@objectstack/embedder-openai 13 3.77 4.71 7.28 1.93× 9.10
@objectstack/metadata 5 82.41 112.34 152.40 1.85× 194.04 held; this window: 190.50
@objectstack/service-sms 11 20.45 25.16 37.63 1.84× 47.04
@objectstack/objectql 9 419.92 582.93 761.82 1.81× 952.27
@objectstack/service-cluster-redis 13 14.80 20.58 26.83 1.81× 28.00 held; this window: 33.55
@objectstack/rest 7 388.85 526.67 702.73 1.81× 878.41
create-objectstack 13 16.12 22.86 29.11 1.81× 38.40 held; this window: 36.39
@objectstack/formula 6 26.84 30.66 48.29 1.80× 56.95 held; this window: 60.36
@objectstack/service-automation 10 247.86 425.27 445.67 1.80× 557.10
@objectstack/driver-turso 8 121.30 168.94 217.89 1.80× 272.37
@objectstack/plugin-security 10 225.59 334.77 405.14 1.80× 474.43 held; this window: 506.43
@objectstack/metadata-protocol 7 345.35 370.78 615.76 1.78× 769.71
@objectstack/service-queue 9 34.50 51.58 61.16 1.77× 83.25 held; this window: 76.46
@objectstack/plugin-sharing 10 106.44 151.33 188.42 1.77× 235.53
@objectstack/service-settings 10 71.85 93.50 126.04 1.75× 157.56
@objectstack/driver-sqlite-wasm 8 50.64 78.52 88.78 1.75× 123.14 held; this window: 110.99
@objectstack/vitest-filter-preflight 6 14.17 17.27 24.66 1.74× 28.93 held; this window: 30.83
@objectstack/trigger-schedule 11 35.07 42.08 60.13 1.71× 72.40 held; this window: 75.17
@objectstack/example-todo 9 41.63 65.32 71.07 1.71× 88.84
@objectstack/lint 7 156.29 170.22 265.74 1.70× 332.18
@objectstack/knowledge-ragflow 13 1.61 2.52 2.72 1.69× 3.40
@objectstack/connector-slack 11 27.03 41.99 44.36 1.64× 55.45
@objectstack/core 6 74.03 82.36 121.13 1.64× 151.42
@objectstack/types 12 18.31 24.57 29.46 1.61× 32.05 held; this window: 36.83
@objectstack/driver-memory 8 87.96 120.89 140.93 1.60× 171.63 held; this window: 176.17
@objectstack/service-messaging 8 83.28 128.51 132.25 1.59× 166.91 held; this window: 165.31
@objectstack/plugin-dev 12 42.61 61.48 66.95 1.57× 87.97 held; this window: 83.69
@objectstack/sdui-parser 3 2.92 3.51 4.58 1.57× 5.18 held; this window: 5.74
@objectstack/mcp 9 56.85 83.77 87.17 1.53× 108.17 held; this window: 108.96
@objectstack/plugin-hono-server 6 41.64 51.97 62.88 1.51× 78.61
@objectstack/cli 9 1730.23 2125.32 2365.87 1.37× 2868.12 held; this window: 2957.35
@objectstack/organizations 10 81.71 102.80 110.32 1.35× 137.91
@objectstack/plugin-audit 7 110.50 141.61 148.74 1.35× 185.93
@objectstack/plugin-email 8 71.33 84.53 95.95 1.35× 119.94
@objectstack/spec 3 1156.48 1330.73 1522.84 1.32× 1903.55
@objectstack/driver-sql 8 275.27 354.23 360.60 1.31× 450.76
@objectstack/metadata-fs 5 40.62 45.68 46.41 1.14× 61.33 held; this window: 58.02

Measured per-shard suite time on the newest run in the set

1: 496s  |  2: 320s  |  3: 297s  |  4: 327s  |  5: 600s  |  6: 454s

Predicted bins, before and after

BEFORE  partition-test-shards: self-test OK (72 measured packages -> 74 shard items, 6 shards, max/mean 1.00x <= 1.3x, floor 1408s, bins 1870.13/1870.41/1872.28/1870.02/1871.88/1871.92s within the 2109.45s density cap, file-level slices: @objectstack/cli x3)
AFTER   partition-test-shards: self-test OK (72 measured packages -> 74 shard items, 6 shards, max/mean 1.00x <= 1.3x, floor 1331s, bins 1827.03/1824.14/1826.85/1826.62/1824.95/1824.59s within the 2125.32s density cap, file-level slices: @objectstack/cli x3)

No checks will start on this PR by themselves

It was opened with the Actions GITHUB_TOKEN, and GitHub's recursion guard means a
PR 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.

Regenerated by .github/workflows/shard-timings-refresh.yml from the test-core-run-summary artifacts of 13 accumulated run(s) (38206660804 38202645321 38198819852 38195222269 38192273698 38186537664 38178693315 38174616574 38170438819 38166241661 38162059938 38157849210 38153696467), newest 38206660804 at 51b43a8. Generated, never hand-edited.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-changeset PR has no user-facing published change; bypasses the changeset gate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants