From: "Jan Beulich" <JBeulich@suse.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [xen-4.3-testing test] 86445: regressions - trouble: blocked/broken/fail/pass
Date: Mon, 21 Mar 2016 05:28:42 -0600 [thread overview]
Message-ID: <56EFE8FA02000078000DEC25@prv-mh.provo.novell.com> (raw)
In-Reply-To: <22252.18849.446618.614751@mariner.uk.xensource.com>
>>> On 18.03.16 at 19:32, <Ian.Jackson@eu.citrix.com> wrote:
> Ian Jackson writes ("Re: [xen-4.3-testing test] 86445: regressions - trouble:
> blocked/broken/fail/pass"):
>> Jan Beulich writes ("Re: [xen-4.3-testing test] 86445: regressions - trouble:
> blocked/broken/fail/pass"):
>> > But these have been recurring throughout the last dozen (or
>> > more) flights, so they don't look that intermittent to me.
>>
>> You are right. I confused myself by looking at the wrong subset of of
>> logs. Something odd is going on, and I will investigate.
>
> I think I have found and fixed the problems. All of them were bugs in
> osstest's suite (Debian release codename) handling, introduced quite
> recently.
>
> I have pushed the fixes to osstest pretest and with luck they will
> pass and then actually fix the problems with the xen-4.3-testing
> tests.
And indeed that was the case - thanks for taking care of this!
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-03-21 11:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 22:13 [xen-4.3-testing test] 86445: regressions - trouble: blocked/broken/fail/pass osstest service owner
2016-03-18 11:29 ` Ian Jackson
2016-03-18 13:48 ` Jan Beulich
2016-03-18 14:44 ` Ian Jackson
2016-03-18 18:32 ` Ian Jackson
2016-03-21 11:28 ` Jan Beulich [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=56EFE8FA02000078000DEC25@prv-mh.provo.novell.com \
--to=jbeulich@suse.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).