[Xen-devel] [xen-unstable-smoke test] 105283: regressions - trouble: broken/fail/pass

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

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

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-amd64-amd64-xl-qemuu-debianhvm-i386  6 xen-boot     fail REGR. vs. 105218
 test-amd64-amd64-libvirt      6 xen-boot                 fail REGR. vs. 105218

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

version targeted for testing:
 xen                  1a6e3220cc19b8705c27ca90dbc615270237f372
baseline version:
 xen                  8844ed299a88848da88b23e6db43b5bcc4ad4bee

Last test of basis   105218  2017-02-01 17:01:00 Z    0 days
Testing same since   105283  2017-02-02 12:01:09 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>
  Jan Beulich <jbeulich@xxxxxxxx>
  Wei Liu <wei.liu2@xxxxxxxxxx>

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


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


Not pushing.

------------------------------------------------------------
commit 1a6e3220cc19b8705c27ca90dbc615270237f372
Author: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>
Date:   Thu Feb 2 12:51:39 2017 +0100

    acpi: switch to dynamic mapping at SYS_STATE_boot
    
    We can switch ACPI from using fixmap to dynamic mapping as soon as
    the system enters SYS_STATE_boot. This will allow us, for example,
    to map MADT on systems with large number of processors where the
    table might not fit into NUM_FIXMAP_ACPI_PAGES (currently set to 4).
    
    To avoid having a window between system entering SYS_STATE_boot and
    vmap area being initialized move vm_init() a little higher.
    
    Signed-off-by: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>
    Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx>

commit 0f72f9ba1f0586afac67bc88f35eba5cc26392cd
Author: Jan Beulich <jbeulich@xxxxxxxx>
Date:   Thu Feb 2 12:50:35 2017 +0100

    x86/HVM: make hvm_find_io_handler() static
    
    This reduces the chance of misuse - calling it must in particular
    always be accompanied by calling the corresponding ->complete() hook.
    Constify its parameter at once.
    
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Reviewed-by: Paul Durrant <paul.durrant@xxxxxxxxxx>

commit 061cd0f0e5c41335150e0d234d8ad0aff7b6da11
Author: Jan Beulich <jbeulich@xxxxxxxx>
Date:   Thu Feb 2 12:48:59 2017 +0100

    x86emul: correct behavior for single iteration REP INS/OUTS
    
    The initial operation done on these paths may raise an exception (for
    ->read_io() that's possible only on the PV path, when the I/O port
    access check has been deferred). We have to suppress put_rep_prefix()
    updating rCX in that case. From an abstract perspective this also
    applies to RETRY being returned.
    
    Reported-by: Wei Liu <wei.liu2@xxxxxxxxxx>
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Reviewed-by: Wei Liu <wei.liu2@xxxxxxxxxx>
    Tested-by: Wei Liu <wei.liu2@xxxxxxxxxx>
    Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
(qemu changes not included)

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel