Bug 342785 - Disable code coverage for performance tests
Summary: Disable code coverage for performance tests
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Releng (show other bugs)
Version: 3.7   Edit
Hardware: All All
: P3 critical (vote)
Target Milestone: 3.7 M7   Edit
Assignee: Kim Moir CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-14 01:17 EDT by Dani Megert CLA
Modified: 2011-04-27 16:02 EDT (History)
2 users (show)

See Also:

Attachments
patch (2.25 KB, patch)
2011-04-14 14:34 EDT, Kim Moir CLA 		no flags Details | Diff
patch (1.21 KB, patch)
2011-04-26 11:02 EDT, Kim Moir CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dani Megert CLA 2011-04-14 01:17:01 EDT 
According to Kim, we run code coverage for the performance tests. This is bad as it can affect performance and I'm not sure we also do it in the perf branch (if not, double bad).

We should disable code coverage for performance tests asap.
Comment 1 Kim Moir CLA 2011-04-14 14:34:11 EDT 
Created attachment 193282 [details]
patch
Comment 2 Kim Moir CLA 2011-04-14 17:27:37 EDT 
Fixed, tagged for I-build.
Comment 3 Kim Moir CLA 2011-04-14 17:27:52 EDT 
Also verified in test build.
Comment 4 Dani Megert CLA 2011-04-15 03:01:18 EDT 
Kim, was code coverage also enabled in the baseline?
Comment 5 Kim Moir CLA 2011-04-15 08:17:41 EDT 
No, this change wasn't backported to the baseline.
Comment 6 Kim Moir CLA 2011-04-26 09:17:03 EDT 
reopening
Comment 7 Kim Moir CLA 2011-04-26 11:02:57 EDT 
Created attachment 194066 [details]
patch
Comment 8 Kim Moir CLA 2011-04-27 16:02:33 EDT 
verified in I20110426-2000. The console log is clean of jacoco report generation calls, no report generation directories were created.