From: Jan Beulich <jbeulich@suse.com>
To: osstest service owner <osstest-admin@xenproject.org>,
xen-devel@lists.xenproject.org
Subject: Re: [Xen-devel] [linux-linus bisection] complete test-amd64-i386-qemuu-rhel6hvm-amd
Date: Tue, 8 Oct 2019 15:15:28 +0200 [thread overview]
Message-ID: <a801fa04-c85a-96da-1376-71a1a7d18dbc@suse.com> (raw)
In-Reply-To: <E1iHpCB-00025s-UB@osstest.test-lab.xenproject.org>
On 08.10.2019 15:06, osstest service owner wrote:
> branch xen-unstable
> xenbranch xen-unstable
> job test-amd64-i386-qemuu-rhel6hvm-amd
> testid xen-boot
>
> Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
> Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
> Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
> Tree: qemuu git://xenbits.xen.org/qemu-xen.git
> Tree: seabios git://xenbits.xen.org/osstest/seabios.git
> Tree: xen git://xenbits.xen.org/xen.git
>
> *** Found and reproduced problem changeset ***
>
> Bug is in tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> Bug introduced: da0c9ea146cbe92b832f1b0f694840ea8eb33cce
> Bug not present: 46713c3d2f8da5e3d8ddd2249bcb1d9974fb5d28
> Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/142439/
I did send a patch for this issue yesterday:
https://lkml.org/lkml/2019/10/7/220 (can't seem to find it on
patchwork).
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-10-08 13:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 13:06 [Xen-devel] [linux-linus bisection] complete test-amd64-i386-qemuu-rhel6hvm-amd osstest service owner
2019-10-08 13:15 ` Jan Beulich [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-05 21:41 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=a801fa04-c85a-96da-1376-71a1a7d18dbc@suse.com \
--to=jbeulich@suse.com \
--cc=osstest-admin@xenproject.org \
--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 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).