Skip to content

ci: refresh PostgreSQL shard weights from retained timings - #1041

Merged
1 commit merged into
mainfrom
workflow/1036-pg-shard-weights
Nov 5, 2026
Merged

1 commit merged into
mainfrom
workflow/1036-pg-shard-weights

Conversation

@rmcdaniel

@rmcdaniel rmcdaniel commented Nov 5, 2026 •

Copy link
Copy Markdown
Member

The PostgreSQL feature shards in #1036's original full run were estimated at about 489 seconds each but took 545–603 seconds. Shard 3 exceeded its 600-second bound. Increase each existing PostgreSQL file weight to the larger of its committed weight and the retained measured duration.

All MySQL weights, test files and deadlines are preserved. The source is run 41966046437, attempt 1, head 5d490bb, using PostgreSQL timing artifacts 13387763296, 13388255961, 13387479423 and 13387509427. All 156 files have unique retained timing entries, including the timed-out shard's 1,040 actual testcase records; its process result remains exit 124. This branch updates the 154 files already on main 98bd986. The two #1036 files keep their existing default until source integration.

Validation: the actual PHP shard verifier passes, representing all 154 main files exactly once across four shards for both backends. A data-only model of the splitter exactly reproduces all four original file manifests. Applying these weights to the measured 156-file corpus projects 572.97–577.65 seconds per shard, compared with 545.10–603.43 using old weights. These are estimates, not a new feature pass or a guaranteed margin. No hosted rerun was requested. The separate MySQL schema repair is draft #1040.

@sonarqubecloud

sonarqubecloud Bot commented Nov 5, 2026

Copy link
Copy Markdown

@rmcdaniel

Copy link
Copy Markdown
Member Author

Exact head 97731fa39668e1efff60ff8657f0c8c0c407a7f3 is now included without file changes in P1 #1043's frozen combined reference 31aa05e42501a206bb2ce5d55b2fb7aeaa708201. The one selected full run, attempt 1, succeeded under the existing deadlines. Actual PostgreSQL shard times were 589.485, 555.181, 543.793 and 508.811 seconds. All four shards passed (2,819 tests / 27,719 assertions / 30 declared skips). These are actual combined-source measurements, superseding a prediction as evidence without changing or extending the 600-second timeout.

Full quality/graph attribution remains on #1043. The original failed #1036 attempt remains preserved; this does not qualify #1036's feature blobs. Workflow owns follow-through; General owns integration of contributor #1044, #1040 and this PR. No merge or repeated full run was performed.

@rmcdaniel rmcdaniel closed this pull request by merging all changes into main in e366443 Nov 5, 2026
@rmcdaniel
rmcdaniel deleted the workflow/1036-pg-shard-weights branch November 5, 2026 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant