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] 14600: trouble: blocked/broken
Date: Fri, 7 Dec 2012 18:03:55 +0000 [thread overview]
Message-ID: <osstest-14600-mainreport@xen.org> (raw)
flight 14600 qemu-upstream-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/14600/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-pvops 2 host-install(2) broken REGR. vs. 14472
build-amd64 2 host-install(2) broken REGR. vs. 14472
build-i386-pvops 2 host-install(2) broken REGR. vs. 14472
build-i386-oldkern 2 host-install(2) broken REGR. vs. 14472
build-amd64-oldkern 2 host-install(2) broken REGR. vs. 14472
build-i386 2 host-install(2) broken REGR. vs. 14472
Tests which did not succeed, but are not blocking:
test-amd64-i386-qemuu-rhel6hvm-amd 1 xen-build-check(1) blocked n/a
test-amd64-i386-qemuu-rhel6hvm-intel 1 xen-build-check(1) blocked n/a
test-amd64-i386-xl-qemuu-win-vcpus1 1 xen-build-check(1) blocked n/a
test-amd64-i386-qemuu-win 1 xen-build-check(1) blocked n/a
test-amd64-amd64-xl-qemuu-win7-amd64 1 xen-build-check(1) blocked n/a
test-amd64-i386-qemuu-win-vcpus1 1 xen-build-check(1) blocked n/a
test-amd64-i386-xl-qemuu-win7-amd64 1 xen-build-check(1) blocked n/a
test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 1 xen-build-check(1) blocked n/a
test-amd64-i386-xend-qemuu-winxpsp3 1 xen-build-check(1) blocked n/a
test-amd64-amd64-xl-qemuu-win 1 xen-build-check(1) blocked n/a
test-amd64-amd64-xl-qemuu-winxpsp3 1 xen-build-check(1) blocked n/a
test-amd64-amd64-qemuu-win 1 xen-build-check(1) blocked n/a
version targeted for testing:
qemuu 3752993df8af5cffa1b8219fe175d235597b4474
baseline version:
qemuu 1e6f3bf92c84d9ba8fdc61f4deb1777e737c7a2c
------------------------------------------------------------
People who touched revisions under test:
------------------------------------------------------------
jobs:
build-amd64 broken
build-i386 broken
build-amd64-oldkern broken
build-i386-oldkern broken
build-amd64-pvops broken
build-i386-pvops broken
test-amd64-i386-qemuu-rhel6hvm-amd blocked
test-amd64-amd64-xl-qemuu-win7-amd64 blocked
test-amd64-i386-xl-qemuu-win7-amd64 blocked
test-amd64-i386-qemuu-rhel6hvm-intel blocked
test-amd64-i386-qemuu-win-vcpus1 blocked
test-amd64-i386-xl-qemuu-win-vcpus1 blocked
test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 blocked
test-amd64-amd64-qemuu-win blocked
test-amd64-i386-qemuu-win blocked
test-amd64-amd64-xl-qemuu-win blocked
test-amd64-i386-xend-qemuu-winxpsp3 blocked
test-amd64-amd64-xl-qemuu-winxpsp3 blocked
------------------------------------------------------------
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 3752993df8af5cffa1b8219fe175d235597b4474
Merge: 1e6f3bf... 6d6c9f5...
Author: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Date: Wed Dec 5 11:31:01 2012 +0000
Merge commit 'v1.3.0' into xen-staging-master-4
reply other threads:[~2012-12-07 18:03 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-14600-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.