From owner-freebsd-current@FreeBSD.ORG Sat Dec 20 21:43:53 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4A9DED0C; Sat, 20 Dec 2014 21:43:53 +0000 (UTC) Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1218326C1; Sat, 20 Dec 2014 21:43:53 +0000 (UTC) Received: by mail-pd0-f180.google.com with SMTP id w10so3398675pde.11; Sat, 20 Dec 2014 13:43:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=EpL1A5N27anyLlVMroIH2vsSlwKBbNOB/l/i5YLf8RQ=; b=tZ5gmrQpa/4IuMh0zEC9zm6F2TAbAvtQJAw2OT1/dpT0SSJFZHczXv4QItt2M/LB0c EMkjlt8o5xBru35j431GIAddpoQ97iAr2J3cldzB1tadiIlvqKxr0Y/ylQRlAvuMRb/d 0N3zSskwmfv9DhvWcd7bJ3q8AEasVS4Jks9QG07Mz3lAagI5/r/zy8ETdjHQuYEDSanh jDyWJPGlrGtuflbWZwQ7uwbAJcaWy1d2VtamVrs+PIZ3HgSTVOkuwaNk60Z6MCxWKeZN KEeVQ5B1MVLwjh79bB+O98BzOxGUFZZKyNhpY0gEe1+q4QZSgVN9AuBUA+7W6fCyxaxS QViw== X-Received: by 10.68.224.6 with SMTP id qy6mr23428107pbc.35.1419111832609; Sat, 20 Dec 2014 13:43:52 -0800 (PST) Received: from ?IPv6:2601:8:ab80:7d6:4806:5459:7892:3518? ([2601:8:ab80:7d6:4806:5459:7892:3518]) by mx.google.com with ESMTPSA id f12sm13333892pat.43.2014.12.20.13.43.51 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 20 Dec 2014 13:43:52 -0800 (PST) Content-Type: multipart/signed; boundary="Apple-Mail=_BB9AA672-700C-4A20-9A19-D3BDB9C9E734"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Build failed in Jenkins: Build-UFS-image #599 From: Garrett Cooper In-Reply-To: Date: Sat, 20 Dec 2014 13:43:50 -0800 Message-Id: References: <1052304530.8.1417827164793.JavaMail.jenkins@jenkins-9.freebsd.org> To: jenkins-admin@freebsd.org X-Mailer: Apple Mail (2.1878.6) Cc: FreeBSD CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Dec 2014 21:43:53 -0000 --Apple-Mail=_BB9AA672-700C-4A20-9A19-D3BDB9C9E734 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Dec 5, 2014, at 19:59, Garrett Cooper wrote: > On Dec 5, 2014, at 16:52, jenkins-admin@freebsd.org wrote: >=20 >> See >=20 > I=92m not entirely sure why the "could not determine = COMPILER_TYPE" error popped up, but I have a couple of = questions/concerns related to the makefile snippet. I looked at the error and the jenkins jobs a bit more and I think the = real problem is that the FreeBSD_Head job is being run in parallel with = the Build-UFS-image job, because the FreeBSD_Head job completes without = issue and the Build-UFS-image job is not being run with -j . I = know based on past experience if the tree is updated but not rebuilt = with -DNO_CLEAN and installkernel/installworld is being run, sporadic = build failures like this will occur, depending on whether or not = something needs to be [re]built. One way to deal with this issue is to svn up a source tree, then rsync = the checked out copy of the source tree to a unique memory disk, build = from there, and install to a unique location as well. Using the jenkins = job identifier should be enough=85 but I=92m not sure what the best way = with Jenkins is to do this, partly because I don=92t know what plugins = are installed on the Jenkins server. Thanks! --Apple-Mail=_BB9AA672-700C-4A20-9A19-D3BDB9C9E734 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJUle2WAAoJEMZr5QU6S73eAYkH/RQOfvvjCIhpW87MoVnIjcvw Wnu2SpwR8XxNM7VHujJfK91hbTs9c/a/9aDCLvKw0vmoo6HRZl8o5ep248g9xrVX L/d5AKnqf/1lUFwI7YQDvuwzCnPCJECA3VcH/NQ751loqH3roxpYoC60WFc/CFgg nZKtgqBwwh16vN1ZjDe5K7vK+7sYjhcc8xoJtwNCia6dbmYmWDrHtOJGT+Rlrg99 bT6bCHuM8LSgCUbfb7ntDQQx4sPaminmayoa9oem8/G4msGuUNSAUMPM+8zuuKxw 3ayyFRZToO6fLgVAZnsI8lljOzK+09u6MHBW3NlbLy+6PajuKXZuDXS568iXNTE= =K9d+ -----END PGP SIGNATURE----- --Apple-Mail=_BB9AA672-700C-4A20-9A19-D3BDB9C9E734--