Bugzilla – Full Text Bug Listing
| Summary: | Can't execute tests in MDT/OCL hudson's job | ||
|---|---|---|---|
| Product: | Community | Reporter: | Adolfo Sanchez-Barbudo Herrera <adolfosbh> |
| Component: | CI-Jenkins | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | matthias.sohn, mtaal, sbouchet |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows Vista | ||
| Whiteboard: | |||
|
Description
Adolfo Sanchez-Barbudo Herrera
Not really. Perhaps the folks on Cross-project have some ideas. -M. - Has the user hudson is using the necessaryfilesystem permissions to see this file ?
- Does ${WORKSPACE} end with a slash ? Otherwise ${WORKSPACE}org.eclipse.mdt/org.eclipse.ocl/releng/org.eclipse.ocl.build-feature/org.eclipse.ocl.tests.launch
would translate to something like
/opt/users/hudsonbuild/.hudson/jobs/buckminster-mdt-ocl-core-nightly/workspaceorg.eclipse.mdt/org.eclipse.ocl/releng/org.eclipse.ocl.build-feature/org.eclipse.ocl.tests.launch
I had the same issue, my problem was that I was materializing the project
containing the launch.config as an eclipse.feature. This resulted in that the
project got a wrong resource path in the workspace (the string -feature was
appended to it by buckminster).
This reply from Thomas solved it for me:
Have a look at the buckminster.cspex in the plugins that get the "-feature"
suffix. They contain the following:
<cspecExtension
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:bc="http://www.eclipse.org/buckminster/Common-1.0"
xmlns="http://www.eclipse.org/buckminster/CSpec-1.0"
componentType="eclipse.feature" version="1.0.0">
Pay special attention to the part that says componentType="eclipse.feature" ;-)
I suggest you remove both the componentType and the version attribute unless
you really want to redefine them.
If you update this bugzilla with your findings then I can refer to it from the
newsgroup (there is a thread in there in which I still need to publish the
solution).
btw, the best way of finding these issues is to do the build run locally. Then
you can open the downloaded workspaces in Eclipse and check them in detail.
gr. Martin
Hi Matthias, Martin, Thanks very much for your quick replies. As commented is not a problem of the path of the config file. The output console says: Cannot open launch config from /opt/users/hudsonbuild/.hudson/jobs/buckminster-mdt-ocl-core-nightly/workspace/org.eclipse.mdt/org.eclipse.ocl/releng/org.eclipse.ocl.build-feature/org.eclipse.ocl.tests.launch and if I do the following in build.eclipse.org: vi /opt/users/hudsonbuild/.hudson/jobs/buckminster-mdt-ocl-core-nightly/workspace/org.eclipse.mdt/org.eclipse.ocl/releng/org.eclipse.ocl.build-feature/org.eclipse.ocl.tests.launch I can actually edit the launch configuration file. Regarding hudson's access permissions, yes since it's a file from the job's workspace it shouldn't be a permissions issue, actually: -rw-r--r-- 1 hudsonbuild callisto-dev 2614 2010-09-09 13:06 org.eclipse.ocl.tests.launch Any other ideas ? Cheers, Adolfo. I don't mean the path in the file system, I mean the resource path of the project (containing the launch config) in the workspace. You can find it by right clicking on a project in eclipse and check the project properties. The path you specify is used to find the workspace resources using their resource paths, this is something different from file system paths.
Another thing is that I don't have the ${workspace} in front of the launch config path, this is what I have in the ant xml I have:
<buckminster command="junit" workspace="${workspacePath}">
<cmdargs>
<arg value="-l" />
<arg value="org.eclipse.emf.texo.test.all/TexoAllTests.launch" />
<arg value="-o" />
<arg value="${testResultsPath}/test-results-texo.xml" />
<arg value="--stdout" />
<arg value="${testResultsPath}/stdout.txt" />
<arg value="--stderr" />
<arg value="${testResultsPath}/stderr.txt" />
<arg value="--flatXML"/>
</cmdargs>
</buckminster>
Also looking at your path, it seems strange to have the launch config inside of a feature project.
(In reply to comment #5) > I don't mean the path in the file system, I mean the resource path of the > project (containing the launch config) in the workspace. You can find it by > right clicking on a project in eclipse and check the project properties. The > path you specify is used to find the workspace resources using their resource > paths, this is something different from file system paths. > I understand, but since I'm using an absolute path to point to the launch configuration file, I simply don't understand why the file "can't be openned". Maybe the error is using that absolute path (see below). In any case, I don't have the componentType and version parameters in the cspec file. > Another thing is that I don't have the ${workspace} in front of the launch > config path, this is what I have in the ant xml I have: I have used both: - Firstly using a relative path in the form "project name"/"launch configuration file" as you have specified below. - Secondly using an absolute path as I'm currently specifying. I've been trying different bits and I haven't been able to solve the trouble. I must be doing something else wrong. > > <buckminster command="junit" workspace="${workspacePath}"> > <cmdargs> > <arg value="-l" /> > <arg value="org.eclipse.emf.texo.test.all/TexoAllTests.launch" > /> > <arg value="-o" /> > <arg value="${testResultsPath}/test-results-texo.xml" /> > <arg value="--stdout" /> > <arg value="${testResultsPath}/stdout.txt" /> > <arg value="--stderr" /> > <arg value="${testResultsPath}/stderr.txt" /> > <arg value="--flatXML"/> > </cmdargs> > </buckminster> > mmm maybe here could be a clue. I'm using a command directly written directly in the "Run buckminster" step: junit -DX.display="${DISPLAY}" --launch "${WORKSPACE}org.eclipse.mdt/org.eclipse.ocl/releng/org.eclipse.ocl.build-feature/org.eclipse.ocl.tests.launch" --flatXML --output "${WORKSPACE}_build_temp/test.results/org.eclipse.ocl.ecore.tests.xml" The output console shows how the command is executed INFO: junit '-DX.display=:20' '--launch' '/opt/users/hudsonbuild/.hudson/jobs/buckminster-mdt-ocl-core-nightly/workspace/org.eclipse.mdt/org.eclipse.ocl/releng/org.eclipse.ocl.build-feature/org.eclipse.ocl.tests.launch' '--flatXML' '--output' '/opt/users/hudsonbuild/.hudson/jobs/buckminster-mdt-ocl-core-nightly/workspace/_build_temp/test.results/org.eclipse.ocl.ecore.tests.xml' I'm wondering why I'm not setting a "workspace" parameter as you have. > Also looking at your path, it seems strange to have the launch config inside of > a feature project. Well, this comes from looking at what other Modeling projects do. I've also tried the (original) launch.configuration file of a plugin which is materialized in the following path in the job's workspace: https://build.eclipse.org/hudson/job/buckminster-mdt-ocl-core-nightly/ws/plugins/org.eclipse.ocl.ecore.tests/launches/ I'll be doing more tries right now. If you figure out any other source of problems with this new information, please let me know. Martin, Good news. The tests have finally been executed. My conclusions: - The launch.configuration file can't be stablished as a file system absolute path for the junit command. As you commented it must be a resource path. - I'm not sure why "org.eclipse.ocl.buid-feature/org.eclipse.ocl.tests.launch" didn't work when I firstly tried it. - Now it's working using the proper plugin which contains the launch configuration file "org.eclipse.ocl.ecore.tests/launches/org.eclipse.ocl.ecore.tests\ \(Standalone\).launch". Maybe when I tried this configuration file, I was already focused on the file system absolute paths. Thanks all very much for your help and interest. P.S: The bug can be closed. Cheers, Adolfo. Great to see this kind of teamwork. -M. |