From: Ian Campbell <ian.campbell@citrix.com>
To: Anthony PERARD <anthony.perard@citrix.com>,
osstest service owner <osstest-admin@xenproject.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: [qemu-mainline test] 65237: regressions - FAIL
Date: Tue, 1 Dec 2015 10:19:23 +0000 [thread overview]
Message-ID: <1448965163.15768.81.camel@citrix.com> (raw)
In-Reply-To: <20151130184739.GA1788@perard.uk.xensource.com>
On Mon, 2015-11-30 at 18:47 +0000, Anthony PERARD wrote:
> On Mon, Nov 30, 2015 at 09:40:28AM +0000, osstest service owner wrote:
> > flight 65237 qemu-mainline real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/65237/
> >
> > Regressions :-(
> >
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> > test-amd64-i386-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 64579
> > test-amd64-i386-xl-qemuu-debianhvm-amd64 9 debian-hvm-install fail REGR. vs. 64579
>
> In this test, qemu SIGABRT with "Bad ram offset efffd000" as an error
> message. The test started to fail when osstest started to test with a guest
> with 5000 of memory instead of 768.
That's still a QEMU and/or Xen bug though, right?
IOW you aren't trying to suggest this is an osstest bug, I think.
NB the size of the guest ram depends on the amount of host RAM available,
so this will vary across hosts.
The apparent switch to 5000 for test-amd64-i386-xl-qemuu-ovmf-amd64 was
from merlot1 starting in flight 65078, but there was a pass on merlot1
at 63741. My guess is that a change in one of the other trees between those
two has exposed the issue.
The test-amd64-i386-xl-qemuu-debianhvm-amd64 case[1] started in 65147 when
it ran on nocera1, but nocera* only went into service last week and haven't
run any flights on this branch before now.
The bisector is having a look at the merlot case[2], there are some interim
progress reports on the osstest-putput list[3] (search for
test-amd64-i386-xl-qemuu-ovmf-amd64).
Looking at the complexity of the graph it'll probably take a little while
to reach a verdict, although it does appear to be making some progress.
Ian.
[0] http://logs.test-lab.xenproject.org/osstest/results/history/test-amd64-i386-xl-qemuu-ovmf-amd64/qemu-mainline.html
[1] http://logs.test-lab.xenproject.org/osstest/results/history/test-amd64-i386-xl-qemuu-debianhvm-amd64/qemu-mainline.html
[2] http://logs.test-lab.xenproject.org/osstest/results/bisect/qemu-mainline/test-amd64-i386-xl-qemuu-ovmf-amd64.debian-hvm-install.html
[3] http://lists.xenproject.org/archives/html/osstest-output/2015-11/threads.html
http://lists.xenproject.org/archives/html/osstest-output/2015-12/threads.html
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-12-01 10:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 9:40 [qemu-mainline test] 65237: regressions - FAIL osstest service owner
2015-11-30 18:47 ` Anthony PERARD
2015-12-01 10:19 ` Ian Campbell [this message]
2015-12-01 15:02 ` Anthony PERARD
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=1448965163.15768.81.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=anthony.perard@citrix.com \
--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 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.