RE: jboss-head-jdk-matrix Build Failed
by Rajesh Rajasekaran
Jgroups 2.4CR2 is not found in the repository.
[synchronizeinfo] .
[get] last modified = Sat Apr 23 12:31:05 EDT 2005
[mkdir] Created dir:
/services/cruisecontrol/checkout/jboss-head/thirdparty/jgroups
[get] Getting:
http://repository.jboss.com/jgroups/2.4CR2/component-info.xml
[get] To:
/services/cruisecontrol/checkout/jboss-head/thirdparty/jgroups/component
-info.xml
[get] Error opening connection java.io.FileNotFoundException:
http://repository.jboss.com/jgroups/2.4CR2/component-info.xml
[get] Error opening connection java.io.FileNotFoundException:
http://repository.jboss.com/jgroups/2.4CR2/component-info.xml
[get] Error opening connection java.io.FileNotFoundException:
http://repository.jboss.com/jgroups/2.4CR2/component-info.xml
[get] Can't get
http://repository.jboss.com/jgroups/2.4CR2/component-info.xml to
/services/cruisecontrol/checkout/jboss-head/thirdparty/jgroups/component
-info.xml
BUILD FAILED
/services/cruisecontrol/checkout/jboss-head/build/build.xml:963: The
following error occurred while executing this line:
/services/cruisecontrol/checkout/jboss-head/build/build-thirdparty.xml:1
41: Unable to get remote
file=/services/cruisecontrol/checkout/jboss-head/thirdparty/jgroups/comp
onent-info.xml
url=http://repository.jboss.com/jgroups/2.4CR2/component-info.xml
Total time: 2 seconds
________________________________
From: qa(a)jboss.com [mailto:qa@jboss.com]
Sent: Wednesday, August 30, 2006 10:21 AM
To: Bela Ban; hmesha(a)jboss.com; jboss-development(a)lists.jboss.org; QA;
wolfc(a)jboss.com
Subject: jboss-head-jdk-matrix Build Failed
Importance: High
View results here ->
http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log
=log20060830105812
BUILD FAILED
Ant Error Message:
/services/cruisecontrol/work/scripts/build-jboss-common.xml:297: The
following error occurred while executing this line:
/services/cruisecontrol/work/scripts/build-jboss-common.xml:64: Exit
code: 1 See compile_jdk15.log in Build Artifacts for details.
Date of build: 08/30/2006 10:58:12
Time to build: 21 minutes 45 seconds
Last changed: 08/30/2006 10:48:44
Last log entry: JBAS-2921
Unit Tests: (0) Total Errors and Failures: (0)
Modifications since last build: (first 50 of 10)
56444
modified
hmesha
//trunk/tomcat/src/main/org/jboss/web/tomcat/tc6/session/JBossCacheServi
ce.java
JBAS-2921
56444
added
hmesha
//trunk/tomcat/src/main/org/jboss/web/tomcat/tc6/session/SessionSerializ
ationFactory.java
JBAS-2921
56438
modified
wolfc
//trunk/server/src/main/org/jboss/naming/client/java/javaURLContextFacto
ry.java
changed lookup order of clientCtx, because it might not be available
(EJBTHREE-667)
56434
modified
wolfc
//trunk/ejb3/src/main/org/jboss/ejb3/SessionContainer.java
EJBTHREE-667: HandleDelegate fixes & Service bean
56434
added
wolfc
//trunk/ejb3/src/test/org/jboss/ejb3/test/iiop/MyServiceBean.java
EJBTHREE-667: HandleDelegate fixes & Service bean
56434
modified
wolfc
//trunk/ejb3/src/main/org/jboss/ejb3/iiop/IORFactory.java
EJBTHREE-667: HandleDelegate fixes & Service bean
56434
modified
wolfc
//trunk/ejb3/src/main/org/jboss/ejb3/stateful/StatefulContainer.java
EJBTHREE-667: HandleDelegate fixes & Service bean
56434
modified
wolfc
//trunk/ejb3/src/test/org/jboss/ejb3/test/iiop/unit/IiopRemoteUnitTestCa
se.java
EJBTHREE-667: HandleDelegate fixes & Service bean
56434
modified
wolfc
//trunk/ejb3/src/main/org/jboss/ejb3/service/ServiceContainer.java
EJBTHREE-667: HandleDelegate fixes & Service bean
56433
unknown
bela(a)jboss.com
//trunk/build/build-thirdparty.xml
upgraded JGroups from 2.4CR1 to 2.4CR2
17 years, 8 months
RE: [JBoss-dev] Re: Remaining tasks for JBAS 4.0.5.CR1
by Dimitris Andreadis
If the EJB3 team wants to improve the status of the ejb3-4.0-testsuite,
today is the last day to act.
We will tag 4.0.5.CR1 tomorrow and hand over to AlexP for building the
installer.
I'll create container tasks to track the improvement of the testsuite
runs for the other JVM combinations, for the next release.
> -----Original Message-----
> From: Ruel Loehr
> Sent: Wednesday, August 30, 2006 5:53 PM
> To: JBoss.org development list; Dimitris Andreadis
> Cc: Ivelin Ivanov; Sacha Labourey
> Subject: RE: [JBoss-dev] Re: Remaining tasks for JBAS 4.0.5.CR1
>
> So the sun 1.4 testsuite is passing:
>
> http://cruisecontrol.jboss.com/cc/artifacts/jboss-4.0-testsuit
> e-sun-1.4/20060830062405/results/index.html
>
> The only thing we are waiting on at this point is for the
> ejb3 problems to addressed?
>
> http://cruisecontrol.jboss.com/cc/artifacts/ejb3-4.0-testsuite
> /20060829220003/results/index.html
>
> Ruel Loehr
> JBoss, a division of Red Hat
> QA
>
> -----------------------------
> 512-342-7840 ext 2011
> Yahoo: ruelloehr
> Skype: ruelloehr
> AOL: dokoruel
>
> -----Original Message-----
> From: jboss-development-bounces(a)lists.jboss.org
> [mailto:jboss-development-bounces@lists.jboss.org] On Behalf
> Of Scott M Stark
> Sent: Wednesday, August 30, 2006 9:46 AM
> To: Dimitris Andreadis
> Cc: Ivelin Ivanov; JBoss.org development list; Sacha Labourey
> Subject: [JBoss-dev] Re: Remaining tasks for JBAS 4.0.5.CR1
>
> I agree with the testsuite strategy of addressing the other
> vms for the final release.
>
> Dimitris Andreadis wrote:
> > Hi,
> >
> > There are a couple of things left for the jbas 4.0.5.CR1 release.
> >
> > There are some harmless but annoying warnings that appear
> upon server
> > shutdown (see the bottom of this message). Three of them
> are triggered
> > by the embedded jbossws.beans in jbossws14.sar, but it seems to be
> > caused by the MainDeployer / Bean deployer?
> > http://jira.jboss.com/jira/browse/JBAS-3471 (any ideas?)
> >
> > Apart from that, we have the testsuites to fix and a
> decision to make.
> > We currently run Branch_4_0 under the following JVM
> combinations with
> > the corresponding results.
> >
> > 1) Sun JVM 1.4 --> 6 failures
> > 2) Sun JVM 5 --> 10 failures
> > 3) Jrockit 1.4 --> 58 failures
> > 4) Jrockit 5 --> 63 failures
> >
> > Traditionally we only care about the Sun JVM 1.4 test runs.
> Does this
> > still hold true, or if not, how far to go with the other JVM
> > combinations? Looking into the failures, I don't think we can reach
> > 100% on all of them within the limits of this CR release, so I'd
> > suggest we target 100% on (1) and schedule JIRA tasks for
> addressing
> > the other failures in future releases.
> >
> > Also note, that many of the failures are transient.
> >
> > Finally, somebody needs to look into the 28 ejb3 testsuite failures.
> >
> > Please take a look at the remaining tasks, or even if not assigned
> > have a go with the remanining testsuite failures
> >
> http://jira.jboss.com/jira/secure/IssueNavigator.jspa?reset=true&mode=
> > hi
> >
> de&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10030&fix
> > fo
> > r=12310576
> >
> > Thanks
> > /Dimitris
> >
> >
> >
>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.405 / Virus Database: 268.11.7/433 - Release
> Date: 8/30/2006
>
>
> --
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.1.405 / Virus Database: 268.11.7/433 - Release
> Date: 8/30/2006
>
>
17 years, 8 months
Remaining tasks for JBAS 4.0.5.CR1
by Dimitris Andreadis
Hi,
There are a couple of things left for the jbas 4.0.5.CR1 release.
There are some harmless but annoying warnings that appear upon server
shutdown (see the bottom of this message). Three of them are triggered
by the embedded jbossws.beans in jbossws14.sar, but it seems to be
caused by the MainDeployer / Bean deployer?
http://jira.jboss.com/jira/browse/JBAS-3471 (any ideas?)
Apart from that, we have the testsuites to fix and a decision to make.
We currently run Branch_4_0 under the following JVM combinations with
the corresponding results.
1) Sun JVM 1.4 --> 6 failures
2) Sun JVM 5 --> 10 failures
3) Jrockit 1.4 --> 58 failures
4) Jrockit 5 --> 63 failures
Traditionally we only care about the Sun JVM 1.4 test runs. Does this
still hold true, or if not, how far to go with the other JVM
combinations? Looking into the failures, I don't think we can reach 100%
on all of them within the limits of this CR release, so I'd suggest we
target 100% on (1) and schedule JIRA tasks for addressing the other
failures in future releases.
Also note, that many of the failures are transient.
Finally, somebody needs to look into the 28 ejb3 testsuite failures.
Please take a look at the remaining tasks, or even if not assigned have
a go with the remanining testsuite failures
http://jira.jboss.com/jira/secure/IssueNavigator.jspa?reset=true&mode=hi
de&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10030&fixfo
r=12310576
Thanks
/Dimitris
16:15:42,079 WARN [MainDeployer] undeploy
'file:/X:/cvs/jboss-public/jboss-4.0/build/output/jboss-4.0.5.CR1/server
/all//deploy-hasingleton' : package not deployed
16:15:42,149 INFO [DefaultPartition] Closing partition DefaultPartition
16:15:44,362 INFO [DefaultPartition] Partition DefaultPartition closed.
16:15:44,372 INFO [DefaultPartition] Partition DefaultPartition
destroyed.
16:15:44,532 INFO [TreeCache] stopService(): closing the channel
16:15:44,843 INFO [TreeCache] stopService(): stopping the dispatcher
16:15:44,873 INFO [SnmpAgentService] SNMP agent stopped
16:15:44,983 WARN [SubscriptionManager] Cannot unbind event dispatcher:
javax.naming.NameNotFoundException: EventDispatcher not bound
16:15:45,013 WARN [ServiceController] Ignoring request to stop
nonexistent service:
jboss.beans:name='jbossws14.sar#jbossws.beans',service=JBossBeanDeployme
nt
16:15:45,013 WARN [ServiceController] Ignoring request to destroy
nonexistent service:
jboss.beans:name='jbossws14.sar#jbossws.beans',service=JBossBeanDeployme
nt
16:15:46,806 INFO [Server] Shutdown complete
Shutdown complete
Halting VM
17 years, 8 months
RE: [JBoss-dev] Re: Remaining tasks for JBAS 4.0.5.CR1
by Ruel Loehr
So the sun 1.4 testsuite is passing:
http://cruisecontrol.jboss.com/cc/artifacts/jboss-4.0-testsuite-sun-1.4/2...
The only thing we are waiting on at this point is for the ejb3 problems to addressed?
http://cruisecontrol.jboss.com/cc/artifacts/ejb3-4.0-testsuite/2006082922...
Ruel Loehr
JBoss, a division of Red Hat
QA
-----------------------------
512-342-7840 ext 2011
Yahoo: ruelloehr
Skype: ruelloehr
AOL: dokoruel
-----Original Message-----
From: jboss-development-bounces(a)lists.jboss.org [mailto:jboss-development-bounces@lists.jboss.org] On Behalf Of Scott M Stark
Sent: Wednesday, August 30, 2006 9:46 AM
To: Dimitris Andreadis
Cc: Ivelin Ivanov; JBoss.org development list; Sacha Labourey
Subject: [JBoss-dev] Re: Remaining tasks for JBAS 4.0.5.CR1
I agree with the testsuite strategy of addressing the other vms for the
final release.
Dimitris Andreadis wrote:
> Hi,
>
> There are a couple of things left for the jbas 4.0.5.CR1 release.
>
> There are some harmless but annoying warnings that appear upon server
> shutdown (see the bottom of this message). Three of them are triggered
> by the embedded jbossws.beans in jbossws14.sar, but it seems to be
> caused by the MainDeployer / Bean deployer?
> http://jira.jboss.com/jira/browse/JBAS-3471 (any ideas?)
>
> Apart from that, we have the testsuites to fix and a decision to make.
> We currently run Branch_4_0 under the following JVM combinations with
> the corresponding results.
>
> 1) Sun JVM 1.4 --> 6 failures
> 2) Sun JVM 5 --> 10 failures
> 3) Jrockit 1.4 --> 58 failures
> 4) Jrockit 5 --> 63 failures
>
> Traditionally we only care about the Sun JVM 1.4 test runs. Does this
> still hold true, or if not, how far to go with the other JVM
> combinations? Looking into the failures, I don't think we can reach 100%
> on all of them within the limits of this CR release, so I'd suggest we
> target 100% on (1) and schedule JIRA tasks for addressing the other
> failures in future releases.
>
> Also note, that many of the failures are transient.
>
> Finally, somebody needs to look into the 28 ejb3 testsuite failures.
>
> Please take a look at the remaining tasks, or even if not assigned have
> a go with the remanining testsuite failures
> http://jira.jboss.com/jira/secure/IssueNavigator.jspa?reset=true&mode=hi
> de&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10030&fixfo
> r=12310576
>
> Thanks
> /Dimitris
>
>
>
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.405 / Virus Database: 268.11.7/433 - Release Date: 8/30/2006
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.405 / Virus Database: 268.11.7/433 - Release Date: 8/30/2006
17 years, 8 months
