Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Date: Wed, 23 Aug 2006 12:43:49 -0700
From: David Van Couvering <David.Vancouvering@Sun.COM>
Subject: Re: Disable jdbcapi/blobclob4BLOB.java from DerbyNet temporarily?
 (Was: Re: Regression Test Failure! - TinderBox_Derby 433825 - Sun DBTG)
In-reply-to: <44EC31A4.2030804@Sun.COM>
Sender: David.Vancouvering@Sun.COM
To: derby-dev@db.apache.org
Message-id: <44ECAFF5.3080407@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
References: <20060823041545.5736.qmail@siv01>
 <54ac72d70608222150o7e708aefi91f9eacf96646faf@mail.gmail.com>
 <44EC31A4.2030804@Sun.COM>
User-Agent: Thunderbird 1.5.0.2 (X11/20060427)

+1

John Embretsen wrote:
> Andrew McIntyre wrote:
>> On 8/22/06, Ole.Solberg@sun.com <Ole.Solberg@sun.com> 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.
> 
>