11:24 p.m.
The JBoss AS integration test suite is now running to completion after a week of
instability.
http://hudson.jboss.org/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x-testSui...
All commits to jbossas/trunk should have an associated JBAS JIRA and run the smoke-tests
target
(minimally) before committing.
For component upgrades targeted for the 6.0.0.CR1 release, be sure to add a sub-task to:
https://jira.jboss.org/browse/JBAS-8253
For 6.0.0.Final:
https://jira.jboss.org/browse/JBAS-8086
Shelly McGowan
JBoss, by Red Hat
3:37 a.m.
On Tue, Aug 31, 2010 at 5:24 AM, Shelly McGowan <smcgowan(a)redhat.com> wrote:
The JBoss AS integration test suite is now running to completion
after a week of instability.
Cool.
http://hudson.jboss.org/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x-testSui...
All commits to jbossas/trunk should have an associated JBAS JIRA and run the smoke-tests
target
(minimally) before committing.
For component upgrades targeted for the 6.0.0.CR1 release, be sure to add a sub-task to:
https://jira.jboss.org/browse/JBAS-8253
For 6.0.0.Final:
https://jira.jboss.org/browse/JBAS-8086
Right now there's a smoke-test failure on the shared-jndi test, where
apparently two deployments (shared-jndi.sar and shared-jndi.war) get
assigned the same component name for the naming reloaded stuff, and it
causes a conflict.
Rémy
10:04 a.m.
On 08/31/2010 09:37 AM, Remy Maucherat wrote:
On Tue, Aug 31, 2010 at 5:24 AM, Shelly
McGowan<smcgowan(a)redhat.com> wrote:
> The JBoss AS integration test suite is now running to completion after a week of
instability.
Cool.
> http://hudson.jboss.org/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x-testSui...
>
> All commits to jbossas/trunk should have an associated JBAS JIRA and run the
smoke-tests target
> (minimally) before committing.
>
> For component upgrades targeted for the 6.0.0.CR1 release, be sure to add a sub-task
to:
> https://jira.jboss.org/browse/JBAS-8253
>
> For 6.0.0.Final:
> https://jira.jboss.org/browse/JBAS-8086
Right now there's a smoke-test failure on the shared-jndi test, where
apparently two deployments (shared-jndi.sar and shared-jndi.war) get
assigned the same component name for the naming reloaded stuff, and it
causes a conflict.
Rémy
I've modified the test to comply with EE 6 specs.
Carlo
10:54 a.m.
I've just committed Jaikiran's patch for:
https://jira.jboss.org/browse/JBAS-792
which will FAIL the build if smoke-tests fail.
Shelly McGowan
JBoss, by Red Hat
----- Original Message -----
From: "Carlo de Wolf" <cdewolf(a)redhat.com>
To: "JBoss.org development list" <jboss-development(a)lists.jboss.org>
Sent: Tuesday, August 31, 2010 10:04:11 AM GMT -05:00 US/Canada Eastern
Subject: Re: [jboss-dev] Committing to jbossas/trunk
On 08/31/2010 09:37 AM, Remy Maucherat wrote:
On Tue, Aug 31, 2010 at 5:24 AM, Shelly
McGowan<smcgowan(a)redhat.com> wrote:
> The JBoss AS integration test suite is now running to completion after a week of
instability.
Cool.
> http://hudson.jboss.org/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x-testSui...
>
> All commits to jbossas/trunk should have an associated JBAS JIRA and run the
smoke-tests target
> (minimally) before committing.
>
> For component upgrades targeted for the 6.0.0.CR1 release, be sure to add a sub-task
to:
> https://jira.jboss.org/browse/JBAS-8253
>
> For 6.0.0.Final:
> https://jira.jboss.org/browse/JBAS-8086
Right now there's a smoke-test failure on the shared-jndi test, where
apparently two deployments (shared-jndi.sar and shared-jndi.war) get
assigned the same component name for the naming reloaded stuff, and it
causes a conflict.
Rémy
I've modified the test to comply with EE 6 specs.
Carlo
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
11:12 a.m.
https://jira.jboss.org/browse/JBAS-7924
Shelly McGowan
JBoss, by Red Hat
----- Original Message -----
From: "Shelly McGowan" <smcgowan(a)redhat.com>
To: "JBoss.org development list" <jboss-development(a)lists.jboss.org>
Sent: Tuesday, August 31, 2010 10:54:58 AM GMT -05:00 US/Canada Eastern
Subject: Re: [jboss-dev] Committing to jbossas/trunk
I've just committed Jaikiran's patch for:
https://jira.jboss.org/browse/JBAS-792
which will FAIL the build if smoke-tests fail.
Shelly McGowan
JBoss, by Red Hat
----- Original Message -----
From: "Carlo de Wolf" <cdewolf(a)redhat.com>
To: "JBoss.org development list" <jboss-development(a)lists.jboss.org>
Sent: Tuesday, August 31, 2010 10:04:11 AM GMT -05:00 US/Canada Eastern
Subject: Re: [jboss-dev] Committing to jbossas/trunk
On 08/31/2010 09:37 AM, Remy Maucherat wrote:
On Tue, Aug 31, 2010 at 5:24 AM, Shelly
McGowan<smcgowan(a)redhat.com> wrote:
> The JBoss AS integration test suite is now running to completion after a week of
instability.
Cool.
> http://hudson.jboss.org/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x-testSui...
>
> All commits to jbossas/trunk should have an associated JBAS JIRA and run the
smoke-tests target
> (minimally) before committing.
>
> For component upgrades targeted for the 6.0.0.CR1 release, be sure to add a sub-task
to:
> https://jira.jboss.org/browse/JBAS-8253
>
> For 6.0.0.Final:
> https://jira.jboss.org/browse/JBAS-8086
Right now there's a smoke-test failure on the shared-jndi test, where
apparently two deployments (shared-jndi.sar and shared-jndi.war) get
assigned the same component name for the naming reloaded stuff, and it
causes a conflict.
Rémy
I've modified the test to comply with EE 6 specs.
Carlo
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
4991
days inactive
4991
days old
jboss-development@lists.jboss.org
4 comments
3 participants
participants (3)
-
Carlo de Wolf -
Remy Maucherat -
Shelly McGowan