mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: Shuah Khan <shuah.kh@samsung.com>,
	Tom Zanussi <tom.zanussi@linux.intel.com>,
	Oleg Nesterov <oleg@redhat.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Fengguang Wu <fengguang.wu@intel.com>,
	Ingo Molnar <mingo@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: (ltc-kernel 10162) Re: [PATCH ftrace/for-next v6] ftracetest: Add POSIX.3 standard and XFAIL result codes
Date: Fri, 3 Oct 2014 16:53:37 -0400	[thread overview]
Message-ID: <20141003165337.21043dee@gandalf.local.home> (raw)
In-Reply-To: <542E8888.9090703@hitachi.com>

On Fri, 03 Oct 2014 20:29:12 +0900
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com> wrote:

> Ping? :)

Just to make sure. This is just the one patch that I missed before,
right?

I pulled it and now testing it (running the tests). I'll push it to my
linux-next branch sometime later today. You'll probably see it as you
wake up ;-)

-- Steve

> 
> (2014/09/29 21:11), Masami Hiramatsu wrote:
> > Steven, could you pick this instead of old v5 patch?
> > 
> > As you pointed, this version shows the log of "unsuppoted" test result.
> > 
> > Thank you,
> > 
> > (2014/09/29 21:02), Masami Hiramatsu wrote:
> >> Add XFAIL and POSIX 1003.3 standard codes (UNRESOLVED/
> >> UNTESTED/UNSUPPORTED) as result codes. These are used for the
> >> results that test case is expected to fail or unsupported
> >> feature (by config).
> >>
> >> To return these result code, this introduces exit_unresolved,
> >> exit_untested, exit_unsupported and exit_xfail functions,
> >> which use real-time signals to notify the result code to
> >> ftracetest.
> >>
> >> This also set "errexit" option for the testcases, so that
> >> the tests don't need to exit explicitly.
> >>
> >> Note that if the test returns UNRESOLVED/UNSUPPORTED/FAIL,
> >> its test log including executed commands is shown on console
> >> and main logfile as below.

  parent reply	other threads:[~2014-10-03 20:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-29 12:02 Masami Hiramatsu
2014-09-29 12:11 ` Masami Hiramatsu
2014-10-03 11:29   ` (ltc-kernel 10162) " Masami Hiramatsu
2014-10-03 12:14     ` Steven Rostedt
2014-10-03 20:53     ` Steven Rostedt [this message]
2014-10-05  2:08       ` Masami Hiramatsu

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=20141003165337.21043dee@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=fengguang.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=oleg@redhat.com \
    --cc=shuah.kh@samsung.com \
    --cc=tom.zanussi@linux.intel.com \
    /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

all inboxes | Powered by JetHome®