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] 8801: tolerable FAIL - PUSHED
Date: Thu, 1 Sep 2011 15:32:03 +0100 [thread overview]
Message-ID: <osstest-8801-mainreport@xen.org> (raw)
flight 8801 xen-4.0-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/8801/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-i386-i386-xl 5 xen-boot fail pass in 8788
test-amd64-i386-xl-multivcpu 9 guest-start fail pass in 8788
test-amd64-amd64-xl 5 xen-boot fail pass in 8788
test-amd64-i386-xl-credit2 10 guest-saverestore fail pass in 8777
test-i386-i386-xl-win 5 xen-boot fail pass in 8788
test-amd64-amd64-xl-sedf 5 xen-boot fail in 8788 pass in 8801
test-amd64-i386-rhel6hvm-intel 5 xen-boot fail in 8788 pass in 8801
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-xl 15 guest-stop fail never pass
test-amd64-amd64-xl-sedf 15 guest-stop fail never pass
test-amd64-i386-rhel6hvm-intel 7 redhat-install fail never pass
test-amd64-i386-rhel6hvm-amd 7 redhat-install fail never pass
test-amd64-i386-win-vcpus1 16 leak-check/check fail never pass
test-amd64-i386-win 16 leak-check/check fail never pass
test-amd64-amd64-win 16 leak-check/check fail never pass
test-i386-i386-win 16 leak-check/check fail never pass
test-amd64-amd64-xl-win 7 windows-install fail never pass
test-amd64-i386-xl-win-vcpus1 7 windows-install fail never pass
test-i386-i386-xl 15 guest-stop fail in 8788 never pass
test-amd64-i386-xl-multivcpu 15 guest-stop fail in 8788 never pass
test-amd64-amd64-xl 15 guest-stop fail in 8788 never pass
test-amd64-i386-xl-credit2 5 xen-boot fail in 8788 like 8763
test-i386-i386-xl-win 7 windows-install fail in 8788 never pass
test-amd64-i386-xl-credit2 15 guest-stop fail in 8777 never pass
version targeted for testing:
xen 0383662ea34c
baseline version:
xen 4b7b75ace863
------------------------------------------------------------
People who touched revisions under test:
Andrew Cooper <andrew.cooper3@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-amd64-xl fail
test-amd64-i386-xl fail
test-i386-i386-xl fail
test-amd64-i386-rhel6hvm-amd fail
test-amd64-i386-xl-credit2 fail
test-amd64-amd64-xl-pcipt-intel fail
test-amd64-i386-rhel6hvm-intel fail
test-amd64-i386-xl-multivcpu fail
test-amd64-amd64-pair pass
test-amd64-i386-pair pass
test-i386-i386-pair pass
test-amd64-amd64-pv pass
test-amd64-i386-pv pass
test-i386-i386-pv pass
test-amd64-amd64-xl-sedf fail
test-amd64-i386-win-vcpus1 fail
test-amd64-i386-xl-win-vcpus1 fail
test-amd64-amd64-win fail
test-amd64-i386-win fail
test-i386-i386-win fail
test-amd64-amd64-xl-win fail
test-i386-i386-xl-win 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
Pushing revision :
+ branch=xen-4.0-testing
+ revision=0383662ea34c
+ . 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 0383662ea34c
+ branch=xen-4.0-testing
+ revision=0383662ea34c
+ . 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 0383662ea34c 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 8 changes to 8 files
reply other threads:[~2011-09-01 14:32 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-8801-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.