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

   ### What problem does this PR solve?
   
   Issue Number: None
   
   Related PR: None
   
   Problem Summary:
   
   `test_changelog_rowset_tso_pruning` obtains second-granularity boundaries 
from `NOW()` and immediately starts the next batch of writes. TSO physical time 
advances asynchronously, so a subsequent transaction can still receive a TSO 
below the boundary despite the preceding 1.2-second sleep.
   
   In [build 1094305](http://43.132.222.7:8111/viewLog.html?buildId=1094305), 
the insertion of `(5, 50)` committed at `05:13:26.034`, but its TSO physical 
time was `05:13:25.988`. The DETAIL query ending at `05:13:26` therefore 
correctly returned that row and failed the expected-result comparison.
   
   Derive each boundary from the current TSO's next whole second and poll 
`information_schema.tso_status` until it reaches that boundary. Use current TSO 
in local mode and committed TSO in cloud mode, following the existing changelog 
test pattern. Format the boundary on FE to preserve its timezone. The existing 
expected results remain unchanged.
   
   ### Release note
   
   None
   
   ### Check List (For Author)
   
   - Test: Manual validation
       - Groovy syntax compilation of the modified suite using 
`org.codehaus.groovy.tools.FileSystemCompiler`: passed.
       - `git diff --check`: passed.
       - Cluster regression was not run: the available FE/BE binaries were 
built from other branches.
   - Behavior changed: No (regression-test synchronization only).
   - 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