On Sat, Apr 30, 2011 at 8:26 PM, Max Rydahl Andersen <
> cc'ed Yahor - doesn't this normally just happens because
we run on a
server without the right libraries and thus the eclipse simply dies?
> Or is there something else known about this Yahor ? you mentioned looking
into reducing number of tests to avoid duplication ? Sounds like
> a rather big reduction though ?
> Any prooflink? I found only these two: , . No failed tests here,
and their number is >>17.
In there its -49 tests...also weird is it not ?
No, this is OK. This is because the reducing you mentioned above (
> > * Seam has 3 test failures: https://issues.jboss.org/browse/JBIDE-8759
> Looks like Victor already commited fixes for this one (based on jira
> > JBT 3.2.1.M1 / JBDS 4.1.0.M1:
> > * Aggregate builder is fixed (I think!), but hit a network snag trying
to fetch latest bits because I disabled the "wait until all upstream are
done" option in the job in order to test my latest publish.sh fixes. Respin
will fix this & allow me to verify my fix worked, then I can re-enable the
> > * One last Seam test failure:
> cc'ed Alexey - not much information available - any ideas ?
> > * AS & Deltacloud jobs time out after 2hrs; job timeout increased to
3hrs. Would respin but Hudson is in shutdown mode.
> Did it timeout because of failure to get all dependencies or was it
actually doing testruns?
> > * JSF was clean (no failures) but now has 7 new tests and 14 new
> Alexey - another case of tests running before builder completes ? Can't
we query the state of the builder and fail on that so we know when that is
the case ?
> jbosstools-dev mailing list