[BugFix] test isolation workgroup manager #67489
Open
+8
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fix test isolation issues introduced in #66690 and #63956.
When tests run in the same process (without gtest-parallel),
ResourceGroupUsageRecorderTest replaces workgroup_manager without calling
start(), leaving driver_executor as nullptr. This causes subsequent tests
to crash with nullptr dereference.
Changes
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist:
Bugfix cherry-pick branch check:
Note
Ensures test isolation and proper workgroup setup to avoid nullptr crashes across tests.
exec_env._workgroup_managerwith a started instance, then restore the original at the end_fragment_ctx->set_workgroup(ExecEnv::GetInstance()->workgroup_manager()->get_default_workgroup())inSetUp()Written by Cursor Bugbot for commit 0545875. This will update automatically on new commits. Configure here.