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)
Testing
General
Tracking
(firefox80 fixed)
RESOLVED
FIXED
mozilla80
Tracking | Status | |
---|---|---|
firefox80 | --- | fixed |
People
(Reporter: Sylvestre, Assigned: andi)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
some jobs takes 1745m and more
Comment 1•4 years ago
|
||
:andi - Any thoughts?
Assignee | ||
Comment 2•4 years ago
|
||
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 | ||
Updated•4 years ago
|
Assignee: nobody → bpostelnicu
Assignee | ||
Comment 3•4 years ago
|
||
Pushed by bpostelnicu@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/ec880b46ef45 reduce `max-run-time` for coverity full tree analysis. r=marco
Comment 5•4 years ago
|
||
bugherder |
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.
Description
•