From: "Jan Beulich" <JBeulich@suse.com>
To: xen-devel <xen-devel@lists.xenproject.org>
Cc: Igor Druzhinin <igor.druzhinin@citrix.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
osstest-admin@xenproject.org,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [xen-unstable test] 112855: regressions - trouble: blocked/broken/fail/pass
Date: Fri, 25 Aug 2017 07:40:11 -0600 [thread overview]
Message-ID: <59A044DB0200007800173CEB@prv-mh.provo.novell.com> (raw)
In-Reply-To: <osstest-112855-mainreport@xen.org>
>>> On 25.08.17 at 05:15, <osstest-admin@xenproject.org> wrote:
> flight 112855 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/112855/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-i386-examine 7 reboot fail REGR. vs. 112809
> test-amd64-i386-freebsd10-amd64 7 xen-boot fail REGR. vs. 112809
These two are watchdog NMIs during the loading of Dom0. Most
likely candidate for introducing the issue is Boris' scrub series.
> build-amd64-xsm 6 xen-build fail REGR. vs. 112809
This looks like a network glitch.
> test-amd64-amd64-xl-qemut-win7-amd64 10 windows-install fail REGR. vs. 112809
> test-amd64-i386-xl-qemut-win7-amd64 10 windows-install fail REGR. vs. 112809
> test-amd64-i386-xl-qemut-ws16-amd64 10 windows-install fail REGR. vs. 112809
The guests here look to all be stuck on early first time boot.
One of the two hvmloader changes would look to be the
primary suspects.
In both problem cases we may alternatively need to see whether
the bisector can narrow it down over the weekend.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-08-25 13:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-25 3:15 [xen-unstable test] 112855: regressions - trouble: blocked/broken/fail/pass osstest service owner
2017-08-25 13:40 ` Jan Beulich [this message]
2017-08-25 17:14 ` Boris Ostrovsky
2017-08-28 7:25 ` Jan Beulich
2017-08-28 13:57 ` Boris Ostrovsky
2017-08-28 14:02 ` Jan Beulich
2017-08-28 14:24 ` Boris Ostrovsky
2017-08-28 14:52 ` Jan Beulich
2017-08-28 15:36 ` Boris Ostrovsky
2017-08-29 8:07 ` Jan Beulich
2017-08-29 12:45 ` Boris Ostrovsky
2017-08-29 13:12 ` Jan Beulich
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=59A044DB0200007800173CEB@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=igor.druzhinin@citrix.com \
--cc=osstest-admin@xenproject.org \
--cc=roger.pau@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.