xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: xen.org <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: ian.jackson@eu.citrix.com
Subject: [xen-unstable test] 18225: regressions - FAIL
Date: Thu, 27 Jun 2013 17:01:16 +0100	[thread overview]
Message-ID: <osstest-18225-mainreport@xen.org> (raw)

flight 18225 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/18225/

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-amd64-amd64-xl-qemuu-winxpsp3 10 guest-saverestore.2 fail REGR. vs. 18222
 build-i386                    4 xen-build                 fail REGR. vs. 18219
 build-i386-oldkern            4 xen-build                 fail REGR. vs. 18219

Regressions which are regarded as allowable (not blocking):
 test-amd64-amd64-xl-sedf-pin 12 guest-saverestore.2       fail REGR. vs. 18222

Tests which did not succeed, but are not blocking:
 test-amd64-i386-qemuu-rhel6hvm-intel  1 xen-build-check(1)         blocked n/a
 test-amd64-i386-pv            1 xen-build-check(1)           blocked  n/a
 test-amd64-amd64-xl-pcipt-intel  9 guest-start                 fail never pass
 test-amd64-i386-xl-credit2    1 xen-build-check(1)           blocked  n/a
 test-amd64-i386-xl-multivcpu  1 xen-build-check(1)           blocked  n/a
 test-amd64-i386-qemut-rhel6hvm-amd  1 xen-build-check(1)           blocked n/a
 test-amd64-i386-rhel6hvm-amd  1 xen-build-check(1)           blocked  n/a
 test-amd64-i386-qemut-rhel6hvm-intel  1 xen-build-check(1)         blocked n/a
 test-amd64-i386-qemuu-rhel6hvm-amd  1 xen-build-check(1)           blocked n/a
 test-amd64-i386-xend-winxpsp3  1 xen-build-check(1)           blocked  n/a
 test-amd64-amd64-xl-qemut-win7-amd64 13 guest-stop             fail never pass
 test-amd64-amd64-xl-qemuu-win7-amd64 13 guest-stop             fail never pass
 test-amd64-i386-xl            1 xen-build-check(1)           blocked  n/a
 test-amd64-amd64-xl-win7-amd64 13 guest-stop                   fail never pass
 test-amd64-i386-rhel6hvm-intel  1 xen-build-check(1)           blocked  n/a
 test-amd64-i386-xl-qemut-win7-amd64  1 xen-build-check(1)          blocked n/a
 test-amd64-amd64-xl-qemut-winxpsp3 13 guest-stop               fail never pass
 test-amd64-amd64-xl-winxpsp3 13 guest-stop                   fail   never pass
 test-amd64-i386-xl-win7-amd64  1 xen-build-check(1)           blocked  n/a
 test-amd64-i386-xl-winxpsp3-vcpus1  1 xen-build-check(1)           blocked n/a
 test-amd64-i386-xl-qemut-winxpsp3-vcpus1  1 xen-build-check(1)     blocked n/a
 test-amd64-i386-xend-qemut-winxpsp3  1 xen-build-check(1)          blocked n/a
 test-amd64-i386-pair          1 xen-build-check(1)           blocked  n/a

version targeted for testing:
 xen                  55e5d9527caa038f0598186271a52419a655ff01
baseline version:
 xen                  62fe11fbd8ceac1700c3494f1de4c688e6a118c1

------------------------------------------------------------
People who touched revisions under test:
  Frediano Ziglio <frediano.ziglio@citrix.com>
  George Dunlap <george.dunlap@eu.citrix.com>
  Ian Campbell <ian.campbell@citix.com>
  Ian Campbell <ian.campbell@citrix.com>
  Ian Murray <murrayie@yahoo.co.uk>
  Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
  Marcel Mol <marcel@mesa.nl>
------------------------------------------------------------

jobs:
 build-amd64                                                  pass    
 build-armhf                                                  pass    
 build-i386                                                   fail    
 build-amd64-oldkern                                          pass    
 build-i386-oldkern                                           fail    
 build-amd64-pvops                                            pass    
 build-i386-pvops                                             pass    
 test-amd64-amd64-xl                                          pass    
 test-amd64-i386-xl                                           blocked 
 test-amd64-i386-rhel6hvm-amd                                 blocked 
 test-amd64-i386-qemut-rhel6hvm-amd                           blocked 
 test-amd64-i386-qemuu-rhel6hvm-amd                           blocked 
 test-amd64-amd64-xl-qemut-win7-amd64                         fail    
 test-amd64-i386-xl-qemut-win7-amd64                          blocked 
 test-amd64-amd64-xl-qemuu-win7-amd64                         fail    
 test-amd64-amd64-xl-win7-amd64                               fail    
 test-amd64-i386-xl-win7-amd64                                blocked 
 test-amd64-i386-xl-credit2                                   blocked 
 test-amd64-amd64-xl-pcipt-intel                              fail    
 test-amd64-i386-rhel6hvm-intel                               blocked 
 test-amd64-i386-qemut-rhel6hvm-intel                         blocked 
 test-amd64-i386-qemuu-rhel6hvm-intel                         blocked 
 test-amd64-i386-xl-multivcpu                                 blocked 
 test-amd64-amd64-pair                                        pass    
 test-amd64-i386-pair                                         blocked 
 test-amd64-amd64-xl-sedf-pin                                 fail    
 test-amd64-amd64-pv                                          pass    
 test-amd64-i386-pv                                           blocked 
 test-amd64-amd64-xl-sedf                                     pass    
 test-amd64-i386-xl-qemut-winxpsp3-vcpus1                     blocked 
 test-amd64-i386-xl-winxpsp3-vcpus1                           blocked 
 test-amd64-i386-xend-qemut-winxpsp3                          blocked 
 test-amd64-amd64-xl-qemut-winxpsp3                           fail    
 test-amd64-amd64-xl-qemuu-winxpsp3                           fail    
 test-amd64-i386-xend-winxpsp3                                blocked 
 test-amd64-amd64-xl-winxpsp3                                 fail    


------------------------------------------------------------
sg-report-flight on woking.cam.xci-test.com
logs: /home/xc_osstest/logs
images: /home/xc_osstest/images

Logs, config files, etc. are available at
    http://www.chiark.greenend.org.uk/~xensrcts/logs

Test harness code can be found at
    http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary


Not pushing.

------------------------------------------------------------
commit 55e5d9527caa038f0598186271a52419a655ff01
Author: Frediano Ziglio <frediano.ziglio@citrix.com>
Date:   Wed Jun 12 13:02:27 2013 +0100

    gcov: Do not use mmap directly but use xc_hypercall_buffer_alloc
    
    xencov.c did not compile on NetBSD so use xc_hypercall_buffer which is
    more portable.
    
    Signed-off-by: Frediano Ziglio <frediano.ziglio@citrix.com>
    Acked-by: Ian Campbell <ian.campbell@citrix.com>

commit 6a4564d537e51cf13b9f873f6c2f3d4130b5382f
Author: George Dunlap <george.dunlap@eu.citrix.com>
Date:   Mon Jun 17 13:48:09 2013 +0100

    4.3 release: Update README
    
    Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com>
    Acked-by: Ian Campbell <ian.campbell@citrix.com>

commit e892ab5ad4238efc1c425ac7a28581c116e674af
Author: Marcel J.E. Mol <marcel@mesa.nl>
Date:   Wed Jun 26 20:29:37 2013 +0200

    pygrub: add fedora 19 grub.cfg example
    
    This grub.cfg from a default fedora 19 Beta install
    caused pygrub failures.The previous pygrub commit
    fixed taht. So this example file added for reference.
    
    Signed-off-by: Marcel Mol <marcel@mesa.nl>
    Acked-by: Ian Campbell <ian.campbell@citrix.com>

commit d513814db6af2b298b8776d7ffc5fb1261e176f4
Author: Marcel J.E. Mol <marcel@mesa.nl>
Date:   Mon Jun 24 18:21:32 2013 +0200

    pygrub/GrubConf: fix boot problem for fedora 19 grub.cfg (2nd attempt)
    
    Booting a fedora 19 domU failed because a it could not properly
    parse the grub.cfg file. This was cased by
    
    	set default="${next_entry}"
    
    This statement actually is within an 'if' statement, so maybe it would
    be better to skip code within if/fi blocks...
    But this patch seems to work fine.
    
    Signed-off-by: Marcel Mol <marcel@mesa.nl>
    Acked-by: Ian Campbell <ian.campbell@citix.com>
    Tested-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>

commit 543a2657182dbb9237d1feeb1d3193096ab2cb2d
Author: Ian Murray <murrayie@yahoo.co.uk>
Date:   Sat Jun 22 13:38:11 2013 +0100

    Xendomains was not correctly suspending domains when a STOP was issued.
    
    The regex was not selecting the { when parsing JSON output of xl list -l.
    It was also not selecting (domain when parsing xl list -l when SXP selected.
    
    Pefixed { with 4 spaces, and removed an extra ( before domain in the regex
    string
    
    Added quotes around the grep strings so the spaces inserted into the string
    didn't not break the grepping.
    
    This has now been tested against 4.3RC5
    
    Signed-off-by: Ian Murray <murrayie@yahoo.co.uk>
    Acked-by: Ian Campbell <ian.campbell@citrix.com>
    Acked-by: George Dunlap <george.dunlap@eu.citrix.com>

commit 442ba0b2f6c16945ad496b31bf18a9e85d199d18
Author: Ian Jackson <ian.jackson@eu.citrix.com>
Date:   Thu Jun 27 11:08:07 2013 +0100

    QEMU_UPSTREAM_REVISION update
(qemu changes not included)

                 reply	other threads:[~2013-06-27 16:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=osstest-18225-mainreport@xen.org \
    --to=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).