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 67378 - Commit validation keeps failing on my machine
Summary: Commit validation keeps failing on my machine
Status: RESOLVED FIXED
Alias: None
Product: ide
Classification: Unclassified
Component: Code (show other bugs)
Version: 5.x
Hardware: All All
: P1 blocker (vote)
Assignee: Jiri Skrivanek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-24 00:22 UTC by _ ttran
Modified: 2005-10-31 17:57 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
results subdir (295.29 KB, application/x-compressed)
2005-10-24 00:23 UTC, _ ttran
Details
results subdir (279.57 KB, application/x-compressed)
2005-10-31 15:16 UTC, _ ttran
Details

Note You need to log in before you can comment on or make changes to this bug.
Description _ ttran 2005-10-24 00:22:05 UTC
It fails consistently at Debugging test.  Yet it passes everytime on the build
machine.  I suspect this is related to robustness of the test suite.

I'll attach the results subdir to the issue.

CC Yarda who cares a lot about commit validation.
Comment 1 _ ttran 2005-10-24 00:23:01 UTC
Created attachment 26258 [details]
results subdir
Comment 2 Jaroslav Tulach 2005-10-24 07:43:20 UTC
CCing? I am founding myself to be assigned to the issue!  
 
But otherwise yes, I care and if the fails for one developer, it is more 
useless than useful. Making P1 and reassigning to Jiri. He can exclude failing 
the test from the suite or work with Trung fix his failures. 
 
Comment 3 Jiri Skrivanek 2005-10-24 07:52:17 UTC
I looked at log messages and find out that there is a bug in test. It appears
only in some circumstances. I am working on it. 
Comment 4 Jiri Skrivanek 2005-10-24 08:16:55 UTC
Debugger test didn't wait for breakpoint and prematurely continued. We waited
for line number in status text but it appeared in port number. It is fixed to
wait for proper message.

/cvs/ide/test/qa-functional/src/validation/IDEValidation.java,v  <-- 
IDEValidation.java
new revision: 1.140; previous revision: 1.139
Comment 5 _ ttran 2005-10-31 14:24:09 UTC
reopen, still failing on my machine. Same place


testDebugging:

      org.netbeans.junit.AssertionFailedErrorException: Wait status text equals
to Thread main stopped at SampleClass1.java:27.
	at org.netbeans.jellytools.JellyTestCase.runBare(JellyTestCase.java:143)
	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.ide.MainWithExec.run(MainWithExec.java:211)
	at org.netbeans.xtest.plugin.ide.Main$3.run(Main.java:290)
	at java.lang.Thread.run(Thread.java:534)

Nested Exception is:
org.netbeans.jemmy.TimeoutExpiredException: Wait status text equals to Thread
main stopped at SampleClass1.java:27.
	at org.netbeans.jemmy.Waiter.waitAction(Waiter.java:140)
	at
org.netbeans.jellytools.MainWindowOperator$StatusTextTracer.waitText(MainWindowOperator.java:522)
	at
org.netbeans.jellytools.MainWindowOperator$StatusTextTracer.waitText(MainWindowOperator.java:504)
	at validation.IDEValidation.testDebugging(IDEValidation.java:865)
	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:324)
	at junit.framework.TestCase.runTest(TestCase.java:154)
	at org.netbeans.junit.NbTestCase.runBare(NbTestCase.java:135)
	at org.netbeans.jellytools.JellyTestCase.runBare(JellyTestCase.java:116)
	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.ide.MainWithExec.run(MainWithExec.java:211)
	at org.netbeans.xtest.plugin.ide.Main$3.run(Main.java:290)
	at java.lang.Thread.run(Thread.java:534)

   
Comment 6 _ ttran 2005-10-31 15:16:45 UTC
Created attachment 26485 [details]
results subdir
Comment 7 Jiri Skrivanek 2005-10-31 17:57:41 UTC
It seems to be a problem with your configuration. In the screen shot I can read
from debug-single output window:

init:
deps-jar:
compile-single:

Java Result: 139
debug-single:
BUILD SUCCESSFUL (total time: 2 seconds)

Please, try to reproduce manually.