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

[Xen-devel] [xen-unstable-smoke test] 113066: trouble: broken/pass

flight 113066 xen-unstable-smoke real [real]

Failures and problems with tests :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 build-arm64                     <job status>                 broken
 test-arm64-arm64-xl-xsm         <job status>                 broken
 build-arm64-pvops               <job status>                 broken

Tests which did not succeed, but are not blocking:
 test-arm64-arm64-xl-xsm       1 build-check(1)               blocked  n/a
 build-arm64-pvops             2 hosts-allocate              broken like 113039
 build-arm64-pvops             3 capture-logs                broken like 113039
 build-arm64                   2 hosts-allocate              broken like 113039
 build-arm64                   3 capture-logs                broken like 113039
 test-armhf-armhf-xl          13 migrate-support-check        fail   never pass
 test-armhf-armhf-xl          14 saverestore-support-check    fail   never pass
 test-amd64-amd64-libvirt     13 migrate-support-check        fail   never pass

version targeted for testing:
 xen                  150dd3946c521a9257c4dd97e6190c6b0df680d3
baseline version:
 xen                  6dfb43d6f2cd8ea6274d203ca00ecfc7c565f11a

Last test of basis   113039  2017-09-04 15:02:08 Z    1 days
Failing since        113052  2017-09-05 13:01:29 Z    0 days    8 attempts
Testing same since   113055  2017-09-05 19:02:28 Z    0 days    6 attempts

People who touched revisions under test:
  Alexandru Isaila <aisaila@xxxxxxxxxxxxxxx>
  Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
  Jan Beulich <jbeulich@xxxxxxxx>
  Olaf Hering <olaf@xxxxxxxxx>
  Tamas K Lengyel <tamas@xxxxxxxxxxxxx>
  Wei Liu <wei.liu2@xxxxxxxxxx>

 build-amd64                                                  pass    
 build-arm64                                                  broken  
 build-armhf                                                  pass    
 build-amd64-libvirt                                          pass    
 build-arm64-pvops                                            broken  
 test-armhf-armhf-xl                                          pass    
 test-arm64-arm64-xl-xsm                                      broken  
 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

broken-job build-arm64 broken
broken-job test-arm64-arm64-xl-xsm broken
broken-job build-arm64-pvops broken
broken-step build-arm64-pvops hosts-allocate
broken-step build-arm64-pvops capture-logs
broken-step build-arm64 hosts-allocate
broken-step build-arm64 capture-logs

Not pushing.

commit 150dd3946c521a9257c4dd97e6190c6b0df680d3
Author: Olaf Hering <olaf@xxxxxxxxx>
Date:   Tue Sep 5 11:03:38 2017 +0200

    libxc/bitops: correct comment for bitmap_size
    The returned value represents now units of bytes instead of longs.
    Fixes commit 11d0044a16 ("tools/libxc: Modify bitmap operations to
    take void pointers").
    Signed-off-by: Olaf Hering <olaf@xxxxxxxxx>
    Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx>

commit 15e4dd5e866b43bbc2d438034445c6582db1d3de
Author: Alexandru Isaila <aisaila@xxxxxxxxxxxxxxx>
Date:   Wed Aug 30 12:04:00 2017 +0300

    common/vm_event: Initialize vm_event lists on domain creation
    The patch splits the vm_event into three structures:vm_event_share,
    vm_event_paging, vm_event_monitor. The allocation for the
    structure is moved to vm_event_enable so that it can be
    allocated/init when needed and freed in vm_event_disable.
    Signed-off-by: Alexandru Isaila <aisaila@xxxxxxxxxxxxxxx>
    Acked-by: Jan Beulich <jbeulich@xxxxxxxx>
    Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx>
    Acked-by: Tamas K Lengyel <tamas@xxxxxxxxxxxxx>

commit eb4e638a474792137414f03409e78477810c3436
Author: Jan Beulich <jbeulich@xxxxxxxx>
Date:   Tue Sep 5 17:32:43 2017 +0200

    x86emul: correct EVEX decoding
    While these are latent issues only for now, correct them right away:
    - unnamed (in the SDM) EVEX bits need to be set/clear respectively
    - EVEX.V' (called RX in our code) needs to uniformly be 1 in non-64-bit
    - EXEX.R' (called R in our code) is uniformly being ignored in
      non-64-bit modes.
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>

commit a6488965ca3ec30f2e0b7022b539bba78c2aeede
Author: Jan Beulich <jbeulich@xxxxxxxx>
Date:   Tue Sep 5 17:32:05 2017 +0200

    x86emul: correct VEX.L handling for VCVT{,T}S{S,D}2SI
    Recent changes to the SDM (and XED) have made clear that older hardware
    raising #UD when the bit is set was really an erratum. Generalize the
    so far AMD-only override.
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>

commit 9c2babd05a213f8802e3cc1c64a2af932b5cbd7d
Author: Jan Beulich <jbeulich@xxxxxxxx>
Date:   Tue Sep 5 17:31:01 2017 +0200

    x86emul: correct VEX.W handling for non-64-bit VPINSRD
    Going though the XED commits from the last couple of months made me
    notice that VPINSRD, other than VPEXTRD, does not clear VEX.W for non-
    64-bit modes, leading to an insertion of stray 32-bits of zero in case
    the original instruction had the bit set.
    Also remove a pointless fall-through in VPEXTRW handling, bringing
    things in line with VPINSRW.
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>

commit 4d3f0fde471e7588ce512eaff1abdab209d8cd4b
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Tue Sep 5 09:40:58 2017 +0100

    x86/emul: Fix the handling of unimplemented Grp7 instructions
    Grp7 is abnormally complicated to decode, even by x86's standards, with
    {s,l}msw being the problematic cases.
    Previously, any value which fell through the first switch statement (looking
    for instructions with entirely implicit operands) would be interpreted by 
    second switch statement (handling instructions with memory operands).
    Unimplemented instructions would then hit the #UD case for having a 
    operand, rather than taking the cannot_emulate path.
    Consolidate the two switch statements into a single one, using ranges to 
    the instructions with memory operands.
    Reported-by: Petre Pircalabu <ppircalabu@xxxxxxxxxxxxxxx>
    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®.