bosswnx commented on PR #67404:
URL: https://github.com/apache/doris/pull/67404#issuecomment-5504655179

   The NonConcurrent Regression failure on this PR is **not caused by this 
change** — it is a pre-existing BE crash on master, now tracked in #67428.
   
   Evidence:
   
   1. This PR is test-only (2 FE assertion updates, zero BE changes), yet the 
regression died with a BE ASAN heap-use-after-free in 
`SharedMemtable::~SharedMemtable` → 
`RowsetWriterContext::remove_segment_allocated_lsns` (group-commit memtable 
flush path, code introduced by #66889).
   2. **PR #67402 — an unrelated test-only PR from another author, based on the 
same master window — hit the byte-for-byte identical crash** (TeamCity build 
1036154 vs. ours 1035988, same stack, same lines).
   3. Timeline: all nonConcurrent runs before Sep 1 16:25 (UTC+8) passed; the 
two runs after #66191/#66899 merged on master both crashed. The UAF was 
introduced Aug 27 (#66889) and became reproducible on the new base.
   
   The cascade of ~49 suite failures is downstream of the BE exit ("available 
backend num is 0"), not separate issues.
   
   Given the above, the NonConcurrent pipeline should fail for any PR based on 
current master. A re-run will hit the same crash until the upstream fix in 
#67428 lands — happy to help there. Everything else on this PR is green: FE UT 
pass, CheckStyle pass, P0 Regression pass, External Regression pass.
   


-- 
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