[Xen-devel] [xen-unstable-smoke test] 87360: regressions - FAIL

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

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

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-armhf-armhf-xl          15 guest-start/debian.repeat fail REGR. vs. 87332

Tests which did not succeed, but are not blocking:
 test-amd64-amd64-libvirt     12 migrate-support-check        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                  04119085f5a2a135e5161535b8821e1aa0d7db8a
baseline version:
 xen                  a67e68c6310e983c76a63cc4863b46ddde6d84db

Last test of basis    87332  2016-03-25 16:08:28 Z    0 days
Testing same since    87360  2016-03-25 21:11:11 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  George Dunlap <george.dunlap@xxxxxxxxxx>
  George Dunlap <george.dunlap@xxxxxxxxxxxxx>
  Ian Jackson <ian.jackson@xxxxxxxxxxxxx>

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


Not pushing.

------------------------------------------------------------
commit 04119085f5a2a135e5161535b8821e1aa0d7db8a
Author: George Dunlap <george.dunlap@xxxxxxxxxxxxx>
Date:   Thu Mar 24 17:17:24 2016 +0000

    xl: Return an error on failed cd-insert
    
    This makes xl more useful in scripts.
    
    The strange thing about this is that the internal cd_insert function
    *already* returned something appropriate, and cd-eject was using it,
    but cd-insert wasn't.
    
    Also:
    
    * Rework cd_insert to return EXIT_FAILURE and EXIT_SUCCESS rather than
    magic constants
    
    * Use 'r' for non-libxl return code, as specified in CODING_STYLE
    
    Signed-off-by: George Dunlap <george.dunlap@xxxxxxxxxxxxx>
    Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>

commit 0614c454209ac67016e2296577abfee9e9dcb012
Author: George Dunlap <george.dunlap@xxxxxxxxxxxxx>
Date:   Thu Mar 24 17:17:23 2016 +0000

    xl: Make set_memory_target return an error code on failure
    
    Also move the rc -> shell code translation into set_memory_max() to
    make the two functions consistent with each other, and with other
    similar examples in xl_cmdimpl.c
    
    Change a 'long long' to "int64_t" while we're at it.
    
    Signed-off-by: George Dunlap <george.dunlap@xxxxxxxxxxxxx>
    Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>

commit 26dbc93a9205e4a08fe12aac3efed980ae3e1ce5
Author: George Dunlap <george.dunlap@xxxxxxxxxxxxx>
Date:   Thu Mar 24 17:17:22 2016 +0000

    libxl: Remove pointless hypercall from libxl_set_memory_target
    
    There's no obvious reason for the call to xc_domain_getinfolist -- all
    it seems to be doing is checking that the domain exists; but if it
    doesn't exist, it will have already failed by this point.
    
    NB that this will change the return value for libxl_set_memory_target:
    now it will return 0 on success, rather than returning 1 (which was
    the previous behavior).  This is more in line with expected behavior,
    and also allows the caller to distingiush between success and other
    failure modes (some of which also return 1).
    
    Signed-off-by: George Dunlap <george.dunlap@xxxxxxxxxx>
    Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
(qemu changes not included)

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