Out of memory or error waiting for container

image: php:7.4-fpm # Choose an image matching your project needs

clone:
      depth: full              # SonarCloud scanner needs the full history to assign issues properly

definitions:
  
  caches:
    sonar: ~/.sonar/cache  # Caching SonarCloud artifacts will speed up your build
  
  steps:
    
    - step: &build-test-sonarcloud
        size: 2x # Double resources available for this step.
        name: Build, test and analyze on SonarCloud
        caches:
          - sonar
        script:
          - pipe: sonarsource/sonarcloud-scan:1.2.1
    
    - step: &check-quality-gate-sonarcloud
        name: Check the Quality Gate on SonarCloud
        script:
          - pipe: sonarsource/sonarcloud-quality-gate:0.1.3

pipelines:                 

  custom:
    run-build-test-sonarcloud:
      - step: *build-test-sonarcloud

This is the Bitbucket Pipeline I am using
PHP is language SonarCloud is scaning

As you see, I’ve tried to double bb container, but it is still failing with out of memory error or waiting for container.
Can any one help ?
pipelineLog-565.txt (10.4 KB) pipelineLog-566.txt (10.4 KB)

Hi @aca-mlstx and welcome to our Community!

We need more details about this issue. Could you please enable debug mode and re-run the analysis, finally uploading the full log here?

To enable debug mode, please update your pipeline like this:

    - step: &build-test-sonarcloud
        size: 2x # Double resources available for this step.
        name: Build, test and analyze on SonarCloud
        caches:
          - sonar
        script:
          - pipe: sonarsource/sonarcloud-scan:1.0.1
            variables:
              DEBUG: "true"

Alexandre, Hello once again. Is there any chance you can take a look ?
Maybe not to upload complete debug online ?
I had upload it, but removed, I can send you in PM

Hi @aca-mlstx, yes could you please send it to me by PM? Thanks!

Seams when I upload file, it does not do a reply.
Please take a look at this file.
Thanks

Hi @aca-mlstx, we are investigating your issue and will update here when some news are available.

Thanks Alex, any idea how long this can take? Is it something that we can say in a week it will be fixed? We tried to change config on our side a couple of times with no success, and we are still paying but unable to process our repositories.

@aca-mlstx, can you please have a look on this related thread an configure the memory for the Docker process instead?

2 Likes

That solved the issue ! Many thanks.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.