Skip to content

Conversation

@NirWolfer
Copy link
Contributor

@NirWolfer NirWolfer commented Sep 7, 2025

Change --aggressiveness-level to medium

Requested in: HPCINFRA-3898

@NirWolfer NirWolfer force-pushed the debug branch 5 times, most recently from 0a56bb6 to 545a5ab Compare September 7, 2025 09:52
@NirWolfer NirWolfer changed the title [skip-ci][DEBUG] testing cov agressive level [CI] testing cov agressive level Sep 7, 2025
@NirWolfer NirWolfer changed the title [CI] testing cov agressive level [CI] Issue: HPCINFRA-3898 coverity agressiveness and exclude files Sep 7, 2025
@galnoam
Copy link
Collaborator

galnoam commented Sep 9, 2025

@NirWolfer can you rebase on bashar changes, i want to see the cov issue we get in the CI
@BasharRadya after the run, put it in the RM ticket

@NirWolfer NirWolfer force-pushed the debug branch 2 times, most recently from 7465382 to a275684 Compare September 15, 2025 06:34
@NirWolfer NirWolfer changed the title [CI] Issue: HPCINFRA-3898 coverity agressiveness and exclude files [CI] Issue: HPCINFRA-3898 coverity agressiveness Sep 15, 2025
@NirWolfer
Copy link
Contributor Author

Please check https://nbuprod.blsm.nvidia.com/swx-media-master/job/libxlio/job/LibXLIO-opensource/1763/
Kept this build forever so you can analyze it

Change --aggressiveness-level to medium

Signed-off-by: NirWolfer <[email protected]>
@NirWolfer NirWolfer marked this pull request as ready for review October 22, 2025 11:35
Copy link

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Greptile Overview

Greptile Summary

This PR increases the Coverity static analysis aggressiveness level from low to medium in the CI pipeline script contrib/jenkins_tests/cov.sh. This configuration change affects how deeply Coverity analyzes the codebase for potential defects during automated testing. The change integrates with the existing CI infrastructure in .ci/ which orchestrates the Jenkins pipeline stages including static analysis steps. By raising the sensitivity, the team aims to catch more subtle code quality issues, though this may also increase false positive reports and slightly extend analysis time. The modification is minimal and self-contained, touching only the cov-analyze command invocation while leaving the build, error reporting, and commit submission logic intact.

Confidence: 5/5

This is a straightforward configuration change with no logic modifications, no security implications, and clear intent documented in the referenced JIRA ticket. The change is low-risk and well-understood within the context of static analysis tooling.

1 file reviewed, no comments

Edit Code Review Agent Settings | Greptile

@NirWolfer
Copy link
Contributor Author

@BasharRadya Please check the coverity errors

@galnoam
Copy link
Collaborator

galnoam commented Nov 2, 2025

@OmriRitblat, please work with bashar on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants