From: osstest service user <osstest@xenbits.xen.org>
To: xen-devel@lists.xensource.com
Cc: ian.jackson@eu.citrix.com
Subject: [ovmf test] 58587: trouble: broken/fail/pass
Date: Tue, 16 Jun 2015 04:34:14 +0000 [thread overview]
Message-ID: <osstest-58587-mainreport@xen.org> (raw)
flight 58587 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58587/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-qemuu-rhel6hvm-amd 3 host-install(3) broken REGR. vs. 58433
test-amd64-amd64-xl-qemuu-debianhvm-amd64 3 host-install(3) broken REGR. vs. 58433
test-amd64-i386-xl-qemuu-ovmf-amd64 3 host-install(3) broken REGR. vs. 58433
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail like 58433
test-amd64-i386-xl-qemuu-win7-amd64 16 guest-stop fail like 58433
version targeted for testing:
ovmf e84fb6ebe76fdf695890db61096f0e71e43b9fd1
baseline version:
ovmf a726471baa812a812a9a8f72a92610f598feaea2
------------------------------------------------------------
People who touched revisions under test:
Qiu Shumin <shumin.qiu@intel.com>
------------------------------------------------------------
jobs:
build-amd64-xsm pass
build-i386-xsm pass
build-amd64 pass
build-i386 pass
build-amd64-libvirt pass
build-i386-libvirt pass
build-amd64-pvops pass
build-i386-pvops pass
test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm pass
test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm pass
test-amd64-i386-qemuu-rhel6hvm-amd broken
test-amd64-amd64-xl-qemuu-debianhvm-amd64 broken
test-amd64-i386-xl-qemuu-debianhvm-amd64 pass
test-amd64-amd64-xl-qemuu-ovmf-amd64 pass
test-amd64-i386-xl-qemuu-ovmf-amd64 broken
test-amd64-amd64-xl-qemuu-win7-amd64 fail
test-amd64-i386-xl-qemuu-win7-amd64 fail
test-amd64-i386-qemuu-rhel6hvm-intel pass
test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 pass
test-amd64-amd64-xl-qemuu-winxpsp3 pass
test-amd64-i386-xl-qemuu-winxpsp3 pass
------------------------------------------------------------
sg-report-flight on osstest.test-lab.xenproject.org
logs: /home/logs/logs
images: /home/logs/images
Logs, config files, etc. are available at
http://logs.test-lab.xenproject.org/osstest/logs
Test harness code can be found at
http://xenbits.xen.org/gitweb?p=osstest.git;a=summary
broken-step test-amd64-i386-qemuu-rhel6hvm-amd host-install(3)
broken-step test-amd64-amd64-xl-qemuu-debianhvm-amd64 host-install(3)
broken-step test-amd64-i386-xl-qemuu-ovmf-amd64 host-install(3)
Not pushing.
------------------------------------------------------------
commit e84fb6ebe76fdf695890db61096f0e71e43b9fd1
Author: Qiu Shumin <shumin.qiu@intel.com>
Date: Mon Jun 15 07:42:48 2015 +0000
MdePkg: Refine the comments for FileHandleIsDirectory.
Make the function comments of FileHandleIsDirectory in FileHandleLib consistent with instance implementation.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Qiu Shumin <shumin.qiu@intel.com>
Reviewed-by: Jaben Carsey <jaben.carsey@intel.com>
Reviewed-by: Liming Gao <liming.gao@intel.com>
git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@17630 6f19259b-4bc3-4df7-8a09-765794883524
reply other threads:[~2015-06-16 4:34 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-58587-mainreport@xen.org \
--to=osstest@xenbits.xen.org \
--cc=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.