Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 454941 - fix documentation for performance tests (ui)
Summary: fix documentation for performance tests (ui)
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Releng (show other bugs)
Version: 4.5   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Releng-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks: 454921
  Show dependency tree
 
Reported: 2014-12-11 15:39 EST by David Williams CLA
Modified: 2020-06-04 18:25 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2014-12-11 15:39:00 EST
I know there's another bug about the performance framework, 
but with this one, I am primarily referring to the "performance.ui" documentation, such as at 

http://git.eclipse.org/c/platform/eclipse.platform.releng.buildtools.git/tree/bundles/org.eclipse.test.performance.ui/readme.html

Some is completely "out of date" and some could just be improved. 


And, somewhere, should discuss the relationship between performance.ui bundle and the performance bundle. The later, as you read about it, it very general purpose and flexible. But, if your plan is to use that in conjunction with performance.ui then there are more constraints on the "order" of certain data. Not sure if that "ordering" is itself a bug, my misunderstanding, or simply something that needs documenting.
Comment 1 Eclipse Genie CLA 2020-06-04 18:25:17 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.