From: Ian Jackson <ian.jackson@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Juergen Gross <jgross@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] [xen-4.8-testing test] 136566: regressions - FAIL
Date: Mon, 17 Jun 2019 14:28:37 +0100 [thread overview]
Message-ID: <23815.38277.145206.191140@mariner.uk.xensource.com> (raw)
In-Reply-To: <5CE4F0F50200007800231309@prv1-mh.provo.novell.com>
Jan Beulich writes ("Re: [xen-4.8-testing test] 136566: regressions - FAIL"):
> 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?
Yes.
> 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 ...
Yes.
However,
4.6 is quite badly broken. See my mail
Subject: Re: [xen-4.6-testing test] 137064: regressions - FAIL
Date: Fri, 31 May 2019 11:33:31 +0100
in which I proposed a force push despite these serious problems.
I'll check with you on irc now whether you agree that this should be
pushed now.
4.7 is broken with HVM guests. You wrote about this today:
Subject: Re: [Xen-devel] [xen-4.7-testing test] 137065: regressions - FAIL
Date: Mon, 17 Jun 2019 08:04:00 +0100
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2019-06-17 13:29 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
2019-05-22 6:49 ` [Xen-devel] " Jan Beulich
2019-06-17 13:28 ` Ian Jackson [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=23815.38277.145206.191140@mariner.uk.xensource.com \
--to=ian.jackson@citrix.com \
--cc=JBeulich@suse.com \
--cc=jgross@suse.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).