From owner-freebsd-current@FreeBSD.ORG Sat Feb 21 23:38:08 2015 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 1C3E7DE7; Sat, 21 Feb 2015 23:38:08 +0000 (UTC) Received: from mail-pa0-x231.google.com (mail-pa0-x231.google.com [IPv6:2607:f8b0:400e:c03::231]) (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 D21468DA; Sat, 21 Feb 2015 23:38:07 +0000 (UTC) Received: by pablf10 with SMTP id lf10so17510277pab.12; Sat, 21 Feb 2015 15:38:07 -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=rqcCiESoG++e7g1zQCh/8e5K0E5hAZoKenFFPjZjkBw=; b=UzNDz9jtDT7IaKVbyXMV0yQygbulwIfbOYiGVPpmztel+rEaMlq1z5mnDfVGOqtueZ AY1wXD7HVjTZy5vPxQAqPCwx188PrCODM9NTqpsfUhZHlsxTPzYzjnmATQepyOhZPNyk RxfiwVVY3xY2Hr2JYlSiTN0P0RM0HgTnnBN3xdV0YCDGsuuqEpjTK4wtRYMQAZfCvRjD nEyH9pi0Ygzb+vJY4Jm92TCmWtWDnqSgSkP2IIYKNnotHg8PSkqzhinlaKk3jZKXsL/4 3peerflqYTjVmX/oDr8modNuyIE9yHrjhKZAhR3E8gl+sFqbETwP6DOqS6DlhXuPdRiG jdLg== X-Received: by 10.68.224.71 with SMTP id ra7mr7484214pbc.140.1424561887353; Sat, 21 Feb 2015 15:38:07 -0800 (PST) Received: from ?IPv6:2601:8:ab80:7d6:d80e:6c7b:d84f:93d? ([2601:8:ab80:7d6:d80e:6c7b:d84f:93d]) by mx.google.com with ESMTPSA id br14sm2841340pdb.38.2015.02.21.15.38.06 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 21 Feb 2015 15:38:06 -0800 (PST) Content-Type: multipart/signed; boundary="Apple-Mail=_BE468487-3CBF-41D5-B924-4152D4CA65AA"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Jenkins build is still unstable: FreeBSD_HEAD-tests2 #740 From: Garrett Cooper In-Reply-To: Date: Sat, 21 Feb 2015 15:38:06 -0800 Message-Id: <89762484-E5C4-4F6D-BC3E-738AF62E3213@gmail.com> References: <410884488.27.1424507811409.JavaMail.jenkins@jenkins-9.freebsd.org> <216426652.28.1424539953124.JavaMail.jenkins@jenkins-9.freebsd.org> <57581809-C918-4490-8A63-D96CEF96AFE9@gmail.com> To: James Gritton X-Mailer: Apple Mail (2.1878.6) Cc: FreeBSD CURRENT , jenkins-admin@freebsd.org 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, 21 Feb 2015 23:38:08 -0000 --Apple-Mail=_BE468487-3CBF-41D5-B924-4152D4CA65AA Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Feb 21, 2015, at 15:35, James Gritton wrote: > On 2015-02-21 16:23, Garrett Cooper wrote: >> On Feb 21, 2015, at 9:32, jenkins-admin@freebsd.org wrote: >>> See >> Jamie, >> For some odd reason the last couple of commits you did to = jail(8) rocked the boat again with the pgrep/pkill -j testcases. I=92ll = look into making them work again, but could you please send patches out = to CR so I can look at them and test them first. I hate the slew of = Jenkins failures emails and I=92m sure there are others who feel the = same. >> Thanks! >=20 > I'm as much at a loss as I was before, on how the changes I made could = have any impact at all. The two recent commits to jls(8) (didn't touch = jail(8)) only matter if you use jls's -v or -s options, neither of which = is used in the pkill test case. >=20 > As with the previous cycle of failures regarding jail(8), the problems = appears not to be the changes I made, but that mere fact that something = was committed to those programs. >=20 > - Jamie Not disguising stderr, here=92s what pops up: $ sudo prove -v pgrep-j_test.sh=20 pgrep-j_test.sh ..=20 1..3 jls: unknown parameter: allow jls: unknown parameter: allow jls: unknown parameter: allow jls: unknown parameter: allow jls: unknown parameter: allow jls: unknown parameter: allow jls: unknown parameter: allow jls: unknown parameter: allow jls: unknown parameter: allow jls: unknown parameter: allow jls: unknown parameter: allow jls: unknown parameter: allow jls: unknown parameter: allow jls: unknown parameter: allow jls: unknown parameter: allow jls: unknown parameter: allow jls: unknown parameter: allow jls: unknown parameter: allow jls: unknown parameter: allow jls: unknown parameter: allow usage: pgrep [-LSfilnoqvx] [-d delim] [-F pidfile] [-G gid] [-M core] = [-N system] [-P ppid] [-U uid] [-c class] [-g pgrp] [-j jid] [-s sid] [-t tty] [-u euid] pattern ... not ok 1 - pgrep -j # pgrep output: '', pidfile output: '3704 = 3706' ok 2 - pgrep -j any --Apple-Mail=_BE468487-3CBF-41D5-B924-4152D4CA65AA 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 iQEcBAEBCgAGBQJU6RbeAAoJEMZr5QU6S73ej9gIAKQdsVFEno6wWOB6KLY348Ck OcLwG79ShG3nHP8IhK+EFlXNzy7RORyMNwFEHd2Ih+TYnzvxlx6WgHeJinH56Jpt xJA26f08FZ0jndktC4KqsBDmUx4/sMac/BMJ3fDZa1EBLM1+pMYS3KgSVLybHiUR bVuTlWwBxZHUmBkuGJSU9v2UIO2zZOTtUpNyKy4urf3riQQJDoakK+RvvwO+cN0z fMoQyaXs10Dt5xb73lD0zfebJlddjOzpIQrQfAgKMWSTmTFKwrGBlZj44NogLbKk s5bBAuq8mGthocayrNUC2vwp2oTUmo/PJe9U+eUci+GSelZFUnqS2PPOM+SvD34= =G/et -----END PGP SIGNATURE----- --Apple-Mail=_BE468487-3CBF-41D5-B924-4152D4CA65AA--