airborne12 commented on PR #62181:
URL: https://github.com/apache/doris/pull/62181#issuecomment-4204596659

   ## CI Pipeline Failure Analysis
   
   ### 1. CloudP0 (build 923092) — Test Race Condition
   
   **Failed test:** `test_drop_index_on_partition` — the test introduced in 
this PR has a race condition in cloud mode.
   
   **Root cause:** In the test's NGRAM_BF section, 
`build_index_on_table("idx_ngram", tableName4)` is called immediately after 
`CREATE INDEX ... USING NGRAM_BF`. However:
   
   1. In cloud mode, `CREATE INDEX ... USING NGRAM_BF` creates an **async 
schema change job** (not a lightweight index change)
   2. The helper `build_index_on_table` (in `plugin_index_change.groovy`) runs 
`BUILD INDEX ON <table>` without specifying the index name in cloud mode
   3. `BuildIndexOp.validate()` iterates `table.getTableIndexes()` to discover 
indexes, but the NGRAM_BF index hasn't been added yet (schema change still in 
progress, only ~3ms gap)
   4. Result: `Index[] is not exist in 
table[test_drop_idx_on_partition_non_inverted]`
   
   **FE log evidence (timestamps):**
   ```
   12:10:22.175 — CREATE INDEX idx_ngram NGRAM_BF → SCHEMA_CHANGE job created
   12:10:22.178 — Schema change job registered (async)
   12:10:22.181 — BUILD INDEX ON table → FAILS (index not yet in table metadata)
   12:10:22.440 — Schema change job starts processing
   12:10:23.941 — Schema change job finishes
   ```
   
   **Fix:** Add `wait_for_last_col_change_finish(tableName4, timeout)` between 
`CREATE INDEX ... USING NGRAM_BF` and `build_index_on_table()` in the 
non-inverted index test section, so the schema change completes before BUILD 
INDEX runs.
   
   ### 2. Coverage FE (build 923248) — Infrastructure Issue
   
   Docker container exited with code 8 during `build.sh --fe` (ran only 27 
seconds). This is a CI infrastructure failure, not a code issue. Retry should 
resolve it.


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