Bug 529669 - Random loss of of JUnit Console
Summary: Random loss of of JUnit Console
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.7   Edit
Hardware: PC All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2018-01-11 08:39 EST by Moritz Aleithe CLA
Modified: 2018-03-19 03:56 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 Moritz Aleithe CLA 2018-01-11 08:39:47 EST 
We are seeing an issue where sometimes the JUnit Consoles (the output written during a JUnit test in the "Console" view) is lost after the Console was not the active Part. This happens in Neon and I think I've already seen it in Oxygen as well. 
Usually this is
Run Test -> 
Work on Something ->
Go Back To Console ->
Output is gone. This is especially annoying if the Test takes several Minutes to run.
Comment 1 Andrey Loskutov CLA 2018-01-11 08:47:58 EST 
Hard to tackle this one without steps to reproduce...
Comment 2 Moritz Aleithe CLA 2018-01-11 08:49:39 EST 
I am currently on collecting more information about when exactly this happens and willing to share, but it seems to be quite random
Comment 3 Moritz Aleithe CLA 2018-03-19 03:56:12 EDT 
I think this happens if anything uses a console view in the meantime, but I'm not 100% sure. 

Our favorite would be if the last JUnit Test console would be kept, until 

a.) we close Eclipse
b.) we run another Test
c.) the console is deleted manually

I changed the ticket importance to "enhancement", since I think the current behavior is not precisely a bug.