Skip to content

Restore dependency-depth build scheduling - #64615

Open
Jake Bailey (jakebailey) wants to merge 2 commits into
microsoft:mainfrom
jakebailey:restore-build-scheduling
Open

Jake Bailey (jakebailey) wants to merge 2 commits into
microsoft:mainfrom
jakebailey:restore-build-scheduling

Conversation

@jakebailey

Copy link
Copy Markdown
Member

#64158 regressed #64220

Parallel builders were consuming reporting order, which can leave a
worker waiting on a dependency while independent projects stay queued.

Project-scoped builds must retain their selected project set, and
reporting must remain stable regardless of worker scheduling.
The scheduling regression needs coverage of full, selected-project, and
references-only builds with two workers. The larger execution-mode
matrix repeats unrelated behavior and obscures that purpose.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🟢 Approval recommended

The focused fix preserves dependency and reporting behavior, with regression coverage for all three build scopes and no identified blockers.

Review effort: Balanced
Findings: None

What changed in this PR

Restores dependency-depth scheduling after the Build Orchestrator API regression, reducing builder idle time while preserving reporting order.

Changes:

  • Schedules full and selected builds by dependency depth.
  • Adds regression coverage for full builds, selected projects, and references-only builds.
File Description
tsc/​internal/​execute/​build/​orchestrator.go Applies dependency-depth scheduling to the selected build tasks.
tsc/​internal/​execute/​build/​graph_test.go Verifies concurrent scheduling, reporting order, and selected outputs.

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.

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

Author: Team For Uncommitted Bug PR for untriaged, rejected, closed or missing bug

Projects

Status: Not started

Development

Successfully merging this pull request may close these issues.

2 participants