xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: "Julien Grall" <julien.grall@arm.com>,
	"Stefano Stabellini" <sstabellini@kernel.org>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	osstest service owner <osstest-admin@xenproject.org>
Subject: Re: [Xen-devel] [xen-4.10-testing test] 137854: regressions - FAIL
Date: Tue, 18 Jun 2019 04:20:39 -0600	[thread overview]
Message-ID: <5D08BAF702000078002392F7@prv1-mh.provo.novell.com> (raw)
In-Reply-To: <osstest-137854-mainreport@xen.org>

>>> On 18.06.19 at 07:56, <osstest-admin@xenproject.org> wrote:
> flight 137854 xen-4.10-testing real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/137854/ 
> 
> Regressions :-(
> 
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 10 debian-hvm-install fail REGR. vs. 137381
>  test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 10 debian-hvm-install fail REGR. vs. 137381

This (also seen on 4.11, but not on 4.12) looks to recur. For a -xsm
test I certainly find it odd to see

(XEN) Initialising XSM SILO mode

in the boot log - I'd expect Flask to be used by these tests. And
indeed the SILO backports look to be flawed / incomplete: While
the Kconfig change should have applied with fuzz only (thus
making the issue apparent), the remaining changes aren't taking
into account that the Kconfig option is FLASK there, not XSM_FLASK.
I'll see about producing a fixup patch; I don't think I want to
pull in the master/4.12 patch doing the rename.

Jan



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

      reply	other threads:[~2019-06-18 10:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-18  5:56 [Xen-devel] [xen-4.10-testing test] 137854: regressions - FAIL osstest service owner
2019-06-18 10:20 ` 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=5D08BAF702000078002392F7@prv1-mh.provo.novell.com \
    --to=jbeulich@suse.com \
    --cc=julien.grall@arm.com \
    --cc=osstest-admin@xenproject.org \
    --cc=sstabellini@kernel.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).