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] 7034: trouble: blocked/broken/fail/pass
Date: Tue, 10 May 2011 16:21:33 +0100	[thread overview]
Message-ID: <osstest-7034-mainreport@xen.org> (raw)

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

Failures and problems with tests :-(

Tests which did not succeed and are blocking:
 build-i386                    2 host-install(2)              broken

Tests which are failing intermittently (not blocking):
 build-i386-oldkern            4 xen-build                    fail pass in 7028
 test-amd64-i386-pair          6 xen-install/dst_host         fail pass in 7028
 test-amd64-i386-pair          5 xen-install/src_host         fail pass in 7028
 test-amd64-i386-pv            4 xen-install                  fail pass in 7028
 test-amd64-i386-rhel6hvm-amd  4 xen-install                  fail pass in 7028
 test-amd64-i386-rhel6hvm-intel  4 xen-install                fail pass in 7028
 test-amd64-i386-win-vcpus1    4 xen-install                  fail pass in 7028
 test-amd64-i386-win           4 xen-install                  fail pass in 7028
 test-amd64-i386-xl-credit2    4 xen-install                  fail pass in 7028
 test-amd64-i386-xl-multivcpu  4 xen-install                  fail pass in 7028
 test-amd64-i386-xl-win-vcpus1  4 xen-install                 fail pass in 7028
 test-amd64-i386-xl            4 xen-install                  fail pass in 7028
 test-amd64-xcpkern-i386-pair  6 xen-install/dst_host         fail pass in 7028
 test-amd64-xcpkern-i386-pair  5 xen-install/src_host         fail pass in 7028
 test-amd64-xcpkern-i386-pv    4 xen-install                  fail pass in 7028
 test-amd64-xcpkern-i386-rhel6hvm-amd  4 xen-install          fail pass in 7028
 test-amd64-xcpkern-i386-rhel6hvm-intel  4 xen-install        fail pass in 7028
 test-amd64-xcpkern-i386-win   4 xen-install                  fail pass in 7028
 test-amd64-xcpkern-i386-xl-credit2  4 xen-install            fail pass in 7028
 test-amd64-xcpkern-i386-xl-multivcpu  4 xen-install          fail pass in 7028
 test-amd64-xcpkern-i386-xl-win  4 xen-install                fail pass in 7028
 test-amd64-xcpkern-i386-xl    4 xen-install                  fail pass in 7028

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-i386-i386-pair           1 xen-build-check(1)           blocked  n/a
 test-i386-i386-pv             1 xen-build-check(1)           blocked  n/a
 test-i386-i386-win            1 xen-build-check(1)           blocked  n/a
 test-i386-i386-xl-win         1 xen-build-check(1)           blocked  n/a
 test-i386-i386-xl             1 xen-build-check(1)           blocked  n/a
 test-i386-xcpkern-i386-pair   1 xen-build-check(1)           blocked  n/a
 test-i386-xcpkern-i386-pv     1 xen-build-check(1)           blocked  n/a
 test-i386-xcpkern-i386-win    1 xen-build-check(1)           blocked  n/a
 test-i386-xcpkern-i386-xl     1 xen-build-check(1)           blocked  n/a

version targeted for testing:
 xen                  19452acd2304
baseline version:
 xen                  4b0692880dfa

------------------------------------------------------------
People who touched revisions under test:
  Aravindh Puthiyaparambil <aravindh@virtuata.com>
  Ian Campbell <Ian.Campbell@eu.citrix.com>
  Ian Jackson <ian.jackson@eu.citrix.com>
  Jacob Shin <jacob.shin@amd.com>
  Jan Beulich <jbeulich@novell.com>
  Keir Fraser <keir@xen.org>
  Liu, Jinsong <jinsong.liu@intel.com>
  Olaf Hering <olaf@aepfle.de>
  Tim Deegan <Tim.Deegan@citrix.com>
  Wei Huang  <wei.huang2@amd.com>
  Wei Huang <wei.huang2@amd.com>
------------------------------------------------------------

jobs:
 build-i386-xcpkern                                           pass     
 build-amd64                                                  pass     
 build-i386                                                   broken   
 build-amd64-oldkern                                          pass     
 build-i386-oldkern                                           fail     
 build-amd64-pvops                                            pass     
 build-i386-pvops                                             pass     
 test-amd64-amd64-xl                                          pass     
 test-amd64-i386-xl                                           fail     
 test-i386-i386-xl                                            blocked  
 test-amd64-xcpkern-i386-xl                                   fail     
 test-i386-xcpkern-i386-xl                                    blocked  
 test-amd64-i386-rhel6hvm-amd                                 fail     
 test-amd64-xcpkern-i386-rhel6hvm-amd                         fail     
 test-amd64-i386-xl-credit2                                   fail     
 test-amd64-xcpkern-i386-xl-credit2                           fail     
 test-amd64-i386-rhel6hvm-intel                               fail     
 test-amd64-xcpkern-i386-rhel6hvm-intel                       fail     
 test-amd64-i386-xl-multivcpu                                 fail     
 test-amd64-xcpkern-i386-xl-multivcpu                         fail     
 test-amd64-amd64-pair                                        pass     
 test-amd64-i386-pair                                         fail     
 test-i386-i386-pair                                          blocked  
 test-amd64-xcpkern-i386-pair                                 fail     
 test-i386-xcpkern-i386-pair                                  blocked  
 test-amd64-amd64-pv                                          pass     
 test-amd64-i386-pv                                           fail     
 test-i386-i386-pv                                            blocked  
 test-amd64-xcpkern-i386-pv                                   fail     
 test-i386-xcpkern-i386-pv                                    blocked  
 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                                           blocked  
 test-amd64-xcpkern-i386-win                                  fail     
 test-i386-xcpkern-i386-win                                   blocked  
 test-amd64-amd64-xl-win                                      fail     
 test-i386-i386-xl-win                                        blocked  
 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.

(No revision log; it would be 369 lines long.)

                 reply	other threads:[~2011-05-10 15:21 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-7034-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).