From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Daniel Kiper <dkiper@net-space.pl>, xen-devel@lists.xensource.com
Cc: daniel.kiper@oracle.com, jbeulich@suse.com
Subject: Re: [xen-unstable bisection] complete test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm
Date: Thu, 2 Mar 2017 10:42:57 +0000 [thread overview]
Message-ID: <e5c528fb-72e2-fcd5-b796-dd9aa9af2468@citrix.com> (raw)
In-Reply-To: <20170302104124.GA6407@router-fw-old.local.net-space.pl>
On 02/03/17 10:41, Daniel Kiper wrote:
> On Wed, Mar 01, 2017 at 11:53:52PM +0000, osstest service owner wrote:
>> branch xen-unstable
>> xenbranch xen-unstable
>> job test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm
>> testid xen-boot
>>
>> Tree: linux git://xenbits.xen.org/linux-pvops.git
>> Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
>> Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
>> Tree: qemuu git://xenbits.xen.org/qemu-xen.git
>> Tree: xen git://xenbits.xen.org/xen.git
>>
>> *** Found and reproduced problem changeset ***
>>
>> Bug is in tree: xen git://xenbits.xen.org/xen.git
>> Bug introduced: c5b9805bc1f793177779ae342c65fcc201a15a47
>> Bug not present: b199c44afa3a0d18d0e968e78a590eb9e69e20ad
>> Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/106324/
>>
>>
>> commit c5b9805bc1f793177779ae342c65fcc201a15a47
>> Author: Daniel Kiper <daniel.kiper@oracle.com>
>> Date: Wed Feb 22 14:38:06 2017 +0100
>>
>> efi: create new early memory allocator
> Does anybody know why this still fails? Andrew applied a fix (workaround) for this yesterday.
Bisection runs from before will still be running. Also, the fix hasn't
passed staging yet.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-02 10:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 23:53 [xen-unstable bisection] complete test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm osstest service owner
2017-03-02 10:41 ` Daniel Kiper
2017-03-02 10:42 ` Andrew Cooper [this message]
2017-03-02 11:09 ` Daniel Kiper
-- strict thread matches above, loose matches on Subject: below --
2023-12-10 19:11 osstest service owner
2022-11-20 8:28 osstest service owner
2021-08-21 23:29 osstest service owner
2020-11-12 12:29 osstest service owner
2020-04-10 1:43 osstest service owner
2018-04-04 9:19 osstest service owner
2016-10-30 4:29 osstest service owner
2016-10-30 16:53 ` Andrew Cooper
2016-10-31 15:00 ` Wei Liu
2016-10-30 17:31 ` Andrew Cooper
2016-10-31 10:31 ` Ian Jackson
2016-10-31 10:37 ` Andrew Cooper
2016-01-15 1:42 osstest service owner
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=e5c528fb-72e2-fcd5-b796-dd9aa9af2468@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=daniel.kiper@oracle.com \
--cc=dkiper@net-space.pl \
--cc=jbeulich@suse.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 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).