CritasWang commented on PR #18987:
URL: https://github.com/apache/iotdb/pull/18987#issuecomment-6356679999

   The failing **SonarCloud Code Analysis** check is not caused by this PR.
   
   - None of the reliability issues it reports are in files this PR changes. 
They are in master code merged after Sonar's last master analysis, for example 
`AlignedChunkData.java:466` (#18901), `DataNodeTableCache.java:426` (#18874) 
and `MemoryPool.java:565` (#18869). Because this branch now contains those 
commits, Sonar counts them as "new code" for this PR.
   - The master baseline on SonarCloud is still at `212214e6ae` (2026-10-22 
03:49 UTC). Since then, every master `Sonar-Codecov` run has been cancelled by 
a newer push or has failed in the `SonarCloud Report` step with `Java heap 
space` during the full DataNode analysis (e.g. runs 39753280297 and 
39890634961). The sonar job does not set `MAVEN_OPTS`, so it runs on the 
default heap.
   - #18833 and #18962 fail the same gate for the same reason.
   
   All other checks pass. Once a master Sonar analysis succeeds again, 
re-running the `sonar` job here should clear the gate.
   


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