From: Andrew Cooper <andrew.cooper3@citrix.com>
To: xen-devel@lists.xen.org
Subject: Re: [xtf test] 111167: regressions - trouble: broken/pass
Date: Thu, 29 Jun 2017 14:22:09 +0100 [thread overview]
Message-ID: <520b0fbc-c873-3d3b-7b18-da4b0f7529f5@citrix.com> (raw)
In-Reply-To: <osstest-111167-mainreport@xen.org>
On 29/06/17 09:54, osstest service owner wrote:
> flight 111167 xtf real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/111167/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-xtf-amd64-amd64-1 59 leak-check/check fail REGR. vs. 111074
> test-xtf-amd64-amd64-4 59 leak-check/check fail REGR. vs. 111074
> test-xtf-amd64-amd64-3 59 leak-check/check fail REGR. vs. 111074
> test-xtf-amd64-amd64-2 59 leak-check/check fail REGR. vs. 111074
> test-xtf-amd64-amd64-5 59 leak-check/check fail REGR. vs. 111074
>
> Tests which did not succeed, but are not blocking:
> test-xtf-amd64-amd64-1 58 xtf/test-hvm64-xsa-221 fail never pass
> test-xtf-amd64-amd64-4 58 xtf/test-hvm64-xsa-221 fail never pass
> test-xtf-amd64-amd64-3 58 xtf/test-hvm64-xsa-221 fail never pass
> test-xtf-amd64-amd64-2 58 xtf/test-hvm64-xsa-221 fail never pass
> test-xtf-amd64-amd64-5 58 xtf/test-hvm64-xsa-221 fail never pass
FYI, this is because the fix for XSA-221 hasn't yet passed the master
push gate.
The problem will resolve itself when master moves forwards.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-06-29 13:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 8:54 [xtf test] 111167: regressions - trouble: broken/pass osstest service owner
2017-06-29 13:22 ` Andrew Cooper [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=520b0fbc-c873-3d3b-7b18-da4b0f7529f5@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=xen-devel@lists.xen.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.