From owner-freebsd-current@FreeBSD.ORG Sat Feb 21 23:43:22 2015 Return-Path: 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 A2FC41DA; Sat, 21 Feb 2015 23:43:22 +0000 (UTC) Received: from mail-pd0-x231.google.com (mail-pd0-x231.google.com [IPv6:2607:f8b0:400e:c02::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 6400699A; Sat, 21 Feb 2015 23:43:22 +0000 (UTC) Received: by pdno5 with SMTP id o5so16300140pdn.8; Sat, 21 Feb 2015 15:43:21 -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=RvEuh/juG+MkdDJ5z0vc04stVIHiGvg2wh85oq+/vrY=; b=YuLHK0PLnEwMiGyZjzg/QQygiMxfhGYEVw0WYxZBtVz+3S8YUJZRkQfq+FmwF6ABbr efX+LlYykLpxFJ6g9NoQh6ZrrQeIAcYBc6JRaaK2ljqw59jRGQTFNbNm6oh1M5XWMFp0 888o2dY3R+ydQWWRf/CNkXrvdlV5x68dbAW2ZBt14trnW+qEao3wd3rlPJX5aqvyrwRi CVfzUnFo4YY5IIebSO0wJq7ZTTY6/DqCPiFnx4CDZn4tL4JJwWeS+6+iWPSuJVCNHNWZ jjUi87/wocAQ7rbSV23J2WZP/gQgRNTZsNohtw/wzmgVVe/yyb1JeFlFEZHYd1c+JA4F dAxg== X-Received: by 10.66.63.106 with SMTP id f10mr7707266pas.0.1424562201795; Sat, 21 Feb 2015 15:43:21 -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 d11sm30118338pbu.10.2015.02.21.15.43.20 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 21 Feb 2015 15:43:20 -0800 (PST) Content-Type: multipart/signed; boundary="Apple-Mail=_1B61C18B-01A2-4966-BAAF-F1CE224EA7CA"; 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: <89762484-E5C4-4F6D-BC3E-738AF62E3213@gmail.com> Date: Sat, 21 Feb 2015 15:43:19 -0800 Message-Id: <86D827FB-E97F-46B3-82E2-DF0DCE80DB22@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> <89762484-E5C4-4F6D-BC3E-738AF62E3213@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:43:22 -0000 --Apple-Mail=_1B61C18B-01A2-4966-BAAF-F1CE224EA7CA Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Feb 21, 2015, at 15:38, Garrett Cooper wrote: > On Feb 21, 2015, at 15:35, James Gritton wrote: >=20 >> 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 >=20 > Not disguising stderr, here=92s what pops up: >=20 > $ 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 You broke parsing dotted parameters in r279083. Thanks, --Apple-Mail=_1B61C18B-01A2-4966-BAAF-F1CE224EA7CA 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 iQEcBAEBCgAGBQJU6RgYAAoJEMZr5QU6S73eOYIH+gIUc4EUdh4f5/rue7ijTwhR 0ZmiaV6eog8m9qepSHHUYUTadR307Czr+9+1zmLTOVckWHAi4h9MxfWe9h7YAasI iOpoVhjywcGc6PtJHvAKETEbZEQF8p5UWvwu91usnkBfU0s1J9iuNUEJEPKlW/lV SjE+7WNKw4mVNZ4TxMsMw3hmOFy8Ypae8luL5hMRTrGUawre6k38Vn9lnsLS8qXd NOGAibZNucN8vNj5CB63jcjSvJEzd6FQoFckGN+hlnLwf3wx2l+gVkkfEG0TbjuR Dhx9j1/7KXs+LniLsPSj4OtqpnKDfhBgJDH3lLZatt1CV9Z5sLVoqioVL+PWtzw= =7161 -----END PGP SIGNATURE----- --Apple-Mail=_1B61C18B-01A2-4966-BAAF-F1CE224EA7CA--