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

[Xen-devel] [libvirt test] 78228: regressions - FAIL

flight 78228 libvirt real [real]

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-armhf-armhf-libvirt-xsm  6 xen-boot                  fail REGR. vs. 78148

Regressions which are regarded as allowable (not blocking):
 test-amd64-amd64-libvirt-vhd  9 debian-di-install            fail   like 78148

Tests which did not succeed, but are not blocking:
 test-armhf-armhf-libvirt-raw 13 guest-saverestore            fail   never pass
 test-armhf-armhf-libvirt-raw 11 migrate-support-check        fail   never pass
 test-amd64-i386-libvirt-xsm  12 migrate-support-check        fail   never pass
 test-armhf-armhf-libvirt     14 guest-saverestore            fail   never pass
 test-armhf-armhf-libvirt     12 migrate-support-check        fail   never pass
 test-amd64-amd64-libvirt     12 migrate-support-check        fail   never pass
 test-amd64-i386-libvirt      12 migrate-support-check        fail   never pass
 test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check 
fail never pass
 test-amd64-amd64-libvirt-xsm 12 migrate-support-check        fail   never pass
 test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check 
fail never pass
 test-armhf-armhf-libvirt-qcow2 11 migrate-support-check        fail never pass
 test-armhf-armhf-libvirt-qcow2 13 guest-saverestore            fail never pass

version targeted for testing:
 libvirt              8f0a15727fe04b9051010f793df3fb55e5e71f22
baseline version:
 libvirt              d6d7e2885badc24e224265283fd59f4c1c492ff9

Last test of basis    78148  2016-01-15 04:22:21 Z    1 days
Testing same since    78228  2016-01-16 04:22:23 Z    0 days    1 attempts

People who touched revisions under test:
  Jiri Denemark <jdenemar@xxxxxxxxxx>
  Michal Privoznik <mprivozn@xxxxxxxxxx>
  Yaniv Kaul <ykaul@xxxxxxxxxx>

 build-amd64-xsm                                              pass    
 build-armhf-xsm                                              pass    
 build-i386-xsm                                               pass    
 build-amd64                                                  pass    
 build-armhf                                                  pass    
 build-i386                                                   pass    
 build-amd64-libvirt                                          pass    
 build-armhf-libvirt                                          pass    
 build-i386-libvirt                                           pass    
 build-amd64-pvops                                            pass    
 build-armhf-pvops                                            pass    
 build-i386-pvops                                             pass    
 test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm           pass    
 test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm            pass    
 test-amd64-amd64-libvirt-xsm                                 pass    
 test-armhf-armhf-libvirt-xsm                                 fail    
 test-amd64-i386-libvirt-xsm                                  pass    
 test-amd64-amd64-libvirt                                     pass    
 test-armhf-armhf-libvirt                                     fail    
 test-amd64-i386-libvirt                                      pass    
 test-amd64-amd64-libvirt-pair                                pass    
 test-amd64-i386-libvirt-pair                                 pass    
 test-armhf-armhf-libvirt-qcow2                               fail    
 test-armhf-armhf-libvirt-raw                                 fail    
 test-amd64-amd64-libvirt-vhd                                 fail    

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 8f0a15727fe04b9051010f793df3fb55e5e71f22
Author: Jiri Denemark <jdenemar@xxxxxxxxxx>
Date:   Fri Jan 15 16:34:37 2016 +0100

    security: Do not restore labels on device tree binary
    A device tree binary file specified by /domain/os/dtb element is a
    read-only resource similar to kernel and initrd files. We shouldn't
    restore its label when destroying a domain to avoid breaking other
    domains configure with the same device tree.
    Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx>

commit 68acc701bd449481e3206723c25b18fcd3d261b7
Author: Jiri Denemark <jdenemar@xxxxxxxxxx>
Date:   Fri Jan 15 10:55:58 2016 +0100

    security: Do not restore kernel and initrd labels
    Kernel/initrd files are essentially read-only shareable images and thus
    should be handled in the same way. We already use the appropriate label
    for kernel/initrd files when starting a domain, but when a domain gets
    destroyed we would remove the labels which would make other running
    domains using the same files very unhappy.
    Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx>

commit c1e0df918b2307b64b7c165bcf62119e628a9048
Author: Yaniv Kaul <ykaul@xxxxxxxxxx>
Date:   Fri Jan 15 08:33:49 2016 +0100

    qemu: Print better warning in qemuAgentNotifyEvent
    We have this function qemuAgentNotifyEvent() which is supposed to
    be called from thread pool responsible for processing qemu
    monitor events. The function then should wake up other thread
    that is waiting for a guest to shutdown or reboot. However, if we
    have received a different error a warning is printed out. This
    warning lacks info on which event is expected.
    Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

Xen-devel mailing list



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