From: Ian Jackson <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Ian Jackson <ian.jackson@eu.citrix.com>
Subject: [OSSTEST PATCH 1/5] ms-flights-summary: Do gather_stats on jobs a bit later
Date: Mon, 18 Jul 2016 15:04:02 +0100 [thread overview]
Message-ID: <1468850646-2283-1-git-send-email-ian.jackson@eu.citrix.com> (raw)
We are going to want to invent a fake status for `preparing' jobs
which have no allocation, separate from ones which do have an
allocation.
Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
---
ms-flights-summary | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/ms-flights-summary b/ms-flights-summary
index ea72088..413b703 100755
--- a/ms-flights-summary
+++ b/ms-flights-summary
@@ -342,11 +342,14 @@ enumerate_flights();
foreach my $f (keys %flights) {
enumerate_jobs($flights{$f});
- gather_stats($flights{$f});
}
gather_events();
+foreach my $f (keys %flights) {
+ gather_stats($flights{$f});
+}
+
printf("<html><head><title>Flights - %s</title></head><body>\n",
$c{DnsDomain} // '?');
printf("<p>Report at ".fmttime(time)." based on plan at ".fmttime($plan->{Start})."</p>\n");
--
2.1.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2016-07-18 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 14:04 Ian Jackson [this message]
2016-07-18 14:04 ` [OSSTEST PATCH 2/5] ms-flights-summary: Do gather_stats without GROUP BY Ian Jackson
2016-07-18 14:04 ` [OSSTEST PATCH 3/5] ms-flights-summary: Invent a `prep.alloc.' pseudo job state Ian Jackson
2016-07-18 14:04 ` [OSSTEST PATCH 4/5] ms-flights-summary: Treat preparing jobs outside the plan as `queued' Ian Jackson
2016-07-18 14:04 ` [OSSTEST PATCH 5/5] sg-execute-flight: Fix an error message 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=1468850646-2283-1-git-send-email-ian.jackson@eu.citrix.com \
--to=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).