Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C6EB8E753 for ; Tue, 4 Dec 2012 13:18:09 +0000 (UTC) Received: (qmail 65965 invoked by uid 500); 4 Dec 2012 13:18:09 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 65920 invoked by uid 500); 4 Dec 2012 13:18:09 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 65912 invoked by uid 99); 4 Dec 2012 13:18:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Dec 2012 13:18:08 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [80.244.253.218] (HELO mail.traeumt.net) (80.244.253.218) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Dec 2012 13:17:59 +0000 Received: from [172.20.10.3] (unknown [46.115.35.139]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.traeumt.net (Postfix) with ESMTPSA id 9E67414297 for ; Tue, 4 Dec 2012 14:12:12 +0100 (CET) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: Failing CLI tests From: Jan Lehnardt In-Reply-To: Date: Tue, 4 Dec 2012 14:17:05 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <90B37C26-4F5E-4677-B9A8-1000617215F6@apache.org> References: To: dev@couchdb.apache.org X-Mailer: Apple Mail (2.1499) X-Virus-Checked: Checked by ClamAV on apache.org On Dec 3, 2012, at 03:36 , Noah Slater wrote: > Okay, I have side-stepped the issue with: >=20 > export AM_DISTCHECK_CONFIGURE_FLAGS=3D--disable-tests >=20 > (--disable-tests was something I added to just skip all this stuff = when I > am working on the build...) >=20 > But my point remains. >=20 > I am using the largest AWS instance size, and I cannot make distcheck. = We > can't release without this, obviously. >=20 > Would really appreciate some help getting this fixed! :D Curious indeed, it works fairly well=99 on my MacBook Air & Mac Mini on SSD & spinning rust. Do we have any AWS-savvy readers here that could aide the debugging of this? Cheers Jan --=20 > On 3 December 2012 02:18, Noah Slater wrote: >=20 >> Just tried another run, and it froze up in the tests. For 10 minutes = or >> more. So I stopped it and started again. >>=20 >> ok 10 batch_save >> ok 11 bulk_docs >> ok 12 changes >> ok 13 coffee >> ok 14 compact >> ok 15 config >> ok 16 conflicts >> ok 17 content_negotiation >> ok 18 cookie_auth >> ok 19 copy_doc >>=20 >>=20 >>=20 >> ^Cmake[1]: *** [check-js] Interrupt >> make: *** [distcheck] Interrupt >>=20 >> And it happens on a second run... >>=20 >> ok 37 oauth_users_db >> ok 38 proxyauth >> ok 39 purge >> ok 40 reader_acl >> ok 41 recreate_doc >> ok 42 reduce >> ok 43 reduce_builtin >> ok 44 reduce_false >> ok 45 reduce_false_temp >>=20 >>=20 >> ^Cmake[1]: *** [check-js] Interrupt >> make: *** [distcheck] Interrupt >>=20 >> This is basically taking up my whole night just trying to get past = these >> tests. >>=20 >>=20 >> On 3 December 2012 02:02, Noah Slater wrote: >>=20 >>> (Suffice it to say, this results in unpredictable, and hence = useless, >>> Travis builds.) >>>=20 >>> I am getting this also: >>>=20 >>> ../test/etap/140-attachment-comp.t ......... Failed 9/85 subtests >>>=20 >>> I feel like a broken record at this point, but I do just want to >>> reitterate: tests that do not work 100% of the time make our testing >>> infrastructure next to useless. Which may be hyperbole, but false = negatives >>> certainly are not helpful. More to the point, they make my job much = harder >>> than it needs to be. I have literally been trying to get distcheck = to pass >>> for two hours now. >>>=20 >>> The only reason it has taken two hours is that one of the tests = fails >>> each time I run it. I feel like I'm playing the world's most boring = and >>> unfun slot machine. All I need is for this distcheck to pass so I = can >>> continue with my work. >>>=20 >>> For reference, I am doing this on High-Memory Quadruple Extra Large = EC2 >>> instance. >>>=20 >>>=20 >>> On 3 December 2012 01:53, Noah Slater wrote: >>>=20 >>>> Hey, >>>>=20 >>>> I am seeing a LOT of this: >>>>=20 >>>> = 7624/home/travis/builds/apache/couchdb/apache-couchdb-1.3.0a-0da9587-git/_= build/../src/couch_replicator/test/05-replication-many-leaves.t >>>> .. 22/? Bailout called. Further testing stopped: Timeout waiting = for >>>> replication to finish >>>>=20 >>>> Now, this occurs for me, somewhere towards the end of a distcheck = run >>>> that can take 20 mins. So obviously, each time this happens, it = costs me 20 >>>> mins of my time. So that's a little frustrating, heh. >>>>=20 >>>> But it only fails intermittently. >>>>=20 >>>> What can be done? >>>>=20 >>>> Thanks, >>>>=20 >>>> -- >>>> NS >>>>=20 >>>=20 >>>=20 >>>=20 >>> -- >>> NS >>>=20 >>=20 >>=20 >>=20 >> -- >> NS >>=20 >=20 >=20 >=20 > --=20 > NS