From: xen.org <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: ian.jackson@eu.citrix.com
Subject: [linux test] 6623: regressions - FAIL
Date: Thu, 24 Mar 2011 06:11:55 +0000 [thread overview]
Message-ID: <osstest-6623-mainreport@xen.org> (raw)
flight 6623 linux real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/6623/
Regressions :-(
Tests which did not succeed and are blocking:
test-amd64-amd64-xl-win 7 windows-install fail REGR. vs. 6615
test-amd64-i386-rhel6hvm-amd 7 redhat-install fail REGR. vs. 6615
test-amd64-i386-xl-credit2 9 guest-start fail REGR. vs. 6615
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-i386-rhel6hvm-intel 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 fail
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
Not pushing.
------------------------------------------------------------
commit 6d6ba2f4ea5f5a11f31ed707445ec4a57d225eb6
Merge: ba5fcb8... c757402...
Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Date: Wed Mar 23 14:58:10 2011 +0000
Merge branch 'stable-2.6.32.x-dom0' of git://xenbits.xen.org/people/sstabellini/linux-pvhvm into xen/next-2.6.32
* 'stable-2.6.32.x-dom0' of git://xenbits.xen.org/people/sstabellini/linux-pvhvm:
xen: set max_pfn_mapped to the last pfn mapped
x86: Cleanup highmap after brk is concluded
input: xen-kbdfront - advertise either absolute or relative coordinates
acpiphp: assume device is in state D0 after powering on a slot.
acpiphp: set current_state to D0 in register_slot
next reply other threads:[~2011-03-24 6:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 6:11 xen.org [this message]
2011-03-24 10:04 ` [linux test] 6623: regressions - FAIL Ian Jackson
2011-03-24 12:03 ` George Dunlap
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-6623-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).