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

[xen-unstable-smoke test] 96182: regressions - FAIL

flight 96182 xen-unstable-smoke real [real]

Regressions :-(

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

Tests which did not succeed, but are not blocking:
 test-amd64-amd64-libvirt     12 migrate-support-check        fail   never pass

version targeted for testing:
 xen                  9808c130f04ff331aca23beee262f3d83eb46e55
baseline version:
 xen                  6a35f1e1fb03bbb957828f9f2cf8bfc47df95ee6

Last test of basis    96177  2016-06-23 13:02:08 Z    0 days
Testing same since    96182  2016-06-23 16:07:29 Z    0 days    1 attempts

People who touched revisions under test:
  Dirk Behme <dirk.behme@xxxxxxxxxxxx>
  Jan Beulich <jbeulich@xxxxxxxx>
  Julien Grall <julien.grall@xxxxxxx>
  Kevin Tian <kevin.tian@xxxxxxxxx>
  Stefano Stabellini <sstabellini@xxxxxxxxxx>

 build-amd64                                                  pass    
 build-armhf                                                  pass    
 build-amd64-libvirt                                          pass    
 test-armhf-armhf-xl                                          fail    
 test-amd64-amd64-xl-qemuu-debianhvm-i386                     pass    
 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 9808c130f04ff331aca23beee262f3d83eb46e55
Author: Dirk Behme <dirk.behme@xxxxxxxxxxxx>
Date:   Wed Jun 22 13:49:07 2016 +0200

    xen/arm: drivers: scif: Don't overwrite firmware settings
    Besides the 14MHz external clock, the SCIF might be clocked by an
    internal 66MHz clock. If this is the case, the current clock source
    selection breaks this configuration. Same for the settings done by
    the firmware for data bits, stop bits and parity.
    Completely drop this and rely on the settings done by the firmware.
    Signed-off-by: Dirk Behme <dirk.behme@xxxxxxxxxxxx>
    Reviewed-by: Julien Grall <julien.grall@xxxxxxx>
    Signed-off-by: Stefano Stabellini <sstabellini@xxxxxxxxxx>

commit 892a43cd9996a45875de14c06828dea859039430
Author: Dirk Behme <dirk.behme@xxxxxxxxxxxx>
Date:   Wed Jun 22 13:49:06 2016 +0200

    xen/arm: drivers: scif: Remove dead code
    The two struct members baud and clock_hz are in the end read only
    variables nowhere used for anything useful. Removing them makes
    the code much simpler without changing any functionality.
    Signed-off-by: Dirk Behme <dirk.behme@xxxxxxxxxxxx>
    Reviewed-by: Julien Grall <julien.grall@xxxxxxx>
    Signed-off-by: Stefano Stabellini <sstabellini@xxxxxxxxxx>

commit 3d5cb5a81f8c68e74be4074db1777741f3059409
Author: Julien Grall <julien.grall@xxxxxxx>
Date:   Thu Jun 23 17:50:19 2016 +0200

    arm: rename gmfn_to_mfn to gfn_to_mfn and use gfn/mfn typesafe
    The correct acronym for a guest physical frame is gfn. Also use
    the recently introduced typesafe gfn/mfn to avoid mixing the two
    different kind of frame.
    Signed-off-by: Julien Grall <julien.grall@xxxxxxx>
    Acked-by: Jan Beulich <jbeulich@xxxxxxxx>
    Acked-by: Stefano Stabellini <sstabellini@xxxxxxxxxx>

commit b45a4f1ed6c865fc1222d71fc82e4b61771b261b
Author: Jan Beulich <jbeulich@xxxxxxxx>
Date:   Thu Jun 23 17:48:45 2016 +0200

    x86emul: support MOVBE and CRC32
    The former in an attempt to at least gradually support all simple data
    movement instructions. The latter just because it shares the opcode
    with the former.
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>

commit d86ad7cb287b5ea05cfee20cdd277005d771886f
Author: Jan Beulich <jbeulich@xxxxxxxx>
Date:   Thu Jun 23 17:47:44 2016 +0200

    VMX: ensure MSR index enum and array remain in sync
    ... by using dedicated initializers. Also add an ASSERT() to make sure
    unintentional addition of holes to the array gets noticed. Ditch
    MSR_INDEX_SIZE as redundant with VMX_MSR_COUNT.
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Acked-by: Kevin Tian <kevin.tian@xxxxxxxxx>

commit 3528b5b4c3b1695ecc7af5622b32042aafbdf6f4
Author: Jan Beulich <jbeulich@xxxxxxxx>
Date:   Thu Jun 23 17:46:55 2016 +0200

    VMX: use non-atomic bitops to manage MSR state
    All host_msr_state accesses are solely on the owning CPU, and all
    guest_msr_state ones solely when the vCPU is current or being switched
    to. This, btw, is also in line with the use of find_first_set_bit()
    (which would be bogus if ->flags could get updated behind its back).
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Acked-by: Kevin Tian <kevin.tian@xxxxxxxxx>
(qemu changes not included)

osstest-output mailing list



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