Bug 413605 - [Tests] Random failures in Rename*Tests
Summary: [Tests] Random failures in Rename*Tests
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.4   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 4.18 M3   Edit
Assignee: Sarika Sinha CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: test
: 421445 (view as bug list)
Depends on:
Blocks: 412551
  Show dependency tree
 
Reported: 2013-07-24 04:20 EDT by Dani Megert CLA
Modified: 2020-10-14 11:24 EDT (History)
3 users (show)

See Also:
Michael_Rennie: review+

Attachments
Test failures (160.11 KB, text/xml)
2013-11-11 05:57 EST, Dani Megert CLA 		no flags Details
Adding Assert to check the refactoring status (1.18 KB, patch)
2014-04-09 07:37 EDT, Sarika Sinha 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 Dani Megert CLA 2013-07-24 04:20:21 EDT 
I20130723-0800.

http://download.eclipse.org/eclipse/downloads/drops4/I20130723-0800/testresults/html/org.eclipse.jdt.debug.tests_win32.win32.x86_7.0.html


breakpoint attached to wrong method expected:<[renamed]Method> but was:<[nonPublicChilds]Method>

junit.framework.ComparisonFailure: breakpoint attached to wrong method expected:<[renamed]Method> but was:<[nonPublicChilds]Method>
at org.eclipse.jdt.debug.tests.refactoring.RenameMethodUnitTests.runMethodBreakpointTest(RenameMethodUnitTests.java:54)
at org.eclipse.jdt.debug.tests.refactoring.RenameMethodUnitTests.testNonPublicMethodBreakpoint(RenameMethodUnitTests.java:128)
at org.eclipse.jdt.debug.tests.AbstractDebugTest.runBare(AbstractDebugTest.java:2391)
at org.eclipse.jdt.debug.tests.DebugSuite$1.run(DebugSuite.java:55)
at java.lang.Thread.run(Thread.java:722)
Comment 4 Dani Megert CLA 2014-01-30 04:08:07 EST 
Happened again in N20140129-2000.
Comment 6 Sarika Sinha CLA 2014-02-27 05:26:00 EST 
The failures are happening during performRefactor or assertions after that.
performRefactor executes PerformRefactoringOperation.
Comment 7 Sarika Sinha CLA 2014-04-09 07:37:39 EDT 
Created attachment 241780 [details]
Adding Assert to check the refactoring status

This addition assert will help us understand the refactoring operation status. This will help us analyze the failing cases where ValidationStatus of refactoring is OK but the Rename of field/method has not happened in file.
Comment 8 Michael Rennie CLA 2014-04-14 11:19:48 EDT 
The additional logging makes sense.
Comment 10 Sarika Sinha CLA 2014-08-13 02:09:01 EDT 
After adding the logging, it has happened first time.
http://download.eclipse.org/eclipse/downloads/drops4/I20140812-0800/testresults/linux.gtk.x86_64_8.0/org.eclipse.jdt.debug.tests.AutomatedSuite.txt

http://download.eclipse.org/eclipse/downloads/drops4/I20140812-0800/logs.php#console

I see some additional message before failures.

Exception in thread "main" java.lang.SecurityException: class "a.JarClass"'s signer information does not match signer information of other classes in the same package
	at java.lang.ClassLoader.checkCerts(ClassLoader.java:895)
	at java.lang.ClassLoader.preDefineClass(ClassLoader.java:665)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:758)
	at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
	at java.net.URLClassLoader.defineClass(URLClassLoader.java:455)
	at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
	at java.net.URLClassLoader$1.run(URLClassLoader.java:367)
	at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(URLClassLoader.java:360)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	at a.RunJar.main(RunJar.java:15)
Comment 11 Sarika Sinha CLA 2015-02-11 04:29:46 EST 
*** Bug 421445 has been marked as a duplicate of this bug. ***
Comment 12 Sarika Sinha CLA 2015-02-11 04:35:30 EST 
http://download.eclipse.org/eclipse/downloads/drops4/N20150210-2000/testresults/html/org.eclipse.jdt.debug.tests_win32.win32.x86_7.0.html

http://download.eclipse.org/eclipse/downloads/drops4/N20150210-2000/testresults/html/org.eclipse.jdt.debug.tests_linux.gtk.x86_64_8.0.html

4 failed on Linux and 35 tests failed on Windows. Both the logs are filled with :
org.eclipse.jdt.debug.tests.TestAgainException: File is not synchronized with the local file system

I also see one starting message as :
java.io.IOException: Document is closed
	at org.eclipse.ui.internal.console.IOConsolePartitioner.streamAppended(IOConsolePartitioner.java:464)
	at org.eclipse.ui.console.IOConsoleOutputStream.notifyParitioner(IOConsoleOutputStream.java:247)
	at org.eclipse.ui.console.IOConsoleOutputStream.encodedWrite(IOConsoleOutputStream.java:242)
	at org.eclipse.ui.console.IOConsoleOutputStream.write(IOConsoleOutputStream.java:199)
	at org.eclipse.ui.console.IOConsoleOutputStream.write(IOConsoleOutputStream.java:208)
	at org.eclipse.debug.internal.ui.views.console.ProcessConsole$StreamListener.streamAppended(ProcessConsole.java:643)
	at org.eclipse.debug.internal.core.OutputStreamMonitor$ContentNotifier.run(OutputStreamMonitor.java:267)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.debug.internal.core.OutputStreamMonitor$ContentNotifier.notifyAppend(OutputStreamMonitor.java:278)
	at org.eclipse.debug.internal.core.OutputStreamMonitor.fireStreamAppended(OutputStreamMonitor.java:118)
	at org.eclipse.debug.internal.core.OutputStreamMonitor.read(OutputStreamMonitor.java:159)
	at org.eclipse.debug.internal.core.OutputStreamMonitor.access$1(OutputStreamMonitor.java:137)
	at org.eclipse.debug.internal.core.OutputStreamMonitor$1.run(OutputStreamMonitor.java:212)
	at java.lang.Thread.run(Thread.java:744)
Comment 18 Sarika Sinha CLA 2016-02-18 02:18:04 EST 
35 Rename tests fail on mac
http://download.eclipse.org/eclipse/downloads/drops4/N20160217-2000/testresults/html/org.eclipse.jdt.debug.tests_macosx.cocoa.x86_64_8.0.html

2 other test fails
testDontSuspendOnUncaughtExceptions	Failure	testDontSuspendOnUncaughtExceptions - you cannot terminate and remove a null debug target

junit.framework.AssertionFailedError: testDontSuspendOnUncaughtExceptions - you cannot terminate and remove a null debug target
at org.eclipse.jdt.debug.tests.AbstractDebugTest.terminateAndRemove(AbstractDebugTest.java:2036)
at org.eclipse.jdt.debug.tests.breakpoints.MiscBreakpointsTests.testDontSuspendOnUncaughtExceptions(MiscBreakpointsTests.java:131)
at org.eclipse.jdt.debug.tests.AbstractDebugTest.runBare(AbstractDebugTest.java:2469)
at org.eclipse.jdt.debug.tests.DebugSuite$1.run(DebugSuite.java:57)
at java.lang.Thread.run(Thread.java:745)


testTerminateAll_01	Failure	expected:<2> but was:<3>

junit.framework.AssertionFailedError: expected:<2> but was:<3>
at org.eclipse.jdt.debug.tests.console.ConsoleTerminateAllActionTests.testTerminateAll_01(ConsoleTerminateAllActionTests.java:66)
at org.eclipse.jdt.debug.tests.AbstractDebugTest.runBare(AbstractDebugTest.java:2469)
at org.eclipse.jdt.debug.tests.DebugSuite$1.run(DebugSuite.java:57)
at java.lang.Thread.run(Thread.java:745)
Comment 19 Sarika Sinha CLA 2016-02-18 05:23:37 EST 
Log is filled with statement :
org.eclipse.jdt.debug.tests.TestAgainException: File is not synchronized with the local file system: file:/Users/hudsonBuild/workspace/ep46N-unit-mac64/workarea/N20160217-2000/eclipse-testing/test-eclipse/Eclipse.app/Contents/Eclipse/jdt_folder/DebugTests/src/a/b/c/MoveeChild.java

Need to analyze if we can we try to synchronize this file if we catch this exception?
Comment 21 Sarika Sinha CLA 2016-04-25 04:19:15 EDT 
Have no idea right now how to handle this.
Comment 25 pasam soujanya CLA 2016-09-21 02:46:35 EDT 
Issue is seen with IBM SDK with the below java version
java version "1.8.0"
Java(TM) SE Runtime Environment (build pxa6480sr3fp12-20160919_01(SR3 FP12))
IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20160915_318796 (JIT enabled, AOT enabled)
J9VM - R28_Java8_SR3_20160915_0912_B318796
JIT  - tr.r14.java.green_20160818_122998
GC   - R28_Java8_SR3_20160915_0912_B318796_CMPRSS
J9CL - 20160915_318796)
JCL - 20160914_01 based on Oracle jdk8u101-b13

Error trace:
(eclipse) junit.framework.ComparisonFailure: breakpoint attached to wrong method expected:<[renamed]Method> but was:<[nonPublicChilds]Method>
ECL 	at org.eclipse.jdt.debug.tests.refactoring.RenameMethodUnitTests.runMethodBreakpointTest(RenameMethodUnitTests.java:54)
ECL 	at org.eclipse.jdt.debug.tests.refactoring.RenameMethodUnitTests.testNonPublicMethodBreakpoint(RenameMethodUnitTests.java:128)
ECL 	at org.eclipse.jdt.debug.tests.AbstractDebugTest.runBare(AbstractDebugTest.java:2466)
ECL 	at org.eclipse.jdt.debug.tests.DebugSuite$1.run(DebugSuite.java:57)
ECL 	at java.lang.Thread.run(Thread.java:785)
Comment 38 Sarika Sinha CLA 2017-07-05 01:03:43 EDT 
1 test failed-
http://download.eclipse.org/eclipse/downloads/drops4/I20170703-2000/testresults/html/org.eclipse.jdt.debug.tests_ep48I-unit-mac64_macosx.cocoa.x86_64_8.0.html

testPublicExceptionBreakpoint	Failure	breakpoint attached to wrong type expected:<a.b.c.[RenamedType]> but was:<a.b.c.[MoveeChild]>

junit.framework.ComparisonFailure: breakpoint attached to wrong type expected:<a.b.c.[RenamedType]> but was:<a.b.c.[MoveeChild]>
at org.eclipse.jdt.debug.tests.refactoring.RenameNonPublicTypeUnitTests.runExceptionBreakpointTest(RenameNonPublicTypeUnitTests.java:258)
at org.eclipse.jdt.debug.tests.refactoring.RenameNonPublicTypeUnitTests.testPublicExceptionBreakpoint(RenameNonPublicTypeUnitTests.java:273)
at org.eclipse.jdt.debug.tests.AbstractDebugTest.runBare(AbstractDebugTest.java:2528)
at org.eclipse.jdt.debug.tests.DebugSuite$1.run(DebugSuite.java:57)
at java.lang.Thread.run(Thread.java:745)
Comment 39 Eclipse Genie CLA 2020-10-13 15:22:55 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 40 Sarika Sinha CLA 2020-10-14 11:24:19 EDT 
Not seeing these test failures recently. 
Resolving this, Will reopen if I see it happening again.