[
https://issues.jboss.org/browse/JBIDE-16755?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-16755:
------------------------------------
Some logged errors / warnings include:
{code}
11:07:06 Caused by: org.osgi.service.resolver.ResolutionException: Uses constraint
violation.
Unable to resolve resource
org.eclipse.jpt.dbws.eclipselink.ui [osgi.identity;
osgi.identity="org.eclipse.jpt.dbws.eclipselink.ui";
type="osgi.bundle"; version:Version="1.1.100.v201310142259";
singleton:="true"]
because it is exposed to package 'javax.xml.bind' from resources
org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi";
type="osgi.bundle"; version:Version="3.10.0.v20140121-0337";
singleton:="true"] and
javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind";
type="osgi.bundle"; version:Version="2.1.9.v201005080401"]
via two dependency chains.
{code}
{code}
11:19:49 org.eclipse.core.runtime.CoreException: No property tester contributes a property
com.google.gdt.eclipse.suite.isLaunchTarget to type class
org.jboss.tools.central.editors.JBossCentralEditorInput
{code}
{code}
11:19:49 !MESSAGE Internal browser is not available: No more handles
12:19:58 Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3,615.041 sec
{code}
{code}
12:19:58 Testcase: testInstall took 3,613.384 sec
12:19:58 Caused an ERROR
12:19:58 Timeout after: 3600000 ms.: Blocking while calculating deps
12:19:58 org.eclipse.swtbot.swt.finder.widgets.TimeoutException: Timeout after: 3600000
ms.: Blocking while calculating deps
12:19:58 at
org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntil(SWTBotFactory.java:412)
12:19:58 at
org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntil(SWTBotFactory.java:386)
12:19:58 at
org.jboss.tools.tests.installation.InstallFromCentralTest.testInstall(InstallFromCentralTest.java:90)
12:19:58 at
org.eclipse.swtbot.swt.finder.junit.SWTBotJunit4ClassRunner.run(SWTBotJunit4ClassRunner.java:54)
12:19:58 at
org.eclipse.swtbot.eclipse.junit.headless.EclipseTestRunner.run(EclipseTestRunner.java:350)
12:19:58 at
org.eclipse.swtbot.eclipse.junit.headless.EclipseTestRunner.run(EclipseTestRunner.java:208)
12:19:58 at
org.eclipse.swtbot.eclipse.junit.headless.UITestApplication.runTests(UITestApplication.java:116)
12:19:58 at
org.eclipse.e4.ui.internal.workbench.swt.E4Testable$1.run(E4Testable.java:72)
12:19:58 at java.lang.Thread.run(Thread.java:744)
{code}
{code}
12:20:13 !MESSAGE "JBoss Tools Common - Mylyn" will be ignored because it is
already installed.
12:20:13 !MESSAGE "Eclipse Git Team Provider" is already present because other
installed software requires it. It will be added to the installed software list.
12:20:13 !MESSAGE "Mylyn Tasks Connector: Bugzilla" is already installed, so an
update will be performed instead.
12:20:13 !MESSAGE "Mylyn Commons" is already present because other installed
software requires it. It will be added to the installed software list.
12:20:13 !MESSAGE "Mylyn Task-Focused Interface" is already present because
other installed software requires it. It will be added to the installed software list.
12:20:13 !MESSAGE "Task focused interface for Eclipse Git Team Provider" is
already present because other installed software requires it. It will be added to the
installed software list.
12:20:13 !MESSAGE "Java implementation of Git" is already present because other
installed software requires it. It will be added to the installed software list.
{code}
install-grinder failing in jenkins - build timing out
-----------------------------------------------------
Key: JBIDE-16755
URL:
https://issues.jboss.org/browse/JBIDE-16755
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build, testing-tools
Affects Versions: 4.2.0.Beta1
Reporter: Martin Malina
Assignee: Mickael Istria
Fix For: 4.2.0.Beta1
(Previously discussed in JBIDE-16269)
These builds are timing out:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g...
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira