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

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

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

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

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                  70f7b6ca0e8208034bdc91d20b2f311bbe63a0a9
baseline version:
 xen                  43550972395f9a3a48bb4086a0faf0f8d442e37d

Last test of basis   116956  2017-12-07 23:02:27 Z    1 days
Testing same since   117015  2017-12-08 22:03:21 Z    0 days    3 attempts

------------------------------------------------------------
People who touched revisions under test:
  Andre Przywara <andre.przywara@xxxxxxx>
  Andre Przywara <andre.przywara@xxxxxxxxxx>
  Julien Grall <julien.grall@xxxxxxx>
  Julien Grall <julien.grall@xxxxxxxxxx>
  Stefano Stabellini <sstabellini@xxxxxxxxxx>

jobs:
 build-amd64                                                  pass    
 build-armhf                                                  pass    
 build-amd64-libvirt                                          pass    
 test-armhf-armhf-xl                                          pass    
 test-arm64-arm64-xl-xsm                                      broken  
 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 test-arm64-arm64-xl-xsm broken

Not pushing.

------------------------------------------------------------
commit 70f7b6ca0e8208034bdc91d20b2f311bbe63a0a9
Author: Andre Przywara <andre.przywara@xxxxxxxxxx>
Date:   Thu Dec 7 16:14:08 2017 +0000

    ARM: VGIC: move gic_remove_irq_from_queues()
    
    gic_remove_irq_from_queues() was not only misnamed, it also has the wrong
    abstraction, as it should not live in gic.c.
    Move it into vgic.c and vgic.h, where it belongs to, and rename it on
    the way.
    
    Signed-off-by: Andre Przywara <andre.przywara@xxxxxxxxxx>
    Reviewed-by: Stefano Stabellini <sstabellini@xxxxxxxxxx>

commit 9630c5ae363b4cbf8eb61366530f40c80680af4d
Author: Julien Grall <julien.grall@xxxxxxx>
Date:   Wed Dec 6 14:51:37 2017 +0000

    xen/arm: gic-v3: Bail out if gicv3_cpu_init fail
    
    When system registers are not enabled, all the access to them will trap
    in EL2. In Xen, system registers will be enabled by gicv3_cpu_init only
    on success. As the rest of the code (e.g gicv3_hyp_init) relies on
    system register, it is better to bail out directly.
    
    This will save time on debugging early boot issue on GICv3 platform.
    
    Signed-off-by: Julien Grall <julien.grall@xxxxxxxxxx>
    Reviewed-by: Stefano Stabellini <sstabellini@xxxxxxxxxx>

commit ac2d8d402370f6f93f82871f3b34ddb9a9ccae05
Author: Julien Grall <julien.grall@xxxxxxxxxx>
Date:   Wed Nov 29 17:46:35 2017 +0000

    xen/arm: Surround HSR_SYSREG macro value with ()
    
    The value of the macro HCR_SYSREG is not surrounded by (). This means
    the behavior may change depend on how it is used.
    
    Thanksfully recent GCC will issue a warning for that.
    
    Signed-off-by: Julien Grall <julien.grall@xxxxxxxxxx>
    Reviewed-by: Stefano Stabellini <sstabellini@xxxxxxxxxx>

commit b819187a15ecea7fe00cffded1bf454b8a6d7dd2
Author: Andre Przywara <andre.przywara@xxxxxxx>
Date:   Thu Oct 19 13:48:37 2017 +0100

    ARM: vGIC: fix nr_irq definition
    
    The global variable "nr_irqs" is used for x86 and some common Xen code.
    To make the latter work easily for ARM, it was #defined to NR_IRQS.
    This not only violated the common habit of capitalizing macros, but
    also caused issues if one wanted to use a rather innocent "nr_irqs" as
    a local variable name or as a function parameter.
    Drop the optimization and make nr_irqs a normal variable for ARM also.
    
    Signed-off-by: Andre Przywara <andre.przywara@xxxxxxx>

commit 2e9b1c655f060b5c4e68bc8499f02253babe1bbc
Author: Andre Przywara <andre.przywara@xxxxxxx>
Date:   Thu Oct 19 13:48:36 2017 +0100

    ARM: remove unneeded gic.h inclusions
    
    gic.h is supposed to hold defines and prototypes for the hardware side
    of the GIC interrupt controller. A lot of parts in Xen should not be
    bothered with that, as they either only care about the VGIC or use
    more generic interfaces.
    Remove unneeded inclusions of gic.h from files where they are actually
    not needed.
    
    Signed-off-by: Andre Przywara <andre.przywara@xxxxxxx>

commit c05aa4afac64ea687c1a2bf9277ba6552809495b
Author: Julien Grall <julien.grall@xxxxxxxxxx>
Date:   Wed Nov 29 17:57:32 2017 +0000

    xen/arm: bootfdt: Use proper default for #address-cells and #size-cells
    
    Per the device-tree specific [1], when the property #address-cells
    and  #size-cells are not present, the default value should be resp. 1
    and 2.
    
    [1] 
https://www.devicetree.org/downloads/devicetree-specification-v0.1-20160524.pdf
    
    Signed-off-by: Julien Grall <julien.grall@xxxxxxxxxx>
    Acked-by: Stefano Stabellini <sstabellini@xxxxxxxxxx>
(qemu changes not included)

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