From owner-freebsd-testing@FreeBSD.ORG Thu Jun 11 21:09:23 2015 Return-Path: Delivered-To: freebsd-testing@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4D387F3A; Thu, 11 Jun 2015 21:09:23 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-qc0-x243.google.com (mail-qc0-x243.google.com [IPv6:2607:f8b0:400d:c01::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0C008199E; Thu, 11 Jun 2015 21:09:23 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by qcvp6 with SMTP id p6so2303034qcv.2; Thu, 11 Jun 2015 14:09:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=t5LHqbQBtfszVb4t9SHHdjG74TQrBfEifuCcKOuvBMc=; b=IXartAjsDRJEXdoPoKyUrZq6q1Cp0+fBsvRs3gg5wHaTnm+UwuikIYChS3XPGgo4AD Svc6kW53Ocr7w6ikbINiNzqnsmjtAv8dqz8qOzfquTe4H2pnYWQGBfx6OWv30OxW96g1 2IvQnITOoGjzJpvYRDcP3d7TBY1B9/rBJZHvdk7XMXSZOA0RYY+XEP7KSIAZEeVK/Vpq 94AG46Q/w4efAJ6Qszcrtqz0GHmBTgLce3sX/EJsUb+ZCHclYVcEj6JhThrucaiTNFKW XV85OjHzouU+JPbieJc82YwCys8QAL+thHC61ZnpoRfyRJKWn91/7SKGrvOG0mhvElcQ fNbg== MIME-Version: 1.0 X-Received: by 10.140.232.131 with SMTP id d125mr15006385qhc.80.1434056962262; Thu, 11 Jun 2015 14:09:22 -0700 (PDT) Received: by 10.140.98.73 with HTTP; Thu, 11 Jun 2015 14:09:22 -0700 (PDT) In-Reply-To: <5579F646.7060604@FreeBSD.org> References: <5579F646.7060604@FreeBSD.org> Date: Thu, 11 Jun 2015 14:09:22 -0700 Message-ID: Subject: Re: Some feedback on the jenkins builds From: NGie Cooper To: Pedro Giffuni Cc: freebsd-testing Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jun 2015 21:09:23 -0000 On Thu, Jun 11, 2015 at 1:57 PM, Pedro Giffuni wrote: > Hi guys; > > Just thought some feedback would be useful: > > 1) It's great to have those summaries on the warnings produced > by clang and gcc. Can we also have those for the different > platforms? It is likely that i386 may show some warnings that > don't happen in amd64. Do you mean gcc 4.9 with i386..? > 2) Perhaps we can save some resources by concatenating the builds: > If there is a failure in amd64, we should not spend time attempting to > build i386 or the other platforms. If the builds for one architecture were sufficiently fast (amd64 or i386), then we could have it build other architectures as part of a downstream build (that way builds would trigger not off svn commits, but instead off build pass/fails). > 3) The clang static checker seems to not be uploading the results. > The main page throws an nginx message and the last result appears > to be from 2015-05-04. I guess there is some ongoing work to start > using the plugin though. > > Again, huge thanks for this great work, it does help! Indeed. A lot of thanks to jenkins-admin and all the hard work they've done here and continue to do here :). -NGie