All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Xen-devel <xen-devel@lists.xenproject.org>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: [OSSTEST PATCH v3 06/25] step status skip: Implement in sg-report-flight
Date: Tue, 6 Sep 2016 14:09:21 +0100	[thread overview]
Message-ID: <1473167380-957-7-git-send-email-wei.liu2@citrix.com> (raw)
In-Reply-To: <1473167380-957-1-git-send-email-wei.liu2@citrix.com>

From: Ian Jackson <ian.jackson@eu.citrix.com>

* When we are doing archaeology, searching for flight(s) which ran a
  particular testid, ignore all flights where the testid was skipped.

* In a flight we are examining for failures we need to justify, do not
  regard `skip' as a failure which requires investigation.  We
  thusg treat `skip' in such a flight very like `pass'.

* Assign a colour (dark grey, almost like the background) and display
  priority (very low) to `skip', so that they turn up nicely in the
  HTML grids.

Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
---
 sg-report-flight | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/sg-report-flight b/sg-report-flight
index ca9ba18..dbb17be 100755
--- a/sg-report-flight
+++ b/sg-report-flight
@@ -162,6 +162,7 @@ sub findaflight ($$$$$) {
 
     my $checkq= db_prepare(<<END);
         SELECT status FROM steps WHERE flight=? AND job=? AND testid=?
+                                   AND status!='skip'
 END
 
     my $thatflight= $specver{that}{flight};
@@ -460,7 +461,7 @@ END
 
             my $fi= { Job => $j, Step => $s };
             
-            if ($s->{status} ne 'pass') {
+            if ($s->{status} ne 'pass' && $s->{status} ne 'skip') {
                 $fi= $storefail->($s);
                 $foundfail= 1;
             }
@@ -1083,7 +1084,8 @@ END
 
 sub html_status2_colour_priority ($) {
     my ($st) = @_;
-    return ($st eq 'pass' ? ('#008800',100) :
+    return ($st eq 'skip' ? ('#555555', 50) :
+            $st eq 'pass' ? ('#008800',100) :
             $st eq 'fail' ? ('#ff8888',200) :
             $st eq 'running' ? ('#666666',250) :
             ('#ffff00',300));
-- 
2.1.4


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

  parent reply	other threads:[~2016-09-06 13:09 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-06 13:09 [OSSTEST PATCH v3 00/25] Integrate XTF into OSSTest Wei Liu
2016-09-06 13:09 ` [OSSTEST PATCH v3 01/25] Executive: Previous duration estimator: use overall time, not sum of steps Wei Liu
2016-09-06 13:09 ` [OSSTEST PATCH v3 02/25] ts-hosts-allocate-Executive: Replace some odd commas with semicolons Wei Liu
2016-09-06 13:09 ` [OSSTEST PATCH v3 03/25] sg-run-job: Add emacs mode comment Wei Liu
2016-09-06 13:09 ` [OSSTEST PATCH v3 04/25] step status skip: Ignore in cs-bisection-step Wei Liu
2016-09-06 13:09 ` [OSSTEST PATCH v3 05/25] step status skip: Ignore in report_run_getinfo Wei Liu
2016-09-06 13:09 ` Wei Liu [this message]
2016-09-06 13:09 ` [OSSTEST PATCH v3 07/25] ts-hosts-allocate-Executive: pass $plan to hid_find_possibilities Wei Liu
2016-09-06 13:09 ` [OSSTEST PATCH v3 08/25] ts-hosts-allocate-Executive: Support diverse-CLASS hostflag Wei Liu
2016-09-06 13:09 ` [OSSTEST PATCH v3 09/25] DO NOT APPLY make-flight-diverse-test: test case for " Wei Liu
2016-09-06 13:09 ` [OSSTEST PATCH v3 10/25] Executive: Support substeps Wei Liu
2016-09-06 13:09 ` [OSSTEST PATCH v3 11/25] DO NOT APPLY make-flight-substep-test Wei Liu
2016-09-06 13:09 ` [OSSTEST PATCH v3 12/25] DO NOT APPLY provide ts-substep-test Wei Liu
2016-09-06 13:09 ` [OSSTEST PATCH v3 13/25] ts-xen-build: always compile in FEP support Wei Liu
2016-09-06 13:09 ` [OSSTEST PATCH v3 14/25] ap-common: add xtf tree Wei Liu
2016-09-06 13:09 ` [OSSTEST PATCH v3 15/25] DO NOT APPLY point xtf to my personal tree Wei Liu
2016-09-06 13:09 ` [OSSTEST PATCH v3 16/25] BuildSupport: move buildcmd_stamped_logged here Wei Liu
2016-09-06 13:09 ` [OSSTEST PATCH v3 17/25] Introduce ts-xtf-build Wei Liu
2016-09-06 13:09 ` [OSSTEST PATCH v3 18/25] sg-run-job: create xtf build recipe Wei Liu
2016-09-06 13:09 ` [OSSTEST PATCH v3 19/25] Introduce ts-xtf-install Wei Liu
2016-09-06 14:01   ` Ian Jackson
2016-09-06 13:09 ` [OSSTEST PATCH v3 20/25] mfi-common: create xtf build job for 4.4 onwards Wei Liu
2016-09-06 14:06   ` Ian Jackson
2016-09-08 17:00     ` Wei Liu
2016-09-08 17:41       ` Ian Jackson
2016-09-08 18:11         ` Wei Liu
2016-09-09 10:09           ` Ian Jackson
2016-09-06 13:09 ` [OSSTEST PATCH v3 21/25] Introduce ts-xtf-fep Wei Liu
2016-09-06 14:07   ` Ian Jackson
2016-09-06 13:09 ` [OSSTEST PATCH v3 22/25] Introduce ts-xtf-run Wei Liu
2016-09-06 13:09 ` [OSSTEST PATCH v3 23/25] sg-run-job: test-xtf recipe Wei Liu
2016-09-06 13:09 ` [OSSTEST PATCH v3 24/25] make-flight: create 5 xtf jobs Wei Liu
2016-09-08 17:01   ` Wei Liu
2016-09-08 17:41     ` Ian Jackson
2016-09-06 13:09 ` [OSSTEST PATCH v3 25/25] Create XTF branch Wei Liu
2016-09-06 14:03   ` Ian Jackson
2016-09-06 19:16     ` Wei Liu
2016-09-08 14:47       ` Ian Jackson
2016-09-08 17:07         ` Wei Liu
2016-09-08 17:45           ` Ian Jackson
2016-09-08 18:07             ` Wei Liu
2016-09-09 10:04               ` Ian Jackson
2016-09-06 19:14   ` 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=1473167380-957-7-git-send-email-wei.liu2@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 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.