Hello.
If possible, I hope the result of the daily-derbyall to be open to public,
some where on the derby site.
Then, we can compare it to result of local-derbyall.
// I think derbyall twice at everyone's local is little hard ....
It will be index of current quality.
Best regards.
/*
Tomohito Nakayama
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Naka
http://www5.ocn.ne.jp/~tomohito/TopPage.html
*/
----- Original Message -----
From: "Bernt M. Johnsen" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, May 26, 2005 8:27 PM
Subject: Running derbyall before submitting patches
Hi all,
The last week or two, derbyall has failed a lot the time. This makes
it hard to verify that I haven't goofed up things when doing changes
in the code (I run derbyall daily as a quality measure). To be able to
work efficiently, many of us are dependent on a reliable test suite.
So, I urge everyone who submits a patch to the Derby to run derbyall
on at least one platform/vm and not only the "relevant" tests for the
patch, even if you "know" that it should not be necessary. I think
this would save us all a lot of work (even more time saved for the
committers, I guess :-).
I know this won't guarantee that derbyall runs correctly all the time,
but the frequency of problems should at least go down.
Thanks
--
Bernt Marius Johnsen, Database Technology Group,
Sun Microsystems, Trondheim, Norway
--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.322 / Virus Database: 266.11.17 - Release Date: 2005/05/25
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.322 / Virus Database: 266.11.17 - Release Date: 2005/05/25
