From dev-return-10824-archive-asf-public=cust-asf.ponee.io@arrow.apache.org Mon Mar 4 15:11:19 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 7EE29180627 for ; Mon, 4 Mar 2019 16:11:18 +0100 (CET) Received: (qmail 95511 invoked by uid 500); 4 Mar 2019 15:11:17 -0000 Mailing-List: contact dev-help@arrow.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@arrow.apache.org Delivered-To: mailing list dev@arrow.apache.org Received: (qmail 95499 invoked by uid 99); 4 Mar 2019 15:11:16 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Mar 2019 15:11:16 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 41489C06CD for ; Mon, 4 Mar 2019 15:11:16 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.903 X-Spam-Level: * X-Spam-Status: No, score=1.903 tagged_above=-999 required=6.31 tests=[DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id wjmcd0Ez0qxA for ; Mon, 4 Mar 2019 15:11:14 +0000 (UTC) Received: from mail-ot1-f68.google.com (mail-ot1-f68.google.com [209.85.210.68]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 35E2D60D1B for ; Mon, 4 Mar 2019 15:11:14 +0000 (UTC) Received: by mail-ot1-f68.google.com with SMTP id b3so4467345otp.4 for ; Mon, 04 Mar 2019 07:11:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=2O3AthB+aBS3FZBVZi7pPtkQ5oQ1d4RcQqzLYj/08vQ=; b=P9xbWftUuVSZURwY3pMgbk2asqnSw6PUKwkKUABSxwN/+G+cV3X+2akUyEvuUs4/Mc t/YznPBQ8spE1r79LNICVXnOOmtAFkd96QTWVmafXYVTDgmHuxTz6qzFp68+0m+x+R/S Cd27X5Z2Y4ZB7AUjkB6ZNTdzb8l4z/9s1lpY2VTshplF7qmQTiJg8prxym5PM+DaX8C8 +jUJhXnGQvpm+58R3Vw0uFEyc2+9VIx0AKE/f3KpojyQXqZzN6pytIVCZVtGIP01iK7m dNV1YBQxHSEi7GT5yz6JX4F7Dafcmvs5MsTRpSvjEJI68Qt+37sqV4Zdw+oe2L3q4WBb c15A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=2O3AthB+aBS3FZBVZi7pPtkQ5oQ1d4RcQqzLYj/08vQ=; b=tbLgh1nygWRNwRRKm90fTOqoe/+Ou4hmSDNtEQbtjmaFijjwpfRcHq25GiiZZOAP45 meUd48rNxfj6WkM8tQEGYHuZCbMf7162PSwCHa9WH68zsHyK2z8rXZ3Pjm5qRwQuuxpV semrRbo5P5R2FSjcI3m7kk38aXd6OzIQYQlI4OnCkSR0IK91wiwv6ybtxEDySUUPrTOg 8tHQ6CXu8qPi+A3R1QdJX+8QhAzvYQtwogkqN4TJwlSWJcpfoQfz+TkeW/s9QSF8BI1N nC2SoSkxmEzt8u8aqQ1EFKEaZj9/iTidb1rtTSzL/XzJ8rMMcBPeijBFCTuF4HfBgc2o VbRw== X-Gm-Message-State: APjAAAWv4WIvViVb6Poh+psQM4XVjVCx6BoR43lMBJKC5v11gWEgpqrE S0r6uvPI1rE/Yg9o5k+duNcfk1uVFa80ID+yWJa7KO1RHHk= X-Google-Smtp-Source: APXvYqyOJ3z23RqqLD20RVaPzdSqtozTEGQx8zTvtjwsOTYz5dJ/SLz7XiNve8Hvc/ro4/Ok9hxYmQXUQZfbB5TQah8= X-Received: by 2002:a9d:72c2:: with SMTP id d2mr13641006otk.228.1551712272833; Mon, 04 Mar 2019 07:11:12 -0800 (PST) MIME-Version: 1.0 References: <20190226211839.78f7b706@fsol> <0482ECDE-AEBA-4BBB-8A19-4A7C0C5D7A72@dremio.com> <618f9400-f122-6b58-eb93-fd777bb10474@python.org> <3F270CE6-5848-49CD-9E6C-3CD75B34BA9D@dremio.com> In-Reply-To: From: Francois Saint-Jacques Date: Mon, 4 Mar 2019 10:11:01 -0500 Message-ID: Subject: Re: Flaky Travis CI builds on master To: dev@arrow.apache.org Content-Type: multipart/alternative; boundary="000000000000d105d10583462a56" --000000000000d105d10583462a56 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello, I created a new label named `ci-failure`, which was retroactively applied to most issues triggering a CI failure in other PRs/master (I searched for travis-ci.org/apache/arrow and tagged them). The goal here is to track issues which generates false positives failure in PRs and ideally minimize this and/or give a very high priority to resolve. The following dashboard https://cwiki.apache.org/confluence/display/ARROW/Continuous+Integration+fa= ilures tracks all task with the `ci-failure` label. I also took the opportunity to tidy the top level navigation page tree, notably - created a Releases page and moved all release pages - created a Dashboards page and moved all related pages - created a Developers page and moved all related pages - Ordered page in importance for new users, e.g. contribute & release at top, moved all committer/maintainer stuff in the lower part Fran=C3=A7ois On Sat, Mar 2, 2019 at 5:53 PM Wes McKinney wrote: > I just gave you edit access. > > If any PMC member would like to be an admin on the Confluence space > (and you are not already), please let me know and I'll add you so you > can help with the wiki admin requests > > On Fri, Mar 1, 2019 at 8:09 PM Francois Saint-Jacques > wrote: > > > > Could someone give me write/edit access to confluence? > > > > Thank you, > > Fran=C3=A7ois > > > > On Fri, Mar 1, 2019 at 3:55 PM Francois Saint-Jacques < > > fsaintjacques@gmail.com> wrote: > > > > > I'll take this. > > > > > > On Fri, Mar 1, 2019 at 3:55 PM Wes McKinney > wrote: > > > > > >> We could create a page on the wiki that shows all open and resolved > > >> issues relating to unexpected CI / build failures. Would someone lik= e > > >> to give this a go? There are probably many historical issues that ca= n > > >> be tagged with the label > > >> > > >> On Fri, Mar 1, 2019 at 12:45 PM Francois Saint-Jacques > > >> wrote: > > >> > > > >> > I agree with adding a tag/label for this and even marking the > failure as > > >> > critical. > > >> > > > >> > > > >> > On Fri, Mar 1, 2019 at 12:18 PM Micah Kornfield < > emkornfield@gmail.com> > > >> > wrote: > > >> > > > >> > > Moving away from the tactical for a minute, I think being able t= o > > >> track > > >> > > these over time would be useful. I can think of a couple of hig= h > > >> level > > >> > > approaches and I was wondering what others think. > > >> > > > > >> > > 1. Use tags appropriately in JIRA and try to generate a report > from > > >> that. > > >> > > 2. Create a new confluence page to try to log each time these > occur > > >> (and > > >> > > route cause). > > >> > > 3. A separate spreadsheet someplace (e.g. Google Sheet). > > >> > > > > >> > > Thoughts? > > >> > > > > >> > > -Micah > > >> > > > > >> > > > > >> > > On Fri, Mar 1, 2019 at 8:55 AM Francois Saint-Jacques < > > >> > > fsaintjacques@gmail.com> wrote: > > >> > > > > >> > > > Also just created > https://issues.apache.org/jira/browse/ARROW-4728 > > >> > > > > > >> > > > On Thu, Feb 28, 2019 at 3:53 AM Ravindra Pindikura < > > >> ravindra@dremio.com> > > >> > > > wrote: > > >> > > > > > >> > > > > > > >> > > > > > > >> > > > > > On Feb 28, 2019, at 2:10 PM, Antoine Pitrou < > antoine@python.org > > >> > > > >> > > > wrote: > > >> > > > > > > > >> > > > > > > > >> > > > > > Le 28/02/2019 =C3=A0 07:53, Ravindra Pindikura a =C3=A9cri= t : > > >> > > > > >> > > >> > > > > >> > > >> > > > > >>> On Feb 27, 2019, at 1:48 AM, Antoine Pitrou < > > >> solipsis@pitrou.net> > > >> > > > > wrote: > > >> > > > > >>> > > >> > > > > >>> On Tue, 26 Feb 2019 13:39:08 -0600 > > >> > > > > >>> Wes McKinney wrote: > > >> > > > > >>>> hi folks, > > >> > > > > >>>> > > >> > > > > >>>> We haven't had a green build on master for about 5 days > now > > >> (the > > >> > > > last > > >> > > > > >>>> one was February 21). Has anyone else been paying > attention > > >> to > > >> > > this? > > >> > > > > >>>> It seems we should start cataloging which tests and bui= ld > > >> > > > environments > > >> > > > > >>>> are the most flaky and see if there's anything we can d= o > to > > >> reduce > > >> > > > the > > >> > > > > >>>> flakiness. Since we are dependent on anaconda.org for > build > > >> > > > toolchain > > >> > > > > >>>> packages, it's hard to control for the 500 timeouts tha= t > > >> occur > > >> > > > there, > > >> > > > > >>>> but I'm seeing other kinds of routine flakiness. > > >> > > > > >>> > > >> > > > > >>> Isn't it https://issues.apache.org/jira/browse/ARROW-468= 4 > ? > > >> > > > > >> > > >> > > > > >> ARROW-4684 seems to be failing consistently in travis CI. > > >> > > > > >> > > >> > > > > >> Can I merge a change if this is the only CI failure ? > > >> > > > > > > > >> > > > > > Yes, you can. > > >> > > > > > > >> > > > > Thanks ! > > >> > > > > > > >> > > > > > > > >> > > > > > Regards > > >> > > > > > > > >> > > > > > Antoine. > > >> > > > > > > >> > > > > > > >> > > > > > >> > > > > >> > > > > --000000000000d105d10583462a56--