This change should not cause these tests not to be run. I just checked this locally by executing <div><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; ">mvn clean test osgi-test:test -f ~/trunk/vpe/tests/pom.xml .</span></div>

<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">All VPE tests have been run in result.</span></font></div>

<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br>

</span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">--Yahor<br></span></font></div><div><div class="gmail_quote"><br></div><div class="gmail_quote">

On Tue, Jun 14, 2011 at 7:24 PM, Nick Boldt <span dir="ltr">&lt;<a href="mailto:nboldt@redhat.com">nboldt@redhat.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

Only hudson config change was to reorg the workflow, as discussed @ F2F.<br>
<br>
== BEFORE ==<br>
<br>
1. mvn clean install -f ~/trunk/vpe/pom.xml<br>
<br>
(if tests or compilation fails, do not publish; downstream aggregation BLOCKED by failure)<br>
<br>
2. publish.sh<br>
<br>
<br>
== AFTER ==<br>
<br>
1. mvn clean install -f ~/trunk/vpe/pom.xml -Dmaven.test.skip<br>
<br>
(if compilation fails, do not publish)<br>
<br>
2. publish.sh<br>
<br>
3. mvn clean test osgi-test:test -f ~/trunk/vpe/tests/pom.xml<br>
<br>
(build can be red due to failing tests, but bits will still be published and aggregated)<br>
<br>
---<br>
<br>
If somehow that change is what&#39;s causing some tests to not be run (or to fail utterly?), then the fault may be mine. I could run the vpe/pom.xml instead of the vpe/tests/pom.xml if that&#39;d help...?<br><font color="#888888">
<br>
Nick</font><div><div></div><div class="h5"><br>
<br>
On 06/14/2011 08:05 AM, Max Rydahl Andersen wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div></div><div class="h5">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
There are two kinds of removed tests:<br>
1. All VPE tests are vanished from jbosstools-3.3_trunk.tests job. I (as well as Nick) do not know the reason why they are vanished. But I guess that somebody removed them from the job to make it stable.<br>
</blockquote>
<br>
*somebody* ? who would that be and how are they removed ?<br>
<br>
I dont think anyone would remove such things without letting the dev team know about.<br>
<br>
Is this a pure hudson configuration change or something in SVN ?<br>
<br>
/max<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2. The quantity of VPE JUnit tests is decreased from 219 to 192. I did it myself in the scope of JBIDE-8487 (Decrease quantity of junit tests).<br>
<br>
--Yahor<br>
<br>
On Tue, Jun 14, 2011 at 1:35 PM, Denis Golovin&lt;<a href="mailto:dgolovin@exadel.com" target="_blank">dgolovin@exadel.com</a>&gt;  wrote:<br>
What tests were removed and why?<br>
<br>
Denis<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Regarding VPE,<br>
<br>
On Tue, Jun 14, 2011 at 2:56 AM, Nick Boldt&lt;<a href="mailto:nboldt@redhat.com" target="_blank">nboldt@redhat.com</a>&gt;  wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Six (6) components are having some problems today. Here&#39;s the list!<br>
<br>
----------------<br>
<br>
== CDI ==<br>
<br>
Many test failures (55?) in these suites:<br>
<br>
  org.jboss.tools.cdi.text.ext.test<br>
  org.jboss.tools.cdi.ui.test<br>
  org.jboss.tools.cdi.seam.config.ui.test<br>
<br>
<br>
<a href="http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-3.3_trunk.component--cdi/345/console" target="_blank">http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-3.3_trunk.component--cdi/345/console</a><br>


<br>
Also, count of tests is down from 454 to 399 (55 tests failing to report<br>
results) since June 9.<br>
<br>
<br>
<a href="http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--cdi/test/" target="_blank">http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--cdi/test/</a><br>
<br>
== JSF ==<br>
<br>
1 or 2 test failures since June 9:<br>
<br>
<br>
<a href="http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--jsf/271/testReport/" target="_blank">http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--jsf/271/testReport/</a><br>
<br>
<br>
<a href="http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--jsf/272/testReport/" target="_blank">http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--jsf/272/testReport/</a><br>
<br>
== Maven ==<br>
<br>
June 10, we had 6 passing tests. 10hrs later, we&#39;re down to ZERO passing<br>
tests.<br>
<br>
<br>
<a href="http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-3.3_trunk.component--maven/changes" target="_blank">http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-3.3_trunk.component--maven/changes</a><br>


<br>
Could this be due to me moving up to a newer version of m2e?<br>
<br>
<a href="http://source.jboss.org/changelog/JBossTools/?cs=32015" target="_blank">http://source.jboss.org/changelog/JBossTools/?cs=32015</a><br>
<br>
== Seam ==<br>
<br>
6 test failures in org.jboss.tools.seam.ui.test, and duplicate spins of<br>
the<br>
same tests (?):<br>
<br>
<br>
<a href="http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-3.3_trunk.component--seam/350/testReport/" target="_blank">http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-3.3_trunk.component--seam/350/testReport/</a><br>


<br>
== WS ==<br>
<br>
4 test failures, 1 missing (down from 180 tests to 179).<br>
<br>
<br>
<a href="http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-3.3_trunk.component--ws/lastCompletedBuild/testReport/" target="_blank">http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-3.3_trunk.component--ws/lastCompletedBuild/testReport/</a><br>


<br>
== VPE / Overall All-in-One test suite ==<br>
<br>
The all-in-one test builder is reporting that nearly 800 tests are<br>
missing<br>
since Friday - from 3239 tests in build #673 to 2441 in build #676!<br>
<br>
Here are the test suites that vanished from the #673 build and are no<br>
longer present in the #676 build - looks like it&#39;s all VPE-related tests<br>
that have vanished.<br>
<br>
</blockquote>
Did somebody disable them in this job because of<br>
<a href="https://issues.jboss.org/browse/JBIDE-8777" target="_blank">https://issues.jboss.org/browse/JBIDE-8777</a> (RHEL5 x64&amp;  VPE issue)?<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Package Duration        Fail    (diff)  Skip    (diff)  Total   (diff)<br>
org.jboss.tools.jsf.vpe.ajax4jsf.test   47 sec  0               0<br>
     24<br>
org.jboss.tools.jsf.vpe.facelets.test   47 sec  0               0<br>
     14<br>
org.jboss.tools.jsf.vpe.jbpm.test       20 sec  0               0<br>
     4<br>
org.jboss.tools.jsf.vpe.jsf.test        9 min 25 sec    0<br>
0<br>
             224<br>
org.jboss.tools.jsf.vpe.jstl.test       1 min 13 sec    0<br>
0<br>
             42<br>
org.jboss.tools.jsf.vpe.myfaces.test    1 min 19 sec    0<br>
0<br>
             43<br>
org.jboss.tools.jsf.vpe.richfaces.test  2 min 39 sec    0<br>
0<br>
             115<br>
org.jboss.tools.jsf.vpe.seam.test       1 min 38 sec    0<br>
0<br>
             65<br>
<br>
org.jboss.tools.struts.vpe.struts.test  1 min 24 sec    0<br>
0<br>
             89<br>
<br>
org.jboss.tools.vpe.html.test   2 min 4 sec     0               0<br>
     111<br>
org.jboss.tools.vpe.jsp.test    43 sec  0               0<br>
23<br>
<br>
org.jboss.tools.vpe.spring.test         55 sec  0               0<br>
     27<br>
org.jboss.tools.vpe.ui.test     38 sec  0               0<br>
12<br>
<br>
org.jboss.tools.vpe.xulrunner.test      2.6 sec 0               0<br>
     7<br>
<br>
Note that the VPE job itself is down from 219 tests to 192, suggesting<br>
similar (or more?) test failures there too.<br>
<br>
</blockquote>
219 to 192 is OK, we removed a part of VPE tests intentionally.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
--<br>
Nick Boldt :: JBoss by Red Hat<br>
Productization Lead :: JBoss Tools&amp;  Dev Studio<br>
<a href="http://nick.divbyzero.com" target="_blank">http://nick.divbyzero.com</a><br>
<br>
<br>
</blockquote>
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
/max<br>
<a href="http://about.me/maxandersen" target="_blank">http://about.me/maxandersen</a><br>
<br>
<br>
<br>
<br></div></div><div class="im">
_______________________________________________<br>
jbosstools-dev mailing list<br>
<a href="mailto:jbosstools-dev@lists.jboss.org" target="_blank">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>
</div></blockquote>
<br>
-- <br><div><div></div><div class="h5">
Nick Boldt :: JBoss by Red Hat<br>
Productization Lead :: JBoss Tools &amp; Dev Studio<br>
<a href="http://nick.divbyzero.com" target="_blank">http://nick.divbyzero.com</a><br>
</div></div></blockquote></div><br></div>