All of lore.kernel.org
 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] 6441: regressions - FAIL
Date: Mon, 14 Mar 2011 17:16:09 +0000	[thread overview]
Message-ID: <osstest-6441-mainreport@xen.org> (raw)

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

Regressions :-(

Tests which did not succeed and are blocking:
 test-amd64-amd64-xl-win       5 xen-boot                   fail REGR. vs. 6396
 test-amd64-i386-rhel6hvm-intel  5 xen-boot                 fail REGR. vs. 6396
 test-amd64-i386-win-vcpus1    5 xen-boot                   fail REGR. vs. 6396

Tests which are failing intermittently (not blocking):
 test-amd64-i386-pair          8 xen-boot/dst_host            fail pass in 6413
 test-amd64-i386-pair          7 xen-boot/src_host            fail pass in 6413
 test-amd64-i386-pv            5 xen-boot                     fail pass in 6413
 test-amd64-i386-win           5 xen-boot                     fail pass in 6413
 test-amd64-i386-xl-win-vcpus1  5 xen-boot                    fail pass in 6413
 test-amd64-xcpkern-i386-win   5 xen-boot                     fail pass in 6413
 test-amd64-xcpkern-i386-xl-credit2 11 guest-localmigrate     fail pass in 6413
 test-i386-i386-pair           8 xen-boot/dst_host            fail pass in 6413
 test-i386-i386-pair           7 xen-boot/src_host            fail pass in 6413
 test-i386-i386-win            5 xen-boot                     fail pass in 6413
 test-i386-i386-xl             9 guest-start                  fail pass in 6413
 test-i386-xcpkern-i386-pair   8 xen-boot/dst_host            fail pass in 6413
 test-i386-xcpkern-i386-pair   7 xen-boot/src_host            fail pass in 6413

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-i386-rhel6hvm-amd  8 guest-saverestore            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-xl-win 13 guest-stop                   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                  84bacd800bf8
baseline version:
 xen                  a8fee4ad3ad0

------------------------------------------------------------
People who touched revisions under test:
  Ian Jackson <ian.jackson@eu.citrix.com>
  Jan Beulich <jbeulich@novell.com>
  Stefano Stabellini <stefano.stabellini@eu.citrix.com>
  Wei Gang <gang.wei@intel.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                                            fail     
 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                           fail     
 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                                          fail     
 test-amd64-xcpkern-i386-pair                                 pass     
 test-i386-xcpkern-i386-pair                                  fail     
 test-amd64-amd64-pv                                          pass     
 test-amd64-i386-pv                                           fail     
 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:   23033:84bacd800bf8
tag:         tip
user:        Jan Beulich <jbeulich@novell.com>
date:        Sat Mar 12 13:20:51 2011 +0000
    
    x86/HPET: adjust types
    
    'unsigned int' is better suited as an array index on x86-64.
    
    'u32' produces better code than 'unsigned long' on x86-64, so use the
    former for storing 32-bit values read from the hardware.
    
    this_cpu() uses an implicit smp_processor_id(), and hence using
    per_cpu() when the result of smp_processor_id() is already available
    is more efficient.
    
    Fold one case of cpu_isset()+cpu_clear() into cpu_test_and_clear().
    
    Drop the unused return value of evt_do_broadcast().
    
    Signed-off-by: Jan Beulich <jbeulich@novell.com>
    Acked-by: Wei Gang <gang.wei@intel.com>
    
    
changeset:   23032:ac572e1df261
user:        Jan Beulich <jbeulich@novell.com>
date:        Sat Mar 12 13:20:11 2011 +0000
    
    x86/HPET: use dynamic allocation for hpet_events[]
    
    Typically there are far less than 32 counters available, and hence
    there's no use in wasting the memory on (almost) every system.
    
    Signed-off-by: Jan Beulich <jbeulich@novell.com>
    Acked-by: Wei Gang <gang.wei@intel.com>
    
    
changeset:   23031:5263151fba9b
user:        Jan Beulich <jbeulich@novell.com>
date:        Sat Mar 12 13:19:34 2011 +0000
    
    x86/HPET: cleanup
    
    - separate init and resume code paths (so that the [larger] init parts
      can go init .init.* sections)
    - drop the separate legacy_hpet_event object, as we can easily re-use
      the first slot of hpet_events[] for that purpose (the whole array is
      otherwise unused when the legacy code is being used)
    - use section placement attributes where reasonable
    
    Signed-off-by: Jan Beulich <jbeulich@novell.com>
    Acked-by: Wei Gang <gang.wei@intel.com>
    
    
changeset:   23030:87aa1277eae0
user:        Jan Beulich <jbeulich@novell.com>
date:        Sat Mar 12 13:19:02 2011 +0000
    
    x86/HPET: fix initialization order
    
    At least the legacy path can enter its interrupt handler callout while
    initialization is still in progress - that handler checks whether
    ->event_handler is non-NULL, and hence all other initialization must
    happen before setting this field.
    
    Do the same to the MSI initialization just in case (and to keep the
    code in sync).
    
    Signed-off-by: Jan Beulich <jbeulich@novell.com>
    
    
changeset:   23029:a8fee4ad3ad0
user:        Stefano Stabellini <stefano.stabellini@eu.citrix.com>
date:        Fri Mar 11 18:22:23 2011 +0000
    
    libxl: do not try to use blktap with qdisk
    
    libxl_device_disk_add tries to use blktap when available even for qdisk
    devices, this patch fixes it.
    
    Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
    Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
    Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
    
    
(qemu changes not included)

                 reply	other threads:[~2011-03-14 17:16 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-6441-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 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.