Coverity analysis failing
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 542
- Forks
- 185
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 4
Description
Since moving the Coverity builds over to the Ubuntu 24.04 Hetzner machines, analysis at https://scan.coverity.com/projects/node-js has been failing.
The Jenkins build succeeds. We are running a newer version of the Coverity build tool on the new machines, so it might be related to that.
I've updated the PATH setting in the job and am rerunning: https://ci.nodejs.org/job/node-daily-coverity/3697/
Hmm. This succeeded and submitted the build, but the analysis on https://scan.coverity.com/projects/node-js has failed:
Last Build Status: Failed. Your build has failed due to the following reason. Please fix the error and upload the build again.
Error details: The build uploaded has been only partially compiled. We recommend at least 85% capture success to avoid false-positives during analysis. As per cov-int/build-log.txt, the percentage of compilation units ready for analysis is 75% which is less than the expected 85%...more
Originally posted by @richardlau in #4144
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Jenkins job linked in the issue and inspect cov-int/build-log.txt for the compilation units missed by Coverity. Compare the Ubuntu 24.04 machine setup and newer Coverity build tool with the prior environment. Done means the build reaches at least 85% capture success and the uploaded analysis succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ubuntu
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100