Help wanted: Can't build tests component
by Victor Rubezhny
Hi, ALL!
Probably this question is actually for Nick or Denis but...
Trying to build tests component by tycho build but constantly getting
the following error as result (See the output below).
The question is: do I need to buy a newer PC (or at least install more
memory)? :o)
Any hints appreciated.
Best Regards,
Victor
=== Cut ===
[ERROR] GC overhead limit exceeded -> [Help 1]
java.lang.OutOfMemoryError: GC overhead limit exceeded
at java.util.Arrays.copyOfRange(Arrays.java:3209)
at java.lang.String.<init>(String.java:215)
at
com.sun.org.apache.xerces.internal.xni.XMLString.toString(XMLString.java:185)
at
com.sun.org.apache.xerces.internal.util.XMLAttributesImpl.getValue(XMLAttributesImpl.java:537)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser$AttributesProxy.getValue(AbstractSAXParser.java:2319)
at
org.eclipse.equinox.internal.p2.persistence.XMLParser$AbstractHandler.parseAttributes(XMLParser.java:314)
at
org.eclipse.equinox.internal.p2.persistence.XMLParser$AbstractHandler.parseRequiredAttributes(XMLParser.java:295)
at
org.eclipse.equinox.internal.p2.persistence.XMLParser$PropertyHandler.parseProperty(XMLParser.java:422)
at
org.eclipse.equinox.internal.p2.persistence.XMLParser$PropertyHandler.<init>(XMLParser.java:411)
at
org.eclipse.equinox.internal.p2.persistence.XMLParser$PropertiesHandler.startElement(XMLParser.java:396)
at
org.eclipse.equinox.internal.p2.persistence.XMLParser$AbstractHandler.startElement(XMLParser.java:165)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:501)
at
com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:179)
at
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:377)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2755)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
at
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
at
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
at
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
at
org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryIO$Parser.parse(MetadataRepositoryIO.java:209)
at
org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryIO.read(MetadataRepositoryIO.java:63)
at
org.eclipse.equinox.internal.p2.metadata.repository.SimpleMetadataRepositoryFactory.load(SimpleMetadataRepositoryFactory.java:107)
at
org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:57)
at
org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:749)
at
org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:651)
at
org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
at
org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
at
org.eclipse.tycho.p2.target.TargetPlatformBuilderImpl.addP2Repository(TargetPlatformBuilderImpl.java:259)
[ERROR]
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryError
j
12 years, 7 months
Missing win32 x86_64 configuration in parent pom
by Jiri Peterka
Hi Nick,
is there any reason for missing configuration for win32 x86_64 in
https://anonsvn.jboss.org/repos/jbosstools/trunk/build/parent/pom.xml in
target-platform-configuration plugin? It seems to be necessary to make
bot test running properly on w64 and it would be good to have it defined
in parent pom. Please add it there if possible
Thanks, regards
Jirka
--- pom.xml 2012-04-25 15:47:26.045219150 +0200
+++ pom2.xml 2012-04-25 15:49:12.195802290 +0200
@@ -149,6 +149,11 @@
<arch>x86</arch>
</environment>
<environment>
+ <os>win32</os>
+ <ws>win32</ws>
+ <arch>x86_64</arch>
+ </environment>
+ <environment>
<os>linux</os>
<ws>gtk</ws>
<arch>x86</arch>
12 years, 7 months
Fwd: Port forwarding
by Max Andersen
Hi Xavier,
Moved to jbosstools list.
And yes, I think that kind of ui would
work great; but doesn't have to be for beta3 :)
Where would you put it ?
As a property on the app ?
/max (sent from my phone)
Begin forwarded message:
> From: Xavier Coulon <xcoulon(a)redhat.com>
> Date: 23. apr. 2012 23.50.26 CEST
> To: Max Andersen <manderse(a)redhat.com>
> Subject: Port forwarding
>
> Hi Max,
>
> Moving on the 'Port forwarding' setup dialog window, just remembered the TCP/IP monitor one:
>
>
>
>
> The nice thing about this table viewer is the "status" and "start" & "stop" buttons..
> Something to reproduce in our tooling, or not ?
>
> Thanks for your feedback.
>
> See you tomorrow
> /Xavier
>
>
>
12 years, 7 months
Automated Tests in tests/ module: What are the Annotated*.java ?
by Mickael Istria
Hello,
Working on the 2 following bugs:
* https://issues.jboss.org/browse/JBIDE-11370 : Get all components to
have tests, and get rid of the "in case there is not test" build steps
* https://issues.jboss.org/browse/JBIDE-11600 :
org.jboss.tools.tests.tests.UtilsTest - java.lang.AssertionError: Not
yet implemented
We are trying to set up the necessary stuff to ensure all modules can
easily write tests and get them executed in their builds without effort.
The issue is that we had to create a dummy test for the tests/ modules
since it did not had test before. The tests modules provides an API to
write tests for JBT/JBDS, so it makes a lot of sense to set up some
tests for this test API, which is used all over the product. But this
dummy test is too dummy. Looking deeper in the content of the tests
module, it looks like there are some automated tests in the plugins/
folder, those tests are not automatically executed at build time. This
is not a clean layout and behavior.
So I am wondering: *what is the purpose of
org.jboss.tools.ui.bot.ext.test.config.Suite and Annotated* class*?
Can/Should it be used for CI testing? I tried it with surefire and got 7
of 9 tests successful.
If this can be automated, please find attached a patch containing the
necessary change to follow the "normal" layout and enable those tests.
If this is not meant to be automated, then what is this?
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
12 years, 7 months