Community
Participate
Working Groups
The shareProjectWithNewlyCreatedRepo test always fails and does so from its first occurrence in the project (commit 3efda97cee7e59041be6d1ef72dd0109b77698db, changeid I7827ed6f5987a8d4a97ff0ca414ee56b92e1c5b4) shareProjectWithNewlyCreatedRepo(org.eclipse.egit.ui.wizards.share.SharingWizardTest) Time elapsed: 6.359 sec <<< ERROR! org.eclipse.swtbot.swt.finder.exceptions.WidgetNotFoundException: Could not find widget. at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntilWidgetAppears(SWTBotFactory.java:348) at org.eclipse.swtbot.swt.finder.SWTBotFactory.widget(SWTBotFactory.java:308) at org.eclipse.swtbot.swt.finder.SWTBot.table(SWTBot.java:2003) at org.eclipse.swtbot.swt.finder.SWTBot.table(SWTBot.java:1993) at org.eclipse.egit.ui.wizards.share.SharingWizard.openWizard(SharingWizard.java:30) at org.eclipse.egit.ui.wizards.share.SharingWizardTest.shareProjectWithNewlyCreatedRepo(SharingWizardTest.java:71) 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:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.eclipse.swtbot.swt.finder.junit.SWTBotJunit4ClassRunner.run(SWTBotJunit4ClassRunner.java:54) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) at org.codehaus.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:75) at org.codehaus.tycho.surefire.osgibooter.AbstractUITestApplication.runTests(AbstractUITestApplication.java:34) at org.eclipse.ui.internal.testing.WorkbenchTestable$1.run(WorkbenchTestable.java:71) at java.lang.Thread.run(Thread.java:619) Caused by: org.eclipse.swtbot.swt.finder.widgets.TimeoutException: Timeout after: 5000 ms.: Could not find widget matching: (of type 'Table') at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntil(SWTBotFactory.java:398) at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntil(SWTBotFactory.java:372) at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntil(SWTBotFactory.java:360) at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntilWidgetAppears(SWTBotFactory.java:346) ... 33 more Platform details: Ubuntu 10.04 KDE 4
when run from Maven it needs to set an appropriate ceiling directory otherwise it will find egit's .git directory
I'll have a look at that. I should have run the maven build locally.
I proposed a fix for the maven problem: http://egit.eclipse.org/r/#change,756 However, the problem Robin reports seems to be different. The SWTBot does not find the table on the Share Project wizard.
The problem here might be that previously failing tests don't clean up so the sharing wizard does not open on the first page, i.e. the one where selection of team provider should occur.
(In reply to comment #4) > The problem here might be that previously failing tests don't clean up so the > sharing wizard does not open on the first page, i.e. the one where selection > of team provider should occur. Forget the part of previously failing test. Even when all previous test pass the same behaviour happens. The wizard's stepo team provider selection is bypassed.
Even with all other tests deleted this one fails
There is only one team provider so Ecliupse doesn't ask the one option only question and proceeds directly to the only possible wizard.
Proposed fix at at http://egit.eclipse.org/r/774 (include the CVS provider)
Merged
