From: xen.org <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: ian.jackson@eu.citrix.com
Subject: [xen-unstable test] 5461: regressions - trouble: blocked/broken/fail/pass
Date: Fri, 28 Jan 2011 18:45:12 +0000 [thread overview]
Message-ID: <osstest-5461-mainreport@xen.org> (raw)
flight 5461 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/5461/
Regressions :-(
Tests which did not succeed and are blocking:
build-amd64-pvops 3 host-build-prep fail REGR. vs. 5237
build-amd64 2 host-install(2) broken
build-i386-pvops 2 host-install(2) broken
test-i386-xcpkern-i386-pair 16 guest-start fail REGR. vs. 5237
test-i386-xcpkern-i386-pv 13 guest-localmigrate.2 fail REGR. vs. 5237
test-i386-xcpkern-i386-win 5 xen-boot fail REGR. vs. 5237
test-i386-xcpkern-i386-xl 9 guest-start fail REGR. vs. 5237
Tests which did not succeed, but are not blocking,
including regressions (tests previously passed) regarded as allowable:
test-amd64-amd64-pair 1 xen-build-check(1) blocked n/a
test-amd64-amd64-pv 1 xen-build-check(1) blocked n/a
test-amd64-amd64-win 1 xen-build-check(1) blocked n/a
test-amd64-amd64-xl-win 1 xen-build-check(1) blocked n/a
test-amd64-amd64-xl 1 xen-build-check(1) blocked n/a
test-amd64-i386-pair 1 xen-build-check(1) blocked n/a
test-amd64-i386-pv 1 xen-build-check(1) blocked n/a
test-amd64-i386-rhel6hvm-amd 1 xen-build-check(1) blocked n/a
test-amd64-i386-rhel6hvm-intel 1 xen-build-check(1) blocked n/a
test-amd64-i386-win-vcpus1 1 xen-build-check(1) blocked n/a
test-amd64-i386-win 1 xen-build-check(1) blocked n/a
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-xl-win-vcpus1 1 xen-build-check(1) blocked n/a
test-amd64-i386-xl 1 xen-build-check(1) blocked n/a
test-amd64-xcpkern-i386-pair 1 xen-build-check(1) blocked n/a
test-amd64-xcpkern-i386-pv 1 xen-build-check(1) blocked n/a
test-amd64-xcpkern-i386-rhel6hvm-amd 1 xen-build-check(1) blocked n/a
test-amd64-xcpkern-i386-rhel6hvm-intel 1 xen-build-check(1) blocked n/a
test-amd64-xcpkern-i386-win 1 xen-build-check(1) blocked n/a
test-amd64-xcpkern-i386-xl-credit2 1 xen-build-check(1) blocked n/a
test-amd64-xcpkern-i386-xl-multivcpu 1 xen-build-check(1) blocked n/a
test-amd64-xcpkern-i386-xl-win 1 xen-build-check(1) blocked n/a
test-amd64-xcpkern-i386-xl 1 xen-build-check(1) blocked n/a
test-i386-i386-pair 1 xen-build-check(1) blocked n/a
test-i386-i386-pv 1 xen-build-check(1) blocked n/a
test-i386-i386-win 1 xen-build-check(1) blocked n/a
test-i386-i386-xl-win 1 xen-build-check(1) blocked n/a
test-i386-i386-xl 1 xen-build-check(1) blocked n/a
version targeted for testing:
xen 722f7b7678dc
baseline version:
xen b59f04eb8978
------------------------------------------------------------
People who touched revisions under test:
Andre Przywara <andre.przywara@amd.com>
Christoph Egger <Christoph.Egger@amd.com>
Daniel Kiper <dkiper@net-space.pl>
Fengzhe Zhang <fengzhe.zhang@intel.com>
George Dunlap <george.dunlap@citrix.com>
Gianni Tedesco <gianni.tedesco@citrix.com>
Ian Campbell <ian.campbell@citrix.com>
Ian Campbell <Ian.Campbell@eu.citrix.com>
Ian Jackson <ian.jackson@eu.citrix.com>
John Weekes <lists.xen@nuclearfallout.net>
Kamala Narasimhan <kamala.narasimhan@citrix.com>
Keir Fraser <keir@xen.org>
M A Young <m.a.young@durham.ac.uk>
Shan Haitao <haitao.shan@intel.com>
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Tim Deegan <Tim.Deegan@citrix.com>
user virtual <virtualusr@gmail.com>
Wei Gang <gang.wei@intel.com>
Wei Wang <wei.wang2@amd.com>
------------------------------------------------------------
jobs:
build-i386-xcpkern pass
build-amd64 broken
build-i386 pass
build-amd64-oldkern pass
build-i386-oldkern pass
build-amd64-pvops broken
build-i386-pvops broken
test-amd64-amd64-xl blocked
test-amd64-i386-xl blocked
test-i386-i386-xl blocked
test-amd64-xcpkern-i386-xl blocked
test-i386-xcpkern-i386-xl fail
test-amd64-i386-rhel6hvm-amd blocked
test-amd64-xcpkern-i386-rhel6hvm-amd blocked
test-amd64-i386-xl-credit2 blocked
test-amd64-xcpkern-i386-xl-credit2 blocked
test-amd64-i386-rhel6hvm-intel blocked
test-amd64-xcpkern-i386-rhel6hvm-intel blocked
test-amd64-i386-xl-multivcpu blocked
test-amd64-xcpkern-i386-xl-multivcpu blocked
test-amd64-amd64-pair blocked
test-amd64-i386-pair blocked
test-i386-i386-pair blocked
test-amd64-xcpkern-i386-pair blocked
test-i386-xcpkern-i386-pair fail
test-amd64-amd64-pv blocked
test-amd64-i386-pv blocked
test-i386-i386-pv blocked
test-amd64-xcpkern-i386-pv blocked
test-i386-xcpkern-i386-pv fail
test-amd64-i386-win-vcpus1 blocked
test-amd64-i386-xl-win-vcpus1 blocked
test-amd64-amd64-win blocked
test-amd64-i386-win blocked
test-i386-i386-win blocked
test-amd64-xcpkern-i386-win blocked
test-i386-xcpkern-i386-win fail
test-amd64-amd64-xl-win blocked
test-i386-i386-xl-win blocked
test-amd64-xcpkern-i386-xl-win 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.
(No revision log; it would be 515 lines long.)
reply other threads:[~2011-01-28 18:45 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-5461-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.