Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » Buckminster vs. Emma/jUnit: "Cannot open launch config" (Eclipse 3.6)
Buckminster vs. Emma/jUnit: "Cannot open launch config" (Eclipse 3.6) [message #544479] Fri, 02 July 2010 18:44 Go to next message
Christian Kesselheim is currently offline Christian Kesselheim
Messages: 59
Registered: June 2010
Member
Hi everybody,

my first attempt to integrate jUnit/Emma seems to have failed, though I
don't know what it precisely is that I must have done wrong.

When calling the emma or junit headless commands as described in "the
book", I get a simply but strangely confusing message: "Cannot open
launch config from XXX". Strange enough, since the launch configuration
path & file in question seems to be perfectly fine.

I've ruled out a lack of file permissions and/or an outdated
buckminster/emma plugin version so far (just upgraded to the most recent
3.6 version for both), so perhaps someone from the community has an idea
on how to proceed?!

Here's what I get so far:

======================= (Console) ==================================
$ java
-Dbuckminster.output.root=/var/lib/hudson/jobs/myproject/wor kspace/buckminster.output
-Dbuckminster.temp.root=/var/lib/hudson/jobs/myproject/works pace/buckminster.temp
-Xms256m -Xmx512m -Declipse.consoleLog=true -jar
/var/lib/hudson/tools/Buckminster_3.6/buckminster/plugins/or g.eclipse.equinox.launcher_1.1.0.v20100507.jar
-application org.eclipse.buckminster.cmdline.headless -data
/var/lib/hudson/jobs/myproject/workspace --loglevel debug -S
/var/lib/hudson/jobs/myproject/workspace/commands.txt
!SESSION 2010-07-02 20:36:40.030
-----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_20
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Framework arguments: -application
org.eclipse.buckminster.cmdline.headless --loglevel debug -S
/var/lib/hudson/jobs/myproject/workspace/commands.txt
Command-line arguments: -application
org.eclipse.buckminster.cmdline.headless -data
/var/lib/hudson/jobs/myproject/workspace --loglevel debug -S
/var/lib/hudson/jobs/myproject/workspace/commands.txt

!ENTRY org.eclipse.buckminster.runtime 0 293 2010-07-02 20:36:41.475
!MESSAGE build
build

!ENTRY org.eclipse.buckminster.core 0 293 2010-07-02 20:36:41.555
!MESSAGE Doing full workspace refresh
Doing full workspace refresh

!ENTRY org.eclipse.buckminster.core 0 293 2010-07-02 20:36:41.556
!MESSAGE Waiting for jobs to end
Waiting for jobs to end

!ENTRY org.eclipse.buckminster.runtime 0 293 2010-07-02 20:36:41.806
!MESSAGE emma '-m' '-l'
'/var/lib/hudson/jobs/myproject/workspace/lu.kreios.myprojec t.client.tests/lu.kreios.myproject.client.tests.launch'
'-o'
'/var/lib/hudson/jobs/myproject/workspace//buckminster.outpu t/junit.results/TEST-lu.kreios.myproject.client.tests-all.xm l'
'--xml'
'/var/lib/hudson/jobs/myproject/workspace//buckminster.outpu t/emma.results/coverage.xml'
'--html'
'/var/lib/hudson/jobs/myproject/workspace//buckminster.outpu t/emma.results/coverage.html'
emma '-m' '-l'
'/var/lib/hudson/jobs/myproject/workspace/lu.kreios.myprojec t.client.tests/lu.kreios.myproject.client.tests.launch'
'-o'
'/var/lib/hudson/jobs/myproject/workspace//buckminster.outpu t/junit.results/TEST-lu.kreios.myproject.client.tests-all.xm l'
'--xml'
'/var/lib/hudson/jobs/myproject/workspace//buckminster.outpu t/emma.results/coverage.xml'
'--html'
'/var/lib/hudson/jobs/myproject/workspace//buckminster.outpu t/emma.results/coverage.html'

!ENTRY org.eclipse.buckminster.core 0 293 2010-07-02 20:36:41.939
!MESSAGE Doing full workspace refresh
Doing full workspace refresh

!ENTRY org.eclipse.buckminster.core 0 293 2010-07-02 20:36:41.953
!MESSAGE Waiting for jobs to end
Waiting for jobs to end
Cannot open launch config from
/var/lib/hudson/jobs/myproject/workspace/lu.kreios.myproject .client.tests/lu.kreios.myproject.client.tests.launch
============================================================ ========

Perhaps its a problem of the new and improved headless jUnit
functionality in 3.6 not being 100% compatible with Buckminster or the
Emma plug-in at present?

Any clues?

Thanks a lot in advance,

Chris

[Updated on: Fri, 02 July 2010 22:41]

Report message to a moderator

Re: Buckminster vs. Emma/jUnit: "Cannot open launch config" (Eclipse 3.6) [message #544644 is a reply to message #544479] Mon, 05 July 2010 07:52 Go to previous messageGo to next message
Stephan  is currently offline Stephan
Messages: 36
Registered: July 2009
Member
Hi Chris

Did you import the project containing the launch.configuration into your workspace (e.g., with a cquery)? Just checking it out to the file system is not sufficent.

Cheers, Stephan
Re: Buckminster vs. Emma/jUnit: "Cannot open launch config" (Eclipse 3.6) [message #544650 is a reply to message #544644] Mon, 05 July 2010 08:02 Go to previous messageGo to next message
Christian Kesselheim is currently offline Christian Kesselheim
Messages: 59
Registered: June 2010
Member
Yes, I did Sad. Otherwise, the remaining parts of my build (e.g. p2 update site creation) probably wouldn't run through. In my previous post, I just left their output out for brevity's sake.

Any idea on how to force Buckminster to give me more information about what's going on behind the scenes? Use tracing? Attach a remote debugger?

Thanks in advance,

Chris
Re: Buckminster vs. Emma/jUnit: "Cannot open launch config" (Eclipse 3.6) [message #544717 is a reply to message #544650] Mon, 05 July 2010 10:55 Go to previous messageGo to next message
Henrik Lindberg is currently offline Henrik Lindberg
Messages: 2500
Registered: July 2009
Senior Member
First two steps...
Turn off multithreaded operation
Turn on debug level logging
- Henrik

Christian Kesselheim <christian.kesselheim@kreios.lu> wrote:
> Yes, I did :(. Otherwise, the remaining parts of my build (e.g. p2
> update site creation) probably wouldn't run through. In my previous
> post, I just left their output out for brevity's sake.
>
> Any idea on how to force Buckminster to give me more information about
> what's going on behind the scenes? Use tracing? Attach a remote
> debugger?
>
> Thanks in advance,
>
> Chris


--
- henrik
Re: Buckminster vs. Emma/jUnit: "Cannot open launch config" (Eclipse 3.6) [message #545461 is a reply to message #544479] Wed, 07 July 2010 20:51 Go to previous messageGo to next message
Achim Demelt is currently offline Achim Demelt
Messages: 160
Registered: July 2009
Senior Member
Christian,

The path given after the "-l" argument must be a path that can be resolved
within the workspace, and not an absolute path in the file system. In your
case, instead of "-l
/var/lib/hudson/jobs/myproject/workspace/lu.kreios.myproject .client.tests/lu.kreios.myproject.client.tests.launch "
you must to use "-l
lu.kreios.myproject.client.tests/lu.kreios.myproject.client. tests.launch "

HTH,
Achim

Christian Kesselheim wrote:

> Hi everybody,
>
> my first attempt to integrate jUnit/Emma seems to have failed, though I
> don't know what it precisely is that I must have done wrong.
>
> When calling the emma or junit headless commands as described in "the
> book", I get a simply but strangely confusing message: "Cannot open
> launch config from XXX". Strange enough, since the launch configuration
> path & file in question seems to be perfectly fine.
>
> I've ruled out a lack of file permissions and/or an outdated
> buckminster/emma plugin version so far (just upgraded to the most recent
> 3.6 version for both), so perhaps someone from the community has an idea
> on how to proceed?!
>
> Here's what I get so far:
>
> ======================= (Console) ==================================
> $ java
> -
Dbuckminster.output.root=/var/lib/hudson/jobs/myproject/work space/buckminster.output
> -
Dbuckminster.temp.root=/var/lib/hudson/jobs/myproject/worksp ace/buckminster.temp
> -Xms256m -Xmx512m -Declipse.consoleLog=true -jar
>
/var/lib/hudson/tools/Buckminster_3.6/buckminster/plugins/or g.eclipse.equinox.launcher_1.1.0.v20100507.jar
> -application org.eclipse.buckminster.cmdline.headless -data
> /var/lib/hudson/jobs/myproject/workspace --loglevel debug -S
> /var/lib/hudson/jobs/myproject/workspace/commands.txt
> !SESSION 2010-07-02 20:36:40.030
> -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.6.0_20
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
> Framework arguments: -application
> org.eclipse.buckminster.cmdline.headless --loglevel debug -S
> /var/lib/hudson/jobs/myproject/workspace/commands.txt
> Command-line arguments: -application
> org.eclipse.buckminster.cmdline.headless -data
> /var/lib/hudson/jobs/myproject/workspace --loglevel debug -S
> /var/lib/hudson/jobs/myproject/workspace/commands.txt
>
> !ENTRY org.eclipse.buckminster.runtime 0 293 2010-07-02 20:36:41.475
> !MESSAGE build
> build
>
> !ENTRY org.eclipse.buckminster.core 0 293 2010-07-02 20:36:41.555
> !MESSAGE Doing full workspace refresh
> Doing full workspace refresh
>
> !ENTRY org.eclipse.buckminster.core 0 293 2010-07-02 20:36:41.556
> !MESSAGE Waiting for jobs to end
> Waiting for jobs to end
>
> !ENTRY org.eclipse.buckminster.runtime 0 293 2010-07-02 20:36:41.806
> !MESSAGE emma '-m' '-l'
>
'/var/lib/hudson/jobs/myproject/workspace/lu.kreios.myprojec t.client.tests/lu.kreios.myproject.client.tests.launch'
> '-o'
>
'/var/lib/hudson/jobs/myproject/workspace//buckminster.outpu t/junit.results/TEST-
lu.kreios.myproject.client.tests-all.xml'
> '--xml'
>
'/var/lib/hudson/jobs/myproject/workspace//buckminster.outpu t/emma.results/coverage.xml'
> '--html'
>
'/var/lib/hudson/jobs/myproject/workspace//buckminster.outpu t/emma.results/coverage.html'
> emma '-m' '-l'
>
'/var/lib/hudson/jobs/myproject/workspace/lu.kreios.myprojec t.client.tests/lu.kreios.myproject.client.tests.launch'
> '-o'
>
'/var/lib/hudson/jobs/myproject/workspace//buckminster.outpu t/junit.results/TEST-
lu.kreios.myproject.client.tests-all.xml'
> '--xml'
>
'/var/lib/hudson/jobs/myproject/workspace//buckminster.outpu t/emma.results/coverage.xml'
> '--html'
>
'/var/lib/hudson/jobs/myproject/workspace//buckminster.outpu t/emma.results/coverage.html'
>
> !ENTRY org.eclipse.buckminster.core 0 293 2010-07-02 20:36:41.939
> !MESSAGE Doing full workspace refresh
> Doing full workspace refresh
>
> !ENTRY org.eclipse.buckminster.core 0 293 2010-07-02 20:36:41.953
> !MESSAGE Waiting for jobs to end
> Waiting for jobs to end
> Cannot open launch config from
>
/var/lib/hudson/jobs/myproject/workspace/lu.kreios.myproject .client.tests/lu.kreios.myproject.client.tests.launch
> ============================================================ ========
>
> Perhaps its a problem of the new and improved headless jUnit
> functionality in 3.6 not being 100% compatible with Buckminster or the
> Emma plug-in at present?
>
> Any clues?
>
> Thanks a lot in advance,
>
> Chris
Re: Buckminster vs. Emma/jUnit: "Cannot open launch config" (Eclipse 3.6) [message #546139 is a reply to message #545461] Sun, 11 July 2010 15:23 Go to previous message
Christian Kesselheim is currently offline Christian Kesselheim
Messages: 59
Registered: June 2010
Member
Achim: Argh, of course Smile. Stupid me!

Works like a charm, now.

Thanks,

Chris
Previous Topic:How to deal with source features in rmap
Next Topic:How-to ignore certain Eclipse builders (e.g. Checkstyle) as part of a headless build?
Goto Forum:
  


Current Time: Sat Oct 25 08:03:07 GMT 2014

Powered by FUDForum. Page generated in 0.03060 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software