Skip to content

Conversation

@eshishki
Copy link
Contributor

@eshishki eshishki commented Jan 5, 2026

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

  • ResourceGroupUsageRecorderTest: save/restore original workgroup_manager, call start()
  • PipeLineFileScanNodeTest: add missing set_workgroup() call

What type of PR is this:

  • BugFix
  • Feature
  • Enhancement
  • Refactor
  • UT
  • Doc
  • Tool

Does this PR entail a change in behavior?

  • [] Yes, this PR will result in a change in behavior.
  • No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

  • Interface/UI changes: syntax, type conversion, expression evaluation, display information
  • Parameter changes: default values, similar parameters but with different default values
  • Policy changes: use new policy to replace old one, functionality automatically enabled
  • Feature removed
  • Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

  • I have added test cases for my bug fix or my new feature
  • This pr needs user documentation (for new or modified features or behaviors)
    • I have added documentation for my new feature or new function
    • This pr needs auto generate documentation
  • This is a backport pr

Bugfix cherry-pick branch check:

  • I have checked the version labels which the pr will be auto-backported to the target branch
    • 4.1
    • 4.0
    • 3.5
    • 3.4
    • 3.3

Note

Ensures test isolation and proper workgroup setup to avoid nullptr crashes across tests.

  • ResourceGroupUsageRecorderTest: replace exec_env._workgroup_manager with a started instance, then restore the original at the end
  • PipeLineFileScanNodeTest: call _fragment_ctx->set_workgroup(ExecEnv::GetInstance()->workgroup_manager()->get_default_workgroup()) in SetUp()

Written by Cursor Bugbot for commit 0545875. This will update automatically on new commits. Configure here.

ResourceGroupUsageRecorderTest was replacing the global workgroup_manager
without calling start(), leaving driver_executor as nullptr. This caused
subsequent tests (test_two_operatories, PipeLineFileScanNodeTest) to crash
when run in the same process without gtest-parallel isolation.

Changes:
- Save and restore original workgroup_manager in ResourceGroupUsageRecorderTest
- Call start() on the new workgroup_manager to initialize executors
- Add set_workgroup() call in PipeLineFileScanNodeTest setup

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <[email protected]>
@eshishki eshishki force-pushed the fix/test-isolation-workgroup-manager branch from ffebe53 to 0545875 Compare January 5, 2026 14:54
@github-actions
Copy link
Contributor

github-actions bot commented Jan 5, 2026

[Java-Extensions Incremental Coverage Report]

pass : 0 / 0 (0%)

@github-actions
Copy link
Contributor

github-actions bot commented Jan 5, 2026

[FE Incremental Coverage Report]

pass : 0 / 0 (0%)

@github-actions
Copy link
Contributor

github-actions bot commented Jan 5, 2026

[BE Incremental Coverage Report]

pass : 0 / 0 (0%)

@alvin-celerdata
Copy link
Contributor

@cursor review

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

✅ Bugbot reviewed your changes and found no bugs!

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.

2 participants