xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: xen.org <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: ian.jackson@eu.citrix.com
Subject: [xen-unstable test] 7307: regressions - FAIL
Date: Tue, 24 May 2011 10:06:37 +0100	[thread overview]
Message-ID: <osstest-7307-mainreport@xen.org> (raw)

flight 7307 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/7307/

Regressions :-(

Tests which did not succeed and are blocking:
 test-amd64-i386-pair         16 guest-start                fail REGR. vs. 7285

Tests which did not succeed, but are not blocking,
including regressions (tests previously passed) regarded as allowable:
 test-amd64-amd64-win         16 leak-check/check             fail   never pass
 test-amd64-amd64-xl-win      13 guest-stop                   fail   never pass
 test-amd64-i386-rhel6hvm-amd  8 guest-saverestore            fail   never pass
 test-amd64-i386-rhel6hvm-intel  8 guest-saverestore            fail never pass
 test-amd64-i386-win-vcpus1   16 leak-check/check             fail   never pass
 test-amd64-i386-win          16 leak-check/check             fail   never pass
 test-amd64-i386-xl-win-vcpus1 13 guest-stop                   fail  never pass
 test-amd64-xcpkern-i386-rhel6hvm-amd  8 guest-saverestore      fail never pass
 test-amd64-xcpkern-i386-rhel6hvm-intel  8 guest-saverestore    fail never pass
 test-amd64-xcpkern-i386-win  16 leak-check/check             fail   never pass
 test-amd64-xcpkern-i386-xl-win 13 guest-stop                   fail never pass
 test-i386-i386-win           16 leak-check/check             fail   never pass
 test-i386-i386-xl-win        13 guest-stop                   fail   never pass
 test-i386-xcpkern-i386-win   16 leak-check/check             fail   never pass

version targeted for testing:
 xen                  4326bcd88b33
baseline version:
 xen                  37c77bacb52a

------------------------------------------------------------
People who touched revisions under test:
  Keir Fraser <keir@xen.org>
  Tim Deegan <Tim.Deegan@citrix.com>
------------------------------------------------------------

jobs:
 build-i386-xcpkern                                           pass     
 build-amd64                                                  pass     
 build-i386                                                   pass     
 build-amd64-oldkern                                          pass     
 build-i386-oldkern                                           pass     
 build-amd64-pvops                                            pass     
 build-i386-pvops                                             pass     
 test-amd64-amd64-xl                                          pass     
 test-amd64-i386-xl                                           pass     
 test-i386-i386-xl                                            pass     
 test-amd64-xcpkern-i386-xl                                   pass     
 test-i386-xcpkern-i386-xl                                    pass     
 test-amd64-i386-rhel6hvm-amd                                 fail     
 test-amd64-xcpkern-i386-rhel6hvm-amd                         fail     
 test-amd64-i386-xl-credit2                                   pass     
 test-amd64-xcpkern-i386-xl-credit2                           pass     
 test-amd64-i386-rhel6hvm-intel                               fail     
 test-amd64-xcpkern-i386-rhel6hvm-intel                       fail     
 test-amd64-i386-xl-multivcpu                                 pass     
 test-amd64-xcpkern-i386-xl-multivcpu                         pass     
 test-amd64-amd64-pair                                        pass     
 test-amd64-i386-pair                                         fail     
 test-i386-i386-pair                                          pass     
 test-amd64-xcpkern-i386-pair                                 pass     
 test-i386-xcpkern-i386-pair                                  pass     
 test-amd64-amd64-pv                                          pass     
 test-amd64-i386-pv                                           pass     
 test-i386-i386-pv                                            pass     
 test-amd64-xcpkern-i386-pv                                   pass     
 test-i386-xcpkern-i386-pv                                    pass     
 test-amd64-i386-win-vcpus1                                   fail     
 test-amd64-i386-xl-win-vcpus1                                fail     
 test-amd64-amd64-win                                         fail     
 test-amd64-i386-win                                          fail     
 test-i386-i386-win                                           fail     
 test-amd64-xcpkern-i386-win                                  fail     
 test-i386-xcpkern-i386-win                                   fail     
 test-amd64-amd64-xl-win                                      fail     
 test-i386-i386-xl-win                                        fail     
 test-amd64-xcpkern-i386-xl-win                               fail     


------------------------------------------------------------
sg-report-flight on woking.cam.xci-test.com
logs: /home/xc_osstest/logs
images: /home/xc_osstest/images

Logs, config files, etc. are available at
    http://www.chiark.greenend.org.uk/~xensrcts/logs

Test harness code can be found at
    http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary


Not pushing.

------------------------------------------------------------
changeset:   23371:4326bcd88b33
tag:         tip
user:        Tim Deegan <Tim.Deegan@citrix.com>
date:        Mon May 23 18:35:32 2011 +0100
    
    drivers/passthrough: fix error paths in pci_add_device*()
    
    When a device can't be allocated to dom0 by the IOMMU, don't leave
    dom0 in the "domain" field.  It causes pci_remove_device()
    to crash trying to remove the dev from the domain's list of devices
    (and was probably the wrong thing to do anyway).
    
    Signed-off-by: Tim Deegan <Tim.Deegan@citrix.com>
    
    
changeset:   23370:2e6719425265
user:        Keir Fraser <keir@xen.org>
date:        Mon May 23 18:35:04 2011 +0100
    
    drivers/passthrough: Revert 23352:ea48976517af -- incorrect bugfix.
    
    Signed-off-by: Keir Fraser <keir@xen.org>
    
    
changeset:   23369:37c77bacb52a
user:        Keir Fraser <keir@xen.org>
date:        Mon May 23 17:38:28 2011 +0100
    
    Fix Config.mk's cc-option for -Wno-* options.
    
    These disable-warning options are handled specially by GCC:
     (a) they are ignored unless the compiler emits a warning; and
     (b) even then they produce a warning rather than an error
    
    To handle this, modify the test invocation of GCC to compile a
    fragment of code that will always provoke a warning (integer assigned
    to pointer). This works around (a) above.
    
    Then, we grep the compiler's stdout/stderr for the option-under-test,
    the presence of which would indicate an "unrecognized command-line
    option" warning/error. This works around (b) above, letting us
    distinguish between the "integer assigned to pointer" and
    "unrecognized command-line option" warnings.
    
    Signed-off-by: Keir Fraser <keir@xen.org>
    
    
(qemu changes not included)

                 reply	other threads:[~2011-05-24  9:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=osstest-7307-mainreport@xen.org \
    --to=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 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).