Return-Path: X-Original-To: apmail-cordova-dev-archive@www.apache.org Delivered-To: apmail-cordova-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 ABC1C17AD6 for ; Thu, 30 Oct 2014 23:03:52 +0000 (UTC) Received: (qmail 28327 invoked by uid 500); 30 Oct 2014 23:03:52 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 28285 invoked by uid 500); 30 Oct 2014 23:03:52 -0000 Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list dev@cordova.apache.org Received: (qmail 28271 invoked by uid 99); 30 Oct 2014 23:03:51 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Oct 2014 23:03:51 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of mmocny@google.com designates 209.85.213.182 as permitted sender) Received: from [209.85.213.182] (HELO mail-ig0-f182.google.com) (209.85.213.182) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Oct 2014 23:03:47 +0000 Received: by mail-ig0-f182.google.com with SMTP id hn18so6099686igb.9 for ; Thu, 30 Oct 2014 16:01:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=0urdWwXI7ExKwoK+eJre/KYc2fZtm3yM+vY/6CwU85M=; b=bg5CsxxSMhdkirPJrUdgFAp7nCL9fr23t3i7Fneqc38FOguCNbiPzJ8/nyVVuAEk4Z N+XCM8yWCQlOvJulLkqCT3vny+KJ4jIqGMHEJa1lirylcnIa3RPIChM9pikIE6sYMsmc w0k4aAWdvZnt4ydM1wKx91DaVH8PkbanXIptOlC2QKJ6Zr7o/uE3PdWLOD9KL9q9JKYh ALxGzmLNEfXdijhNE7uRINdHEbAGerZXBNbp7Ug8iSCiRtYvW2B5htzf7U0MqQc2ivwb gCZsCy4DUpQHQmsF7IraOMirP+dOXIyedgs395w45At09qYcrpSYPOupnQicKwaJTotC 8SEw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=0urdWwXI7ExKwoK+eJre/KYc2fZtm3yM+vY/6CwU85M=; b=TkHFlReRf9PlTNSp8BVsIvtu/qhRFBA274CFjbzF6b0xmQhrzJs37diCGOr5CeKgP7 c2R6XnWvrviUwmxhaQ3/9LA2BDrzC+VKmE1/acnE1bZSNlibOrHXJKfVEUeuZFfX6ozU GREW8y1uwVJFIinj2aglzjakqGzsDIOli9VtQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-type; bh=0urdWwXI7ExKwoK+eJre/KYc2fZtm3yM+vY/6CwU85M=; b=ZZiyr2gBgNa/9Q2PirXMCdJ03oT3ZEfCBRvIDYSYaKh+bcQCO7XqsPEjdgmCEh7qmG Vo7XMYsj3USSTg7qh5E52pQsAy9JH1JE2g/EA354cYCS/3HPEKwtXdsNgRxvTLH9No5+ a3wh0rRtCckScxe5shMYJRAUC62nQdZWczz0AF29RVbFEb5oE7LXgQQ+9rXq2NzcEK51 QBK5JuzKMU1XKo5wlF2UjMjHxqxQtr4udM8J7kdpvfL9Rj/qnYFnGGaLXVbI1R2o1E26 LF7/9vGkTlXY0zu1lS2wukXOFHhQviQ7UiwZe0jKdE1XDu3a5GBTBPj4JB377Q7tzyhO Dgvw== X-Gm-Message-State: ALoCoQlpi1K/YCXnxSRzLDiNvOqcGmfMXiIHZjSgjltupwQX15hFHZnkBaKOIJgp9/zXFHRU19sD X-Received: by 10.50.61.209 with SMTP id s17mr486155igr.34.1414710117447; Thu, 30 Oct 2014 16:01:57 -0700 (PDT) MIME-Version: 1.0 Sender: mmocny@google.com Received: by 10.64.59.168 with HTTP; Thu, 30 Oct 2014 16:01:37 -0700 (PDT) In-Reply-To: <58142C088411D042B70782AD5D5B23E12539C19B@SYD1217> References: <58142C088411D042B70782AD5D5B23E12539C125@SYD1217> <58142C088411D042B70782AD5D5B23E12539C19B@SYD1217> From: Michal Mocny Date: Thu, 30 Oct 2014 19:01:37 -0400 X-Google-Sender-Auth: BzEyHV28E4gB3H74FVjjnWS6L_w Message-ID: Subject: Re: [mobile-spec] consistency and reliability To: dev Cc: Shazron , "Toda, Shingo" Content-Type: multipart/alternative; boundary=047d7bdc14e602d5cb0506abde0c X-Virus-Checked: Checked by ClamAV on apache.org --047d7bdc14e602d5cb0506abde0c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I've seen that in the past and it usually happens due to misuse of jasmine, which seems unfortunately quite brittle. Specifically, if done() isn't called, or an async event fires after a test has already failed / timed out and calls done(), or registers new tests with it() etc, weird things will happen. Usually its a sign that a test is not handling failures appropriately, but it is a bit unfortunate that jasmine is so brittle. -Michal On Thu, Oct 30, 2014 at 6:10 PM, Toda, Shingo wrote: > This is exactly what I got too. > > Regards, > Shingo > > From: Shazron [mailto:shazron@gmail.com] > Sent: Friday, October 31, 2014 9:02 AM > To: dev@cordova.apache.org > Cc: Toda, Shingo > Subject: Re: [mobile-spec] consistency and reliability > > Seems to be exactly what I am seeing. > Here's the image as a link: http://i.imgur.com/n6ST1Kd.png?1 > > On Thu, Oct 30, 2014 at 2:57 PM, Toda, Shingo > wrote: > Hi Shazron > > Our team are running mobilespec for Android, iOS and Windows. I cannot se= e > the attachment but we also have been seeing what you=E2=80=99ve gotten si= nce new > style mobilespec was introduced. It seems that each plugin test run works > fine but if all tests get run at once I am likely to get more than one > report in a run reporting that there are a number of specs like 900 specs > (I don=E2=80=99t think specs are so much). > > I noticed that some of the specs were called more than once when I got > multiple reports. I usually disable FileTransfer, Globalization and Media > specs at first then run test for them individually because I saw some of > those tests got called more than once. This could be just my case so it > might not be yours. > > Regards, > Shingo > > From: Shazron [mailto:shazron@gmail.com] > Sent: Friday, October 31, 2014 7:54 AM > To: dev@cordova.apache.org > Subject: [mobile-spec] consistency and reliability > > > `cordova-mobile-spec/createmobilespec/createmobilespec.js --ios > --globalplugins` > > Has anyone gotten mobile-spec to work consistently? I get wildly differen= t > results on each run. Sometimes there is more than one report in a run. Se= e: > > [Inline image 1] > > --047d7bdc14e602d5cb0506abde0c--