All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com,
	osstest service owner <osstest-admin@xenproject.org>
Subject: [PATCH OSSTEST] stop allowing libvirt failures (Was: Re: [xen-unstable-smoke test] 78436: tolerable FAIL - PUSHED)
Date: Mon, 18 Jan 2016 16:06:14 +0000	[thread overview]
Message-ID: <1453133174.6020.174.camel@citrix.com> (raw)
In-Reply-To: <osstest-78436-mainreport@xen.org>

On Mon, 2016-01-18 at 15:44 +0000, osstest service owner wrote:
> flight 78436 xen-unstable-smoke real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/78436/
> 
> Failures :-/ but no regressions.
> 
> Regressions which are regarded as allowable (not blocking):
>  test-amd64-amd64-libvirt      6 xen-boot                  fail REGR. vs. 78183

Well that ain't right...

8<---------

From 13e31f297f9f5e95d510fe7d88dc1c7088fe8c63 Mon Sep 17 00:00:00 2001
From: Ian Campbell <ian.campbell@citrix.com>
Date: Mon, 18 Jan 2016 15:54:15 +0000
Subject: [PATCH] stop allowing libvirt failures

In Feb/Mar 2015 (not long after adding the libvirt tests) we appear to
have added test-@@-libvirt@@ to the set of allowed failures in
response to some issues with libvirtd crashing.

However looking at the history of test-@@-libvirt@@ on all branches
both in the COLO and in Cambridge (which was the production instance
back then) I don't see any evidence that this issue is still ongoing
(which matches my recollection of it having been fixed).

Therefore remove the entries allowing libvirt failures.

This effectively reverts:

00023a5af6ff allow files: Allow all libvirt test failures on other branches
83b8c8eafb18 allow.all: Do not regard libvirt guest start failures as regressions

Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
---
 allow.all     | 1 -
 allow.libvirt | 1 -
 2 files changed, 2 deletions(-)
 delete mode 100644 allow.libvirt

diff --git a/allow.all b/allow.all
index 8060595..785d0b2 100644
--- a/allow.all
+++ b/allow.all
@@ -2,7 +2,6 @@ test-@@-rtds@@
 build-@@                        logs-capture@@
 test-@@-pcipt@@
 test-@@-qemuu-@@		guest-localmigrate
-test-@@-libvirt@@
 test-@@-rumpuserxen@@		rumpuserxen-demo-xenstorels/xenstorels
 test-@@-win7-@@			guest-stop
 test-@@-rumpuserxen-@@		rumpuserxen-demo-xenstorels/xenstorels.repeat
diff --git a/allow.libvirt b/allow.libvirt
deleted file mode 100644
index abc7669..0000000
--- a/allow.libvirt
+++ /dev/null
@@ -1 +0,0 @@
-!test-@@-libvirt@@
-- 
2.6.1


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

  reply	other threads:[~2016-01-18 16:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-18 15:44 [xen-unstable-smoke test] 78436: tolerable FAIL - PUSHED osstest service owner
2016-01-18 16:06 ` Ian Campbell [this message]
2016-01-18 16:13   ` [PATCH OSSTEST] stop allowing libvirt failures (Was: Re: [xen-unstable-smoke test] 78436: tolerable FAIL - PUSHED) Ian Campbell
2016-01-19 13:44   ` 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=1453133174.6020.174.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=osstest-admin@xenproject.org \
    --cc=xen-devel@lists.xensource.com \
    /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.