chore: updated memory for sonar#2619
Merged
Merged
Conversation
aryamohanan
force-pushed
the
chore-sonar-mem
branch
5 times, most recently
from
June 30, 2026 04:42
0d1be89 to
b06af05
Compare
abhilash-sivan
approved these changes
Jul 1, 2026
abhilash-sivan
left a comment
abhilash-sivan
left a comment
Contributor
There was a problem hiding this comment.
LGTM. Shall we merge this and unblock PR pipeline ? Or we can remove sonar scanning till this gets sorted!
aryamohanan
force-pushed
the
chore-sonar-mem
branch
from
July 3, 2026 06:57
b06af05 to
61b054b
Compare
kirrg001
reviewed
Jul 9, 2026
| - name: print-all-results | ||
| image: public.ecr.aws/docker/library/node:$(params.node-version) | ||
| imagePullPolicy: IfNotPresent | ||
| resources: |
Contributor
There was a problem hiding this comment.
Did you try it without?
Because AFAIK this is only to reserve a certain amount when the container starts.
I expected that
"--max-old-space-size=6144"
^ this config will be enough
Contributor
Author
There was a problem hiding this comment.
Yeah, it worked without allocating resources
aryamohanan
force-pushed
the
chore-sonar-mem
branch
from
July 10, 2026 13:34
61b054b to
c020389
Compare
kirrg001
approved these changes
Jul 13, 2026
aryamohanan
force-pushed
the
chore-sonar-mem
branch
from
July 14, 2026 03:33
2307fa1 to
9439cb6
Compare
aryamohanan
force-pushed
the
chore-sonar-mem
branch
from
July 14, 2026 03:34
9439cb6 to
408e1b6
Compare
aryamohanan
marked this pull request as ready for review
July 14, 2026 08:50
aryamohanan
commented
Jul 14, 2026
kirrg001
approved these changes
Jul 14, 2026
aryamohanan
commented
Jul 14, 2026
aryamohanan
commented
Jul 14, 2026
|
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
3 participants
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.