Hi,
--- marc fleury [EMAIL PROTECTED] wrote:
we wish you a prompt recovery :)
Well - I needed an excuse for a rebuild of the system - 2.4 here we
come
Thanks,
Chris
=
Need somewhere to Live in London - http://freeflats.com
__
Do You
Hi,
There will be no more daily build/test reports mailings for a while -
this is due to a technical problem with my server - it won't boot up!
The hard disk seems to have corrupted some key boot binaries/libs.
I guess it gives me an excuse to upgrade it...
See ya,
Chris
=
Need somewhere
we wish you a prompt recovery :)
marcf
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Chris
|Kimpton
|Sent: Wednesday, August 01, 2001 5:50 AM
|To: [EMAIL PROTECTED]
|Subject: Re: [JBoss-dev] jboss daily test results - ON HOLD
|
|
|Hi
Hi,
--- Jason Dillon [EMAIL PROTECTED] wrote:
One of the reasons I am using the blackdown JDK is that it has a
green threads option - which I am using - which should eliminate
any
thread limit issues - but it is also showing a low count on the
tests.
What are the thread limit issues?
Hi,
--- Tobias Frech [EMAIL PROTECTED] wrote:
Chris Kimpton wrote:
snip
Alternatively, there are various bugs in these jdk's/Linux
versions
that are causing problems... but I am surprised it is showing up
so
subtlely...
Any other ideas on what could be causing it?
I must
Hi,
Looking at the test results more closely:
For the IBM jdk:
The jbossmq test just seems to die.
The mdb test just dies - but with Interrupted Socket Exception errors
- perhaps it does not handle this?
The jmsra test and testEJBspec tests complete, but have Interrupted
Socket Exception
One of the reasons I am using the blackdown JDK is that it has a
green threads option - which I am using - which should eliminate any
thread limit issues - but it is also showing a low count on the
tests.
What are the thread limit issues?
I must look at tinderbox some more - this would
You know the philosophy scratch your own itch. SF is open source.
- Original Message -
From: Jason Dillon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, July 26, 2001 5:15 PM
Subject: Re: [JBoss-dev] jboss daily test results
The SF people are very resonable and would most
I am seeing different results on a 2.4.3-12 kernel than your results, each of
which is different depending on which VM you use.
## Run 1
JBoss daily test results
SUMMARY
Number of tests run: 145
Successful tests: 145
Errors:
Hi,
--- Jason Dillon [EMAIL PROTECTED] wrote:
Huh? Why did the number of tests drop?
Good question - we did seem to hit a memory/number of sockets limit a
few weeks back - perhaps there is some variation in the tests that
means they sometimes use more resources...
Strangely, it went back
to too
many processes
on linux.
- Original Message -
From: Chris Kimpton [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, July 23, 2001 4:24 AM
Subject: Re: [JBoss-dev] jboss daily test results
Hi,
--- Jason Dillon [EMAIL PROTECTED] wrote:
Huh? Why did the number
: Chris Kimpton [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, July 23, 2001 9:47 AM
Subject: Re: [JBoss-dev] jboss daily test results
Hi,
I just switched to the latest IBM jdk1.3 and I now get 145 tests - of
which one fails - see http://lubega.com for details.
I will try and get
]
To: [EMAIL PROTECTED]
Sent: Monday, July 23, 2001 4:24 AM
Subject: Re: [JBoss-dev] jboss daily test results
Hi,
--- Jason Dillon [EMAIL PROTECTED] wrote:
Huh? Why did the number of tests drop?
Good question - we did seem to hit a memory/number of sockets
limit a
few weeks
.
- Original Message -
From: Chris Kimpton [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, July 23, 2001 9:47 AM
Subject: Re: [JBoss-dev] jboss daily test results
Hi,
I just switched to the latest IBM jdk1.3 and I now get 145 tests - of
which one fails - see http://lubega.com
Huh? Why did the number of tests drop?
--jason
On Sun, 22 Jul 2001 [EMAIL PROTECTED] wrote:
JBoss daily test results
SUMMARY
Number of tests run: 59
Successful tests: 59
Errors:0
Failures: 0
Hi,
--- Scott M Stark [EMAIL PROTECTED] wrote:
The test run includes less than half the current tests. Based on
the run log
it looks
like the server ran out of threads during the lock test and the
server
shutsdown
after than and all subsequent tests silently fail. What is the OS
maker
Hi,
I am re-running them to see if it works now.
All clean now...
SUMMARY
Number of tests run: 132
Successful tests: 132
Errors:0
Failures: 0
] jboss daily test results
Hi,
I am re-running them to see if it works now.
All clean now...
SUMMARY
Number of tests run: 132
Successful tests: 132
Errors:0
Failures: 0
Could we have the detail of each test html'ifyed. I would do it, but I
don't know much about xml stylesheets. Mozilla just strips out all of the
tags, which makes it a bit hard to look at.
--jason
On Thu, 12 Jul 2001, Chris Kimpton wrote:
Hi,
I am re-running them to see if it works
It also looks like the server failed to startup correctly, with a few:
java.net.BindException: Address already in use
--jason
On Wed, 11 Jul 2001, Scott M Stark wrote:
The test run includes less than half the current tests. Based on the run log
it looks
like the server ran out of
I don't know if this is possibly relevant,
While working on my jca/jdbc Firebird driver I experienced:
with read committed isolation, got a very similar error (couldn't transfer
-50.0), caused by deadlock exception in database. It occured 2 times,
once/ multithreaded test.
with snapshot (more
--- [EMAIL PROTECTED] wrote:
JBoss daily test results
SUMMARY
Number of tests run: 112
Successful tests: 112
Errors:0
Failures: 0
Something
Here is the server side exception to the error reported by the unit test:
[Account] java.lang.NullPointerException
[Account] at
org.jboss.ejb.plugins.EntitySynchronizationInterceptor$InstanceSynchronizati
on.beforeCompletion(EntitySynchronizationInterceptor.java:371)
[Account] at
Hi,
Thanks for that - I've re-run them and get these results...
JBoss daily test results
SUMMARY
Number of tests run: 112
Successful tests: 111
Errors:1
Failures: 0
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of
|[EMAIL PROTECTED]
|Sent: Saturday, July 07, 2001 9:47 PM
|To: [EMAIL PROTECTED]
|Subject: [JBoss-dev] jboss daily test results
|
|
|
|
|JBoss daily test results
|
|SUMMARY
|
|Number of tests run: 112
Now that is what it should look like ;)
--jason
On Sun, 8 Jul 2001 [EMAIL PROTECTED] wrote:
JBoss daily test results
SUMMARY
Number of tests run: 112
Successful tests: 112
Errors:0
Failures: 0
|Now that is what it should look like ;)
yeah, the strange part is that I didn't do anything :)
I just waited (well was working on the website forums)
and poof, just like that, they were gone :)
marcf
|
|--jason
|
|
|On Sun, 8 Jul 2001 [EMAIL PROTECTED] wrote:
|
|
|
| JBoss daily test
Looks like the server did not startup correctly... you might need to kill -9
your java processes. =(
--jason
On Sat, 7 Jul 2001 [EMAIL PROTECTED] wrote:
JBoss daily test results
SUMMARY
Number of tests run: 9
Successful tests: 9
Hi,
--- Jason Dillon [EMAIL PROTECTED] wrote:
I don't get this. When you run jbosstest/dist/bin/jmsratest.sh all
of the
tests succeed. This test only fails when it is run as part of the
full
test suite. It looks like a test that runs before this one mucks
with
something. I checked
It is intermittent as well - some days they all fail, some days they
all work - there are some other tests that seem to be rarely/never
get through - I get a total of around 94 tests when I run the same
thing manually...
From a few hours of looking into I would say there is something
I don't get this. When you run jbosstest/dist/bin/jmsratest.sh all of the
tests succeed. This test only fails when it is run as part of the full
test suite. It looks like a test that runs before this one mucks with
something. I checked that all of the tests in this suite run correctly in
any
Hi,
Georg Rehfeld wrote:
isn't it a shame, that we keep getting these 5 errors every night?
Yes.
Sorry, that I hadn't the time yet to look after them, isn't it meant
for the authors to correct the bugs?
I think that's the purpose of the tests.
Chris does a nice job to help us, but some
James Cook wrote:
I assume that tests are run from the HEAD branch? If so, I would also assume
that the current 2.2.2 (stable?) release also suffered quite a few
errors/failures?
Why would you assume that? HEAD and 2.2.2 are quite distinctly different
branches.
I assume that tests are run from the HEAD branch? If so, I would also assume
that the current 2.2.2 (stable?) release also suffered quite a few
errors/failures?
jim
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
[EMAIL PROTECTED]
Sent: Saturday,
...hopefully it wasn't me... ;-)
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [JBoss-dev] jboss daily test results
Date: Mon, 21 May 2001 02:43:57 +0100
=
==THIS IS AN AUTOMATED EMAIL -
Hi,
Suite: org.jboss.test.cts.test.AllJUnitTests
Test:testRemoveSessionObject
Type:failure
Exception: junit.framework.AssertionFailedError
Message: [EJB 1.1, p42] Expected 'RemoveException',
detail:java.rmi.ServerException: RemoteException occurred in server
The new details format page looks great.
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, May 08, 2001 6:46 PM
Subject: [JBoss-dev] jboss daily test results
=
==THIS IS AN
The timing increase seems to be do to the latest version of Hypersonic. I see
a long pause(20-30) secs on the console after these msgs:
[Hypersonic] Starting
Server 1.4 is running
Press [Ctrl]+[C] to abort
...
JBoss 2.3 BETA Started in 0m:37s
This used to start in under 10 secs on my box so
Hi,
Did these changes;
P jboss/src/etc/conf/default/jboss.conf
P jboss/src/etc/conf/default/log4j.properties
P jboss/src/main/org/jboss/logging/Log.java
U jboss/src/main/org/jboss/logging/LogToCategory.java
P jboss/src/main/org/jboss/logging/Logger.java
P
]
Sent: Wednesday, April 25, 2001 2:03 AM
Subject: Re: [JBoss-dev] jboss daily test results
Hi,
Did these changes;
P jboss/src/etc/conf/default/jboss.conf
P jboss/src/etc/conf/default/log4j.properties
P jboss/src/main/org/jboss/logging/Log.java
U jboss/src/main/org/jboss/logging
Hi,
From: Scott M Stark [EMAIL PROTECTED]
Something is amiss with your server as these errors are all related to
the JMX connector not being bound in JNDI and I don't see this
problem. When I run the tests I am seeing the same errors as before.
Perhaps it ran during the middle of a set of
against the build.
- Original Message -
From: Chris Kimpton [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, April 25, 2001 10:20 AM
Subject: Re: [JBoss-dev] jboss daily test results
Hi,
From: Scott M Stark [EMAIL PROTECTED]
Something is amiss with your server
42 matches
Mail list logo
