[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[ecf-dev] https://bugs.eclipse.org/338062 (was Re: jms build/test)
- From: Markus Alexander Kuppe <ecf-dev_eclipse.org@xxxxxxxxxxx>
- Date: Thu, 24 Feb 2011 11:34:10 +0100
- Delivered-to: firstname.lastname@example.org
- User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:126.96.36.199) Gecko/20101208 Lightning/1.0b2 Thunderbird/3.1.7
On 02/24/2011 12:53 AM, Scott Lewis wrote:
> Hi Markus,
> I don't understand this (from the log for the junit launch):
> !ENTRY org.eclipse.osgi 4 0 2011-02-23 17:38:34.005
> !MESSAGE Application error
> !STACK 1
> java.lang.IllegalArgumentException: Bundle
> "org.eclipse.ecf.tests.provider.jms.activemq" not found. Possible causes
> include missing dependencies, too restrictive version ranges, or a
> non-matching required execution environment.
> as I'm pretty sure the o.e.e.tests.provider.jms.activemq bundle is
> actually there (it was there, and I didn't remove it or anything), and I
> didn't actually change the dependencies...other than removing a single
> test class that was made obsolete by the RSA stuff.
> So I'm confused about how to diagnose further...any ideas appreciated.
> Could it be something about the VM version requirement or something? (I
> believe I may have seen these sorts of junit classload failures locally
> when the jre version is out of line somehow)
> On 2/23/2011 11:33 AM, Markus Alexander Kuppe wrote:
>> On 02/23/2011 08:14 PM, Scott Lewis wrote:
>>> Hi Folks,
>>> The JMS build  seems to be failing because the test launch config is
>>> not starting...i.e. here's what's at the bottom of the log:
>>> <output deleted>
>>> INFO: bglaunch '--launch'
>>> 'org.eclipse.ecf.tests.provider.jms.activemq/' '--ignoremissing'
>>> INFO: junit '--launch'
>>> '-o' '/opt/hudson/jobs/C-HEAD-jms.feature/workspace//junit_result.xml'
>>> ERROR: The application could not start. Details can be found in the log.
>>> WARN: Process /opt/sun-jdk-188.8.131.52/bin/java (Feb 23, 2011 5:38:31 PM)
>>> terminated with exit status 13.
>>> Recording test results
>>> [WARNINGS] Skipping publisher since build result is FAILURE
>>> Archiving artifacts
>>> Sending e-mails to: ecf-build@xxxxxxxxxxx
>>> Sending e-mails to: ecf-build@xxxxxxxxxxx slewis@xxxxxxxxxxxxx
>>> Finished: FAILURE
>>> Anyone know why this would be? Where is the log described in 'Details
>>> can be found in the log.'?