xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
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] 67861: all pass
Date: Tue, 11 Oct 2016 17:20:33 +0100	[thread overview]
Message-ID: <osstest-67861-mainreport@xen.org> (raw)

This run is configured for baseline tests only.

flight 67861 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/67861/

Perfect :-)
All tests in this flight passed as required
version targeted for testing:
 ovmf                 b3b58d4da79639ffb02e9a0556e21962bf918d1e
baseline version:
 ovmf                 3643e8e70d3053476aeecd01b3053918f7c74b61

Last test of basis    67859  2016-10-11 09:16:33 Z    0 days
Testing same since    67861  2016-10-11 14:17:47 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Star Zeng <star.zeng@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 b3b58d4da79639ffb02e9a0556e21962bf918d1e
Author: Star Zeng <star.zeng@intel.com>
Date:   Wed Sep 28 18:17:55 2016 +0800

    PcAtChipsetPkg AcpiTimerLib: Clear bits [31:24] after reading by IoRead32()
    
    Clear bits [31:24] after reading ACPI timer count by IoRead32(), and also add
    comments "Note: The implementation uses the lower 24-bits of the ACPI timer
    and is compatible with both 24-bit and 32-bit ACPI timers." in INF.
    
    Cc: Michael Kinney <michael.d.kinney@intel.com>
    Cc: Jiewen Yao <jiewen.yao@intel.com>
    Cc: Liming Gao <liming.gao@intel.com>
    Cc: Laszlo Ersek <lersek@redhat.com>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Star Zeng <star.zeng@intel.com>
    Reviewed-by: Michael Kinney <michael.d.kinney@intel.com>
    Reviewed-by: Laszlo Ersek <lersek@redhat.com>

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

                 reply	other threads:[~2016-10-11 16:20 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-67861-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).