Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 80065 invoked from network); 30 May 2007 22:33:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 May 2007 22:33:47 -0000 Received: (qmail 63626 invoked by uid 500); 30 May 2007 22:33:51 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 63411 invoked by uid 500); 30 May 2007 22:33:51 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 63395 invoked by uid 99); 30 May 2007 22:33:51 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 May 2007 15:33:51 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [192.18.43.133] (HELO sca-es-mail-2.sun.com) (192.18.43.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 May 2007 15:33:44 -0700 Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id l4UMXNuc022530 for ; Wed, 30 May 2007 15:33:23 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JIV00201LABX800@fe-sfbay-09.sun.com> (original mail from Michelle.Caisse@Sun.COM) for derby-dev@db.apache.org; Wed, 30 May 2007 15:33:23 -0700 (PDT) Received: from [192.168.1.102] ([64.142.9.219]) by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JIV000XELBMMK80@fe-sfbay-09.sun.com> for derby-dev@db.apache.org; Wed, 30 May 2007 15:33:22 -0700 (PDT) Date: Wed, 30 May 2007 15:34:01 -0700 From: Michelle Caisse Subject: Re: norway specific failure in CollationTest2 In-reply-to: <465DF498.50207@sbcglobal.net> Sender: Michelle.Caisse@Sun.COM To: derby-dev@db.apache.org Reply-to: Michelle.Caisse@Sun.COM Message-id: <465DFBD9.3000807@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=UTF-8 Content-transfer-encoding: 8BIT References: <1180558138.17593.22.camel@eiger> <465DE909.5010605@sun.com> <465DF498.50207@sbcglobal.net> User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) X-Virus-Checked: Checked by ClamAV on apache.org For a quick response, in Norwegian, a sequence of two 'a' characters is equivalent to a single 'a'-with-a-circle-on-top character. Maybe someone who both knows more about Norwegian and character sets can confirm later. -- Michelle Mike Matrigali wrote: > I'll try to figure out what is going on with the CollationTest2 test. > I am not seeing it in my environment, and it does not seem to have > shown up in any of the publically posted nightly regression tests. > > Can someone from Norway help, is it possible that 2 strings used in > the test, are to be treated as equal in Norway?: > "Wσgan" "Waagan" > > The first string contains an unfamilar character (to my english > environment - I am not sure my mailer will even handle it correctly) > as it's second letter, and I am wondering if I should have used a > unicode escape for the data > instead. See the data string in the runDerby2670()routine of the > CollationTest2 test. > > Is there a chance that in norway aa is supposed to be treated > as equal to the second letter in the first string listed? If so then > either order may be right, and the test is incorrectly testing for > one order or the other. > > I tried to take the data from a donated test case and put it into > the junit test. It could be I messed something up on my side dealing > with a non english character in some step of the way (file handling, > code sets, editor, ...). > > Rick Hillegas wrote: > >> Julius Stroffek wrote: >> >>> Hi All, >>> >>> When I ran junit tests now for trunk I get 17 errors and 70 failures of >>> many different kinds. >>> >>> My junit console output with exceptions thrown is attached. Probably it >>> is something wrong with my test environment or so, but I have no idea >>> what happened. Are there any issues with upgrade tests due to a new >>> release? Probably this is not the case since these tests does not fail >>> in daily and tinderbox test runs. >>> >>> I always delete the contents of the current directory where I run tests >>> (which ends using as derby.system.home). I tried to checkout the source >>> again and start from a scratch but it does not helped. >>> >>> I run junit throught suites.All. >>> >> >> Hi Julo, >> >> I saw tons of upgrade errors in tests which I ran yesterday. Those >> errors disappeared after I synced my client to the mainline this >> morning. Now I am seeing the error which you are seeing in >> CollationTest2. Otherwise, the tests run cleanly for me. >> >> Regards, >> -Rick >>