From: "Jan Beulich" <JBeulich@suse.com>
To: xen-devel <xen-devel@lists.xenproject.org>
Cc: ian.jackson@eu.citrix.com
Subject: Re: [xen-unstable test] 18454: regressions - FAIL
Date: Thu, 18 Jul 2013 08:13:29 +0100 [thread overview]
Message-ID: <51E7B1B902000078000E5D20@nat28.tlf.novell.com> (raw)
In-Reply-To: <osstest-18454-mainreport@xen.org>
>>> On 18.07.13 at 08:24, xen.org <ian.jackson@eu.citrix.com> wrote:
> flight 18454 xen-unstable real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/18454/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-amd64-xl-qemuu-winxpsp3 10 guest-saverestore.2 fail REGR. vs. 18431
> test-amd64-i386-xl-qemut-winxpsp3-vcpus1 7 windows-install fail REGR. vs. 18431
So this isn't a race after all (but I'm nevertheless glad the races
should now all be dealt with):
Jul 18 03:28:20.051054 (XEN) vmap(ffff82c000209000:0x2)
Jul 18 03:29:15.995060 (XEN) vunmap(ffff82c000209000:0x3)
> Regressions which are regarded as allowable (not blocking):
> test-amd64-i386-qemut-rhel6hvm-intel 7 redhat-install fail like 18431
Jul 18 02:28:33.727064 (XEN) vmap(ffff82c000209000:0x2)
Jul 18 02:28:39.375057 (XEN) vunmap(ffff82c000209000:0x3)
Something is mapping 2 pages and then unmapping three, thus
apparently destroying an earlier mapping. What I still need to
understand is why the guard page that we put between vmap
regions doesn't cover that (or in fact trigger some assertion).
Jan
prev parent reply other threads:[~2013-07-18 7:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 6:24 [xen-unstable test] 18454: regressions - FAIL xen.org
2013-07-18 7:13 ` 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=51E7B1B902000078000E5D20@nat28.tlf.novell.com \
--to=jbeulich@suse.com \
--cc=ian.jackson@eu.citrix.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 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.