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 cust-asf.ponee.io (Postfix) with SMTP id 40474165F35 for ; Tue, 25 Jul 2017 02:35:12 +0200 (CEST) Received: (qmail 70594 invoked by uid 500); 25 Jul 2017 00:35:11 -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 70582 invoked by uid 99); 25 Jul 2017 00:35:11 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Jul 2017 00:35:11 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 8E80D1A07D9 for ; Tue, 25 Jul 2017 00:35:10 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.901 X-Spam-Level: X-Spam-Status: No, score=-0.901 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd2-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 (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id lW3CcWMNx5EF for ; Tue, 25 Jul 2017 00:35:08 +0000 (UTC) Received: from mail-wr0-f179.google.com (mail-wr0-f179.google.com [209.85.128.179]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 1628C5FD0C for ; Tue, 25 Jul 2017 00:35:08 +0000 (UTC) Received: by mail-wr0-f179.google.com with SMTP id v105so82130209wrb.0 for ; Mon, 24 Jul 2017 17:35:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=BTnaGF/9xxGW5IGaSBvWawH/eKSkzgmbxFLTt0/O4I0=; b=RiKp/WWSiKPP3v/o03JaU15yo3+EucytHGcdLM3Ok3SDzIWOohhpNJruMQ8zY4xmwM ivh0slYURYoamBrERQ6eDuGqQ9lIpYwBr81FMaBhEU7mVRpBOwR6L8LY74nwhpTisuXG FosPZ56vNHS5ojxtoJFgKBUOxohAzmqnI5ou2pM3molzZhfCY8siYAFyXDiBO1Jui2x3 USawG8yWepSWUADlGmHKrcrqu1hT5QtPo2IRjFDx6NkN6Zw12XKf/CxGPdEU7lV106k8 HoSy2ZKlvvPSWKJXkvipqoitFBDKAcjuO+RBmdoaZOVCzER6Bgjym8zyIg6dDzbPxTyp LCSA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=BTnaGF/9xxGW5IGaSBvWawH/eKSkzgmbxFLTt0/O4I0=; b=hZJb/QX05Ff5C/R5+l6V9e5FkbKZp97pgTGXTJPn3W2VtkPVAjBue5uhOW5GJcYtER g5KrJPTCZqjA/mp3Gd5Ucj8V1MrGfQZE5w91yQJ2lyR33HawjOZJN8YaOVOQ+QmkiFIW fSVlnEBJ/DPAh5h1cLp9CsYDArpckOWH7S9q9mNuvGxg4ymsETDrFYfxuYdrVbYMmA9p VbbeigqIt7Zco2hQFyvZInwLko5tDXdEyqyCAc6hf5qEJkJ1HuhNm/C6MPNePMxSIdy+ KOv8q3o9Od08mtdZQ7AbesRVnOgPUhV7zCv1GzhaFb7jvCqzpMpG75jtFW+iE30iKAQx ZP7Q== X-Gm-Message-State: AIVw111v0Weg07bjgkwPAKWwlXToSTSKcYpp5q/Pi7W9v+l059KbOCpn BaEouAEEDeDsqywwFL9pRyIHxdgfjF9XeHU= X-Received: by 10.223.160.6 with SMTP id k6mr15735849wrk.220.1500942906891; Mon, 24 Jul 2017 17:35:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.141.178 with HTTP; Mon, 24 Jul 2017 17:34:46 -0700 (PDT) In-Reply-To: References: From: Philipp Moritz Date: Mon, 24 Jul 2017 17:34:46 -0700 Message-ID: Subject: Re: CI reliability? To: dev@arrow.apache.org Content-Type: multipart/alternative; boundary="94eb2c0677decb25eb05551980f0" --94eb2c0677decb25eb05551980f0 Content-Type: text/plain; charset="UTF-8" I'm really sorry for the inconvenience! This should fix one part of the problem and make the build times a lot more tolerable: https://github.com/ apache/arrow/pull/882 (we should still fix the recomputation problem) -- Philipp. On Mon, Jul 24, 2017 at 5:24 PM, Jacques Nadeau wrote: > Got it, thanks Wes. I haven't been working with travis for retriggering so > didn't know if there was something more elegant. > > On Mon, Jul 24, 2017 at 4:01 PM, Wes McKinney wrote: > > > That particular job is timing out because it's configured in a way > > that's causing various steps to be recomputed > > > > https://issues.apache.org/jira/browse/ARROW-1253 > > > > I plan to fix it as soon as I can get the package builds for 0.5.0 > > sorted out, maybe later tonight, but have already been working around > > the clock as it is. > > > > Generally the CI has been pretty reliable; occasionally we get a > > Homebrew timeout or some other flakiness that's related to Travis CI > > infrastructure. > > > > If you're concerned about whether you've broken a build I usually do > > git commit --amend to re-trigger the build. > > > > On Mon, Jul 24, 2017 at 6:15 PM, Jacques Nadeau > > wrote: > > > Hey All, > > > > > > I'm wondering how reliable the CI stuff has been. I just saw a ci job > > that > > > was terminated due to time limits. Is that a common occurrence? Is > there > > an > > > easy way to retrigger? > > > > > > https://travis-ci.org/apache/arrow/builds/257002967 > > > > > > thanks, > > > Jacques > > > --94eb2c0677decb25eb05551980f0--