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] 67717: all pass
Date: Thu, 15 Sep 2016 13:54:13 +0100 [thread overview]
Message-ID: <osstest-67717-mainreport@xen.org> (raw)
This run is configured for baseline tests only.
flight 67717 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/67717/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf f8db6527da8678f1480f08ba99b745279e8d104a
baseline version:
ovmf 062f9fd2cfaad09f6dd0e302094bc030827eb706
Last test of basis 67713 2016-09-14 21:50:50 Z 0 days
Testing same since 67717 2016-09-15 10:49:16 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Yonghong Zhu <yonghong.zhu@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-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 f8db6527da8678f1480f08ba99b745279e8d104a
Author: Yonghong Zhu <yonghong.zhu@intel.com>
Date: Wed Sep 14 13:59:01 2016 +0800
BaseTools: Fix the bug to handle the read-only file
change the 'r+b' to 'rb' for some file's open, since these files we only
read it and no need to write. It can fix the bug that the file's attribute
had been set to read-only.
Cc: Liming Gao <liming.gao@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Yonghong Zhu <yonghong.zhu@intel.com>
Reviewed-by: Liming Gao <liming.gao@intel.com>
commit 04b1d73a0dac00f5a394db89f928a18a6ce5ec15
Author: Yonghong Zhu <yonghong.zhu@intel.com>
Date: Wed Sep 14 13:36:07 2016 +0800
IntelFrameworkPkg/FrameworkSpecConformance.txt: Update the URL
Update the URL since http://edk2.tianocore.org is not valid
Cc: Liming Gao <liming.gao@intel.com>
Cc: Jeff Fan <jeff.fan@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Yonghong Zhu <yonghong.zhu@intel.com>
Reviewed-by: Liming Gao <liming.gao@intel.com>
Reviewed-by: Jeff Fan <jeff.fan@intel.com>
commit 445bfd921462d50a226a833f5b1c3e375efdd434
Author: Yonghong Zhu <yonghong.zhu@intel.com>
Date: Wed Sep 14 13:27:06 2016 +0800
edksetup.sh: update the URL in edksetup.sh
Update the URL since http://edk2.tianocore.org is not valid
Cc: Liming Gao <liming.gao@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Yonghong Zhu <yonghong.zhu@intel.com>
Reviewed-by: Liming Gao <liming.gao@intel.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
reply other threads:[~2016-09-15 12:54 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-67717-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 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.