Skip to content

Split Test Suite steps - #5863

Open
JasonAtClockwork wants to merge 2 commits into
jlarabie/shard-test-suitefrom
jlarabie/shard-test-suite-2
Open

Split Test Suite steps#5863
JasonAtClockwork wants to merge 2 commits into
jlarabie/shard-test-suitefrom
jlarabie/shard-test-suite-2

Conversation

@JasonAtClockwork

@JasonAtClockwork JasonAtClockwork commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Description of Changes

Split of Test Suite to finish up: #5839

  • Split Rust tests into one build job and four shards
  • Run doctests and UI tests in the Rust build job
  • Group serial and feature tests into their own job
  • Run C# and C++ tests in separate jobs
  • Reduce debug info to keep test artifacts smaller (was over 5GB)

API and ABI breaking changes

No breaking changes

Rollback safety impact

n/a

Expected complexity level and risk

1 - Just splitting up CI

Testing

  • 90% just passing through CI making sure the timing is solid
  • Little local run through to make sure ci cargo test is good

@JasonAtClockwork JasonAtClockwork changed the title Jlarabie/shard test suite 2 Split Test Suite steps Sep 2, 2026
@JasonAtClockwork
JasonAtClockwork changed the base branch from master to jlarabie/shard-test-suite September 4, 2026 16:09
@JasonAtClockwork
JasonAtClockwork force-pushed the jlarabie/shard-test-suite-2 branch from dcef84a to 74f0e0c Compare September 4, 2026 18:49
@JasonAtClockwork

Copy link
Copy Markdown
Contributor Author

After doing the work on splitting sdk-test from Test Suite I'm starting to think I should put the sdk-test under the cargo ci test house again but leave it broken apart for CI. That way for local dev work if you want to run it all it's the single command and not two. Thoughts?

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