Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 442533 - We should not have empty performance targets
Summary: We should not have empty performance targets
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 4.5   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 4.5 M2   Edit
Assignee: Dani Megert CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 442455
  Show dependency tree
 
Reported: 2014-08-25 16:02 EDT by David Williams CLA
Modified: 2014-09-01 07:45 EDT (History)
1 user (show)

See Also:

Attachments
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 David Williams CLA 2014-08-25 16:02:08 EDT 
See bug 442455 for more detail, but it is confusing (at best) for us to some tests marked as having performance tests, when they really don't. 

From what I could see, the bundles below have an empty performance target.
Would appreciate either removing the empty targets, or "comment them out" so they are not detected by the CBI-tool (and test framework) that mark them as "performance tests".


eclipse.platform.text/org.eclipse.core.filebuffers.tests/test.xml
eclipse.platform.text/org.eclipse.jface.text.tests
eclipse.platform.text/org.eclipse.search.tests
eclipse.platform.text/org.eclipse.text.tests
eclipse.platform.text/org.eclipse.ui.editors.tests
eclipse.platform.text/org.eclipse.ui.workbench.texteditor.tests