Skip to content

Split long-running integ tests to stay under 10 min#8887

Open
licjun wants to merge 1 commit intodevelopfrom
feat/optimize-ci-splits
Open

Split long-running integ tests to stay under 10 min#8887
licjun wants to merge 1 commit intodevelopfrom
feat/optimize-ci-splits

Conversation

@licjun
Copy link
Copy Markdown
Contributor

@licjun licjun commented Apr 2, 2026

Changes

Split two long-running PR integration test configs that were exceeding 10 minutes:

integ-buildcmd-main → integ-buildcmd-python + integ-buildcmd-main

  • Extracted test_build_cmd_python.py (19 tests, 42% of load, 702 lines) into its own integ-buildcmd-python job
  • Remaining integ-buildcmd-main now runs dotnet + provided + rust + node (26 tests)

integ-all-other → integ-local + integ-all-other

  • Extracted tests/integration/local (413 tests, 82% of load) into its own integ-local job
  • Remaining integ-all-other now runs init + pipeline + root + scripts + telemetry + docs (89 tests)

Before

Job Time
integ-buildcmd-main ubuntu 3.11 12m 42s
integ-buildcmd-main ubuntu 3.10 11m 37s
integ-buildcmd-main windows 3.11 15m 54s
integ-buildcmd-main windows 3.10 14m 58s
integ-all-other windows 3.11 11m 8s
integ-all-other windows 3.10 12m 15s

Expected After

All split jobs should complete within 10 minutes.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

- Split integ-buildcmd-main: extract python tests (19 tests, 42% of load) into integ-buildcmd-python
- Split integ-all-other: extract local tests (413 tests, 82% of load) into integ-local
@licjun licjun requested a review from a team as a code owner April 2, 2026 17:39
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