From: Ian Jackson <ian.jackson@eu.citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Wei Liu <wei.liu2@citrix.com>
Subject: Re: [PATCH XTF 3/3] xtf-runner: regularise runner exit code
Date: Mon, 25 Jul 2016 18:05:21 +0100 [thread overview]
Message-ID: <22422.18129.501438.934884@mariner.uk.xensource.com> (raw)
In-Reply-To: <9a4ad5ca-d0c4-5ac8-f18e-a39df869b05b@citrix.com>
Andrew Cooper writes ("Re: [PATCH XTF 3/3] xtf-runner: regularise runner exit code"):
> On 25/07/16 12:25, Ian Jackson wrote:
> > In particular, Error might mask a failure.
>
> Indeed it could. Either should cause a prompt investigation and effort
> to resolve the issues, but one must be more severe than the other and
> this is the way things are specified.
Is this really how XenRT expects things to be explained to it ?
This seems to be a very unusual approach. Normally, in any program,
the unbounded class of errors will be always reported in the exit
status.
If we are running xtf inside osstest, I trust we aren't relying on
this aggregated exit status ?
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-07-25 17:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 15:44 [PATCH XTF 0/3] Runner exit code clean up Wei Liu
2016-07-21 15:44 ` [PATCH XTF 1/3] xtf-runner: sync all test states Wei Liu
2016-07-21 18:49 ` Andrew Cooper
2016-07-21 15:44 ` [PATCH XTF 2/3] xtf-runner: provide a set of exit codes for different states Wei Liu
2016-07-21 16:27 ` Ian Jackson
2016-07-21 16:29 ` Wei Liu
2016-07-21 16:37 ` Wei Liu
2016-07-21 18:56 ` Andrew Cooper
2016-07-21 15:44 ` [PATCH XTF 3/3] xtf-runner: regularise runner exit code Wei Liu
2016-07-21 19:04 ` Andrew Cooper
2016-07-22 9:29 ` Wei Liu
2016-07-22 9:35 ` Andrew Cooper
2016-07-25 11:25 ` Ian Jackson
2016-07-25 12:09 ` Andrew Cooper
2016-07-25 17:05 ` Ian Jackson [this message]
2016-07-26 8:57 ` 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=22422.18129.501438.934884@mariner.uk.xensource.com \
--to=ian.jackson@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=wei.liu2@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.