Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Coverity analysis failing

未关闭
#4,287 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
38/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
冷清
技术栈
ubuntu
领域
ci-cd, devops

调研方向

从 issue 中链接的 Jenkins job 开始,检查 cov-int/build-log.txt,找出 Coverity 遗漏的编译单元。将 Ubuntu 24.04 机器的设置和较新的 Coverity build tool 与之前的环境进行比较。当构建达到至少 85% 的 capture success 且上传的分析成功时,即视为完成。

由索引模型根据 Issue 内容生成。

描述

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

主要语言
Jinja
星标
541
派生
185
平均合并
2 天 18 小时
30 天内合并 PR
6

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

nodejs/build 的其他 Issue

查看 nodejs/build 的全部 Issue

相似的 Issue

更多 DevOps Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。