Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-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 A708818DAC for ; Wed, 28 Oct 2015 03:48:21 +0000 (UTC) Received: (qmail 11318 invoked by uid 500); 28 Oct 2015 03:48:21 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 11227 invoked by uid 500); 28 Oct 2015 03:48:20 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 11209 invoked by uid 99); 28 Oct 2015 03:48:20 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Oct 2015 03:48:20 +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 366DEC138E for ; Wed, 28 Oct 2015 03:48:20 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.021 X-Spam-Level: X-Spam-Status: No, score=-0.021 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=cloudera_com.20150623.gappssmtp.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id S1CUXbFBA7aY for ; Wed, 28 Oct 2015 03:48:19 +0000 (UTC) Received: from mail-lf0-f50.google.com (mail-lf0-f50.google.com [209.85.215.50]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id D09052095A for ; Wed, 28 Oct 2015 03:48:18 +0000 (UTC) Received: by lfbn126 with SMTP id n126so146566367lfb.2 for ; Tue, 27 Oct 2015 20:48:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudera_com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to:content-type; bh=oX2n2yhq6ym9oLcRXSi3ij9rWmXiDOen6YqXPIgfeFI=; b=ZFRRx28zPwKA+tcQ1jhWoKaUb5yUCxyuawrEV2IqX7o4YUfLBhR6NTJs6zTwDnfit+ q5Mb7hMLBVJN8Nvwd8WGntDWIRzaCd0tOTKdsC91eKf+5CadOrnYAtoUOa799uJCy4tz tKK7mBwKU/vvqtxwapTHyjVWF3NGbstmAw88hWhbJ/LWc96GHonbH0eYErGuqk/M0n9q sQ7DimMnyIoEco32PJDi1QCls+WxWlSN6rhK4Kgps3hgtfYSyU/FY4HBlKuJ+89nGGHw fjMjWMCRl+wwJUveg3wmAG5BEocT72twK9RdKPvNNFho+CLNEv4rVQLVcVv45IHodEKx 9glQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=oX2n2yhq6ym9oLcRXSi3ij9rWmXiDOen6YqXPIgfeFI=; b=ji9Vvzz+JIOOpfjtL6cELtSmJ32uaRnQavdTOX9Hvesx8UuNixI82J35nzgjRTPF8/ FCUAJmTiEEUrItBzjC+SS7MJJjtq2+MZ6vffQVvCfim/La6o7iA7WNg2a41gkuzlK+DK L1pSWEeYuQJw7EYvUk2uGD1StOKQ8ummgk2j75xvHtJee/tKs6P5dVLnZOnT7ivzC8QC j7DWSIe5LihBJPbnnXdUPN8YKnaJsLiB/CRNrOCsptaU8IFqiZLK+Q6US+gqmFHv+QSb Ci0r5tbLoC1bWV8h77YiTFhjqDcQYaqxJm52m4ciZEgb21TfkaPhDMukP+qlT+kJ+TWQ kUDw== X-Gm-Message-State: ALoCoQnJ2ykKWsn5vRFD/VJ/JJ1BsPN5FZarO22XSA5khWJtn01k4Wmp3UbhrGQI1qJ+JdnM1m1U X-Received: by 10.25.15.83 with SMTP id e80mr14552983lfi.34.1446004098270; Tue, 27 Oct 2015 20:48:18 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.138.9 with HTTP; Tue, 27 Oct 2015 20:47:58 -0700 (PDT) From: Sean Busbey Date: Tue, 27 Oct 2015 22:47:58 -0500 Message-ID: Subject: [DISCUSS] reducing our load on builds.a.o To: dev Content-Type: text/plain; charset=UTF-8 Heya Folks, Right now our post-commit unit tests for our various branches take 1-2 hours to run per config (that's 6x0.94, 4x0.98, 1.0, 1.1, 2x1.2, 2x1.3, master) https://builds.apache.org/view/H-L/view/HBase/ These only run when a change happens in the given branch, and currently only get checked once an hour for changes. It looks like for 1+ we're averaging something like every 4 hours. If folks don't mind, I'd like to tune these down to look for changes less frequently. I'm thinking once a day for pre-1.0, every 8 hours for released versions in the 1.x major line, and every 4 for unreleased 1.x and 2.x versions. Thoughts? Anyone think we could tune down even more? -- Sean