Re: [I] There is something wrong with CI for UT FT other modules [hudi]

["rangareddy (via GitHub)" <gi...@apache.org>]

rangareddy commented on issue #16390:
URL: https://github.com/apache/hudi/issues/16390#issuecomment-5068148012

   This issue was reviewed as part of the JIRA-migrated backlog triage.
   
   Findings: The report captures a single Azure Pipelines failure ('We stopped hearing from agent Azure Pipelines 7'), which is a transient CI agent disconnect (agent terminated / starved for CPU / lost network) rather than a reproducible Hudi code defect. There is no stack trace, no minimal reproduction, and no evidence of a standing/recurring failure condition tied to a specific module or test. The Azure CI definition still exists in master, but a one-off agent timeout is not something that can be reproduced or fixed at the code level from this report.
   
   Could you share whether this is still recurring on current master and, if so, links to recent failing runs (module, test, and frequency)? If we don't hear back in 30 days we'll close this as not reproducible.


-- 
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: commits-unsubscribe@hudi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org