<br><br><div class="gmail_quote">On Fri, Apr 29, 2011 at 3:20 PM, Max Rydahl Andersen <span dir="ltr"><<a href="mailto:max.andersen@redhat.com">max.andersen@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
> JBT 3.3.0.M1 / JBDS 5.0.0.M1:<br>
><br>
> * Savara/Scribble missing (refactored?) feature: <a href="https://issues.jboss.org/browse/JBIDE-8817" target="_blank">https://issues.jboss.org/browse/JBIDE-8817</a> (blocks aggregate build)<br>
<br>
cc'ed Gary - I understand that as already have been fixed. Gary - maybe missing some release/push somewhere?<br>
<br>
> * AS - single test failure: <a href="https://issues.jboss.org/browse/JBIDE-8816" target="_blank">https://issues.jboss.org/browse/JBIDE-8816</a><br>
<br>
cc'ed Rob - that looks like you not updating the tests after you refactored publishers ?!<br>
<br>
> * VPE had 219 tests on Jan 11; now only 17 tests are running and of those, 6 are failing<br>
<br>
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?<br>
Or is there something else known about this Yahor ? you mentioned looking into reducing number of tests to avoid duplication ? Sounds like<br>
a rather big reduction though ?<br></blockquote><div>Any prooflink? I found only these two: [1], [2]. No failed tests here, and their number is >>17.</div><div><a href="http://hudson.qa.jboss.com/hudson/view/DevStudio_Trunk/job/jbosstools-3.3_trunk.component--vpe/218/testReport/">http://hudson.qa.jboss.com/hudson/view/DevStudio_Trunk/job/jbosstools-3.3_trunk.component--vpe/218/testReport/</a></div>
<div><a href="http://hudson.qa.jboss.com/hudson/view/DevStudio_Stable_Branch/job/jbosstools-3.2_stable_branch.component--vpe/84/testReport/">http://hudson.qa.jboss.com/hudson/view/DevStudio_Stable_Branch/job/jbosstools-3.2_stable_branch.component--vpe/84/testReport/</a></div>
<div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
<br>
> * Seam has 3 test failures: <a href="https://issues.jboss.org/browse/JBIDE-8759" target="_blank">https://issues.jboss.org/browse/JBIDE-8759</a><br>
<br>
Looks like Victor already commited fixes for this one (based on jira comments)<br>
<br>
<br>
> JBT 3.2.1.M1 / JBDS 4.1.0.M1:<br>
><br>
> * 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 block-while-upstream-spinning option.<br>
><br>
> * One last Seam test failure: <a href="https://issues.jboss.org/browse/JBIDE-8818" target="_blank">https://issues.jboss.org/browse/JBIDE-8818</a><br>
<br>
cc'ed Alexey - not much information available - any ideas ?<br>
<br>
><br>
> * AS & Deltacloud jobs time out after 2hrs; job timeout increased to 3hrs. Would respin but Hudson is in shutdown mode.<br>
<br>
Did it timeout because of failure to get all dependencies or was it actually doing testruns?<br>
<br>
> * JSF was clean (no failures) but now has 7 new tests and 14 new failures: <a href="https://issues.jboss.org/browse/JBIDE-8819" target="_blank">https://issues.jboss.org/browse/JBIDE-8819</a><br>
<br>
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 ?<br>
<br>
/max<br>
<br>
<br>
_______________________________________________<br>
jbosstools-dev mailing list<br>
<a href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a><br>
</blockquote></div><br>