[
https://issues.apache.org/jira/browse/CALCITE-6865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17931282#comment-17931282
]
Alessandro Solimando edited comment on CALCITE-6865 at 2/27/25 8:00 PM:
------------------------------------------------------------------------
Fixed via
[{{85f8872}}|https://github.com/apache/calcite/commit/85f8872b7f6fc661c3d7ee8f04ab2aea49279ec1],
thanks [~mbudiu] [~nobigo] [~caicancai] [~suibianwanwan] for your reviews!
was (Author: asolimando):
Fixed via
[{{85f8872}}|https://github.com/apache/calcite/commit/85f8872b7f6fc661c3d7ee8f04ab2aea49279ec1],
thanks [~mbudiu] [~nobigo] [~caicancai] [~suibianwanwan] for your reviews!
> Sonar analysis fails due to OOM
> -------------------------------
>
> Key: CALCITE-6865
> URL: https://issues.apache.org/jira/browse/CALCITE-6865
> Project: Calcite
> Issue Type: Task
> Components: build
> Affects Versions: 1.38.0
> Reporter: Alessandro Solimando
> Assignee: Alessandro Solimando
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.39.0
>
>
> Sonar is again failing exactly as in CALCITE-6484,
> [here|https://ci-builds.apache.org/job/Calcite/job/Calcite-sonar/job/PR-4204/9/cloudbees-pipeline-explorer/]
> an example of failure in CI.
> A wild guess is that we keep adding code and complexity to the codebase, so
> Sonar resources increase over time, but I don't have any precise RCA.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
