Skip to content
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

i#7318: Do not propagate idle status on rebalance #7319

Closed
wants to merge 1 commit into from

Conversation

derekbruening
Copy link
Contributor

Rebalancing was propagating an idle status from a runqueue to the caller, where it was treated as an error when it is in fact innocuous.

Adds a unit test that reproduces the error without the fix and passes with the fix.

Fixes #7318

Rebalancing was propagating an idle status from a runqueue to the
caller, where it was treated as an error when it is in fact innocuous.

Adds a unit test that reproduces the error without the fix and passes
with the fix.

Fixes #7318
@derekbruening
Copy link
Contributor Author

This is seemingly hung indefinitely. Closing in favor of clone I made at #7323.

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.

drmemtrace scheduler turns all-blocked runqueue into fatal STATUS_IDLE error
2 participants