From: Platform Team regression test user <citrix-osstest@xenproject.org>
To: xen-devel@lists.xensource.com, osstest-admin@xenproject.org
Subject: [ovmf baseline-only test] 71632: tolerable FAIL
Date: Tue, 4 Jul 2017 12:50:01 +0100 [thread overview]
Message-ID: <osstest-71632-mainreport@xen.org> (raw)
This run is configured for baseline tests only.
flight 71632 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/71632/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
build-i386-libvirt 5 libvirt-build fail like 71630
build-amd64-libvirt 5 libvirt-build fail like 71630
version targeted for testing:
ovmf 1e6add9e476696461526163bde843570cfdffb39
baseline version:
ovmf fb5a64de3a8be8482c3173f85cddda5ae204fe40
Last test of basis 71630 2017-07-04 03:49:09 Z 0 days
Testing same since 71632 2017-07-04 06:16:49 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Chris Ruffin <chris.ruffin@intel.com>
jobs:
build-amd64-xsm pass
build-i386-xsm pass
build-amd64 pass
build-i386 pass
build-amd64-libvirt fail
build-i386-libvirt fail
build-amd64-pvops pass
build-i386-pvops pass
test-amd64-amd64-xl-qemuu-ovmf-amd64 pass
test-amd64-i386-xl-qemuu-ovmf-amd64 pass
------------------------------------------------------------
sg-report-flight on osstest.xs.citrite.net
logs: /home/osstest/logs
images: /home/osstest/images
Logs, config files, etc. are available at
http://osstest.xs.citrite.net/~osstest/testlogs/logs
Test harness code can be found at
http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary
Push not applicable.
------------------------------------------------------------
commit 1e6add9e476696461526163bde843570cfdffb39
Author: Chris Ruffin <chris.ruffin@intel.com>
Date: Thu Jun 22 14:59:49 2017 -0400
BaseTools: suppress usage instructions with rebuild options
When using edksetup.bat Rebuild, the script outputs usage instructions
to the console, when no usage error is encountered. Update the usage
instructions and suppress these usage instructions when using the
Rebuild, ForceRebuild options.
Change-Id: Ica98e19f3d5198df2519106e4c55314c255e04ac
Cc: Liming Gao <liming.gao@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Chris Ruffin <chris.ruffin@intel.com>
Reviewed-by: Yonghong Zhu <yonghong.zhu@intel.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
reply other threads:[~2017-07-04 11:50 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-71632-mainreport@xen.org \
--to=citrix-osstest@xenproject.org \
--cc=osstest-admin@xenproject.org \
--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).