From: "Jan Beulich" <JBeulich@suse.com>
To: "osstest service owner" <osstest-admin@xenproject.org>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] [xen-4.8-testing test] 136566: regressions - FAIL
Date: Wed, 22 May 2019 00:49:25 -0600 [thread overview]
Message-ID: <5CE4F0F50200007800231309@prv1-mh.provo.novell.com> (raw)
Message-ID: <20190522064925.uqkxkrIBKabngXHYqPG5KDs4K3pYc0Qq5YAh1_pLApE@z> (raw)
In-Reply-To: <osstest-136566-mainreport@xen.org>
>>> On 22.05.19 at 03:07, <osstest-admin@xenproject.org> wrote:
> flight 136566 xen-4.8-testing real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/136566/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-xtf-amd64-amd64-4 50 xtf/test-hvm64-lbr-tsx-vmentry fail REGR. vs. 130965
> test-xtf-amd64-amd64-4 70 xtf/test-hvm64-xsa-278 fail REGR. vs. 130965
> build-amd64-prev 6 xen-build fail REGR. vs. 130965
> build-i386-prev 6 xen-build fail REGR. vs. 130965
Am I mistaken in understanding that these two will go away only once
the 4.7 tree gets a push (which, even when its own build failures have
got addressed, will require a 4.6 push to occur first), and in turn the
respective 4.9 failures will go away only once we get a push here? If
so - what's the state of these old trees? So far I had been under the
impression that necessary build fix backports had been identified and
applied ...
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-05-22 6:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 1:07 [xen-4.8-testing test] 136566: regressions - FAIL osstest service owner
2019-05-22 1:07 ` [Xen-devel] " osstest service owner
2019-05-22 6:49 ` Jan Beulich [this message]
2019-05-22 6:49 ` Jan Beulich
2019-06-17 13:28 ` 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=5CE4F0F50200007800231309@prv1-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=osstest-admin@xenproject.org \
--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).