Skip to content

Test scheduling solution stability #5793

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Conversation

rdettai
Copy link
Collaborator

@rdettai rdettai commented Jun 11, 2025

Description

I noticed that sometime the scheduling solution changes when the same problem is solved multiple times. This PR adds a test to ensure that this happens only once and we don't end up with an unstable solution.

How was this PR tested?

This PR doesn't change the logic, only adds tests.

@rdettai rdettai requested a review from fulmicoton-dd June 11, 2025 08:33
@@ -208,6 +208,27 @@ fn assert_enforce_nodes_cpu_capacity_post_condition(
);
}

// ----------------------------------------------------
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

not related to the PR, just moved this up because it was wrongly placed.

Comment on lines +214 to +217
// No need to fill indexer_assignments with empty assignments.
if num_shards == 0 {
return;
}
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

this doesn't change the logic, just ensures a more consistent representation of the state so that we can compare it better in tests.

@rdettai rdettai force-pushed the test-solution-stability branch from 8976249 to 5b9c955 Compare June 11, 2025 08:41
@rdettai rdettai force-pushed the explicit-scheduling-rescaling branch from c065f94 to 1b57434 Compare June 11, 2025 09:20
@rdettai rdettai force-pushed the test-solution-stability branch from 5b9c955 to b62e363 Compare June 11, 2025 09:20
Base automatically changed from explicit-scheduling-rescaling to main June 11, 2025 12:47
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