Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 28 May 2015 18:15:26 +0000 (GMT)
From:      jenkins-admin@freebsd.org
To:        jenkins-admin@FreeBSD.org, freebsd-current@freebsd.org
Subject:   FreeBSD_HEAD-tests - Build #1065 - Still Unstable
Message-ID:  <727303121.7.1432836926389.JavaMail.jenkins@jenkins-9.freebsd.org>
In-Reply-To: <99519814.4.1432807155540.JavaMail.jenkins@jenkins-9.freebsd.org>
References:  <99519814.4.1432807155540.JavaMail.jenkins@jenkins-9.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
FreeBSD_HEAD-tests - Build #1065 - Still Unstable:

Check console output at https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests/1065/ to view the results.
From owner-freebsd-current@FreeBSD.ORG  Thu May 28 19:09:38 2015
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@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 C4834A1;
 Thu, 28 May 2015 19:09:38 +0000 (UTC)
 (envelope-from crodr001@gmail.com)
Received: from mail-la0-x229.google.com (mail-la0-x229.google.com
 [IPv6:2a00:1450:4010:c03::229])
 (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 4A034300;
 Thu, 28 May 2015 19:09:38 +0000 (UTC)
 (envelope-from crodr001@gmail.com)
Received: by laat2 with SMTP id t2so39481136laa.1;
 Thu, 28 May 2015 12:09:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:in-reply-to:references:date:message-id:subject
 :from:to:cc:content-type;
 bh=lfgaETHRDUlGk7iJHRLtfQmLBcIxuOBMZAxUUoSPC0I=;
 b=G382AxFwbcmPbVlKC5twSG5BhvB2iOMpymMxGxOZd/GADtjzoSYE3z07qU6O60Qij4
 LnpmpMGcUB0mNktVFzkagvWEnFsBhvNFoDjMe2w7PPOkZmGtYvOTEeqzUZmibtwNWkT6
 sWNOK3BxlfK4AFE0e/Yl4YzOSixyNhO17kcdg7PMF6W55usuHE0WfThqgbs0wp9KMReR
 k9O8Ru++KCXsA4vTHX3dMjNLucxK48LZIlE0mUcM/lTPQ4iThfoGaEWN6TQ1vToaeVPS
 34atXDL5S3ldXnNP8roEawPzo1e+5hwPwFKr45JmrF6BB8A5pyQT4BF6p2Z0AN5NNG07
 M7UQ==
MIME-Version: 1.0
X-Received: by 10.152.22.34 with SMTP id a2mr4355108laf.59.1432840175848; Thu,
 28 May 2015 12:09:35 -0700 (PDT)
Sender: crodr001@gmail.com
Received: by 10.112.164.38 with HTTP; Thu, 28 May 2015 12:09:35 -0700 (PDT)
In-Reply-To: <55670C5A.6080500@FreeBSD.org>
References: <CAG=rPVdLjmj8oOeqQQOLr6ShvU=2H3y0j5hg4q8UrB70rj3Xpg@mail.gmail.com>
 <55670C5A.6080500@FreeBSD.org>
Date: Thu, 28 May 2015 12:09:35 -0700
X-Google-Sender-Auth: b3LYPLe1GB-7AstPi3l37TQJVZU
Message-ID: <CAG=rPVcfs4LB36L8ToOFkVad5t=CWb6wSOog=SfWT-8t-7tDwg@mail.gmail.com>
Subject: Re: Need help reducing compilation warnings in CURRENT
From: Craig Rodrigues <rodrigc@FreeBSD.org>
To: Johannes Jost Meixner <xmj@freebsd.org>
Cc: freebsd-current Current <freebsd-current@freebsd.org>, 
 "freebsd-testing@freebsd.org" <freebsd-testing@freebsd.org>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.20
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>;
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 28 May 2015 19:09:39 -0000

On Thu, May 28, 2015 at 5:38 AM, Johannes Jost Meixner <xmj@freebsd.org>
wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Hi Craig,
>
> I'll gladly help (good excuse to learn C), but looking at those errors
> in general, one thing pops out:
>
> The warnings are almost all in contrib/ areas. Hence, any fix might
> want to probably be submitted to upstream first.
>


Sure, if we can push fixes upstream that would be great.
However, we shouldn't let that block us from comitting fixes to FreeBSD.
The advantage of having code in the FreeBSD repo is that we can
change it if we need to, even if the fix isn't yet in the upstream sources.
Contrib code is not made out of stone that can't be modified!

--
Craig



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?727303121.7.1432836926389.JavaMail.jenkins>