Perform CodeQL Analysis throwing Error " Exit code was 32 and last log line was: CodeQL detected code written in Java/Kotlin but could not process any of it."

[MXR707]

Perform CodeQL Analysis

Question

Body

Error: Encountered a fatal error while running "/__w/_tool/CodeQL/2.16.3/x64/codeql/codeql database finalize --finalize-dataset --threads=4 --ram=14565 /__w/xxxxxxSearch/xxxxxSearch/codeql_dbs/java". Exit code was 32 and last log line was: CodeQL detected code written in Java/Kotlin but could not process any of it. Review our troubleshooting guide at https://gh.io/troubleshooting-code-scanning/no-source-code-seen-during-build . See the logs for more details.
Could not determine current commit SHA using git. Continuing with data from user input or environment.

steps:
- name: Checkout repository
uses: actions/checkout@v2

# Initializes the CodeQL tools for scanning.
- name: Initialize CodeQL
  uses: github/codeql-action/init@v2
  with:
    languages: ${{ matrix.language }}
    db-location: '${{ github.workspace }}/codeql_dbs'
- name: Build code
    run: |
      rm -f wcbd-deploy-server-local-search-*.zip || true
        mkdir -p /code_repository/search/workspace/
        cp -r ${GITHUB_WORKSPACE}/search-config-ext /code_repository/search/workspace/
        cd /opt/WebSphere/CommerceServer90/wcbd/
        ./wcbd-ant -buildfile wcbd-build.xml -Dbuild.type=local -Dapp.type=search -Dbuild.label=1234
  - name: Perform CodeQL Analysis
    uses: github/codeql-action/analyze@v2
    with:
      category: "/language:${{matrix.language}}"

[jketema]

Hi @MXR707,

Thanks for your question. Would you be willing to share the logs produced by CodeQL? Without those, it is not really possible to determine with things are failing. If sharing those is not possible, you might want to have a look at them yourself, to see if you can find any suspicious in them.

[MXR707]

Hello @jketema
Please find the log for "Perform CodeQL Analysis"

[jketema]

Hi. This looks like the output of the workflow run on GH actions. Is that correct?

[MXR707]

yes that's correct.

[jketema]

Apologies for not being clear enough in that case. What I'm interested in is the logs that are included in the debug artifacts. How to get those is described here: https://docs.github.com/en/code-security/code-scanning/troubleshooting-code-scanning/logs-not-detailed-enough.

Note that those logs may contain sensitive information, so you might want to scrutinise them closely and sensor them before sharing them here. Alternatively, and assuming you're a customer paying for GitHub advanced security, you could open a support ticket and share the logs privately. How to contact support is described here: https://docs.github.com/en/support/contacting-github-support.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬