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

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 build-amd64-libvirt           5 libvirt-build            fail REGR. vs. 100341

Tests which did not succeed, but are not blocking:
 test-amd64-amd64-libvirt      1 build-check(1)               blocked  n/a
 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                  2e426d6eecfd358b6a78553e63fcb24548010537
baseline version:
 xen                  72798298c751a3df21473a0d86d05ec7bb46e258

Last test of basis   100341  2016-08-08 10:02:49 Z    0 days
Testing same since   100344  2016-08-08 13:01:47 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Andrew Cooper <andrew.coop...@citrix.com>
  George Dunlap <george.dun...@citrix.com>
  Ian Jackson <ian.jack...@citrix.com>
  Ian Jackson <ian.jack...@eu.citrix.com>
  Wei Liu <wei.l...@citrix.com>

jobs:
 build-amd64                                                  pass    
 build-armhf                                                  pass    
 build-amd64-libvirt                                          fail    
 test-armhf-armhf-xl                                          pass    
 test-amd64-amd64-xl-qemuu-debianhvm-i386                     pass    
 test-amd64-amd64-libvirt                                     blocked 


------------------------------------------------------------
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 2e426d6eecfd358b6a78553e63fcb24548010537
Author: Andrew Cooper <andrew.coop...@citrix.com>
Date:   Wed Aug 3 16:56:56 2016 +0000

    x86/traps: Drop use_error_code parameter from do_{,guest_}trap()
    
    Whether or not an error code is needed can be determinted entirely from the
    trapnr paramter, as error codes are architecturally specified.
    
    Introduce TRAP_HAVE_EC as a bitmap of reserved vectors which have error 
codes,
    and drop the use_error_code from all callsites.
    
    As a result, the DO_ERROR{,_NOCODE}() macros become entirely superflouous 
and
    can be dropped.  Update the exception_table to point straight at do_trap().
    
    Signed-off-by: Andrew Cooper <andrew.coop...@citrix.com>
    Reviewed-by: Jan Beulich <jbeul...@suse.com>

commit 9ee1d0395576283b24c87f8d5ec7bb123cadc27c
Author: Ian Jackson <ian.jack...@eu.citrix.com>
Date:   Mon Aug 8 11:21:31 2016 +0100

    libxl: CODING_STYLE: Forbid if (...) { stmt; } else stmt;
    
    And clarify that the rule about omitting braces for single statements
    is optional (it is even contradicted by the example).
    
    Signed-off-by: Ian Jackson <ian.jack...@eu.citrix.com>
    Acked-by: Wei Liu <wei.l...@citrix.com>

commit 0cd19069c88744c6558015934633727a69988bce
Author: Wei Liu <wei.l...@citrix.com>
Date:   Mon Aug 1 10:55:59 2016 +0100

    xl: use xenconsole startup protocol
    
    If user asks xl to automatically connect to console when creating a
    guest, use the new startup protocol before trying to unpause domain so
    that we don't lose any console output.
    
    Signed-off-by: Wei Liu <wei.l...@citrix.com>
    Acked-by: Ian Jackson <ian.jack...@eu.citrix.com>

commit f2333d5f9f9fd8e823bad7bf8804c9423b97eb08
Author: Wei Liu <wei.l...@citrix.com>
Date:   Mon Aug 1 10:36:57 2016 +0100

    docs: document xenconsole startup protocol
    
    Signed-off-by: Wei Liu <wei.l...@citrix.com>
    Acked-by: Ian Jackson <ian.jack...@eu.citrix.com>

commit 731df782267983d06c929fb513f420a1579021f9
Author: Wei Liu <wei.l...@citrix.com>
Date:   Mon Aug 1 10:28:00 2016 +0100

    libxl: libxl_{primary_,}console_exec now take notify_fd argument
    
    The new argument will be passed down to xenconsole process, which then
    uses it to notify readiness.
    
    Signed-off-by: Wei Liu <wei.l...@citrix.com>
    Acked-by: Ian Jackson <ian.jack...@eu.citrix.com>

commit 88502c075a393508a6315c4f905132b03be42347
Author: Wei Liu <wei.l...@citrix.com>
Date:   Mon Aug 1 12:20:09 2016 +0100

    libxl: factor out libxl__console_tty_path
    
    No other user yet.
    
    Signed-off-by: Wei Liu <wei.l...@citrix.com>
    Acked-by: Ian Jackson <ian.jack...@eu.citrix.com>

commit 373f99d2eafd084073731486a20a3a5a2e120548
Author: Wei Liu <wei.l...@citrix.com>
Date:   Fri Jul 29 18:24:25 2016 +0100

    tools/console: introduce --start-notify-fd option for console client
    
    The console client will write 0x00 to that fd before entering console
    loop to indicate its readiness.
    
    Signed-off-by: Wei Liu <wei.l...@citrix.com>
    Acked-by: Ian Jackson <ian.jack...@eu.citrix.com>

commit 9fc57406d5b629ad0190b3b3d2d034f88896d5cb
Author: Wei Liu <wei.l...@citrix.com>
Date:   Fri Jul 29 18:22:26 2016 +0100

    tools/console: fix help string in client
    
    There is no short '-t' option.
    
    Signed-off-by: Wei Liu <wei.l...@citrix.com>
    Acked-by: Ian Jackson <ian.jack...@eu.citrix.com>

commit 78ac45c9af9374ccce53e5e150872ad40cf33706
Author: George Dunlap <george.dun...@citrix.com>
Date:   Mon Aug 8 11:07:46 2016 +0100

    CODING_STYLE: Allow single-sentence comments without full stops
    
    One of the common ways in which contributors trip up over the
    CODING_STYLE guides is by not putting a full stop at the end of a
    comment when there is only a single sentence.  Calling these out is a
    waste of everybody's time: The full stop at the end of a comment with
    a single sentence (or a single phrase) adds absolutely nothing to the
    legibility of the code.
    
    Modify CODING_STYLE to allow comments with a single sentence or
    sentence fragment to either have a full stop or not, while making it
    clear that comments with multiple sentences must have a full stop at
    the end of each sentence.
    
    Signed-off-by: George Dunlap <george.dun...@citrix.com>
    Acked-by: Ian Jackson <ian.jack...@citrix.com>
(qemu changes not included)

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

Reply via email to