All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: "xen.org" <Ian.Jackson@eu.citrix.com>, xen-devel@lists.xensource.com
Subject: Re: [linux-next test] 31271: tolerable trouble: broken/fail/pass
Date: Fri, 31 Oct 2014 10:51:25 +0000	[thread overview]
Message-ID: <545369AD.7000206@citrix.com> (raw)
In-Reply-To: <osstest-31271-mainreport@xen.org>

On 31/10/14 04:22, xen.org wrote:
> flight 31271 linux-next real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/31271/
> 
> Failures :-/ but no regressions.

>  test-amd64-amd64-xl-qemut-win7-amd64                         fail    
>  test-amd64-i386-xl-qemut-win7-amd64                          fail    
>  test-amd64-amd64-xl-qemuu-win7-amd64                         fail    
>  test-amd64-i386-xl-qemuu-win7-amd64                          fail    
>  test-amd64-amd64-xl-win7-amd64                               fail    
>  test-amd64-i386-xl-win7-amd64                                fail

All the windows tests are failing because:

Shutting down domain 18
PV control interface not available: external graceful shutdown not possible.
Use "-F" to fallback to ACPI power event.
shutdown failed (rc=-10)

Which is expected behaviour and not a failure.  This problem is
universal across all the different test runs.

Either PV drivers need to be installed into the guest or the test needs
to be fixed to use the ACPI power event.

David

  reply	other threads:[~2014-10-31 10:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-31  4:22 [linux-next test] 31271: tolerable trouble: broken/fail/pass xen.org
2014-10-31 10:51 ` David Vrabel [this message]
2014-10-31 13:15   ` Konrad Rzeszutek Wilk
2014-10-31 13:21     ` Andrew Cooper

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=545369AD.7000206@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=Ian.Jackson@eu.citrix.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 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.