924060929 opened a new pull request, #69894:
URL: https://github.com/apache/doris/pull/69894

   ### What problem does this PR solve?
   
   Issue Number: N/A
   
   Problem Summary:
   
   Two FE unit tests depend on asynchronous work without owning its complete 
lifecycle:
   
   - 
`SplitProducerTest.readThatOutlivesItsStatementLoadsNothingIntoTheClosedScope` 
waits for the source-close signal and immediately checks the producer 
completion count. `SplitProducer.finish` invokes the completion callback after 
closing the source, so the assertion can run before that callback. Wait for the 
assignment termination future, which completes after both cleanup and the 
callback.
   - `StmtExecutorTest.testSuccessfulRetryRendersMergedProfileAndActualRows` 
registers its profile with the global background `ProfileManager` while also 
writing and reading the profile synchronously. Use a real manager whose daemon 
is not started, scoped to this test, so automatic spill, memory release and 
archival cannot interfere with the temporary storage lifecycle. Preserve the 
real persistence path and all merged-profile and actual-row assertions, and 
include the readback content in the failing assertion.
   
   The tests originated in #69718 and #68658 respectively. These test-only 
changes are independent of the Coordinator refactoring in #69830. The exact CI 
interleaving was not reproduced locally; both original tests also passed local 
repeated execution. No production behavior changes.
   
   ### Release note
   
   None
   
   ### Check List (For Author)
   
   - Test: Both affected classes passed with each target case repeated 50 times 
(179 executions total) before extraction; FE Checkstyle (0 violations). 
Validation on the independent master-based branch is in progress.
   - Behavior changed: No
   - Does this need documentation: No
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to