All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad@kernel.org>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: xen-devel@lists.xenproject.org, Marcos.Matsunaga@oracle.com
Subject: Re: [PATCH v1 5/7] ts-livepatch: Initial test-cases.
Date: Mon, 21 Nov 2016 17:47:01 -0500	[thread overview]
Message-ID: <20161121224700.GB126025@osstest.dumpdata.com> (raw)
In-Reply-To: <22573.41190.373074.369457@mariner.uk.xensource.com>

On Thu, Nov 17, 2016 at 12:21:58PM +0000, Ian Jackson wrote:
> Konrad Rzeszutek Wilk writes ("[PATCH v1 5/7] ts-livepatch: Initial test-cases."):
> > There are 32 test-cases in there. Before we run
> > any of them we verify that the payload files are present
> > in /usr/lib/debug.
> > 
> > If so we go through all of the test-cases.

Thank you!

Let me answer only to some as I am fixing the rest per your comments:
> 
> Is it ever possible to continue with the rest of the livepatch tests
> after one of these command invocations has failed, or does it leave
> the system in an undefined state ?  If it _is_ possible then it would

If the invocations have failed that could mean: 
 - We don't have livepatching enabled (somebody swapped the hypervisor?)
 - The livepatching did not work right and we have code in the
   hypervisor that patched something else. Undefined results.
 - It may be that the test-case failed to load due to dependencies
   issues - and while that means the system can recover - the test
   should fail immediately.

> be possible to provide per-step results to osstest, but that's only
> valuable if this would tell us something meaningfully interesting in
> terms of regressions - eg if we might tolerate a regression of one
> step but still care about the others.

At this stage I believe all of these test-cases should work. If they
don't we got big problems.
..
> > +	{cmd => "xen-livepatch revert xen_hello_world", rc => 256},
> 
> libxl exit statuses are not very good and should not be relied on,
> really.  Instead, you should arrange to:

But this is not libxl. The error values are very much defined
by xen-livepatch.

>   * Run the command with LC_MESSAGES=C

Aye.
>   * Fail the test if the exit status is zero

But some of the test-cases are suppose to return 0 - as the program
executed correctly.

>   * Collect its stderr output (by appending 2>&1)
>   * Match the stderr output against a regexp in the perl program

Right.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2016-11-21 19:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-17  1:37 [PATCH v1] OSSTest test-harness for livepatches Konrad Rzeszutek Wilk
2016-11-17  1:37 ` [PATCH v1 1/7] ts-xen-build: Enable livepatch Konrad Rzeszutek Wilk
2016-11-17 11:45   ` Ian Jackson
2016-11-17  1:37 ` [PATCH v1 2/7] ts-xen-build: Build the livepatch test-cases Konrad Rzeszutek Wilk
2016-11-17 11:49   ` [PATCH v1 3/7] ts-xen-build: Install livepatch regressions tests. [and 1 more messages] Ian Jackson
2016-11-21 21:28     ` Konrad Rzeszutek Wilk
2016-12-12 16:12       ` Ian Jackson
2016-11-17  1:37 ` [PATCH v1 3/7] ts-xen-build: Install livepatch regressions tests Konrad Rzeszutek Wilk
2016-11-17  1:37 ` [PATCH v1 4/7] OssTest: Add target_cmd_root_rc which returns return code Konrad Rzeszutek Wilk
2016-11-17 11:53   ` Ian Jackson
2016-11-17  1:37 ` [PATCH v1 5/7] ts-livepatch: Initial test-cases Konrad Rzeszutek Wilk
2016-11-17 12:21   ` Ian Jackson
2016-11-21 22:47     ` Konrad Rzeszutek Wilk [this message]
2016-12-12 16:17       ` Ian Jackson
2016-11-17  1:37 ` [PATCH v1 6/7] sg-run-job: Add the test-livepatch Konrad Rzeszutek Wilk
2016-11-17 12:23   ` Ian Jackson
2016-11-17  1:37 ` [PATCH v1 7/7] make-flight/mfi-common: Add them in the matrix Konrad Rzeszutek Wilk
2016-11-17 12:24   ` Ian Jackson
2016-12-12 19:01     ` Konrad Rzeszutek Wilk
2016-12-12 16:19       ` Ian Jackson
2016-11-17 12:28 ` [PATCH v1] OSSTest test-harness for livepatches Ian Jackson

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=20161121224700.GB126025@osstest.dumpdata.com \
    --to=konrad@kernel.org \
    --cc=Marcos.Matsunaga@oracle.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.