From: Wei Liu <wei.liu2@citrix.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Wei Liu <wei.liu2@citrix.com>
Subject: Re: [OSSTEST PATCH RFC v2 11/14] Introduce ts-xtf-run
Date: Tue, 9 Aug 2016 09:11:02 +0100 [thread overview]
Message-ID: <20160809081102.GA19873@citrix.com> (raw)
In-Reply-To: <22440.40275.903579.381477@mariner.uk.xensource.com>
On Mon, Aug 08, 2016 at 03:55:15PM +0100, Ian Jackson wrote:
> Wei Liu writes ("[OSSTEST PATCH RFC v2 11/14] Introduce ts-xtf-run"):
> > This is the main script for running XTF. It will first perform
> > selftest, and then run each XTF test case as a substep.
> ...
> > +# XTF results (runner returned numeric values) and OSStest results:
> > +#
> > +# SUCCESS(0) -> pass
> > +# SKIP(3) -> skip
> > +# ERROR(4) -> fail
> > +# FAILURE(5) -> fail
> > +#
> > +sub xtf_result_to_osstest_result ($) {
> > + my ($xret) = @_;
> > +
> > + return "pass" if $xret == 0;
> > + return "skip" if $xret == 3;
> > + return "fail" if $xret == 4;
> > + return "fail" if $xret == 5;
> > + die "xtf runner gave unexpected result $xret";
>
> Wouldn't it be nicer to delete the separate comment and write
>
> + return "pass" if $xret == 0; # XTF SUCCESS
>
> etc. ?
>
> > + if (! eval {
> ^
> This space is anomalous coding style.
>
>
> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
Fixed both issues and added your ack. Thanks.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-08-09 8:11 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 9:22 [OSSTEST PATCH RFC v2 00/14] Integrate XTF into OSSTest Wei Liu
2016-08-08 9:22 ` [OSSTEST PATCH RFC v2 01/14] ts-xen-build: always compile in FEP support Wei Liu
2016-08-08 14:46 ` Ian Jackson
2016-08-08 9:22 ` [OSSTEST PATCH RFC v2 02/14] DO NOT APPLY ts-leak-check: sleep 5 seconds before collecting stuff Wei Liu
2016-08-08 9:22 ` [OSSTEST PATCH RFC v2 03/14] ap-common: add xtf tree Wei Liu
2016-08-08 14:46 ` Ian Jackson
2016-08-08 9:22 ` [OSSTEST PATCH RFC v2 04/14] DO NOT APPLY point xtf to my personal tree Wei Liu
2016-08-08 9:22 ` [OSSTEST PATCH RFC v2 05/14] BuildSupport: move buildcmd_stamped_logged here Wei Liu
2016-08-08 14:47 ` Ian Jackson
2016-08-08 9:22 ` [OSSTEST PATCH RFC v2 06/14] Introduce ts-xtf-build Wei Liu
2016-08-08 14:48 ` Ian Jackson
2016-08-08 9:22 ` [OSSTEST PATCH RFC v2 07/14] sg-run-job: create xtf build recipe Wei Liu
2016-08-08 9:22 ` [OSSTEST PATCH RFC v2 08/14] Introduce ts-xtf-install Wei Liu
2016-08-08 14:49 ` Ian Jackson
2016-08-08 9:22 ` [OSSTEST PATCH RFC v2 09/14] mfi-common: create xtf build job for 4.8 onwards Wei Liu
2016-08-08 14:51 ` Ian Jackson
2016-08-08 16:21 ` Wei Liu
2016-08-08 16:26 ` Andrew Cooper
2016-08-08 16:58 ` Wei Liu
2016-08-08 9:22 ` [OSSTEST PATCH RFC v2 10/14] Introduce ts-xtf-fep Wei Liu
2016-08-08 14:52 ` Ian Jackson
2016-08-08 9:22 ` [OSSTEST PATCH RFC v2 11/14] Introduce ts-xtf-run Wei Liu
2016-08-08 14:55 ` Ian Jackson
2016-08-09 8:11 ` Wei Liu [this message]
2016-08-08 16:29 ` Andrew Cooper
2016-08-08 16:56 ` Ian Jackson
2016-08-08 9:22 ` [OSSTEST PATCH RFC v2 12/14] sg-run-job: test-xtf recipe Wei Liu
2016-08-08 14:56 ` Ian Jackson
2016-08-08 9:22 ` [OSSTEST PATCH RFC v2 13/14] make-flight: create 5 xtf jobs Wei Liu
2016-08-08 14:56 ` Ian Jackson
2016-08-08 9:22 ` [OSSTEST PATCH RFC v2 14/14] Create XTF branch Wei Liu
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=20160809081102.GA19873@citrix.com \
--to=wei.liu2@citrix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).