My first analyses has failed when added project Analysis ID "38152260-0ab1-4a18-846f-1f2371079b5f"

SonarQube Cloud
23

Hi,

Can we see that log?

How are you passing the debug parameter?

 
Thx,
Ann

24

I re-run using github actions interface:

Screenshot 2025-02-10 at 12.56.03
Screenshot 2025-02-10 at 12.56.031282×428 24.8 KB

I’ll send a log when it succeeded and when it failed.

Here it is when when it failed before removing c and cpp files:
logs_34094501483.zip (3.5 MB)

And here it is when it succeeded, using debug logging from github:
logs_34172687235.zip (3.4 MB)

Here it is when I run without debug logging:

Run SonarSource/sonarqube-scan-action@v4
  with:
    scannerVersion: 6.2.1.4610
    scannerBinariesUrl: https://binaries.sonarsource.com/Distribution/sonar-scanner-cli
  env:
    SONAR_TOKEN: ***
Run ${GITHUB_ACTION_PATH}/scripts/sanity-checks.sh
  ${GITHUB_ACTION_PATH}/scripts/sanity-checks.sh
  shell: /bin/bash --noprofile --norc -e -o pipefail {0}
  env:
    SONAR_TOKEN: ***
    INPUT_PROJECTBASEDIR: 
Run actions/cache@v4
  with:
    path: /Users/runner/work/_temp/sonar-scanner-cli-6.2.1.4610-macOS-ARM64
    key: sonar-scanner-cli-6.2.1.4610-macOS-ARM64
    enableCrossOsArchive: false
    fail-on-cache-miss: false
    lookup-only: false
    save-always: false
  env:
    SONAR_TOKEN: ***
    SEGMENT_DOWNLOAD_TIMEOUT_MINS: 1
Received 8388608 of 42524401 (19.7%), 8.0 MBs/sec
Cache Size: ~41 MB (42524401 B)
/opt/homebrew/bin/gtar -xf /Users/runner/work/_temp/7cb9fbd6-11dd-42c8-b862-40e20636c147/cache.tzst -P -C /Users/runner/work/app-inpeaceapp-ios/app-inpeaceapp-ios --delay-directory-restore --use-compress-program unzstd
Cache restored successfully
Cache restored from key: sonar-scanner-cli-6.2.1.4610-macOS-ARM64
Run echo "${RUNNER_TEMP}/sonar-scanner-cli-6.2.1.4610-macOS-ARM64/bin" >> $GITHUB_PATH
  echo "${RUNNER_TEMP}/sonar-scanner-cli-6.2.1.4610-macOS-ARM64/bin" >> $GITHUB_PATH
  shell: /bin/bash --noprofile --norc -e -o pipefail {0}
  env:
    SONAR_TOKEN: ***
Run ${GITHUB_ACTION_PATH}/scripts/run-sonar-scanner-cli.sh 
  ${GITHUB_ACTION_PATH}/scripts/run-sonar-scanner-cli.sh 
  shell: /bin/bash --noprofile --norc -e -o pipefail {0}
  env:
    SONAR_TOKEN: ***
    INPUT_PROJECTBASEDIR: 
    SONAR_SCANNER_JRE: /Users/runner/work/_temp/sonar-scanner-cli-6.2.1.4610-macOS-ARM64/jre
/Users/runner/work/_actions/SonarSource/sonarqube-scan-action/v4/scripts/run-sonar-scanner-cli.sh: line 80: scanner_args[@]: unbound variable
Error: Process completed with exit code 1.

Screenshot 2025-02-10 at 13.02.02
Screenshot 2025-02-10 at 13.02.022155×1183 271 KB

25

Hi,

Thanks for trying this. I think the debug parameter is providing an argument to the underlying script and that’s why that one works.

I’m not actually able to read your logs. I get a null-byte warning, and they both end abruptly in the same place.

And I’m going to flag this for more expert eyes.

 
Ann

27

Thanks Ann, I’ll be waiting for further feedback then!

29

Hello @TadashiY,

I was able to reproduce the problem, and it seems to be limited to the macos runners. Until we are able to resolve it, can you try replacing macos-latest with ubuntu-latest in your build.yaml file, and let us know if that fixes the problem?

Hope this helps! :crossed_fingers:

Aleksandra

30

Sharing an update - we have created a ticket to tackle this issue when we have some availability. Thanks for reporting it and feel free to follow the progress on the ticket.

Regarding my previous message, if the suggestion does not fix the issue, I would suggest running analyses with the debug logs enabled until a fix becomes available.

Thanks!

33

Hello, I’m facing the same issue on macos runners and due to the fact we’re working on a Swift project we can’t switch to ubuntu. Our company has adopted SonarQube Cloud throughout all repositories so that makes it even worse for us. Is there any rough estimation on when there will be a fix?