"Old" tested version had not actually been tested; therefore in this
flight we test it, rather than a new candidate.  The baseline, if
any, is the most recent actually tested revision.

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

Failures :-/ but no regressions.

Tests which did not succeed, but are not blocking:
 test-amd64-amd64-libvirt     13 migrate-support-check        fail   never pass
 test-arm64-arm64-xl-xsm      13 migrate-support-check        fail   never pass
 test-arm64-arm64-xl-xsm      14 saverestore-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                  8f853dbc06361416bb1faa6ca7721e3982adbf38
baseline version:
 xen                  e1f912cbf7178798b0646c7d0753b8d67e139e75

Last test of basis   122888  2018-05-16 18:02:08 Z    1 days
Failing since        122898  2018-05-17 15:00:29 Z    0 days    5 attempts
Testing same since                          (not found)         0 attempts

------------------------------------------------------------
People who touched revisions under test:
  Konrad Rzeszutek Wilk <konrad.w...@oracle.com>
  Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>

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


Push not applicable.

------------------------------------------------------------
commit 8f853dbc06361416bb1faa6ca7721e3982adbf38
Author: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
Date:   Wed May 2 17:49:19 2018 +0300

    xen/kbdif: Add features to disable keyboard and pointer
    
    It is now not fully possible to control if and which virtual devices
    are created by the frontend, e.g. keyboard and pointer devices
    are always created and multi-touch device is created if the
    backend advertises multi-touch support. In some cases this
    behavior is not desirable and better control over the frontend's
    configuration is required.
    
    Add new XenStore feature fields, so it is possible to individually
    control set of exposed virtual devices for each guest OS:
     - set feature-disable-keyboard to 1 if no keyboard device needs
       to be created
     - set feature-disable-pointer to 1 if no pointer device needs
       to be created
    
    Keep old behavior by default.
    
    Signed-off-by: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
    Reviewed-by: Konrad Rzeszutek Wilk <konrad.w...@oracle.com>
    Signed-off-by: Konrad Rzeszutek Wilk <konrad.w...@oracle.com>
    Release-acked-by: Juergen Gross <jgr...@suse.com>
(qemu changes not included)

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

Reply via email to