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

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

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

Failures and problems with tests :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 build-arm64-xsm                 <job status>                 broken
 build-arm64-xsm               4 host-install(4)        broken REGR. vs. 125729

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

version targeted for testing:
 xen                  4c9a6546e4c33ba2b170d5c1d0c340c1dd384ffc
baseline version:
 xen                  ed5f8d9ca47e69e30221c37ec812f2b38af19d83

Last test of basis   125729  2018-08-01 11:00:39 Z    1 days
Testing same since   125741  2018-08-02 10:01:09 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
  Kevin Tian <kevin.tian@xxxxxxxxx>

jobs:
 build-arm64-xsm                                              broken  
 build-amd64                                                  pass    
 build-armhf                                                  pass    
 build-amd64-libvirt                                          pass    
 test-armhf-armhf-xl                                          pass    
 test-arm64-arm64-xl-xsm                                      blocked 
 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
    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 build-arm64-xsm broken
broken-step build-arm64-xsm host-install(4)

Not pushing.

------------------------------------------------------------
commit 4c9a6546e4c33ba2b170d5c1d0c340c1dd384ffc
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Wed Jan 24 16:59:42 2018 +0000

    xen: Remove domain_crash_synchronous() completely
    
    domain_crash_synchronous() is unsafe to use in general as it may leave
    spinlocks held, temporary memory allocated, etc.
    
    With domain_crash_synchronous() removed from the ARM code in 4.11, take the
    opportunity to remove the infrastructure completely by opencoding the 
softirq
    loop in the remaining callsites, all of which are destined for deletion.
    
    None of these sites are at risk of having a pending ioreq to qemu, which 
means
    that the vcpu_end_shutdown_deferral() isn't necessary.
    
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx>
    Reviewed-by: Roger Pau Monné <roger.pau@xxxxxxxxxx>

commit 499a76634d74f4ec663629fe85239e05d0352bb9
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Tue Feb 6 12:01:08 2018 +0000

    x86/vmx: Avoid using domain_crash_syncrhonous() in vmx_vmentry_failure()
    
    There is no need for the syncrhonous varient, as the vmentry failure path 
can
    just return to processing softirqs.
    
    This is in aid of trying to remove domain_crash_syncrhonous() from the
    codebase.
    
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx>
    Acked-by: Kevin Tian <kevin.tian@xxxxxxxxx>

commit 48dbb2dbe9d9f92a2890a15bb48a0598c065b9f8
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Wed Aug 1 12:47:50 2018 +0100

    x86/vmx: Avoid hitting BUG_ON() after EPTP-related domain_crash()
    
    If the EPTP pointer can't be located in the altp2m list, the domain
    is (legitimately) crashed.
    
    Under those circumstances, execution will continue and guarentee to hit the
    BUG_ON(idx >= MAX_ALTP2M) (unfortunately, just out of context).
    
    Return from vmx_vmexit_handler() after the domain_crash(), which also has 
the
    side effect of reentering the scheduler more promptly.
    
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Reviewed-by: Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx>
    Acked-by: Kevin Tian <kevin.tian@xxxxxxxxx>
(qemu changes not included)

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