[jbosstools-dev] Beta1 build status: 19 builds are red!

[Nick Boldt]

Well, looks like the reason for all this fail was a dirty cache of old 
M5 builds which were not being purged correctly. 
(https://issues.jboss.org/browse/JBDS-2028)

Now that that's working again and everything is respinning, we're down 
to only a handful of remaining problems, and the JBT aggregate should be 
built clean in the next half hour or so, after which the JBDS and SOA 
builds can start.

---

For JBT Core Components:

JSF & VPE: org.jboss.tools.jsf.ui.test failed in build #56 but was fine 
in build #55 w/ no changes to the JDF code in between. Suspect it's a 
RHEL6 problem (https://issues.jboss.org/browse/JBIDE-10960). SWT No More 
Handles failure in one VPE build, no code coverage report in another. 
These are "bad smells" but not blocking Beta1.

Maven & Seam: 1 test failure each. Again, not blocking, but should be 
tended to.

http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_3.3.indigo/job/jbosstools-3.3_stable_branch.component--maven/53/testReport/junit/org.jboss.tools.maven.configurators.tests/SeamConfiguratorTest/testJBIDE10790_earConfiguration/

http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_3.3.indigo/job/jbosstools-3.3_stable_branch.component--seam/63/testReport/junit/org.jboss.tools.seam.core.test/SeamCoreAllTests/testCleanBuild/

---

For JBDS Core & Installer:

Blocked by upstream builds, but should hopefully be blue in a few hours.

---

For SOA Tooling Components:

ESB: test failures, but waiting on JBT Aggregate to respin which might 
fix these.

---

For JBT/JBDS SOA Tooling:

Downstream aggregate builds for JBT SOA and JBDS SOA are still pending 
upstream completion. Hopefully they'll be blue by morning.

Cheers,


On 02/19/2012 04:39 PM, Snjezana Peco wrote:
> Hello Nick,
>
> The IJBossCentralConfigurator and DefaultJBossCentralConfigurator class
> as well as the configurators extension point have been moved from the
> o.j.t.central to the o.j.t.project.examples plugin.
> That's why the central component wasn't built correctly.
> I have moved the template directory from the central plugin to the
> project.examples and updated their pom.xml.
> Now the both plugins are built correctly.
> However, you have to check if the pom.xml in the project.examples plugin
> is valid.
> The changes have been committed to the trunk and 3.3.0.Beta1 branch.
>
> The runtime and portlet component compile locally, but aren't built
> because they are using some older version of the as and tests component.
>
> Snjeza
>
> Nick Boldt wrote:
>> Currently experiencing cascade failures insofar as components that
>> depend on other components are failing because their upstream are
>> failing.
>>
>> All red jobs:
>>
>> http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_3.3.indigo/portlet/dashboard_portlet_25/
>>
>>
>> ---
>>
>> Here's the problem stack - looks like some refactoring last week
>> (moving stuff from Central to Examples) might have caused some havoc
>> to components that depend on these shared classes.
>>
>> common: test failure
>>
>> https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.component--common/lastCompletedBuild/testReport/org.jboss.tools.common.el.core.test/CommonELAllTests/testTypeResolution/
>>
>>
>> WS: compile failure
>>
>> https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.component--ws/53/console
>>
>>
>> Runtime: compile failure
>>
>> https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.component--runtime/46/console
>>
>>
>> Examples: SVN checkout failures for vmg19-rhel5-x86; slave
>> disconnected, reported to ci-issues@, and we're respinning.
>>
>> https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.component--examples/46/
>>
>>
>> Portlet: compile failure
>>
>> https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.component--portlet/38/console
>>
>>
>> Maven: compile failure due to project examples
>>
>> https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.component--maven/
>>
>>
>> Central: compile failure
>>
>> https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.component--central/25/console
>>
>>
>> (Also failing in trunk:
>> http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--central/)
>>
>>
>> JBT Aggregate: missing o.j.t.maven.jpa feature due to upstream maven
>> component failure
>>
>> ESB, SOA Tooling: blocked by upstream.
>>
>

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com