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

[osstest service owner <osstest-admin@xxxxxxxxxxxxxx>]

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

Regressions :-(

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

Tests which did not succeed, but are not blocking:
 test-arm64-arm64-xl-xsm       1 build-check(1)               blocked  n/a
 test-armhf-armhf-xl           1 build-check(1)               blocked  n/a
 test-amd64-amd64-libvirt      1 build-check(1)               blocked  n/a

version targeted for testing:
 xen                  af09b7d79cb8ae7498882e61efec75486eb69544
baseline version:
 xen                  6c47c37b9b40d6fe40bce8c8fd39135f6d549c8c

Last test of basis   146882  2020-02-11 16:00:54 Z    1 days
Failing since        146893  2020-02-11 20:01:02 Z    1 days   15 attempts
Testing same since   146935  2020-02-12 11:06:10 Z    0 days    9 attempts

------------------------------------------------------------
People who touched revisions under test:
  Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
  Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
  Jan Beulich <jbeulich@xxxxxxxx>
  Juergen Gross <jgross@xxxxxxxx>
  Julien Grall <julien@xxxxxxx>
  Roger Pau Monné <roger.pau@xxxxxxxxxx>

jobs:
 build-arm64-xsm                                              fail    
 build-amd64                                                  pass    
 build-armhf                                                  fail    
 build-amd64-libvirt                                          fail    
 test-armhf-armhf-xl                                          blocked 
 test-arm64-arm64-xl-xsm                                      blocked 
 test-amd64-amd64-xl-qemuu-debianhvm-amd64                    pass    
 test-amd64-amd64-libvirt                                     blocked 


------------------------------------------------------------
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 af09b7d79cb8ae7498882e61efec75486eb69544
Author: Juergen Gross <jgross@xxxxxxxx>
Date:   Wed Feb 12 10:55:06 2020 +0100

    xen: remove empty softirq_init()
    
    softirq_init() is empty since Xen 4.1. Remove it together with its call
    sites.
    
    Signed-off-by: Juergen Gross <jgross@xxxxxxxx>
    Acked-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>

commit 66b282bbb1aa64a3d7a6f7d705cf10ba844cd611
Author: Jan Beulich <jbeulich@xxxxxxxx>
Date:   Wed Feb 12 10:54:08 2020 +0100

    AMD/IOMMU: drop redundant code
    
    The level 1 special exit path is unnecessary in iommu_pde_from_dfn() -
    the subsequent code takes care of this case quite fine.
    
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>

commit 6827bea2b3b99153821b8b7446bdced27f720188
Author: Jan Beulich <jbeulich@xxxxxxxx>
Date:   Wed Feb 12 10:52:20 2020 +0100

    dom0-build: fix build with clang5
    
    With non-empty CONFIG_DOM0_MEM clang5 produces
    
    dom0_build.c:344:24: error: use of logical '&&' with constant operand 
[-Werror,-Wconstant-logical-operand]
        if ( !dom0_mem_set && CONFIG_DOM0_MEM[0] )
                           ^  ~~~~~~~~~~~~~~~~~~
    dom0_build.c:344:24: note: use '&' for a bitwise operation
        if ( !dom0_mem_set && CONFIG_DOM0_MEM[0] )
                           ^~
                           &
    dom0_build.c:344:24: note: remove constant to silence this warning
        if ( !dom0_mem_set && CONFIG_DOM0_MEM[0] )
                          ~^~~~~~~~~~~~~~~~~~~~~
    1 error generated.
    
    Obviously neither of the two suggestions are an option here. Oddly
    enough swapping the operands of the && helps, while e.g. casting or
    parenthesizing doesn't. Another workable variant looks to be the use of
    !! on the constant.
    
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Acked-by: Julien Grall <julien@xxxxxxx>
    Acked-by: Roger Pau Monné <roger.pau@xxxxxxxxxx>

commit 1b3cec69bf300e012a0269f0a4f28cca1ebf22c9
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Wed Feb 5 15:25:21 2020 +0000

    tools/libxl: Combine legacy CPUID handling logic
    
    While we are in the process of overhauling boot time CPUID/MSR handling, the
    existing logic is going to have to remain in roughly this form for backwards
    compatibility.
    
    Fold libxl__cpuid_apply_policy() and libxl__cpuid_set() together into a 
single
    libxl__cpuid_legacy() to reduce the complexity for callers.
    
    No functional change.
    
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>

commit dacb80f9757c011161cec6609f39837c9ea8caa8
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Wed Jan 8 12:53:49 2020 +0000

    tools/libxl: Remove libxl_cpuid_{set,apply_policy}() from the API
    
    These functions should never have been exposed.  They don't have external
    users, and can't usefully be used for several reasons.
    
    Move libxl_cpuid_{set,apply_policy}() to being internal functions, and leave
    an equivalent of the nop stubs in the API for caller compatibility.
    
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
(qemu changes not included)

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