[ 
https://issues.apache.org/jira/browse/HIVE-29180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18018310#comment-18018310
 ] 

Stamatis Zampetakis commented on HIVE-29180:
--------------------------------------------

I run the Sonar analysis locally and published the new scan for the master 
branch (https://sonarcloud.io/summary/new_code?id=apache_hive&branch=master) a 
few minutes ago. This should mitigate the problem till new commits start 
landing on master. I haven't reproduced the problem locally so still not sure 
why it fails with OOM on CI, I will keep looking.

> SonarQube reports issues unrelated to changes in the pull request
> -----------------------------------------------------------------
>
>                 Key: HIVE-29180
>                 URL: https://issues.apache.org/jira/browse/HIVE-29180
>             Project: Hive
>          Issue Type: Bug
>          Components: Build Infrastructure
>            Reporter: Stamatis Zampetakis
>            Assignee: Stamatis Zampetakis
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: sonarqube-bad-report.png
>
>
> SonarQube runs on every pull request and performs static code analysis 
> notifying contributors and reviewers about potential issues in the code.
> Lately, SonarQube started reporting way too many issues that are clearly 
> unrelated to the changes in the pull request and this seems to affect every 
> new PR that is submitted on GitHub.
> One such example can be seen in:
> https://github.com/apache/hive/pull/6049#issuecomment-3237772048
> The problem was first reported in the dev list:
> https://lists.apache.org/thread/m36fc3dldd23nj8mncdjmzx33k87flm5



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to