+1
John Embretsen wrote:
Andrew McIntyre wrote:
On 8/22/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
[Auto-generated mail]
*TinderBox_Derby* 433825/2006-08-23 03:43:00 CEST
*derbyall*
Failed Tests OK Skip Duration Platform
-------------------------------------------------------
*Jvm: 1.5*
1 672 671 2 121.16% SunOS-5.10_i86pc-i386
Ah well, close but no cigar. We've got two test runs that show
different diffs for the same test with the same version of JCC and a
static set of masters.
While converting the test to a junit test in order to make it
deterministic would be ideal, I will not be frying that fish anytime
soon. So, I think the test should be removed from running against JCC
by adding it to DerbyNet.exclude until someone comes up with a better
solution.
andrew
I agree.
BTW, please include the Jira issue number (in this case DERBY-1691) in
commit messages, so that it is possible to track related changes via Jira.
