Bug 181810 - [JUnit] JUnit view "Show Failures Only" is initially very slow
Summary: [JUnit] JUnit view "Show Failures Only" is initially very slow
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Markus Keller CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-10 13:59 EDT by James Synge CLA
Modified: 2022-11-28 08:48 EST (History)
0 users

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 James Synge CLA 2007-04-10 13:59:31 EDT 
After running a test suite with many tests (~800 in my case, with ~5 failures), if one clicks Show Failures Only in the JUnit view, it can take many seconds to respond (it may depend on the number of failures); this surprised me because it isn't clear that there is a lot of work to be done to filter out the passing tests.  Subsequent presses of the button are fast.

Platform is 3.3M5.
Comment 1 Michael Rennie CLA 2007-04-10 14:06:00 EDT 
moving to jdt.ui (JUnit)
Comment 2 Eclipse Genie CLA 2020-09-04 12:08:40 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.

If you have further information on the current state of the bug, please add it. 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.
Comment 3 Eclipse Genie CLA 2022-11-28 08:48:00 EST 
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.

If you have further information on the current state of the bug, please add it. 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.