Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 322682 - JUnit action fails, can't open launch configuration.
Summary: JUnit action fails, can't open launch configuration.
Status: RESOLVED INVALID
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Buckminster (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: buckminster.core-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-13 14:31 EDT by Miles Parker CLA
Modified: 2019-02-25 14:41 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Miles Parker CLA 2010-08-13 14:31:36 EDT
Buckminster can't find my junit launch file. I'm still not sure that this isn't a configuration issue on my end, but I've tried everything I can think of to fix it. This happens on Eclipse build and local build. I haven't been able to get 

*************
Message:

Cannot open launch config from org.eclipse.amp.build/org.eclipse.amp.amf.acore.test.launch
[snip: unrelated SVN issue]
Archiving artifacts
Finished: FAILURE

*************
Configuration:

setpref targetPlatformPath="${WORKSPACE}/buildroot/target.platform"

import -Declipse.download="file:/home/data/httpd/download.eclipse.org" "${checkout.location}org.eclipse.amp/releng/org.eclipse.amp.releng/releng/amp-platform.cquery"

resolve "${checkout.location}org.eclipse.amp/releng/org.eclipse.amp.releng/releng/amp.cquery"

build

junit --launch "org.eclipse.amp.build/org.eclipse.amp.amf.acore.test.launch" --flatXML --output "${WORKSPACE}/amp.test.results/org.eclipse.amp.amf.acore.tests.xml"
junit --launch "org.eclipse.amp.build/org.eclipse.amf.acore.edit.test.launch" --flatXML --output "${WORKSPACE}/amp.test.results/org.eclipse.amf.acore.edit.tests.xml"

perform --properties "${WORKSPACE}/buildroot/build.properties" "org.eclipse.amp.build#build"
perform --properties "${WORKSPACE}/buildroot/build.properties" "org.eclipse.amp.releng#setup.promoter"

*************
Releng project:   /cvsroot/modeling org.eclipse.amp/releng/org.eclipse.amp.releng

Build Project: /cvsroot/modeling org.eclipse.amp/org.eclipse.amp/features/org.eclipse.amp.build

*************
Job: https://build.eclipse.org/hudson/view/Athena%20CBI/job/cbi-amp-nightly/

*************
Console (this won't stick around forever): https://build.eclipse.org/hudson/view/Athena%20CBI/job/cbi-amp-nightly/609/console

*************

See: http://www.eclipse.org/forums/index.php?t=rview&goto=552673#msg_552673If
Comment 1 Miles Parker CLA 2010-08-13 22:22:28 EDT
OK, I went through the procedure of installing the whole thing in my workspace, and discovered that my .project file was named org.eclipse.amp.build.feature. Argh! The test hasn't completed yet but I'm going to assume that that was the issue. Marking invalid.