[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [xen-unstable-smoke test] 105644: regressions - trouble: blocked/broken/fail/pass

flight 105644 xen-unstable-smoke real [real]

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-amd64-amd64-xl-qemuu-debianhvm-i386 15 guest-localmigrate/x10 fail REGR. 
vs. 105642
 build-armhf                   5 xen-build                fail REGR. vs. 105642

Tests which did not succeed, but are not blocking:
 test-armhf-armhf-xl           1 build-check(1)               blocked  n/a
 test-arm64-arm64-xl-xsm       1 build-check(1)               blocked  n/a
 build-arm64                   5 xen-build                    fail   never pass
 test-amd64-amd64-libvirt     12 migrate-support-check        fail   never pass
 build-arm64-pvops             5 kernel-build                 fail   never pass

version targeted for testing:
 xen                  04dbb71096143b54f8b5e1acfce8d55150609d3f
baseline version:
 xen                  58b4db0832de1ee355a342feea7e1545219bef12

Last test of basis   105642  2017-02-08 16:04:21 Z    0 days
Testing same since   105644  2017-02-08 18:01:23 Z    0 days    1 attempts

People who touched revisions under test:
  Andrew Cooper <andrew.cooper3@xxxxxxxxxx>

 build-amd64                                                  pass    
 build-arm64                                                  fail    
 build-armhf                                                  fail    
 build-amd64-libvirt                                          pass    
 build-arm64-pvops                                            fail    
 test-armhf-armhf-xl                                          blocked 
 test-arm64-arm64-xl-xsm                                      broken  
 test-amd64-amd64-xl-qemuu-debianhvm-i386                     fail    
 test-amd64-amd64-libvirt                                     pass    

sg-report-flight on osstest.test-lab.xenproject.org
logs: /home/logs/logs
images: /home/logs/images

Logs, config files, etc. are available at

Explanation of these reports, and of osstest in general, is at

Test harness code can be found at

Not pushing.

commit 04dbb71096143b54f8b5e1acfce8d55150609d3f
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Tue Feb 7 14:01:29 2017 +0000

    x86/p2m: Stop other vcpus using a nested p2m before clearing it
    Until the IPI has completed, other processors might be running on this 
    p2m object.  clear_domain_page() does not guarantee to make 8-byte atomic
    updates, which means that a pagewalk on a remote processor might encounter a
    partial update.
    This is currently safe as other issues prevents a nested p2m ever being 
    between two cpus (although this is contrary to the original plan).
    Setting p2m->np2m_base to P2M_BASE_EADDR before the IPI ensures that the 
    processors won't continue to use the flushed mappings.
    While modifying this function, remove all the trailing whitespace and tweak
    style in the affected areas.
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Reviewed-by: Tim Deegan <tim@xxxxxxx>
    Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx>

commit 11c397c207dda26084be8a5da5bd78c74b4b3651
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Wed Dec 7 13:52:02 2016 +0000

    x86/time: Adjust init-time handling of pit0_ticks
    There is no need for the volatile cast in the timer interrupt; the compiler
    may not elide the update.  This reduces the generated assembly from a read,
    local modify, write to a single add instruction.
    Drop the memory barriers from timer_irq_works(), as they are not needed.
    pit0_ticks is only modified by timer_interrupt() running on the same CPU, so
    all that is required is a volatile reference to prevent the compiler from
    eliding the second read.
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx>
(qemu changes not included)

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.