Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 17364 invoked from network); 8 Jul 2010 13:43:01 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 8 Jul 2010 13:43:01 -0000 Received: (qmail 39563 invoked by uid 500); 8 Jul 2010 13:42:59 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 39225 invoked by uid 500); 8 Jul 2010 13:42:57 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 39201 invoked by uid 99); 8 Jul 2010 13:42:56 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Jul 2010 13:42:56 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of zachary.zolton@gmail.com designates 74.125.82.180 as permitted sender) Received: from [74.125.82.180] (HELO mail-wy0-f180.google.com) (74.125.82.180) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Jul 2010 13:42:49 +0000 Received: by wya21 with SMTP id 21so804982wya.11 for ; Thu, 08 Jul 2010 06:42:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:content-type :content-transfer-encoding; bh=PNOs+Ly0tk4408nY1QqHifRLzEHuXAeVcv25QdLUvus=; b=Jy3LgfXF4HMo2k6FCgRk/fC8FqriE6i2AzkdnaS4gSGC/Afp0UiC+up06Nmm6HH3c0 AAzmWEBHRCAqOYUyCviVKQfAfWhAaRBYigRU9oYtxPcweOjtwhzOeUKUsGPUmB3DPIft nBGVvvkXshhXMfuc943HCQ/P90M5rEvkLIetI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=pM7022rm9udXNPKw/PeecPIl4Ij5reJyOK12A3B5xKTVgaEwmEcGG7rMDVWjiysrqj e9cMdEgscfuorKnTg7O5KZaJIryXbDS2f0xqTQ/1LTFwCTwB3dkjUJZT4mwlS5BW4YXY 9BndnxyX4sqcYdoswfEm9MCWOzhN9D9H95Ops= Received: by 10.216.180.145 with SMTP id j17mr2627332wem.109.1278596548379; Thu, 08 Jul 2010 06:42:28 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.181.8 with HTTP; Thu, 8 Jul 2010 06:42:08 -0700 (PDT) In-Reply-To: References: <-5509213296060124934@unknownmsgid> From: Zachary Zolton Date: Thu, 8 Jul 2010 08:42:08 -0500 Message-ID: Subject: Re: Trying to test 1.0 artefact To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Hmm... I just did a fresh download and make dev, and all the tests ran fine the first time. However the second time I received this failure: compact failure 2086ms=09 1. Assertion failed: db.info().disk_size < deletesize Then a different failure the third time running all the tests: rev_stemming error 79ms=09 1. Exception raised: {"error":"file_exists","reason":"The database could not be created, the file already exists."} FWIW, I did completely clear my browser cache, stopped my other CouchDB 0.11 instance, and I'm now running the 1.0 artefact on port 5984. On Wed, Jul 7, 2010 at 10:58 PM, J Chris Anderson wrote: > > On Jul 7, 2010, at 8:42 PM, Zachary Zolton wrote: > >> Sorry, if I wasn't clear enough earlier. (^w^) That log was captured >> while running all the tests in Futon. >> >> I'm running the test suite in Firefox 3.6.3, and the table contains >> the following after I run: >> http://friendpaste.com/4v4ryhrweSu1PRifAVBMlQ >> > > That does look bad. > > Are you sure you are running a good install of CouchDB? Just now while te= sting the 0.11.1 release I had a bunch of errors and it turned out I was ru= nning CouchDB 1.0 with the 0.11.1 test suite. (This can happen if you do th= e make install step) > > But since you are running using utils/run it's probably not a version mis= match. > > Did you run `make dev` before running utils/run? > > The other thing to do is to clear your browser cache. > > Chris > >> -Zach >> >> >> On Wed, Jul 7, 2010 at 10:05 PM, Robert Newson = wrote: >>> The test page reports "success" for each test. Some tests verify that >>> error conditions are handled, so the log always contains some alarming >>> error messages. Hopefully that's what happened here. >>> >>> Sent from my iPad >>> >>> On 7 Jul 2010, at 22:57, J Chris Anderson wrote: >>> >>>> >>>> On Jul 7, 2010, at 7:43 PM, Zachary Zolton wrote: >>>> >>>>> Friends, >>>>> >>>>> I'm having trouble running the browser tests for the 1.0 artefact... >>>>> Have I done something silly? >>>>> >>>> >>>> What do you mean? Are there failures when you run them? >>>> >>>>> I'm on Mac OS X 10.6.4 with Erlang R13B04, and running via the >>>>> ./utils/run script. >>>>> >>>>> Here's a link to the logs from when I ran all the tests: >>>>> http://friendpaste.com/2SmffccO5aRrLcz5f1XZgV >>>>> >>>> >>>> The logs look ok to me (didn't read them, =A0but it looks like the tes= t suite successfully finished.) >>>> >>>>> Is there any other data I should provide? >>>>> >>>>> >>>>> Cheers, >>>>> >>>>> Zach >>>> >>> > >