On Tue, 2017-01-10 at 19:23 -0500, Konrad Windszus wrote: > I fixed the previous testing errors in for the sling-ide build 91, > but build 92 fails now in > > org.eclipse.swtbot.swt.finder.widgets.TimeoutException: Timeout > after: 5000 ms.: Could not find auto complete proposal using matcher > table with item () > at > org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntil(SWTBotFactory.j > ava:437) > at > org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntil(SWTBotFactory.j > ava:411) > at > org.eclipse.swtbot.eclipse.finder.widgets.SWTBotEclipseEditor.waitUnt > il(SWTBotEclipseEditor.java:784) > at > org.eclipse.swtbot.eclipse.finder.widgets.SWTBotEclipseEditor.getAuto > CompleteProposals(SWTBotEclipseEditor.java:245) > at > org.apache.sling.ide.test.impl.ui.sightly.SightlyAutocompletionTest$A > utocompletionCallable.call(SightlyAutocompletionTest.java:145) > at > org.apache.sling.ide.test.impl.ui.sightly.SightlyAutocompletionTest.a > ttributeAutocompletion(SightlyAutocompletionTest.java:84) > > @Robert: Do you have any idea how we could make the SWTBot based > tests more reliable. Should we increase the timeout like described in > https://wiki.eclipse.org/SWTBot/FAQ#Can_I_change_the_timeout_for_exec > ution_of_SWTBot_tests.3F?
I am not sure if it's a timing issue or another instability in the tests. We can try increasing the timeout, sure, but that's no guarantee it won't fail in another 10 runs. Robert > > > > > On 10 Jan 2017, at 19:08, Apache Jenkins Server <[email protected] > > che.org> wrote: > > > > See <https://builds.apache.org/job/sling-ide/changes> > > > >
