This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 62678 - CLITest failure with good log
Summary: CLITest failure with good log
Status: VERIFIED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Jaroslav Tulach
URL:
Keywords: TEST
Depends on:
Blocks:
 
Reported: 2005-08-19 15:29 UTC by Jaroslav Tulach
Modified: 2008-12-22 19:49 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Diff between successful and unsuccessful run (1.75 KB, patch)
2005-08-21 11:11 UTC, Jaroslav Tulach 		Details | Diff
The diff of successful and failed run with -U50 (2.73 KB, patch)
2005-08-21 11:18 UTC, Jaroslav Tulach 		Details | Diff
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 Jaroslav Tulach 2005-08-19 15:29:36 UTC 
testFileExistsButItCannotBeRead: 
 
  
      junit.framework.AssertionFailedError: Failed as No result produced with 
text: 
state: 10 thread: Thread[Default RequestProcessor,1,system] blocked 
state: 5 thread: Thread[Default RequestProcessor,1,system] not blocked 
state: 83 thread: Thread[Default RequestProcessor,1,system] not blocked 
state: 85 thread: Thread[Default RequestProcessor,1,system] blocked 
state: 5 thread: Thread[Default RequestProcessor,1,system] not blocked 
state: 83 thread: Thread[Default RequestProcessor,1,system] not blocked 
state: 85 thread: Thread[Default RequestProcessor,1,system] blocked 
state: 5 thread: Thread[Default RequestProcessor,1,system] not blocked 
state: 83 thread: Thread[Default RequestProcessor,1,system] not blocked 
state: 85 thread: Thread[Default RequestProcessor,1,system] blocked 
state: 5 thread: Thread[Default RequestProcessor,1,system] not blocked 
state: 83 thread: Thread[Default RequestProcessor,1,system] not blocked 
state: 85 thread: Thread[Default RequestProcessor,1,system] blocked 
state: 20 thread: Thread[Default RequestProcessor,1,system] not blocked 
state: 0 thread: Thread[Default RequestProcessor,1,system] not blocked 
state: 5 thread: Thread[Default RequestProcessor,1,system] not blocked 
state: 28 thread: Thread[Default RequestProcessor,1,system] not blocked 
state: 65 thread: Thread[CLI Requests Server,1,system] not blocked 
state: 30 thread: Thread[Default RequestProcessor,1,system] not blocked 
state: 32 thread: Thread[Default RequestProcessor,1,system] not blocked 
state: 65 thread: Thread[CLI Requests Server,1,system] not blocked 
state: 33 thread: Thread[Default RequestProcessor,1,system] not blocked 
state: 83 thread: Thread[Default RequestProcessor,1,system] not blocked 
state: 70 thread: Thread[CLI Handler Thread Handler: 1,1,system] not blocked 
state: 90 thread: Thread[CLI Handler Thread Handler: 1,1,system] not blocked 
state: 93 thread: Thread[CLI Handler Thread Handler: 1,1,system] not blocked 
state: 85 thread: Thread[Default RequestProcessor,1,system] blocked 
 
        at junit.framework.Assert.fail(Assert.java:47) 
        at 
org.netbeans.CLIHandlerTest$InitializeRunner.resultFile(CLIHandlerTest.java:637) 
        at 
org.netbeans.CLIHandlerTest.testFileExistsButItCannotBeRead(CLIHandlerTest.java:99) 
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
        at java.lang.reflect.Method.invoke(Method.java:585) 
        at junit.framework.TestCase.runTest(TestCase.java:154) 
        at org.netbeans.CLIHandlerTest.runTest(CLIHandlerTest.java:68) 
        at org.netbeans.junit.NbTestCase.runBare(NbTestCase.java:135) 
        at junit.framework.TestResult$1.protect(TestResult.java:106) 
        at junit.framework.TestResult.runProtected(TestResult.java:124) 
        at junit.framework.TestResult.run(TestResult.java:109) 
        at junit.framework.TestCase.run(TestCase.java:118) 
        at org.netbeans.junit.NbTestCase.run(NbTestCase.java:122) 
        at junit.framework.TestSuite.runTest(TestSuite.java:208) 
        at junit.framework.TestSuite.run(TestSuite.java:203) 
        at 
org.netbeans.xtest.testrunner.JUnitTestRunner.runTests(JUnitTestRunner.java:167) 
        at 
org.netbeans.xtest.testrunner.JUnitTestRunner.runTests(JUnitTestRunner.java:118) 
        at 
org.netbeans.xtest.plugin.jvm.JUnitTestRunnerLauncher.main(JUnitTestRunnerLauncher.java:41)
Comment 1 Jaroslav Tulach 2005-08-21 11:11:59 UTC 
Created attachment 24108 [details]
Diff between successful and unsuccessful run
Comment 2 Jaroslav Tulach 2005-08-21 11:18:14 UTC 
Created attachment 24109 [details]
The diff of successful and failed run with -U50
Comment 3 Jaroslav Tulach 2005-08-21 11:33:04 UTC 
I improved the log: CLIHandlerTest.java new revision: 1.15 
 
However the problem is that there was an access to "state 33" which means that 
there was an SocketException, I am not sure why and what exception it was, but 
maybe the machine was misconfigured, so let's wait for another failure.
Comment 4 Jaroslav Tulach 2005-08-24 08:54:03 UTC 
new failure even with better log testFileExistsButItCannotBeRead: 
 
  
      junit.framework.AssertionFailedError: Failed as No result produced with 
text: 
state: 10 thread: Thread[InitializeRunner blocks on 10,1,system] blocked 
state: 5 thread: Thread[InitializeRunner blocks on 85,1,system] not blocked 
state: 83 thread: Thread[InitializeRunner blocks on 85,1,system] not blocked 
state: 85 thread: Thread[InitializeRunner blocks on 85,1,system] blocked 
state: 5 thread: Thread[InitializeRunner blocks on 85,1,system] not blocked 
state: 83 thread: Thread[InitializeRunner blocks on 85,1,system] not blocked 
state: 85 thread: Thread[InitializeRunner blocks on 85,1,system] blocked 
state: 5 thread: Thread[InitializeRunner blocks on 85,1,system] not blocked 
state: 83 thread: Thread[InitializeRunner blocks on 85,1,system] not blocked 
state: 85 thread: Thread[InitializeRunner blocks on 85,1,system] blocked 
state: 5 thread: Thread[InitializeRunner blocks on 85,1,system] not blocked 
state: 83 thread: Thread[InitializeRunner blocks on 85,1,system] not blocked 
state: 85 thread: Thread[InitializeRunner blocks on 85,1,system] blocked 
state: 20 thread: Thread[InitializeRunner blocks on 10,1,system] not blocked 
state: 0 thread: Thread[InitializeRunner blocks on 10,1,system] not blocked 
state: 65 thread: Thread[CLI Requests Server,1,system] not blocked 
state: 5 thread: Thread[InitializeRunner blocks on 85,1,system] not blocked 
state: 28 thread: Thread[InitializeRunner blocks on 85,1,system] not blocked 
state: 30 thread: Thread[InitializeRunner blocks on 85,1,system] not blocked 
state: 32 thread: Thread[InitializeRunner blocks on 85,1,system] not blocked 
state: 65 thread: Thread[CLI Requests Server,1,system] not blocked 
state: 33 thread: Thread[InitializeRunner blocks on 85,1,system] not blocked 
state: 83 thread: Thread[InitializeRunner blocks on 85,1,system] not blocked 
state: 70 thread: Thread[CLI Handler Thread Handler: 1,1,system] not blocked 
state: 90 thread: Thread[CLI Handler Thread Handler: 1,1,system] not blocked 
state: 93 thread: Thread[CLI Handler Thread Handler: 1,1,system] not blocked 
state: 85 thread: Thread[InitializeRunner blocks on 85,1,system] blocked
Comment 5 Jaroslav Tulach 2005-09-16 13:38:49 UTC 
#62678: Fixing the test, currently the port number has been modified and not 
the key for connecting. However I am not sure if this helps to stop the 
failures, as the failure probably occured sooner than the port started to be 
stored in the file. 
 
Members: 
        CLIHandlerTest.java:1.1->1.2
Comment 6 Jaromir Uhrik 2006-01-16 15:44:22 UTC 
Marking this issue as VERIFIED since the issue reporter == issue owner.