Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jdt-dev] Performance tests failing with Tycho: "We should have found org.eclipse.jdt.core project in workspace!!!"

Adding platform-releng-dev as CC in case someone there has a clue.

On 11/06/2013 10:29 AM, Mickael Istria wrote:
Hi all,

As we've made progress with having tests running with surefire (and then later enable Hudson vote plugin for Gerrit), I see that it's currently impossible to run Performance Tests with Tycho.
Indeed, if you go in org.eclipse.jdt.core.tests.performance module, and run:
  $ mvn clean verify -Pbuild-individual-bundles -DskipTests=false -Dmaven.test.skip=false
You get the following report from surefire:
Failed tests:   testSearchAllTypeNameMatches(org.eclipse.jdt.core.tests.performance.FullSourceWorkspaceSearchTests): We should have found org.eclipse.jdt.core project in workspace!!!
  testSearchType(org.eclipse.jdt.core.tests.performance.FullSourceWorkspaceSearchTests): We should have found org.eclipse.jdt.core project in workspace!!!
  testSearchField(org.eclipse.jdt.core.tests.performance.FullSourceWorkspaceSearchTests): We should have found org.eclipse.jdt.core project in workspace!!!
  testSearchMethod(org.eclipse.jdt.core.tests.performance.FullSourceWorkspaceSearchTests): We should have found org.eclipse.jdt.core project in workspace!!!
  ...
This seems to mean that org.eclipse.jdt.core must be available as a project in workspace. Then I have a few questions:
1. Are this tests executed by current builder? If not, I can simply make them become an "eclipse-plugin" instead of "eclipse-test-plugin".
2. Is this really mandatory to have a project there? Wouldn't the jar'd plugin be enough? I don't know anything about how this performance test are run. Is it using this approach: http://git.eclipse.org/c/platform/eclipse.platform.releng.git/plain/bundles/org.eclipse.test.performance/doc/Performance%20Tests%20HowTo.html ?
3. Where is this project expected to come from? IMO, the test should be responsible of setting up its resources (ideally in a JUnit @Before or @BeforeClass, or in the script running it) but it appears it's not what is happening here.

Thanks in advance.

--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets

Back to the top