jboss-development September 2006

jboss-development@lists.jboss.org

31 participants
746 discussions

Start a nNew thread

ejb3-head-testsuite Build Completed With Testsuite Errors

by qa＠jboss.com

20 years, 1 month

1
0
0 / 0

jbossws-4.0-testsuite-1.5 Build Failed

by qa＠jboss.com

20 years, 1 month

1
0
0 / 0

jboss-portal-2.6-testsuite Build Completed With Testsuite Errors

by qa＠jboss.com

20 years, 1 month

1
0
0 / 0

jboss-serialization-testsuite Build Completed With Testsuite Errors

by qa＠jboss.com

20 years, 1 month

1
0
0 / 0

jbossws-head-testsuite-1.5 Build Completed With Testsuite Errors

by qa＠jboss.com

20 years, 1 month

1
0
0 / 0

jboss-portal-2.4-testsuite Build Completed With Testsuite Errors

by qa＠jboss.com

20 years, 1 month

1
0
0 / 0

jboss-4.0-testsuite-1.6 Build Failed

by qa＠jboss.com

20 years, 1 month

1
0
0 / 0

jboss-4.0-testsuite-1.4 Build Completed With Testsuite Errors

by qa＠jboss.com

20 years, 1 month

1
0
0 / 0

RE: Fixing the testsuite for JRockit

by Ryan Campbell

The testsuite runs should now be isolated from each other. There have been a couple classes of problems: 1. At one point (few weeks ago), we were running testsuites in parallel on two different boxes, but the clustering tests conflicted. We stopped doing this. 2. We have historically (months ago) seen stale JBoss processes hanging around, but I haven't seen this recently. We go to great lengths to make sure the box is clean. Maybe this has regressed, but I haven't seen this. -----Original Message----- From: Dimitris Andreadis Sent: Thursday, September 07, 2006 9:05 AM To: JBoss.org development list; QA Subject: Fixing the testsuite for JRockit An important task for the jbas codebase is to fix the testsuite when run under the jrockit JVM. This is initially for the 4.x branch but the fixes should apply verbatim to jboss head. The starting point is here (see linked tasks & subtasks) http://jira.jboss.com/jira/browse/JBAS-3598 http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite-1.4 At any time there are anywhere between 54-58 failures, so if something is in your area please have a go. We'll be assigning tasks to people, soon. Same thing for the testsuite when run under sun-jdk5 (around 10 failures) http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite-sun-1 .5 http://jira.jboss.com/jira/browse/JBAS-3611 There are also a lot of transient failures in parts of the testsuite that are more sensitive to timing/cpu issues (e.g. JMS), so subsequent runs often produce different results. This may also have to do with testsuite runs that interfere with each other. If we can (a) improve those parts of the testsuite and (b) make sure testsuite runs are more isolated from each other, that would be an improvement. (I see already a related task from Adrian: http://jira.jboss.com/jira/browse/JBAS-3221) Thanks /Dimitris

20 years, 1 month

1
0
0 / 0

RE: [JBoss-dev] Log4j version

by Brian Stansberry

Hmm, JGroups and JBC use commons-logging, and to get the benefit of log4j TRACE support, commons-logging would have to be upgraded to 1.1.0 as well. JCL 1.4.0 maps trace() to Log4j DEBUG. jboss-development-bounces(a)lists.jboss.org wrote: > Only that some post 1.2.8 version did break when used with > jboss. If its tested and shown to work we can consider updating to it. > > Brian Stansberry wrote: >> Is there any particular reason the AS is shipping log4j 1.2.8 when >> they're up to 1.2.13? We're discussing bundling 1.2.13 with JBoss >> Cache and JGroups as it has TRACE support out of the box. >> >> A quick search showed >> > http://www.jboss.com/index.html?module=bb&op=viewtopic&t=67835 where >> Adrian mentions a general aversion to upgrading due to previous >> upgrade issues. Wondering if there is any else we should know about. >> >> _______________________________________________ >> 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 Brian Stansberry Lead, AS Clustering JBoss, a division of Red Hat Ph: 510-396-3864 skype: bstansberry

20 years, 1 month

1
0
0 / 0

← Newer
1
...
55
56
57
58
59
60
61
...
75
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-development September 2006