This is an automated email from the ASF dual-hosted git repository.

dataroaring pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris.git


The following commit(s) were added to refs/heads/master by this push:
     new 4352eee1d00 [fix](test) Try to fix possible -238 in 
test_non_overlap_seg_heavy_sc (#58333)
4352eee1d00 is described below

commit 4352eee1d007429a423976d1ba617960e183f936
Author: Siyang Tang <[email protected]>
AuthorDate: Thu Dec 4 16:11:01 2025 +0800

    [fix](test) Try to fix possible -238 in test_non_overlap_seg_heavy_sc 
(#58333)
    
    ### What problem does this PR solve?
    
    Problem Summary:
    
    Success Rate: 95.5% in test_non_overlap_seg_heavy_sc, the rest 0.05%
    fail because -238 may happend due to the large number of segment and not
    in time segcompaction. Try to reduce some segment, but not too much to
    ensure this case can trigger a certain path in vmerge iterator.
---
 .../suites/schema_change_p0/test_non_overlap_seg_heavy_sc.groovy        | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/regression-test/suites/schema_change_p0/test_non_overlap_seg_heavy_sc.groovy 
b/regression-test/suites/schema_change_p0/test_non_overlap_seg_heavy_sc.groovy
index 9e5f716f06d..7707f5e79f5 100644
--- 
a/regression-test/suites/schema_change_p0/test_non_overlap_seg_heavy_sc.groovy
+++ 
b/regression-test/suites/schema_change_p0/test_non_overlap_seg_heavy_sc.groovy
@@ -40,7 +40,7 @@ suite("test_non_overlap_seg_heavy_sc", "nonConcurrent") {
     GetDebugPoint().clearDebugPointsForAllBEs();
     GetDebugPoint().enableDebugPointForAllBEs("MemTable.need_flush");
     try {
-        sql """ INSERT INTO ${tblName} select number, number, number from 
numbers("number" = "3240960") """
+        sql """ INSERT INTO ${tblName} select number, number, number from 
numbers("number" = "1240960") """
 
         sql """ DELETE FROM ${tblName} WHERE v2 = 24 """
 


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

Reply via email to