Linux NFS development
 help / color / mirror / Atom feed
From: Calum Mackay <calum.mackay@oracle.com>
To: "Mkrtchyan, Tigran" <tigran.mkrtchyan@desy.de>,
	"J. Bruce Fields" <bfields@fieldses.org>
Cc: Calum Mackay <calum.mackay@oracle.com>,
	Jeff Layton <jlayton@kernel.org>, Dai Ngo <dai.ngo@oracle.com>,
	linux-nfs <linux-nfs@vger.kernel.org>,
	Frank Filz <ffilzlnx@mindspring.com>
Subject: Re: [pynfs RFC PATCH] nfs4.0/testserver.py: don't return an error when tests fail
Date: Sat, 25 Feb 2023 15:57:12 +0000	[thread overview]
Message-ID: <f7c1e360-9d93-c522-b24a-5aeecf9a17f0@oracle.com> (raw)
In-Reply-To: <436117750.41744935.1677325526601.JavaMail.zimbra@desy.de>


[-- Attachment #1.1: Type: text/plain, Size: 2658 bytes --]

On 25/02/2023 11:45 am, Mkrtchyan, Tigran wrote:
> 
> ----- Original Message -----
>> From: "J. Bruce Fields" <bfields@fieldses.org>
>> To: "Jeff Layton" <jlayton@kernel.org>
>> Cc: "Dai Ngo" <dai.ngo@oracle.com>, "linux-nfs" <linux-nfs@vger.kernel.org>, "Frank Filz" <ffilzlnx@mindspring.com>
>> Sent: Thursday, 23 February, 2023 16:11:32
>> Subject: Re: [pynfs RFC PATCH] nfs4.0/testserver.py: don't return an error when tests fail
> 
>> I orginally thought I'd continue maintaining pynfs on a volunteer basis,
>> but I haven't been.  These all look like reasonable changes, but someone
>> else probably needs to step in to make sure they're handled in a
>> reasonable amount of time.
>>
> 
> Well, I already have a fork in github that is used by others. Thus I can try to
> pick the patches from the mailing list and try to keep the tree up-to-date.

hi Tigran, I was going to take it over from Bruce, unless you'd prefer 
to, which is fine?

cheers,
calum.

> 
> Tigran.
>> --b.
>>
>> On Wed, Feb 22, 2023 at 08:49:52AM -0500, Jeff Layton wrote:
>>> This script was originally changed in eb3ba0b60055 ("Have testserver.py
>>> have non-zero exit code if any tests fail"), but the same change wasn't
>>> made to the 4.1 testserver.py script.
>>>
>>> There also wasn't much explanation for it, and it makes it difficult to
>>> tell whether the test harness itself failed, or whether there was a
>>> failure in a requested test.
>>>
>>> Stop the 4.0 testserver.py from exiting with an error code when a test
>>> fails, so that a successful return means only that the test harness
>>> itself worked, not that every requested test passed.
>>>
>>> Cc: Frank Filz <ffilzlnx@mindspring.com>
>>> Signed-off-by: Jeff Layton <jlayton@kernel.org>
>>> ---
>>>   nfs4.0/testserver.py | 2 --
>>>   1 file changed, 2 deletions(-)
>>>
>>> I'm not sure about this one. I've worked around this in kdevops for now,
>>> but it would really be preferable if it worked this way, imo. If this
>>> isn't acceptable, maybe we can add a new option that enables this
>>> behavior?
>>>
>>> Frank, what was the original rationale for eb3ba0b60055 ?
>>>
>>> diff --git a/nfs4.0/testserver.py b/nfs4.0/testserver.py
>>> index f2c41568e5c7..4f4286daa657 100755
>>> --- a/nfs4.0/testserver.py
>>> +++ b/nfs4.0/testserver.py
>>> @@ -387,8 +387,6 @@ def main():
>>>   
>>>       if nfail < 0:
>>>           sys.exit(3)
>>> -    if nfail > 0:
>>> -        sys.exit(2)
>>>   
>>>   if __name__ == "__main__":
>>>       main()
>>> --
>>> 2.39.2

-- 
Calum Mackay
Linux Kernel Engineering
Oracle Linux and Virtualisation

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2023-02-25 15:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22 13:49 [pynfs RFC PATCH] nfs4.0/testserver.py: don't return an error when tests fail Jeff Layton
2023-02-23 15:11 ` J. Bruce Fields
2023-02-25 11:45   ` Mkrtchyan, Tigran
2023-02-25 15:57     ` Calum Mackay [this message]
2023-02-26 19:25       ` Mkrtchyan, Tigran
2023-02-23 16:22 ` Frank Filz
2023-02-23 17:08   ` Jeff Layton
2023-02-23 19:38     ` Mkrtchyan, Tigran
2023-02-23 22:43       ` Frank Filz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f7c1e360-9d93-c522-b24a-5aeecf9a17f0@oracle.com \
    --to=calum.mackay@oracle.com \
    --cc=bfields@fieldses.org \
    --cc=dai.ngo@oracle.com \
    --cc=ffilzlnx@mindspring.com \
    --cc=jlayton@kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=tigran.mkrtchyan@desy.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox