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

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

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

Failures and problems with tests :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-arm64-arm64-xl-xsm         <job status>                 broken
 build-armhf                     <job status>                 broken
 test-amd64-amd64-xl-qemuu-debianhvm-i386    <job status>                broken
 test-amd64-amd64-libvirt        <job status>                 broken
 build-armhf                   4 host-install(4)        broken REGR. vs. 133382
 test-armhf-armhf-xl             <job status>                 broken  in 133436
 test-armhf-armhf-xl        4 host-install(4) broken in 133436 REGR. vs. 133382

Tests which are failing intermittently (not blocking):
 test-arm64-arm64-xl-xsm       4 host-install(4)          broken pass in 133436
 test-amd64-amd64-xl-qemuu-debianhvm-i386 4 host-install(4) broken pass in 
133436

Tests which did not succeed, but are not blocking:
 test-armhf-armhf-xl           1 build-check(1)               blocked  n/a
 test-amd64-amd64-libvirt      4 host-install(4)             broken like 133375
 test-amd64-amd64-libvirt    13 migrate-support-check fail in 133436 never pass
 test-arm64-arm64-xl-xsm     13 migrate-support-check fail in 133436 never pass
 test-arm64-arm64-xl-xsm 14 saverestore-support-check fail in 133436 never pass

version targeted for testing:
 xen                  1c858928009c51178a9c6cac9e42343ee81dfe37
baseline version:
 xen                  e72ecc7615410e5bf1a1c9a4c7772322c16eeb82

Last test of basis   133382  2019-02-22 22:00:38 Z    3 days
Testing same since   133430  2019-02-25 23:00:55 Z    0 days    4 attempts

------------------------------------------------------------
People who touched revisions under test:
  Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
  Julien Grall <julien.grall@xxxxxxx>

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


------------------------------------------------------------
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

broken-job test-arm64-arm64-xl-xsm broken
broken-job build-armhf broken
broken-job test-amd64-amd64-xl-qemuu-debianhvm-i386 broken
broken-job test-amd64-amd64-libvirt broken
broken-step test-arm64-arm64-xl-xsm host-install(4)
broken-step test-amd64-amd64-xl-qemuu-debianhvm-i386 host-install(4)
broken-step test-amd64-amd64-libvirt host-install(4)
broken-step build-armhf host-install(4)
broken-job test-armhf-armhf-xl broken

Not pushing.

------------------------------------------------------------
commit 1c858928009c51178a9c6cac9e42343ee81dfe37
Author: Julien Grall <julien.grall@xxxxxxx>
Date:   Mon Feb 18 10:21:06 2019 +0000

    xen/arm: domain_build: Panic message should end with a newline
    
    Since commit 25eb5eec79 "xen: Fix inconsistent callers of panic()" all
    the panic message should end with a newline. Unfortunately, some
    commits pushed afterwards does not follow the rule.
    
    Modify the offending panic messages to avoid more inconsistency.
    
    Signed-off-by: Julien Grall <julien.grall@xxxxxxx>
    Acked-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Reviewed-by: Stefano Stabellini <sstabellini@xxxxxxxxxx>
    Release-acked-by: Juergen Gross <jgross@xxxxxxxx>

commit cc85de570c7ed91b32f123bef35e4ac2692cbfef
Author: Julien Grall <julien.grall@xxxxxxx>
Date:   Mon Feb 18 10:14:36 2019 +0000

    xen/arm: domain_build: Require the property "cpus" when building a domU
    
    The 3rd argument of function dt_property_read_u32() is only valid when
    the call succeeded. So we cannot assume the value will not be modifed
    in case of failure.
    
    The documentation of Dom0less does not give a default value when the
    property "cpus" is not set. So require the property in the configuration.
    
    Coverity-ID: 1476825
    Signed-off-by: Julien Grall <julien.grall@xxxxxxx>
    Reviewed-by: Stefano Stabellini <sstabellini@xxxxxxxxxx>
    Release-acked-by: Juergen Gross <jgross@xxxxxxxx>

commit 83ba64c3ebf0e8d3834e3e5b79acb2ceb2cd9bba
Author: Julien Grall <julien.grall@xxxxxxx>
Date:   Mon Feb 18 09:42:27 2019 +0000

    xen/arm: psci: Populate arm_smccc_res on PSCI_FEATURES call
    
    Commit 0bc6a68da5 "xen/arm: Replace call_smc with arm_smccc_smc"
    mistakenly forgot to populate arm_smccc_res. So a garbage value was
    used as return value.
    
    Coverity-ID: 1476827
    Signed-off-by: Julien Grall <julien.grall@xxxxxxx>
    Reviewed-by: Stefano Stabellini <sstabellini@xxxxxxxxxx>
    Release-acked-by: Juergen Gross <jgross@xxxxxxxx>
(qemu changes not included)

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