chore: updated memory for sonar#2619
Draft
aryamohanan wants to merge 3 commits into
Draft
Conversation
aryamohanan
force-pushed
the
chore-sonar-mem
branch
from
ad7e0d3 to
6734c1c
Compare
aryamohanan
force-pushed
the
chore-sonar-mem
branch
from
6734c1c to
0d1be89
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We're seeing an issue with SonarCloud coverage. PRs that have coverage enabled may fail with the following error:
The bridge server is unresponsive. It might be because you don't have enough memory.Increases the memory available to the SonarCloud analysis step by:
Increasing the pod memory request to 6 GiB.
Setting NODE_OPTIONS=--max-old-space-size=6144 to increase the maximum heap size available to the Node.js process used by the Sonar scanner.
Setting SONAR_SCANNER_OPTS=-Xmx4g to increase the JVM heap size available to the Sonar Scanner.
These changes are intended to prevent out-of-memory conditions during analysis and improve the reliability of SonarCloud coverage processing.