xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Jackson <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Roger Pau Monne <roger.pau@citrix.com>
Subject: [OSSTEST PATCH] cs-hosts-list: Document the --arches, --kernels and --suites options
Date: Fri, 28 Jul 2017 16:28:23 +0100	[thread overview]
Message-ID: <1501255703-23850-1-git-send-email-ian.jackson@eu.citrix.com> (raw)

These have a rather counterintuitive behaviour which is nevertheless
useful.  Document it, and the reasoning.

CC: Roger Pau Monne <roger.pau@citrix.com>
Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
---
 cs-hosts-list | 37 +++++++++++++++++++++++++++++++++++++
 1 file changed, 37 insertions(+)

diff --git a/cs-hosts-list b/cs-hosts-list
index 16b5219..306b04e 100755
--- a/cs-hosts-list
+++ b/cs-hosts-list
@@ -22,6 +22,43 @@
 # prints the names of all hosts which have all of the HOSTFLAGs set,
 # one per line
 
+# options
+#
+#    --arches=ARCH,...
+#             For each host, also print an architecture and a kernel
+#             which are suitable for use with the host (with spaces in
+#             between).  "Suitable" means that the the hostflag
+#             arch-[KERNEL-]ARCH is set, where [KERNEL-] means "linux".
+#
+#             If there is no suitable arch/kernel combination, prints
+#             "NONE NONE" instead.  NB, such hosts are not
+#             excluded from the list.
+#
+#             The arch/kernel search loops over kernels (see
+#             --kernels), and for each kernel loops over arches (in
+#             the order specified here), and stops at the first match.
+#             Ie the kernel ordering takes priority.
+#
+#    --kernels=KERNEL,...
+#             Specifies an alternative list of kernels to try.
+#             The default is "xen" and "linux".
+#             Ignored unless --arches also specified.
+#
+#    --suites=SUITE,....
+#             For each host, also print a Debian suite which is
+#             suitable for use with the host.  "Suitable" means
+#             the hostflag suite-SUITE is set.  If there is no
+#             suitable suite, prints "NONE" instead.
+#
+#             May be combined with --arches.  The output for
+#             --arches always comes first.
+#
+# We still list hosts for which some of the requested information is
+# lacking because such a situation would represent some kind of
+# misconfiguration.  Printing NONE will cause a consumer such as
+# make-hosts-flight to generate jobs which will fail, rather than
+# simply ignoring the problem.
+
 use strict qw(vars);
 use DBI;
 unshift @INC, qw(.);
-- 
2.1.4


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

             reply	other threads:[~2017-07-28 15:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-28 15:28 Ian Jackson [this message]
2017-08-01  7:32 ` [OSSTEST PATCH] cs-hosts-list: Document the --arches, --kernels and --suites options Roger Pau Monne

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=1501255703-23850-1-git-send-email-ian.jackson@eu.citrix.com \
    --to=ian.jackson@eu.citrix.com \
    --cc=roger.pau@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).