JBT 3.3.0.M2 status -- test failures in CDI, JSF, Maven, Seam, WS, VPE, Struts
by Nick Boldt
Six (6) components are having some problems today. Here's the list!
----------------
== CDI ==
Many test failures (55?) in these suites:
org.jboss.tools.cdi.text.ext.test
org.jboss.tools.cdi.ui.test
org.jboss.tools.cdi.seam.config.ui.test
http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job...
Also, count of tests is down from 454 to 399 (55 tests failing to report
results) since June 9.
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--cdi...
== JSF ==
1 or 2 test failures since June 9:
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--jsf...
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--jsf...
== Maven ==
June 10, we had 6 passing tests. 10hrs later, we're down to ZERO passing
tests.
http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job...
Could this be due to me moving up to a newer version of m2e?
http://source.jboss.org/changelog/JBossTools/?cs=32015
== Seam ==
6 test failures in org.jboss.tools.seam.ui.test, and duplicate spins of
the same tests (?):
http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job...
== WS ==
4 test failures, 1 missing (down from 180 tests to 179).
http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job...
== VPE / Overall All-in-One test suite ==
The all-in-one test builder is reporting that nearly 800 tests are
missing since Friday - from 3239 tests in build #673 to 2441 in build #676!
Here are the test suites that vanished from the #673 build and are no
longer present in the #676 build - looks like it's all VPE-related tests
that have vanished.
Package Duration Fail (diff) Skip (diff) Total (diff)
org.jboss.tools.jsf.vpe.ajax4jsf.test 47 sec 0 0 24
org.jboss.tools.jsf.vpe.facelets.test 47 sec 0 0 14
org.jboss.tools.jsf.vpe.jbpm.test 20 sec 0 0 4
org.jboss.tools.jsf.vpe.jsf.test 9 min 25 sec 0 0 224
org.jboss.tools.jsf.vpe.jstl.test 1 min 13 sec 0 0 42
org.jboss.tools.jsf.vpe.myfaces.test 1 min 19 sec 0 0 43
org.jboss.tools.jsf.vpe.richfaces.test 2 min 39 sec 0 0 115
org.jboss.tools.jsf.vpe.seam.test 1 min 38 sec 0 0 65
org.jboss.tools.struts.vpe.struts.test 1 min 24 sec 0 0 89
org.jboss.tools.vpe.html.test 2 min 4 sec 0 0 111
org.jboss.tools.vpe.jsp.test 43 sec 0 0 23
org.jboss.tools.vpe.spring.test 55 sec 0 0 27
org.jboss.tools.vpe.ui.test 38 sec 0 0 12
org.jboss.tools.vpe.xulrunner.test 2.6 sec 0 0 7
Note that the VPE job itself is down from 219 tests to 192, suggesting
similar (or more?) test failures there too.
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
13 years, 7 months
MD5 hashes does not match
by Max Rydahl Andersen
Problems downloading artifact: osgi.bundle,org.jboss.tools.common.projecttemplates,3.3.0.v20110611-0147-H293-M2.
MD5 hash is not as expected. Expected: 889cd7babcfc1eec5fe0922688902007 and found 07669eb1ff891f644db48db795183d93.
I'm getting various incarnations of the above when trying to install/update from updatesite.
Is this one of those "nightly trunk is overwritten blindly" bugs again?
/max
http://about.me/maxandersen
13 years, 7 months
Be aware of nasty Indigo File leak!
by Max Rydahl Andersen
Hi,
This is about https://bugs.eclipse.org/bugs/show_bug.cgi?id=349105
Over the last couple of weeks we have had several bugs being reported on Linux systems in many parts of the
tooling about running out of file descriptors for no apparent reason.
Yesterday Snjezana discovered that the possible root cause for many of these are that equinox (the base of osgi in eclipse)
were not closing of the inputstreams of all jars in your eclipse install when you run with -clean OR after a fresh install/update
from an updatesite.
This causes Eclipse to crash almost instantly OR if you have a "smallish" installation it will survive for a while but then crash
when some operation in eclipse requires a bunch of file descriptors and crosses the magical "1000" limit Linux installations
by default run with.
The bug turned out to be a regression in Eclipse 3.7 codebase, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=349105 for
details and is currently in review for inclusion in the final release.
This mail is to just let you be aware of that if you get issues about file descriptors running out then restart eclipse and retry.
If it still fails then the problem is most likely still in your code, if it does not fail it is most likely caused by this Indigo regression.
FYI, on linux and mac you can see what files are held open by Eclipse by using lsof -p <pidofeclipse>
2XFYI, Mac users aren't affected by this since ulimit is set to unlimited and Windows does not have this kind of limitation. GAM or GAP! :)
/max
http://about.me/maxandersen
13 years, 7 months
Updated release dates for JBoss Tools 3.2.1 (3.3.0.M2 stays the same)
by Max Rydahl Andersen
Hi,
We had a call earlier today discussing how to steer the delayed 3.2.1.CR2 (assumed to become final) and 3.2 M2
The short version is that 3.2.0.M2 stays as planned and we shift/bend 3.2.1.CR2 around it.
That gives the following schedule:
1st June: 3.2.1.CR1pushed out to staging today (Nick will post about that when it happens)
14th June: 3.3.0.M2 code freeze
~16th June: 3.3.0.M2 build candidate for QE/smoketesting
19th June: What's'new Ready for review/assembly
22nd June: 3.3.0.M2 release (together with AS7/Eclipse Indigo)
27th June: 3.2.1.CR2 Codefreeze
~30th June: 3.2.1.CR2 build candidate for QE/full testing on staging
~15th July: 3.2.1.Final rebuild / release
I'll get jira updated tonight/tomorrow to reflect these dates.
/max
http://about.me/maxandersen
13 years, 8 months
bot.tests ? what is that ?
by Max Rydahl Andersen
Hi,
It's apparently been around since April but I didn't notice it until today.
What is bot.tests ? Why is it there in the root and why is it named differently than everything else ?
The log message just says:
"r30495 | nickboldt | 2011-04-12 00:19:42 +0200 (Tue, 12 Apr 2011) | 1 line
move bot tests from tests/ module as they're all downstream from there; collect them all into a single update site here"
The content seem to just be one feature...who uses/maintain it ?
Is this not named better as integrationtests if its intended for some overall test updatesite/feature aggregator ?
/max
http://about.me/maxandersen
13 years, 8 months
Hibernate tools component build failures
by Denis Golovin
Dima,
could you take care of hibernate tools compilation errors. It's been
failing since May 30th. Looks like internal API was changed between Dali
releases.
[WARNING] The requested profile "unified.site" could not be activated because it does not exist.
[ERROR] Failed to execute goal org.sonatype.tycho:maven-osgi-compiler-plugin:0.10.0:compile (default-compile) on project org.jboss.tools.hibernate.jpt.core: Compilation failure: Compilation failure:
[ERROR] /qa/hudson_ws/workspace/jbosstools-3.3_trunk.component--hibernatetools/sources/plugins/org.jboss.tools.hibernate.jpt.core/src/org/jboss/tools/hibernate/jpt/core/internal/context/java/HibernateJavaQueryContainerImpl.java (at line 309):[-1,-1]
[ERROR] public Iterator<JavaQuery> queries() {
[ERROR] ^^^^^^^^^
[ERROR] The method queries() of type HibernateJavaQueryContainerImpl must override or implement a supertype method
[ERROR]
[ERROR] /qa/hudson_ws/workspace/jbosstools-3.3_trunk.component--hibernatetools/sources/plugins/org.jboss.tools.hibernate.jpt.core/src/org/jboss/tools/hibernate/jpt/core/internal/context/java/AbstractHibernateNamedQueryImpl.java (at line 25):[-1,-1]
[ERROR] public class AbstractHibernateNamedQueryImpl<T extends HibernateQueryAnnotation> extends AbstractJavaQuery<T>
Thanks
Denis
13 years, 8 months