Caideyipi commented on PR #19051:
URL: https://github.com/apache/iotdb/pull/19051#issuecomment-6598065285

   CI failure investigation for [job 
125682983290](https://github.com/apache/iotdb/actions/runs/41564560556/job/125682983290),
 run at `f680cfa4de6abd506d80c2d02439d3b58042a074`.
   
   The reported failures come from test preconditions. Commit 
`8fdf070a2cc12653d2f1c3d7da4babe22c40f787` fixes them:
   
   - Wait for the initial row at every DataNode before injecting the live-node 
metadata fault. IoTConsensus replication is asynchronous; the original 
immediate assertion raced replication.
   - Check that existing tables retain their creation-time TTL after a database 
TTL change, then explicitly change the table TTL. The test still verifies 
expired-read filtering, the overridden table, and recovered-node write 
rejection after a missed broadcast.
   - Keep the auto-sync recovery reproducer with an explicit skip reason and 
reference to #18874 and `IoTDBTreeToTableViewAutoSyncIT`. `auto_sync_schema` is 
currently absent from `TABLE_ALLOWED_PROPERTIES`, and the existing auto-sync 
cases are also ignored. This recovery scenario remains a coverage gap until 
that feature is enabled.
   
   Validation on Apache IoTDB with JDK 17 and `TableClusterIT`:
   
   - Spotless, `git diff --check`, and the IT selection/shard check passed.
   - Required IoTDB dependencies were built from clean source. The P0 recovery 
class passed all 9 tests; a focused rerun of the changed P0 method also passed. 
The P0 code is identical in the final commit.
   - The final TTL method passed at `8fdf070a2cc12653d2f1c3d7da4babe22c40f787` 
(1 test, 0 failures/errors/skips; Maven exit 0). The auto-sync method is 
intentionally ignored; it was skipped in the earlier class run. Other PR suites 
were not rerun in this investigation.
   
   An additional potential kernel issue surfaced while testing `ALTER TABLE 
inherited SET PROPERTIES ttl=DEFAULT` after changing the database TTL from 
seven days to one day: `SHOW TABLES` reported one day, while a query still 
returned two-day-old data. That reset/default propagation path needs separate 
investigation; production code is unchanged.
   
   Reviewed PR head: `339f1074518b0a611f86f9a094250b62a8e86942` (after the 
original failed run). Final local commit and confirmed source-branch/PR head: 
`8fdf070a2cc12653d2f1c3d7da4babe22c40f787`. The update is pushed. The PR 
remains a draft pending an independent review of the complete current diff.
   


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

Reply via email to