ci: give the Coverity scan enough CPU and memory to run in parallel

[orbalayla-nvidia]

Summary

The cloudai-ci-coverity job takes 23-35 minutes. Almost all of it is cov-analyze: under the 4Gi memory limit it logs

Using 4 workers as limited by CPU(s)
Revising to 1 worker due to memory constraints.

and analyzes single-threaded. The 4 CPU/1Gi/4Gi values were carried over from the release pipeline in #1075.

cov-analyze runs one worker per CPU, and each worker needs its own memory. This raises the Coverity container to requests: {memory: 4Gi, cpu: 1000m}, limits: {memory: 32Gi, cpu: 8000m}, so it runs 8 workers. Requests stay small, so the pod still schedules easily.

Test Plan

Ran cloudai-ci-coverity on the same code with each setting. Some runs happened at the same time as 4Gi PR runs; the node kernel shows which kind of node each run landed on:

Build	Limits	Node kernel	Workers	cov-analyze	Whole job	Defects
#22	4 CPU / 4Gi	5.4	1	21:54	23.4 min	0
#23	4 CPU / 4Gi	5.15	1	32:18	33.8 min	0
#26	4 CPU / 8Gi	5.4	3	7:27	10.2 min	0
#24	4 CPU / 16Gi	5.4	4	6:27	8.5 min	0
#21	4 CPU / 16Gi	5.15	4	6:30	10.1 min	0
#25	4 CPU / 16Gi	5.15	4	9:54	12.3 min	0
#30	8 CPU / 32Gi	5.15	8	4:35	5.5 min	0
#31	8 CPU / 32Gi	5.15	8	4:35	5.7 min	0

Every earlier 4Gi run (#1-#20) also revised to 1 worker. The amount scanned stays the same: about 40.8k-41.0k paths over 5.5k functions in every run.

Additional Notes

The release pipeline's Coverity stage uses the same 4 CPU/4Gi limits and probably has the same slowdown. That pipeline is not changed here.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Repository: NVIDIA/cloudai/.coderabbit.yaml
• Review profile: ASSERTIVE
• Plan: Enterprise
• Run ID: 34a5c9f5-415a-47ec-b1a5-1825627b16ab

📥 Commits

Reviewing files that changed from the base of the PR and between 8946293 and 8f1ce51.

📒 Files selected for processing (1)

• .ci/pipeline/coverity_matrix.yaml

Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 11 remain after this review.

---

📝 Walkthrough

Walkthrough

The Coverity pipeline comment now describes the toolbox image and tag as matching the release pipeline. Container memory requests and CPU and memory limits have increased.

Changes

Coverity scan resources

Layer / File(s)	Summary
Update Coverity container resources .ci/pipeline/coverity_matrix.yaml	The comment describes the toolbox image and tag as matching the release pipeline and states that the increased limits support 8 workers. The memory request changed from 1Gi to 4Gi. The CPU limit changed from 4000m to 8000m, and the memory limit changed from 4Gi to 32Gi.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~5 minutes

Change: Bug fix

Suggested reviewers: podkidyshev

Merge Risk: ⚪ Minimal · up to 8f1ce

The Coverity scan receives the increased resources described. No concrete operational or user-facing failure is established, so the change appears ready to merge subject to normal checks.

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: increasing CPU and memory resources so the Coverity scan can run in parallel.
Description check	✅ Passed	The description explains the resource changes, the Coverity scan bottleneck, and test results. It is directly related to the changeset.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

_{Comment @coderabbitai help to get the list of available commands.}

[orbalayla-nvidia]

/build

[orbalayla-nvidia]

/build