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

   ### What problem does this PR solve?
   
   Issue Number: N/A
   
   Related PR: N/A
   
   Problem Summary:
   
   The regression case can overlap with a dynamic-partition scheduler run that 
was started while the global interval was one second. Restoring the interval to 
600 seconds does not cancel that in-flight run. If it drops the out-of-range 
`p1900` partition while the multi-row INSERT is committing, the INSERT can fail 
even though the scheduler reached its intended final state.
   
   The prior workaround depended on an exact exception message and issued `show 
partitions` inside a `TestAction` check closure. That nested DSL call changes 
the action current SQL, making the failure report and its string-based 
classification brittle.
   
   This change drains the likely preceding short-interval run before INSERT, 
captures the INSERT exception without nested DSL calls, and tolerates only the 
known terminal state: `p1900` is absent while the `2024`, `2900`, and `3000` 
auto-created partitions remain. All other failures still fail the case. The 
intentional one-second cleanup interval is restored to 600 seconds in `finally`.
   
   ### Release note
   
   None.
   
   ### Check List (For Author)
   
   - Test: Regression test
     - `./run-regression-test.sh --run -f 
regression-test/suites/partition_p0/auto_partition/test_auto_dynamic.groovy 
--times 3` (run twice; 6/6 passes)
   - Behavior changed: No product behavior; narrows regression-case tolerance 
to the known scheduler race.
   - 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