From: xen.org <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: ian.jackson@eu.citrix.com
Subject: [linux test] 6635: tolerable FAIL - PUSHED
Date: Thu, 24 Mar 2011 16:26:53 +0000 [thread overview]
Message-ID: <osstest-6635-mainreport@xen.org> (raw)
flight 6635 linux real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/6635/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-i386-rhel6hvm-intel 7 redhat-install fail pass in 6625
Tests which did not succeed, but are not blocking,
including regressions (tests previously passed) regarded as allowable:
test-amd64-amd64-win 16 leak-check/check fail never pass
test-amd64-amd64-xl-win 13 guest-stop fail never pass
test-amd64-i386-rhel6hvm-amd 8 guest-saverestore 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-i386-xl-win-vcpus1 13 guest-stop fail never pass
test-i386-i386-win 16 leak-check/check fail never pass
test-i386-i386-xl-win 13 guest-stop fail never pass
version targeted for testing:
linux 6d6ba2f4ea5f5a11f31ed707445ec4a57d225eb6
baseline version:
linux ba5fcb8b8ac91d8b65c8a9c2545bf3d416fdc151
------------------------------------------------------------
People who touched revisions under test:
------------------------------------------------------------
jobs:
build-amd64 pass
build-i386 pass
build-amd64-pvops pass
build-i386-pvops pass
test-amd64-amd64-xl pass
test-amd64-i386-xl pass
test-i386-i386-xl pass
test-amd64-i386-rhel6hvm-amd fail
test-amd64-i386-xl-credit2 pass
test-amd64-i386-rhel6hvm-intel fail
test-amd64-i386-xl-multivcpu pass
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-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=linux
+ revision=6d6ba2f4ea5f5a11f31ed707445ec4a57d225eb6
+ . 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 linux 6d6ba2f4ea5f5a11f31ed707445ec4a57d225eb6
+ branch=linux
+ revision=6d6ba2f4ea5f5a11f31ed707445ec4a57d225eb6
+ . 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
+ case "$branch" in
+ cd /export/home/osstest/repos/xen
+ git push xen@xenbits.xensource.com:git/linux-pvops 6d6ba2f4ea5f5a11f31ed707445ec4a57d225eb6:master
Counting objects: 1
Counting objects: 61, done.
Compressing objects: 9% (1/11)
Compressing objects: 18% (2/11)
Compressing objects: 27% (3/11)
Compressing objects: 36% (4/11)
Compressing objects: 45% (5/11)
Compressing objects: 54% (6/11)
Compressing objects: 63% (7/11)
Compressing objects: 72% (8/11)
Compressing objects: 81% (9/11)
Compressing objects: 90% (10/11)
Compressing objects: 100% (11/11)
Compressing objects: 100% (11/11), done.
Writing objects: 2% (1/39)
Writing objects: 5% (2/39)
Writing objects: 7% (3/39)
Writing objects: 10% (4/39)
Writing objects: 12% (5/39)
Writing objects: 15% (6/39)
Writing objects: 17% (7/39)
Writing objects: 20% (8/39)
Writing objects: 23% (9/39)
Writing objects: 25% (10/39)
Writing objects: 28% (11/39)
Writing objects: 30% (12/39)
Writing objects: 33% (13/39)
Writing objects: 35% (14/39)
Writing objects: 38% (15/39)
Writing objects: 41% (16/39)
Writing objects: 43% (17/39)
Writing objects: 46% (18/39)
Writing objects: 48% (19/39)
Writing objects: 51% (20/39)
Writing objects: 53% (21/39)
Writing objects: 56% (22/39)
Writing objects: 58% (23/39)
Writing objects: 61% (24/39)
Writing objects: 64% (25/39)
Writing objects: 66% (26/39)
Writing objects: 69% (27/39)
Writing objects: 71% (28/39)
Writing objects: 74% (29/39)
Writing objects: 76% (30/39)
Writing objects: 79% (31/39)
Writing objects: 82% (32/39)
Writing objects: 84% (33/39)
Writing objects: 87% (34/39)
Writing objects: 89% (35/39)
Writing objects: 92% (36/39)
Writing objects: 94% (37/39)
Writing objects: 97% (38/39)
Writing objects: 100% (39/39)
Writing objects: 100% (39/39), 6.38 KiB, done.
Total 39 (delta 33), reused 34 (delta 28)
To xen@xenbits.xensource.com:git/linux-pvops
ba5fcb8..6d6ba2f 6d6ba2f4ea5f5a11f31ed707445ec4a57d225eb6 -> master
reply other threads:[~2011-03-24 16:26 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-6635-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.