Closed Bug 1648710 Opened 4 years ago Closed 4 years ago

Evaluate why some coverity-full-analysis takes forever to run

Categories

(Testing :: General, task, P3)

Product:
Testing
Component:
General
Type:
task

Tracking

(firefox80 fixed)

Status:
RESOLVED FIXED
Milestone:
mozilla80
Tracking Flags:
Tracking Status
firefox80 --- fixed

People

(Reporter: Sylvestre, Assigned: andi)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

image.png
11.43 KB, image/png
Details
Bug 1648710 - reduce `max-run-time` for coverity full tree analysis. r=marco
47 bytes, text/x-phabricator-request
Details | Review
Attached image image.png —

some jobs takes 1745m and more

:andi - Any thoughts?

Severity: -- → S3
Flags: needinfo?(bpostelnicu)
Priority: -- → P3
See Also: → 1527818

According to the Synopsys documentation for Coverity Static-Analysis they strongly advise NOT to run the analysis in virtualization environments due to potentially poor performance. Also besides their obvious good-practive, Coverity is very poor optimized when it comes to consume all of the threads available, specially during the last phase of the analysis after the build has been completed, the process is mainly single threaded. But still the fact that there is very great degree of variation for job time from roughly 200 minutes to over 1500minutes I will submit a support ticket.

Flags: needinfo?(bpostelnicu)
Assignee: nobody → bpostelnicu
Pushed by bpostelnicu@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ec880b46ef45
reduce `max-run-time` for coverity full tree analysis. r=marco

https://hg.mozilla.org/mozilla-central/rev/ec880b46ef45

Status: NEW → RESOLVED
Closed: 4 years ago
status-firefox80: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla80
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: