Community
Participate
Working Groups
Starting late in the 3.1 cycle (like during the RCs, or possible only the final release), our team has noticed a problem with the junit view. Sometimes, the "bar" doesnt' display right. When the problem occurs, the bar is either not visible at all, or a small snippet (1-2%) of the bar is visible on the left. The view shows the launch as finished. Running the same launch again (CTRL-F11) has ALWAYS worked correctly. This happens frequently (on any given system, we see it happening over a dozen times a day). I've never seen it happen on Linux (which I use), but I've been pairing at other Windows stations a lot more lately so I don't *know* if the OS is a factor.
David, could you take a screenshot when you see this again? Do you have JUnit as fast view (if yes: hidden or active?) when this happens? Is only the bar wrong, or are test results missing in the Hierarchy tab as well?
I will try to get you the screen shot. The heirarchy is there and compelte, but the summary (# of tests, etc) is usually wrong. I think it said "7/0" last time I saw it. There is another symptom (which might be an entirely different bug) where the bar is disappearing completely, the numbers are zeroed, and the heirarchy is empty. I *think* this is a case of some "other launch" is being run, and as we have the checkbox on to clear terminated launches when a new one runs, the view gets cleared. But let me emphasize, the USER did not start another launch. It seems to remove the launch immediately after finishing. I've got one user running with that preference set to see if it's related to that.
My Guinea Pig reports that since turning off "Remove terminated launches when a new launch is created", (about 12 working hours), neither version of the problem has been seen.
Created attachment 25461 [details] Screenshot of JUnit View with "wonky" bar In this particular failure, the heirarchy view was empty, but I have definately seen this where it wasn't.
David, is this a problem in 3.2?
I don't know. None of the Windows desktops are running 3.2. I'll try to coerce someone to try it out there.
Setting to remind, please reopen if you see this again in 3.2. I could not reproduce when this originally happened, and the updating code has been rewritten largely -- I think this should not happen again in 3.2.
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.
