From: Wei Liu <wei.liu2@citrix.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: xen-devel@lists.xenproject.org, Wei Liu <wei.liu2@citrix.com>
Subject: Re: [OSSTEST PATCH 0/7] Apropos of XTF: Improve failed step selection
Date: Tue, 30 Aug 2016 17:00:39 +0100 [thread overview]
Message-ID: <20160830160039.GR8502@citrix.com> (raw)
In-Reply-To: <1470932283-17445-1-git-send-email-ian.jackson@eu.citrix.com>
On Thu, Aug 11, 2016 at 05:17:56PM +0100, Ian Jackson wrote:
> Running XTF in osstest is likely to produce failures where multiple
> steps fail interestingly. We would like to prefer to report, and
> bisect, earlier steps.
>
> This series does that.
>
> Wei, NB, this has a conflict with the XTF pre series that you have
> taken over. The conflict is not trivial, but easy. The conflicting
> patch is:
> Executive: Previous duration estimator: use overall time, not sum of steps
>
The rebased patch is as followed, please check.
---8<---
From bbdc727965b4d4280bac670823f013d078a54b93 Mon Sep 17 00:00:00 2001
From: Ian Jackson <ian.jackson@eu.citrix.com>
Date: Fri, 8 Jul 2016 19:30:58 +0100
Subject: [OSSTEST PATCH] Executive: Previous duration estimator: use overall
time, not sum of steps
Cc: ian.jackson@eu.citrix.com
Some jobs runs steps in parallel. Do not add up all the insividual
step durations. Instead, calculate the duration as the time between
first step start and last step finish.
Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
[ wei: rebase and fix conflict ]
Signed-off-by: Wei Liu <wei.liu2@citrix.com>
---
Osstest/Executive.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Osstest/Executive.pm b/Osstest/Executive.pm
index 7e31b35..2187a73 100644
--- a/Osstest/Executive.pm
+++ b/Osstest/Executive.pm
@@ -1068,7 +1068,7 @@ END
FROM steps
WHERE flight=? AND job=?
)
- SELECT sum(finished-started)
+ SELECT sum(max(finished)-min(started))
AS duration
FROM tsteps
WHERE step != 'ts-hosts-allocate'
--
2.1.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-08-30 16:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 16:17 [OSSTEST PATCH 0/7] Apropos of XTF: Improve failed step selection Ian Jackson
2016-08-11 16:17 ` [OSSTEST PATCH 1/7] duration_estimator: Introduce $duration_duration_qtxt and @d_d_args Ian Jackson
2016-08-11 16:17 ` [OSSTEST PATCH 2/7] duration_estimator: Reformat inner SQL query with more newlines Ian Jackson
2016-08-11 16:17 ` [OSSTEST PATCH 3/7] duration_estimator: Reorganise inner SQL query to use WITH Ian Jackson
2016-08-11 16:18 ` [OSSTEST PATCH 4/7] duration_estimator: Be able to estimate job duration up to a particular step Ian Jackson
2016-08-11 16:18 ` [OSSTEST PATCH 5/7] sg-report-flight: Fix misleading value in call to duration_estimator Ian Jackson
2016-08-11 16:18 ` [OSSTEST PATCH 6/7] sg-report-flight: Fix a missing newline in a DEBUG message Ian Jackson
2016-08-11 16:18 ` [OSSTEST PATCH 7/7] sg-report-flight: Report earlier, earlier step failures Ian Jackson
2016-08-11 17:05 ` [OSSTEST PATCH 0/7] Apropos of XTF: Improve failed step selection Wei Liu
2016-08-30 16:00 ` Wei Liu [this message]
2016-08-30 16:08 ` Ian Jackson
2016-08-30 16:13 ` Andrew Cooper
2016-09-05 18:08 ` Wei Liu
2016-09-06 9:45 ` Ian Jackson
2016-09-06 9:46 ` 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=20160830160039.GR8502@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).