xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Platform Team regression test user
	<citrix-osstest@xenproject.org>,
	xen-devel@lists.xensource.com, osstest-admin@xenproject.org
Subject: Re: [xen-unstable baseline-only test] 67995: regressions - FAIL
Date: Fri, 4 Nov 2016 23:14:26 +0000	[thread overview]
Message-ID: <2eea60c1-af45-4fb7-7fd9-50f1950fee66@citrix.com> (raw)
In-Reply-To: <osstest-67995-mainreport@xen.org>

On 04/11/2016 22:59, Platform Team regression test user wrote:
> This run is configured for baseline tests only.
>
> flight 67995 xen-unstable real [real]
> http://osstest.xs.citrite.net/~osstest/testlogs/logs/67995/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  test-xtf-amd64-amd64-5       10 xtf-fep                   fail REGR. vs. 67981
>  test-xtf-amd64-amd64-1       10 xtf-fep                   fail REGR. vs. 67981
>  test-xtf-amd64-amd64-2       10 xtf-fep                   fail REGR. vs. 67981
>  test-xtf-amd64-amd64-3       10 xtf-fep                   fail REGR. vs. 67981
>  test-xtf-amd64-amd64-4       10 xtf-fep                   fail REGR. vs. 67981

The switch from debug to non-debug has resulted in FEP being disabled by
default.  OSSTest should explicitly enable FEP in the builds of Xen
which it uses.

~Andrew

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

      reply	other threads:[~2016-11-04 23:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-04 22:59 [xen-unstable baseline-only test] 67995: regressions - FAIL Platform Team regression test user
2016-11-04 23:14 ` 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=2eea60c1-af45-4fb7-7fd9-50f1950fee66@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=citrix-osstest@xenproject.org \
    --cc=osstest-admin@xenproject.org \
    --cc=xen-devel@lists.xensource.com \
    /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).