Bug 428166 - [test][model]CopyMoveResourcesTests.testCopyCU05 failed
Summary: [test][model]CopyMoveResourcesTests.testCopyCU05 failed
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.4   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Jay Arthanareeswaran CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: test
: 428321 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-02-14 03:25 EST by Dani Megert CLA
Modified: 2020-01-13 02:20 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dani Megert CLA 2014-02-14 03:25:55 EST
N20140213-2000.

http://download.eclipse.org/eclipse/downloads/drops4/N20140213-2000/testresults/html/org.eclipse.jdt.core.tests.model_macosx.cocoa.x86_5.0.html


Destination container not changed

junit.framework.AssertionFailedError: Destination container not changed
at org.eclipse.jdt.core.tests.model.CopyMoveResourcesTests.copyPositive(CopyMoveResourcesTests.java:82)
at org.eclipse.jdt.core.tests.model.CopyMoveResourcesTests.testCopyCU05(CopyMoveResourcesTests.java:325)
at org.eclipse.jdt.core.tests.model.SuiteOfTestCases$Suite.runTest(SuiteOfTestCases.java:104)
at org.eclipse.jdt.core.tests.model.SuiteOfTestCases$Suite.superRun(SuiteOfTestCases.java:88)
at org.eclipse.jdt.core.tests.model.SuiteOfTestCases$1.protect(SuiteOfTestCases.java:76)
at org.eclipse.jdt.core.tests.model.SuiteOfTestCases$Suite.run(SuiteOfTestCases.java:85)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:657)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:310)
at org.eclipse.test.CoreTestApplication.runTests(CoreTestApplication.java:36)
at org.eclipse.test.CoreTestApplication.run(CoreTestApplication.java:32)
at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:133)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:103)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:374)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:228)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1462)
at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
at org.eclipse.core.launcher.Main.main(Main.java:34)
Comment 1 Manoj N Palat CLA 2014-07-17 10:23:42 EDT
*** Bug 428321 has been marked as a duplicate of this bug. ***
Comment 2 shankha banerjee CLA 2014-08-27 23:44:43 EDT
testCopyCU04 failed.
Similar call stack.

Build ID: M20140827-1200
Comment 3 Sasikanth Bharadwaj CLA 2014-10-16 04:09:14 EDT
testCopyCU04 failed.
Similar call stack.

Build ID: N20141015-2000
Comment 4 Sasikanth Bharadwaj CLA 2014-10-16 04:09:58 EDT
(In reply to comment #3)
> testCopyCU04 failed.
> Similar call stack.
> 
> Build ID: N20141015-2000

http://download.eclipse.org/eclipse/downloads/drops4/N20141015-2000/testresults/html/org.eclipse.jdt.core.tests.model_macosx.cocoa.x86_64_7.0.html
Comment 5 shankha banerjee CLA 2014-10-29 19:13:48 EDT
testCopyImportStatic Failed.
Build ID: I20141028-2000
Test Location: http://download.eclipse.org/eclipse/downloads/drops4/I20141028-2000/testresults/html/org.eclipse.jdt.core.tests.model_win32.win32.x86_7.0.html

Similar Call Stack.
Comment 6 Sasikanth Bharadwaj CLA 2014-11-27 04:12:09 EST
testCopyCU07 failed
Build Id N20141126-2000
platform Linux
http://download.eclipse.org/eclipse/downloads/drops4/N20141126-2000/testresults/html/org.eclipse.jdt.core.tests.model_linux.gtk.x86_64_8.0.html
details: Added children not correct for element copy
stacktrace: junit.framework.AssertionFailedError: Added children not correct for element copy
	at org.eclipse.jdt.core.tests.model.CopyMoveResourcesTests.copyPositive(CopyMoveResourcesTests.java:96)
	at org.eclipse.jdt.core.tests.model.CopyMoveResourcesTests.testCopyCU07(CopyMoveResourcesTests.java:389)
	at org.eclipse.jdt.core.tests.model.SuiteOfTestCases$Suite.runTest(SuiteOfTestCases.java:104)
	at org.eclipse.jdt.core.tests.model.SuiteOfTestCases$Suite.superRun(SuiteOfTestCases.java:88)
	at org.eclipse.jdt.core.tests.model.SuiteOfTestCases$1.protect(SuiteOfTestCases.java:76)
	at org.eclipse.jdt.core.tests.model.SuiteOfTestCases$Suite.run(SuiteOfTestCases.java:85)
	at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:657)
	at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:310)
	at org.eclipse.test.CoreTestApplication.runTests(CoreTestApplication.java:36)
	at org.eclipse.test.CoreTestApplication.run(CoreTestApplication.java:32)
	at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
	at org.eclipse.core.launcher.Main.main(Main.java:34)
Comment 7 shankha banerjee CLA 2015-01-01 08:20:14 EST
Failed: testCopyCU01
N20141229-2000.
Platform: Linux
Comment 8 Eclipse Genie CLA 2020-01-13 02:20:37 EST
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.