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

[Xen-devel] [xen-unstable-smoke test] 146081: regressions - FAIL



flight 146081 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/146081/

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 build-arm64-xsm               6 xen-build                fail REGR. vs. 146048
 build-armhf                   6 xen-build                fail REGR. vs. 146048

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
 test-amd64-amd64-libvirt     13 migrate-support-check        fail   never pass

version targeted for testing:
 xen                  c7de94fd6ec5aba53ce5b8fd6ceb6031c53bb28d
baseline version:
 xen                  03bfe526ecadc86f31eda433b91dc90be0563919

Last test of basis   146048  2020-01-13 14:00:30 Z    1 days
Failing since        146068  2020-01-14 12:00:48 Z    0 days    2 attempts
Testing same since   146081  2020-01-14 15:00:50 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
  Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
  Jan Beulich <jbeulich@xxxxxxxx>
  Julien Grall <julien@xxxxxxx>
  Paul Durrant <pdurrant@xxxxxxxxxx>
  Stefano Stabellini <sstabellini@xxxxxxxxxx>
  Wei Liu <wl@xxxxxxx>

jobs:
 build-arm64-xsm                                              fail    
 build-amd64                                                  pass    
 build-armhf                                                  fail    
 build-amd64-libvirt                                          pass    
 test-armhf-armhf-xl                                          blocked 
 test-arm64-arm64-xl-xsm                                      blocked 
 test-amd64-amd64-xl-qemuu-debianhvm-amd64                    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
    http://logs.test-lab.xenproject.org/osstest/logs

Explanation of these reports, and of osstest in general, is at
    http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master
    http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master

Test harness code can be found at
    http://xenbits.xen.org/gitweb?p=osstest.git;a=summary


Not pushing.

------------------------------------------------------------
commit c7de94fd6ec5aba53ce5b8fd6ceb6031c53bb28d
Author: Julien Grall <julien@xxxxxxx>
Date:   Thu Dec 19 08:12:21 2019 +0000

    xen/arm: Place a speculation barrier sequence following an eret instruction
    
    Some CPUs can speculate past an ERET instruction and potentially perform
    speculative accesses to memory before processing the exception return.
    Since the register state is often controlled by lower privilege level
    at the point of an ERET, this could potentially be used as part of a
    side-channel attack.
    
    Newer CPUs may implement a new SB barrier instruction which acts
    as an architected speculation barrier. For current CPUs, the sequence
    DSB; ISB is known to prevent speculation.
    
    The latter sequence is heavier than SB but it would never be executed
    (this is speculation after all!).
    
    Introduce a new macro 'sb' that could be used when a speculation barrier
    is required. For now it is using dsb; isb but this could easily be
    updated to cater SB in the future.
    
    This is XSA-312.
    
    Signed-off-by: Julien Grall <julien@xxxxxxx>

commit f1cf75c2d18fcfc96744ef0380a757e8f91705a6
Author: Julien Grall <julien@xxxxxxx>
Date:   Mon Jan 13 22:05:31 2020 +0000

    docs/misc: livepatch: Escape backslash
    
    pandoc is currently failing to generate the pdf with the following
    error:
    ! Undefined control sequence.
    l.1048   metadata string format is: key=value\0
    
    In this case, we want to print \0 so we need to backslash-escape the
    first character.
    
    Interestingly pandoc will not complain when creating html and will just
    ignore \0 completely.
    
    Fixes: 5083e0ff93 ("livepatch: Add metadata runtime retrieval mechanism")
    Signed-off-by: Julien Grall <julien@xxxxxxx>
    Reviewed-by: Ross Lagerwall <ross.lagerwall@xxxxxxxxxx>
    Reviewed-by: Pawel Wieczorkiewicz <wipawel@xxxxxxxxx>

commit 9c8705f8fe5bfb75a6a00163308d297059b61f6a
Author: Julien Grall <julien@xxxxxxx>
Date:   Sat Jan 11 00:03:44 2020 +0000

    docs/misc: pvcalls: Verbatim block should be indented with 4 spaces
    
    At the moment, the diagram is only indented with 2 spaces. So pandoc
    will try to badly interpret it and not display it correctly.
    
    Fix it by indenting all the block by 4 spaces (i.e an extra 2 spaces).
    
    Fixes: d661611d08 ("docs/markdown: Switch to using pandoc, and fix 
underscore escaping")
    Signed-off-by: Julien Grall <julien@xxxxxxx>
    Acked-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Acked-by: Stefano Stabellini <sstabellini@xxxxxxxxxx>

commit 101398e1f81ca7a4f45ab54c4d0c4fee7b3a7bd8
Author: Paul Durrant <pdurrant@xxxxxxxxxx>
Date:   Thu Jan 9 11:15:05 2020 +0000

    tools/Rules.mk: fix distclean
    
    Running 'make distclean' under tools will currently result in:
    
    tools/Rules.mk:245: *** You have to run ./configure before building or 
installing the tools.  Stop.
    
    This patch adds 'distclean', 'subdir-distclean%' and 'subdir-clean%' to
    no-configure-targets, which allows 'make distclean' to run to completion.
    
    Fixes: 00691c6c (tools: Allow to make *-dir-force-update without 
./configure)
    Signed-off-by: Paul Durrant <pdurrant@xxxxxxxxxx>
    Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
    Acked-by: Wei Liu <wl@xxxxxxx>

commit 892b9dcebdb7f646657e11cfdd95a385107bbefa
Author: Jan Beulich <jbeulich@xxxxxxxx>
Date:   Tue Jan 14 12:03:47 2020 +0100

    IRQ: u16 is too narrow for an event channel number
    
    FIFO event channels allow ports up to 2^17, so we need to use a wider
    field in struct pirq. Move "masked" such that it may share the 8-byte
    slot with struct arch_pirq on 64-bit arches, rather than leaving a
    7-byte hole in all cases.
    
    Take the opportunity and also add a comment regarding "arch" placement
    within the structure.
    
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Acked-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
(qemu changes not included)

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

 


Rackspace

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