public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] [RFC] lib/tst_test: Report 0 if test has both TPASS	and TCONF
Date: Fri, 8 Sep 2017 03:21:29 -0400 (EDT)	[thread overview]
Message-ID: <1529683625.10671733.1504855289141.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20170907155745.9116-1-chrubis@suse.cz>



----- Original Message -----
> It's probably a bit more logical to report a succes if only part of the
> test was skipped and the rest was sucessful. That way we can distinguish
> tests that were compiled-out completely or where the kernel does not
> support the particular syscall at all. The difference is about 15
> testcases that report TPASS instead of TCONF after this change.

Looks good to me. I've noticed more TCONFs too with your all_filesystems patch,
where some filesystems didn't support all features.

Regards,
Jan

  reply	other threads:[~2017-09-08  7:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-07 15:57 [LTP] [PATCH] [RFC] lib/tst_test: Report 0 if test has both TPASS and TCONF Cyril Hrubis
2017-09-08  7:21 ` Jan Stancek [this message]
2017-09-08  8:55   ` Cyril Hrubis

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=1529683625.10671733.1504855289141.JavaMail.zimbra@redhat.com \
    --to=jstancek@redhat.com \
    --cc=ltp@lists.linux.it \
    /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