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

[Xen-devel] [xen-unstable-smoke test] 124738: trouble: blocked/broken/queued/running

flight 124738 xen-unstable-smoke running [real]

Failures and problems with tests :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 build-amd64                     <job status>                 broken
 build-arm64-xsm                 <job status>                 broken
 build-armhf                     <job status>                 broken
 build-arm64-pvops               <job status>                 broken
 build-armhf-pvops               <job status>                 broken
 build-arm64-xsm               4 host-install(4)        broken REGR. vs. 124502
 build-amd64                   4 host-install(4)        broken REGR. vs. 124502
 build-armhf                   4 host-install(4)        broken REGR. vs. 124502
 test-amd64-amd64-libvirt        <none executed>              queued
 test-amd64-amd64-xl-qemuu-debianhvm-i386    <none executed>             queued
 build-amd64-pvops             3 syslog-server                running
 build-amd64-pvops             4 host-install(4)              running

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
 build-amd64-libvirt           1 build-check(1)               blocked  n/a
 build-armhf-pvops             4 host-install(4)       broken baseline untested
 build-arm64-pvops             4 host-install(4)       broken baseline untested

version targeted for testing:
 xen                  23839a0fa0bbe78c174cd2bb49083e153f0f99df
baseline version:
 xen                  437211cb696515ee5bd5dae0ab72866c9f382a33

Last test of basis   124502  2018-06-21 10:00:31 Z    7 days
Failing since        124698  2018-06-25 15:00:35 Z    3 days    2 attempts
Testing same since                          (not found)         0 attempts

People who touched revisions under test:
  Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
  Jan Beulich <jbeulich@xxxxxxxx>
  Olaf Hering <olaf@xxxxxxxxx>
  Paul Durrant <paul.durrant@xxxxxxxxxx>
  Roger Pau Monné <roger.pau@xxxxxxxxxx>
  Wei Liu <wei.liu2@xxxxxxxxxx>

 build-arm64-xsm                                              broken  
 build-amd64                                                  broken  
 build-armhf                                                  broken  
 build-amd64-libvirt                                          blocked 
 build-amd64-pvops                                            running 
 build-arm64-pvops                                            broken  
 build-armhf-pvops                                            broken  
 test-armhf-armhf-xl                                          blocked 
 test-arm64-arm64-xl-xsm                                      blocked 
 test-amd64-amd64-xl-qemuu-debianhvm-i386                     queued  
 test-amd64-amd64-libvirt                                     queued  

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 test-amd64-amd64-libvirt queued
broken-job build-amd64 broken
broken-job test-amd64-amd64-xl-qemuu-debianhvm-i386 queued
broken-job build-arm64-xsm broken
broken-job build-armhf broken
broken-step build-arm64-xsm host-install(4)
broken-step build-amd64 host-install(4)
broken-step build-armhf host-install(4)
broken-job build-arm64-pvops broken
broken-job build-armhf-pvops broken
broken-step build-armhf-pvops host-install(4)
broken-step build-arm64-pvops host-install(4)

Not pushing.

commit 23839a0fa0bbe78c174cd2bb49083e153f0f99df
Author: Jan Beulich <jbeulich@xxxxxxxx>
Date:   Tue Jun 26 15:23:08 2018 +0200

    x86/EFI: further correct FPU state handling around runtime calls
    We must not leave a vCPU with CR0.TS clear when it is not in fully eager
    mode and has not touched non-lazy state. Instead of adding a 3rd
    invocation of stts() to vcpu_restore_fpu_eager(), consolidate all of
    them into a single one done at the end of the function.
    Rename the function at the same time to better reflect its purpose, as
    the patches touches all of its occurences anyway.
    The new function parameter is not really well named, but
    "need_stts_if_not_fully_eager" seemed excessive to me.
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Reviewed-by: Paul Durrant <paul.durrant@xxxxxxxxxx>

commit bbc721a82c9480e8083ffe315505af072b43b12f
Author: Olaf Hering <olaf@xxxxxxxxx>
Date:   Thu May 17 16:29:57 2018 +0200

    libxl: fix return code in qmp_synchronous_send
    Use error code from libxl namespace, a plain -1 is not valid in this 
    Signed-off-by: Olaf Hering <olaf@xxxxxxxxx>
    Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx>

commit 22bf5be3237cb482a2ffd772ffd20ce37285eebf
Author: Olaf Hering <olaf@xxxxxxxxx>
Date:   Mon Jun 18 14:55:36 2018 +0200

    stubdom/vtpm: fix memcmp in TPM_ChangeAuthAsymFinish
    gcc8 spotted this error:
    error: 'memcmp' reading 20 bytes from a region of size 8 
    Signed-off-by: Olaf Hering <olaf@xxxxxxxxx>
    Reviewed-by: Samuel Thibault <samuel.thibault@xxxxxxxxxxxx>

commit e8e58be2b77708fd4d6ba6bca3f70bc507fde4be
Author: Roger Pau Monné <roger.pau@xxxxxxxxxx>
Date:   Tue Jun 26 08:48:14 2018 +0200

    x86/dom0: add extra RAM regions as UNUSABLE for PVH memory map
    When running as PVH Dom0 the native memory map is used in order to
    craft a tailored memory map for Dom0 taking into account it's memory
    Dom0 memory is always going to be smaller than the total amount
    of memory present on the host, so in order to prevent Dom0 from
    relocating PCI BARs over RAM regions mark all the RAM regions not
    available to Dom0 as UNUSABLE in the memory map.
    Signed-off-by: Roger Pau Monné <roger.pau@xxxxxxxxxx>
    Acked-by: Jan Beulich <jbeulich@xxxxxxxx>

commit e017c882ef8bc1301054f3b4e341fb76f8affb8c
Author: Jan Beulich <jbeulich@xxxxxxxx>
Date:   Tue Jun 26 08:47:17 2018 +0200

    x86/HVM: alter completion-needed checking
    The function only looks at the ioreq_t, so pass it a pointer to just
    that. Also use it in hvmemul_do_io().
    Suggested-by: Paul Durrant <paul.durrant@xxxxxxxxxx>
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Reviewed-by: Paul Durrant <paul.durrant@xxxxxxxxxx>

commit 3310e3cd648f3713c824790bd71d8ec405a09d05
Author: Jan Beulich <jbeulich@xxxxxxxx>
Date:   Tue Jun 26 08:41:08 2018 +0200

    x86/HVM: attempts to emulate FPU insns need to set fpu_initialised
    My original way of thinking here was that this would be set anyway at
    the point state gets reloaded after the adjustments hvmemul_put_fpu()
    does, but the flag should already be set before that - after all the
    guest may never again touch the FPU before e.g. getting migrated/saved.
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Acked-by: Paul Durrant <paul.durrant@xxxxxxxxxx>

commit 2b222ddede90a110e0b7a570ba29c74779692490
Author: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
Date:   Mon Jun 25 15:17:04 2018 +0100

    configure: Rerun autogen.sh (on stretch)
    This is just a version number update.
    Signed-off-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>

commit fe24641c8fd846cd7f63cd16a96ff51db495a798
Author: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
Date:   Mon Jun 25 15:14:29 2018 +0100

    README, Makefiles, Config.mk: Update for branching 4.11 vs 4.12-unstable
    Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
(qemu changes not included)

Xen-devel mailing list



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