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] 66873: trouble: broken/pass
Date: Sun, 31 Jul 2016 17:28:34 +0100 [thread overview]
Message-ID: <osstest-66873-mainreport@xen.org> (raw)
This run is configured for baseline tests only.
flight 66873 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/66873/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 3 host-install(3) broken REGR. vs. 66871
version targeted for testing:
ovmf 2c855d3aaf36da80f8c4f0ae12d31900a628b0a9
baseline version:
ovmf 92e9b9f9df2d51c80844adbb785ac236a687d2d6
Last test of basis 66871 2016-07-31 04:48:25 Z 0 days
Testing same since 66873 2016-07-31 13:19:14 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
David Wei <david.wei@intel.com>
Lu, ShifeiX A <shifeix.a.lu@intel.com>
lushifex <shifeix.a.lu@intel.com>
Wei, David <david.wei@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 broken
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
broken-step test-amd64-amd64-xl-qemuu-ovmf-amd64 host-install(3)
Push not applicable.
------------------------------------------------------------
commit 2c855d3aaf36da80f8c4f0ae12d31900a628b0a9
Author: Lu, ShifeiX A <shifeix.a.lu@intel.com>
Date: Thu Jul 28 16:21:28 2016 +0800
Vlv2DeviceRefCodePkg&Vlv2DevicePkg:Add sample WSMT table.
This is an sample WSMT table, which we only
update BIT0 and BIT1 of Protections flags fields.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: lushifex <shifeix.a.lu@intel.com>
Reviewed-by: David Wei <david.wei@intel.com>
commit b52e697b2a68e37e973653877733484ad2f65c29
Author: lushifex <shifeix.a.lu@intel.com>
Date: Fri Jul 29 17:31:52 2016 +0800
Vlv2TbltDevicePkg:Signal EndOfDxe Event.
According to PI spec,EndOfDxe Event should be signaled
before DxeSmmReadyToLock protocol installation.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: lushifex <shifeix.a.lu@intel.com>
Reviewed-by: David Wei <david.wei@intel.com>
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
commit 1c32ee1c58b9173dff0d135aafa09034de313855
Author: Wei, David <david.wei@intel.com>
Date: Sat Jul 30 15:47:29 2016 +0800
Vlv2TbltDevicePkg:Change RESET_VALUE of FADT
Change RESET_VALUE of ACPI FADT to 0x0E, which could trigger full reset.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: David Wei <david.wei@intel.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
reply other threads:[~2016-07-31 16:28 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-66873-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.