Skip to content

[Build] Rebalance Spark test shards with fresh suite durations - #7867

Open
timothyw553 wants to merge 2 commits into
delta-io:masterfrom
timothyw553:rebalance-test-durations
Open

timothyw553 wants to merge 2 commits into
delta-io:masterfrom
timothyw553:rebalance-test-durations

Conversation

@timothyw553

@timothyw553 timothyw553 commented Oct 14, 2026 •

Copy link
Copy Markdown
Collaborator

Which Delta project/connector is this regarding?

  • Spark
  • Standalone
  • Flink
  • Kernel
  • Other (Build)

Description

Follow-up to #6069. Regenerate project/test-durations.csv from the last 12 master runs.

Spark test shards are unbalanced right now: in the same run, shards take ~65 to ~150 min. Only 40 of the 100 suites in the old CSV are still in the current top 100. Many were renamed (e.g. generatedsuites.* subpackages, CatalogOwned -> CatalogManaged), so the slowest suites today (up to ~35 min) get hash-assigned instead of balanced.

How was this patch tested?

CI on this PR will show the new shard times.

Does this PR introduce any user-facing changes?

No.

This pull request and its description were written by Isaac.

Refresh project/test-durations.csv from the last 12 master runs. Many suites
in the old list were renamed, so the heaviest current suites were hash-assigned
and shards ranged from ~65 to ~150 minutes.

Also make collect_test_durations.py use completed runs and skip failed shard
jobs instead of requiring a successful run (master runs are currently marked
failed even when all shards pass), and print the average for
AVG_TEST_SUITE_DURATION_EXCLUDING_TOP_N.

Co-authored-by: Isaac <no-reply@databricks.com>
Signed-off-by: Timothy Wang <timothy.art@gmail.com>
Co-authored-by: Isaac <no-reply@databricks.com>
Signed-off-by: Timothy Wang <timothy.art@gmail.com>
@timothyw553

Copy link
Copy Markdown
Collaborator Author

this was a failed experiment... shard 7 on Spark 4.1 and 4.2 run for 3 hours

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

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant