From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xenproject.org
Subject: Re: [OSSTEST PATCH 13/13] Reporting: sg-report-flight: Put overall pushgate stats in email
Date: Tue, 30 Jun 2015 10:56:07 +0100 [thread overview]
Message-ID: <1435658167.21469.61.camel@citrix.com> (raw)
In-Reply-To: <21906.26226.562292.410499@mariner.uk.xensource.com>
On Tue, 2015-06-30 at 10:50 +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [OSSTEST PATCH 13/13] Reporting: sg-report-flight: Put overall pushgate stats in email"):
> > On Mon, 2015-06-29 at 18:14 +0100, Ian Jackson wrote:
> > > This adds something like this (would have appeared in 37638):
> > >
> > > Last test of basis 37629 2015-06-24 21:36:10 Z 4 days
> > > Testing same since 37635 2015-06-28 03:05:56 Z 1 days 4 attempts
> > > Failing since 37630 2015-06-26 10:35:44 Z 3 days 9 attempts
> >
> > Chronologically shouldn't the second and third lines be the other way
> > around?
>
> I guess. I will swap them.
Acked-by: Ian Campbell <ian.campbell@citrix.com>
prev parent reply other threads:[~2015-06-30 9:56 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 17:14 [OSSTEST PATCH 00/13] Linux 4.1, and reporting improvements Ian Jackson
2015-06-29 17:14 ` [OSSTEST PATCH 01/13] ts-leak-check: Report leaked loop block devices Ian Jackson
2015-06-30 8:55 ` Ian Campbell
2015-06-29 17:14 ` [OSSTEST PATCH 02/13] Test Linux 4.1 Ian Jackson
2015-06-30 8:58 ` Ian Campbell
2015-06-29 17:14 ` [OSSTEST PATCH 03/13] Reporting: sg-report-flight: Fix undefined value in $worstrow[] Ian Jackson
2015-06-30 9:04 ` Ian Campbell
2015-06-30 9:39 ` Ian Jackson
2015-06-29 17:14 ` [OSSTEST PATCH 04/13] Reporting: In report_run_getinfo, abstract code for returning Ian Jackson
2015-06-30 9:05 ` Ian Campbell
2015-06-29 17:14 ` [OSSTEST PATCH 05/13] Reporting: report_run_getinfo produces ColourAttr Ian Jackson
2015-06-30 9:06 ` Ian Campbell
2015-06-30 9:25 ` Ian Jackson
2015-06-30 9:34 ` Ian Campbell
2015-06-29 17:14 ` [OSSTEST PATCH 06/13] Reporting: sg-report-job-history: Honour --limit Ian Jackson
2015-06-30 9:07 ` Ian Campbell
2015-06-29 17:14 ` [OSSTEST PATCH 07/13] Reporting: report_run_getinfo produces Content Ian Jackson
2015-06-30 9:07 ` Ian Campbell
2015-06-29 17:14 ` [OSSTEST PATCH 08/13] Reporting: Break out report_blessingscond Ian Jackson
2015-06-30 9:11 ` Ian Campbell
2015-06-30 9:31 ` Ian Jackson
2015-06-30 9:44 ` Ian Campbell
2015-06-30 9:54 ` Ian Jackson
2015-06-30 11:01 ` Ian Campbell
2015-06-29 17:14 ` [OSSTEST PATCH 09/13] Reporting sg-report-job-history: support --max-flight Ian Jackson
2015-06-30 9:12 ` Ian Campbell
2015-06-29 17:14 ` [OSSTEST PATCH 10/13] Reporting: sg-report-host-history: Support --max-flight Ian Jackson
2015-06-30 9:12 ` Ian Campbell
2015-06-29 17:14 ` [OSSTEST PATCH 11/13] Reporting: In history tables, show multiple failure steps Ian Jackson
2015-06-30 9:15 ` Ian Campbell
2015-06-29 17:14 ` [OSSTEST PATCH 12/13] Reporting: Provide report_find_push_age_info Ian Jackson
2015-06-30 9:39 ` Ian Campbell
2015-06-29 17:14 ` [OSSTEST PATCH 13/13] Reporting: sg-report-flight: Put overall pushgate stats in email Ian Jackson
2015-06-30 9:33 ` Ian Campbell
2015-06-30 9:50 ` Ian Jackson
2015-06-30 9:56 ` Ian Campbell [this message]
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=1435658167.21469.61.camel@citrix.com \
--to=ian.campbell@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 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.