From: Paul Durrant <Paul.Durrant@citrix.com>
To: Ian Jackson <Ian.Jackson@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Wei Liu <wei.liu2@citrix.com>, 'Jan Beulich' <JBeulich@suse.com>
Subject: Re: [xen-unstable test] 108068: regressions - FAIL
Date: Tue, 2 May 2017 14:06:18 +0000 [thread overview]
Message-ID: <c2a925b3061a4ff09e143262c3d70111@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <22792.37355.937427.625692@mariner.uk.xensource.com>
> -----Original Message-----
> From: Ian Jackson [mailto:ian.jackson@eu.citrix.com]
> Sent: 02 May 2017 15:04
> To: Paul Durrant <Paul.Durrant@citrix.com>
> Cc: 'Jan Beulich' <JBeulich@suse.com>; Wei Liu <wei.liu2@citrix.com>; xen-
> devel <xen-devel@lists.xenproject.org>
> Subject: RE: [Xen-devel] [xen-unstable test] 108068: regressions - FAIL
>
> Paul Durrant writes ("RE: [Xen-devel] [xen-unstable test] 108068: regressions
> - FAIL"):
> > It's very hard to say. There's nothing particularly conclusive in the logs.
> QEMU has definitely requested a reset as can be seen in
> >
> > http://logs.test-lab.xenproject.org/osstest/logs/108068/test-amd64-i386-
> xl-qemut-winxpsp3-vcpus1/italia0---var-log-xen-qemu-dm-
> win.guest.osstest--incoming.log
> >
> > but really no clue why. The most obvious reason would be a BSOD in the
> OS, but without catching it in the act there's not much we can tell.
>
> Does a Windows BSOD not crash or hang the VM ? Rebooting as a result
> is pretty unhelpful in our context (and many others I guess).
Unless you modify the config of the OS (as XenRT does) then the default action is to reboot. I assume this is to attempt to maintain availability on the normal case.
Paul
>
> > IMO testing OS that are so massively out of date is probably not
> worthwhile. If there is any real problem then I'd expect it to manifest across
> multiple versions of Windows and so other tests should catch such an issue.
>
> I don't have an opinion about this. I can drop this test.
>
> Does anyone object ?
>
> Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-05-02 14:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 18:49 [xen-unstable test] 108068: regressions - FAIL osstest service owner
2017-05-02 9:10 ` Jan Beulich
2017-05-02 12:45 ` Ian Jackson
2017-05-02 13:27 ` Andrew Cooper
2017-05-02 13:42 ` Ian Jackson
2017-05-02 13:46 ` Andrew Cooper
2017-05-02 13:30 ` Wei Liu
2017-05-02 13:32 ` Jan Beulich
2017-05-02 13:40 ` Paul Durrant
2017-05-02 13:44 ` Ian Jackson
2017-05-02 13:58 ` Paul Durrant
2017-05-02 14:04 ` Ian Jackson
2017-05-02 14:05 ` Wei Liu
2017-05-02 14:06 ` Paul Durrant [this message]
2017-05-02 14:11 ` Jan Beulich
2017-05-02 14:14 ` Paul Durrant
2017-05-02 14:29 ` Ian Jackson
2017-05-03 16:05 ` Newer Windows in Xen Project osstest test lab Ian Jackson
2017-05-03 16:19 ` Paul Durrant
2017-05-04 12:20 ` [OSSTEST PATCH 1/3] make-flight: Factor out do_hvm_win_test_one Ian Jackson
2017-05-04 12:20 ` [OSSTEST PATCH 2/3] make-flight: Add tests for some more recent Windows versions Ian Jackson
2017-05-04 12:20 ` [OSSTEST PATCH 3/3] make-flight: Drop Windows XP tests Ian Jackson
2017-05-04 13:19 ` Jan Beulich
2017-05-11 14:37 ` Proposal to drop Windows XP tests from Xen Project CI Ian Jackson
2017-05-04 16:00 ` Ian Jackson
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=c2a925b3061a4ff09e143262c3d70111@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=Ian.Jackson@citrix.com \
--cc=JBeulich@suse.com \
--cc=wei.liu2@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 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).