From: xen.org <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: ian.jackson@eu.citrix.com
Subject: [xen-4.0-testing test] 9612: tolerable FAIL - PUSHED
Date: Wed, 26 Oct 2011 00:58:46 +0100 [thread overview]
Message-ID: <osstest-9612-mainreport@xen.org> (raw)
flight 9612 xen-4.0-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/9612/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
build-i386-pvops 4 kernel-build fail pass in 9610
test-amd64-amd64-xl-sedf 5 xen-boot fail in 9610 pass in 9612
Tests which did not succeed, but are not blocking,
including regressions (tests previously passed) regarded as allowable:
test-amd64-amd64-xl-pcipt-intel 8 debian-fixup fail never pass
test-amd64-i386-pv 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 1 xen-build-check(1) blocked n/a
test-i386-i386-xl 1 xen-build-check(1) blocked n/a
test-i386-i386-pv 1 xen-build-check(1) blocked n/a
test-amd64-amd64-xl 15 guest-stop fail never pass
test-amd64-i386-xl-credit2 1 xen-build-check(1) blocked n/a
test-amd64-amd64-xl-sedf 14 guest-localmigrate/x10 fail like 9599
test-amd64-i386-pair 1 xen-build-check(1) blocked n/a
test-i386-i386-pair 1 xen-build-check(1) blocked n/a
test-amd64-i386-win 1 xen-build-check(1) blocked n/a
test-amd64-i386-rhel6hvm-intel 1 xen-build-check(1) blocked n/a
test-amd64-i386-rhel6hvm-amd 1 xen-build-check(1) blocked n/a
test-amd64-i386-win-vcpus1 1 xen-build-check(1) blocked n/a
test-amd64-amd64-win 16 leak-check/check fail never pass
test-i386-i386-win 1 xen-build-check(1) blocked n/a
test-amd64-amd64-xl-win 7 windows-install fail never pass
test-i386-i386-xl-win 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-multivcpu 15 guest-stop fail in 9610 never pass
test-amd64-i386-xl 15 guest-stop fail in 9610 never pass
test-i386-i386-xl 15 guest-stop fail in 9610 never pass
test-amd64-i386-xl-credit2 14 guest-localmigrate/x10 fail in 9610 blocked in 9599
test-amd64-i386-win 16 leak-check/check fail in 9610 never pass
test-amd64-i386-rhel6hvm-intel 7 redhat-install fail in 9610 never pass
test-amd64-i386-rhel6hvm-amd 7 redhat-install fail in 9610 never pass
test-amd64-i386-win-vcpus1 16 leak-check/check fail in 9610 never pass
test-i386-i386-win 16 leak-check/check fail in 9610 never pass
test-i386-i386-xl-win 7 windows-install fail in 9610 never pass
test-amd64-i386-xl-win-vcpus1 7 windows-install fail in 9610 never pass
version targeted for testing:
xen a5cc3b953ed9
baseline version:
xen da9f945b3db8
------------------------------------------------------------
People who touched revisions under test:
Keir Fraser <keir@xen.org>
Wei Huang <wei.huang2@amd.com>
------------------------------------------------------------
jobs:
build-amd64 pass
build-i386 pass
build-amd64-oldkern pass
build-i386-oldkern pass
build-amd64-pvops pass
build-i386-pvops fail
test-amd64-amd64-xl fail
test-amd64-i386-xl blocked
test-i386-i386-xl blocked
test-amd64-i386-rhel6hvm-amd blocked
test-amd64-i386-xl-credit2 blocked
test-amd64-amd64-xl-pcipt-intel fail
test-amd64-i386-rhel6hvm-intel blocked
test-amd64-i386-xl-multivcpu blocked
test-amd64-amd64-pair pass
test-amd64-i386-pair blocked
test-i386-i386-pair blocked
test-amd64-amd64-pv pass
test-amd64-i386-pv blocked
test-i386-i386-pv blocked
test-amd64-amd64-xl-sedf fail
test-amd64-i386-win-vcpus1 blocked
test-amd64-i386-xl-win-vcpus1 blocked
test-amd64-amd64-win fail
test-amd64-i386-win blocked
test-i386-i386-win blocked
test-amd64-amd64-xl-win fail
test-i386-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
Pushing revision :
+ branch=xen-4.0-testing
+ revision=a5cc3b953ed9
+ . cri-lock-repos
++ . cri-common
+++ umask 002
+++ getconfig Repos
+++ perl -e '
use Osstest;
readconfigonly();
print $c{Repos} or die $!;
'
++ repos=/export/home/osstest/repos
++ repos_lock=/export/home/osstest/repos/lock
++ '[' x '!=' x/export/home/osstest/repos/lock ']'
++ OSSTEST_REPOS_LOCK_LOCKED=/export/home/osstest/repos/lock
++ exec with-lock-ex -w /export/home/osstest/repos/lock ./ap-push xen-4.0-testing a5cc3b953ed9
+ branch=xen-4.0-testing
+ revision=a5cc3b953ed9
+ . cri-lock-repos
++ . cri-common
+++ umask 002
+++ getconfig Repos
+++ perl -e '
use Osstest;
readconfigonly();
print $c{Repos} or die $!;
'
++ repos=/export/home/osstest/repos
++ repos_lock=/export/home/osstest/repos/lock
++ '[' x/export/home/osstest/repos/lock '!=' x/export/home/osstest/repos/lock ']'
+ : xen@xenbits.xensource.com
+ : xen@xenbits.xensource.com:git/linux-pvops
+ : master
+ : tested/2.6.39.x
+ case "$branch" in
+ cd /export/home/osstest/repos/xen-4.0-testing.hg
+ hg push -r a5cc3b953ed9 ssh://xen@xenbits.xensource.com/HG/xen-4.0-testing.hg
pushing to ssh://xen@xenbits.xensource.com/HG/xen-4.0-testing.hg
searching for changes
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 1 changesets with 2 changes to 2 files
reply other threads:[~2011-10-25 23:58 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-9612-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.