From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
"Hu, Robert" <robert.hu@intel.com>
Cc: xen-devel@lists.xensource.com,
osstest service owner <osstest-admin@xenproject.org>,
"Jin, Gordon" <gordon.jin@intel.com>
Subject: Re: Nested HVM in xen-unstable tests
Date: Mon, 23 Nov 2015 10:20:27 +0000 [thread overview]
Message-ID: <1448274027.4973.27.camel@citrix.com> (raw)
In-Reply-To: <22095.12829.362563.377733@mariner.uk.xensource.com>
On Fri, 2015-11-20 at 14:45 +0000, Ian Jackson wrote:
> osstest service owner writes ("[xen-unstable test] 64750: regressions -
> FAIL"):
> > flight 64750 xen-unstable real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/64750/
> ...
> > test-amd64-amd64-qemuu-nested 16 debian-hvm-install/l1/l2 fail
> > baseline untested
>
> It appears that this new test case is failing in xen-unstable. The
> logs are here:
>
> http://logs.test-lab.xenproject.org/osstest/logs/64750/test-amd64-amd64-qemuu-nested/info.html
After investigating my earlier reply to Robert I noticed that some recent
instances of test-amd64-amd64-qemuu-nested seems to have run on rimava,
which is an AMD machine.
At the very least I think we want to add hvm-intel to the host flags for
this test case, but I suspect we might also want to go one step further and
split into test-amd64-amd64-qemuu-nested-intel and test-amd64-amd64-qemuu-
nested-amd with appropriate flags for each.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-11-23 10:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 22:39 [xen-unstable test] 64750: regressions - FAIL osstest service owner
2015-11-20 14:45 ` Nested HVM in xen-unstable tests Ian Jackson
2015-11-22 6:26 ` Hu, Robert
2015-11-23 10:04 ` Ian Campbell
2015-11-23 10:20 ` Ian Campbell [this message]
2015-11-23 10:49 ` [PATCH OSSTEST] make-flight: Run separate nested jobs on AMD and Intel Ian Campbell
2015-11-23 11:27 ` Ian Jackson
2015-11-23 11:40 ` Ian Jackson
2015-11-25 5:32 ` Hu, Robert
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=1448274027.4973.27.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=gordon.jin@intel.com \
--cc=osstest-admin@xenproject.org \
--cc=robert.hu@intel.com \
--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 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.