[SPARK-54835][SQL][TESTS][FOLLOWUP] Drain listener bus before registering listener in test#54397
Closed
cloud-fan wants to merge 1 commit intoapache:masterfrom
Closed
[SPARK-54835][SQL][TESTS][FOLLOWUP] Drain listener bus before registering listener in test#54397cloud-fan wants to merge 1 commit intoapache:masterfrom
cloud-fan wants to merge 1 commit intoapache:masterfrom
Conversation
…stener in test Drain the listener bus before registering the QueryExecutionListener to avoid events from other tests causing flaky failures. Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
Author
pan3793
approved these changes
Feb 20, 2026
dongjoon-hyun
changed the title
Member
|
Merged to master. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
What changes were proposed in this pull request?
This is a followup to #53596. In the test "CTAS/RTAS should trigger two query executions", we drain the listener bus before registering the
QueryExecutionListener, to avoid events from other tests breaking this test with unexpectedexecutionCountincrements.Why are the changes needed?
Without draining the listener bus first, pending events from previous tests could fire after the listener is registered, causing flaky test failures. Other test suites follow this same pattern.
Does this PR introduce any user-facing change?
No. Test-only change.
How was this patch tested?
Existing test.
Was this patch authored or co-authored using generative AI tooling?
Yes.
Made with Cursor