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

[xen-unstable-smoke test] 134140: trouble: blocked/broken/pass

flight 134140 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-xsm                 <job status>                 broken
 build-arm64-xsm               4 host-install(4)        broken REGR. vs. 133991

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                  e88afede8cbc18032bcab49b3a25b472d5516cf5
baseline version:
 xen                  cb70a26f78848fe45f593f7ebc9cfaac760a791b

Last test of basis   133991  2019-03-22 15:00:46 Z    5 days
Failing since        134068  2019-03-25 12:00:51 Z    2 days   12 attempts
Testing same since   134136  2019-03-27 18:00:28 Z    0 days    2 attempts

People who touched revisions under test:
  Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
  Wei Liu <wei.liu2@xxxxxxxxxx>

 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

Explanation of these reports, and of osstest in general, is at

Test harness code can be found at

broken-job build-arm64-xsm broken
broken-step build-arm64-xsm host-install(4)

Not pushing.

commit e88afede8cbc18032bcab49b3a25b472d5516cf5
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Tue Jul 10 13:53:21 2018 +0100

    libx86: Recalculate synthesised cpuid_policy fields when appropriate
    When filling a policy, either from CPUID or an incomming leaf stream,
    recalculate the synthesised vendor value.  All callers are expected to want
    this behaviour.
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx>

commit 1c2c9f85dd36bd908441b37ab73172358509c9b5
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Wed Mar 20 14:56:15 2019 +0000

    tools/libxc: Use x86_cpuid_lookup_vendor() rather than opencoding the logic
    This doesn't address any of the assumptions that "anything which isn't AMD 
    Intel".  This logic is expected to be replaced wholesale with libx86 in the
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx>

commit 00b4f4d0fb75dc183b499e78d1abcb865dbc30d7
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Tue Jul 10 13:53:21 2018 +0100

    x86/cpuid: Drop get_cpu_vendor() completely
    get_cpu_vendor() tries to do a number of things, and ends up doing none of
    them well.
    For calculating the vendor itself, use x86_cpuid_lookup_vendor() which is
    implemented in a far more efficient manner than looping over cpu_devs[].
    For setting up this_cpu, set it up once on the BSP only, rather than
    latest-takes-precident across the APs.  Such a system is probably not going 
    boot, but this feels like a less dangerous course of action.  Adjust the
    printed errors to be more clear in the mismatch case.
    This removes the only user of cpu_dev->c_ident[], so drop that field as 
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx>

commit e72309ffbe7c4e507649c74749f130cda691131c
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Wed Mar 20 14:05:11 2019 +0000

    libx86: Introduce x86_cpuid_lookup_vendor()
    Also introduce constants for the vendor strings in CPUID leaf 0.
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx>

commit 8eed571409a7f81ec9327cfa95d7c298333e22e4
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Tue Mar 26 14:23:03 2019 +0000

    CI: Add a CentOS 6 container and build jobs
    CentOS 6 is probably the most frequently broken build, so adding it to CI
    would be a very good move.
    One problem is that CentOS 6 comes with Python 2.6, and Qemu requires 2.7.
    There appear to be no sensible ways to get Python 2.7 into a CentOS 6
    environments, so modify the build script to skip the Qemu upstream build
    instead.  Additionally, SeaBIOS requires GCC 4.6 or later, so skip it as 
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx>

commit 1316369dca610352cce3aaf76e90db1cce75ed9f
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Fri Mar 22 11:12:28 2019 +0000

    CI: Fix indentation in containerize script
    The script is mostly indented with spaces, but there are three tabs.  Fix 
    up to be consistent.
    No functional change.
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx>
(qemu changes not included)

osstest-output mailing list



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