From: xen.org <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: ian.jackson@eu.citrix.com
Subject: [qemu-upstream-unstable test] 13375: regressions - FAIL
Date: Wed, 27 Jun 2012 21:33:19 +0100 [thread overview]
Message-ID: <osstest-13375-mainreport@xen.org> (raw)
flight 13375 qemu-upstream-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/13375/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-win7-amd64 12 guest-localmigrate/x10 fail REGR. vs. 13338
Tests which did not succeed, but are not blocking:
test-amd64-i386-qemuu-rhel6hvm-intel 11 leak-check/check fail never pass
test-amd64-i386-qemuu-rhel6hvm-amd 11 leak-check/check fail never pass
test-amd64-i386-xl-qemuu-win-vcpus1 13 guest-stop fail never pass
test-amd64-amd64-xl-qemuu-winxpsp3 13 guest-stop fail never pass
test-amd64-amd64-xl-qemuu-win 13 guest-stop fail never pass
test-amd64-amd64-xl-qemuu-win7-amd64 13 guest-stop fail never pass
test-i386-i386-qemuu-win 16 leak-check/check fail never pass
test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 13 guest-stop fail never pass
test-amd64-i386-qemuu-win-vcpus1 16 leak-check/check fail never pass
test-amd64-i386-xend-qemuu-winxpsp3 16 leak-check/check fail never pass
test-amd64-i386-qemuu-win 16 leak-check/check fail never pass
test-i386-i386-xl-qemuu-winxpsp3 13 guest-stop fail never pass
test-amd64-amd64-qemuu-win 16 leak-check/check fail never pass
test-i386-i386-xl-qemuu-win 13 guest-stop fail never pass
version targeted for testing:
qemuu dbaf62769e1bfa7636208a4f00ea2331f5c40685
baseline version:
qemuu 4e8785001421e97c4f1c18d27ce77d717f9561d4
------------------------------------------------------------
People who touched revisions under test:
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
------------------------------------------------------------
jobs:
build-amd64 pass
build-i386 pass
build-amd64-oldkern pass
build-i386-oldkern pass
build-amd64-pvops pass
build-i386-pvops pass
test-amd64-i386-qemuu-rhel6hvm-amd fail
test-amd64-amd64-xl-qemuu-win7-amd64 fail
test-amd64-i386-xl-qemuu-win7-amd64 fail
test-amd64-i386-qemuu-rhel6hvm-intel fail
test-amd64-i386-qemuu-win-vcpus1 fail
test-amd64-i386-xl-qemuu-win-vcpus1 fail
test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 fail
test-amd64-amd64-qemuu-win fail
test-amd64-i386-qemuu-win fail
test-i386-i386-qemuu-win fail
test-amd64-amd64-xl-qemuu-win fail
test-i386-i386-xl-qemuu-win fail
test-amd64-i386-xend-qemuu-winxpsp3 fail
test-amd64-amd64-xl-qemuu-winxpsp3 fail
test-i386-i386-xl-qemuu-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 dbaf62769e1bfa7636208a4f00ea2331f5c40685
Author: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Date: Wed Jun 27 12:49:50 2012 +0000
Fix backport error introduced by f1cf76785270ebc9798c82ad5f7419129bde7e56
Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
reply other threads:[~2012-06-27 20:33 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-13375-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.