Community
Participate
Working Groups
http://download.eclipse.org/eclipse/downloads/drops4/N20141120-2000/testresults/html/org.eclipse.swt.tests_macosx.cocoa.x86_64_7.0.html junit.framework.AssertionFailedError at org.eclipse.swt.tests.junit.browser.Test_BrowserSuite.testBrowser5(Test_BrowserSuite.java:41) 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)
Haven't seen this failure happen before and no recent code changes that could have caused it, it could either be something intermittent or is related to the Mac test machine's upgrade to Yosemite (bug 447634).
Fails consistently.
I ran the tests locally on both OSX 10.9 & 10.10 and the tests pass on both machines. But, it seems to coincide with upgrading the test machine to Yosemite. (bug in comment 2). Dani, If it is possible to view the console output, I'll set the verbose flag to true for this test for the next N-build and check the output?
(In reply to Lakshmi Shanmugam from comment #3) > I ran the tests locally on both OSX 10.9 & 10.10 and the tests pass on both > machines. > But, it seems to coincide with upgrading the test machine to Yosemite. (bug > in comment 2). > > Dani, > If it is possible to view the console output, I'll set the verbose flag to > true for this test for the next N-build and check the output? Yes, the console can be seen.
Console output: PLUGIN_PATH </Users/hudsonBuild/workspace/ep45N-unit-mac64/workarea/N20141124-2000/eclipse-testing/test-eclipse/eclipse/plugins/org.eclipse.swt.tests_3.104.0.N20141124-2000> javascript window.open with location and size parameters - args: /Users/hudsonBuild/workspace/ep45N-unit-mac64/workarea/N20141124-2000/eclipse-testing/test-eclipse/eclipse/plugins/org.eclipse.swt.tests_3.104.0.N20141124-2000/data/browser5.html Expected Event Sequence: Visibility.show OpenWindow 0 Visibility.show browser 0 location Point {100, 157} size Point {1300, 663} Expected location Point {100, 200} size Point {300, 100} Failure Browser location is (100, 157) instead of (100, 200). Not sure why.
Same test failure happens in M-build too (M20141203-0800).
Temporarily disabled the test for both master and maintenance branch. http://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/?id=71bce95db2e48a63fb52c99ffea76a1881b01017 http://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/?h=R4_4_maintenance&id=e6418e1f3b0b7edb3cc890823f7d842b14646659
The tests have been refactored in master (4.8) and Bug 525339 tracks the intermittent failures of the test on the 4.7.1 maintenance branch. Closing report.
