Bug 252609 - Transient ConsoleLineTracker test failures
Summary: Transient ConsoleLineTracker test failures
Status: VERIFIED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.5   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: 3.4.2   Edit
Assignee: Michael Rennie CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 224619 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-10-29 11:57 EDT by Michael Rennie CLA
Modified: 2013-05-06 04:26 EDT (History)
1 user (show)

See Also:

Attachments
patch (1.25 KB, patch)
2008-10-29 12:05 EDT, Michael Rennie CLA 		no flags Details | Diff
patch (5.09 KB, patch)
2008-10-30 12:30 EDT, Darin Wright CLA 		no flags Details | Diff
View All 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 Michael Rennie CLA 2008-10-29 11:57:45 EDT 
I20081029-0100 has some more of the transient ConsoleLineTracker test failures.

The failure is not reproducible locally. We should disable the offending tests in the build until we can figure out the reason for the failure(s).
Comment 1 Michael Rennie CLA 2008-10-29 12:00:06 EDT 
the failure(s) in question (for I20081029-0100) are:

ConsoleLineTrackerTests#testSimpleLineCounter	

  -> Failure Wrong number of lines output expected:<11> but was:<13>

ConsoleLineTrackerTests#testIntConcatenation	

  -> Failure Wrong number of lines output expected:<2> but was:<4>
Comment 2 Michael Rennie CLA 2008-10-29 12:05:53 EDT 
Created attachment 116435 [details]
patch

removes the offending tests until we can figure out why they non-deterministically fail
Comment 3 Darin Wright CLA 2008-10-30 12:22:20 EDT 
Re-openin to address the failure. I found that when the tests fail on Java 6 there are in fact two extra lines output to the console:

ERROR: JDWP Unable to get JNI 1.2 environment, jvm->GetEnv() return code = -2
JDWP exit error AGENT_ERROR_NO_JNI_ENV(183): [../../../src/share/back/util.c:820]

See associated bug at Sun:

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6476706


The workaround appears to be to put a System.exit(0) in the test program.
Comment 4 Darin Wright CLA 2008-10-30 12:23:05 EDT 
oops, must click "Reopen"
Comment 5 Darin Wright CLA 2008-10-30 12:30:43 EDT 
Created attachment 116538 [details]
patch

Patch fixes tests program with "System.exit(0)" and adds logging to the tests in case they fail (we'll see the failed output in the console logs).
Comment 6 Darin Wright CLA 2008-10-31 10:45:32 EDT 
Fixed.
Comment 7 Darin Wright CLA 2008-10-31 10:45:43 EDT 
Please verify, Mike.
Comment 8 Darin Wright CLA 2008-10-31 12:24:17 EDT 
Also applied in 3.4.2 stream to avoid transient failures there.
Comment 9 Michael Rennie CLA 2008-12-08 12:51:51 EST 
verified
Comment 10 Dani Megert CLA 2013-05-06 04:26:22 EDT 
*** Bug 224619 has been marked as a duplicate of this bug. ***