Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 21 Feb 2015 15:43:19 -0800
From:      Garrett Cooper <yaneurabeya@gmail.com>
To:        James Gritton <jamie@freebsd.org>
Cc:        FreeBSD CURRENT <freebsd-current@freebsd.org>, jenkins-admin@freebsd.org
Subject:   Re: Jenkins build is still unstable: FreeBSD_HEAD-tests2 #740
Message-ID:  <86D827FB-E97F-46B3-82E2-DF0DCE80DB22@gmail.com>
In-Reply-To: <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> <F6F699AF-1572-446E-940A-0915CC352649@gmail.com> <57581809-C918-4490-8A63-D96CEF96AFE9@gmail.com> <d3a5656fa8c344da43c986ce85c83c15@gritton.org> <89762484-E5C4-4F6D-BC3E-738AF62E3213@gmail.com>

index | next in thread | previous in thread | raw e-mail

[-- Attachment #1 --]
On Feb 21, 2015, at 15:38, Garrett Cooper <yaneurabeya@gmail.com> wrote:

> On Feb 21, 2015, at 15:35, James Gritton <jamie@freebsd.org> wrote:
> 
>> On 2015-02-21 16:23, Garrett Cooper wrote:
>>> On Feb 21, 2015, at 9:32, jenkins-admin@freebsd.org wrote:
>>>> See <https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests2/740/>;
>>> 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’ll 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’m sure there are others who feel the same.
>>> Thanks!
>> 
>> 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.
>> 
>> 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.
>> 
>> - Jamie
> 
> Not disguising stderr, here’s what pops up:
> 
> $ sudo prove -v pgrep-j_test.sh 
> pgrep-j_test.sh .. 
> 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 <jid> # pgrep output: '', pidfile output: '3704 3706'
> ok 2 - pgrep -j any

You broke parsing dotted parameters in r279083.
Thanks,


[-- Attachment #2 --]
-----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-----
help

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86D827FB-E97F-46B3-82E2-DF0DCE80DB22>