All of lore.kernel.org
 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] 68033: all pass
Date: Mon, 14 Nov 2016 11:25:03 +0000	[thread overview]
Message-ID: <osstest-68033-mainreport@xen.org> (raw)

This run is configured for baseline tests only.

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

Perfect :-)
All tests in this flight passed as required
version targeted for testing:
 ovmf                 8677a56af68ea7fc93938c710be2ec53752ae961
baseline version:
 ovmf                 ffd6b0b1b65e620816fb16fe551f92309f4b7269

Last test of basis    68029  2016-11-13 05:48:23 Z    1 days
Testing same since    68033  2016-11-14 09:16:38 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Jeff Fan <jeff.fan@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 8677a56af68ea7fc93938c710be2ec53752ae961
Author: Jeff Fan <jeff.fan@intel.com>
Date:   Fri Nov 11 19:51:36 2016 +0800

    UefiCpuPkg/DxeMpLib: Place APs to suitable state on Legacy OS boot
    
    Currently, DxeMpLib only places APs into specified c-state in Exit Boot Service
    callback function for UEFI OS boot. We need to put APs into specified c-state
    for legacy OS boot also.
    
    https://bugzilla.tianocore.org/show_bug.cgi?id=210
    
    Cc: Laszlo Ersek <lersek@redhat.com>
    Cc: Paolo Bonzini <pbonzini@redhat.com>
    Cc: Feng Tian <feng.tian@intel.com>
    Cc: Jiewen Yao <jiewen.yao@intel.com>
    Cc: Michael D Kinney <michael.d.kinney@intel.com>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Jeff Fan <jeff.fan@intel.com>
    Reviewed-by: Feng Tian <feng.tian@intel.com>

commit 86af2eb8b4ec03e59c8c26cf7d51d294a7f905e7
Author: Jeff Fan <jeff.fan@intel.com>
Date:   Fri Nov 11 19:48:09 2016 +0800

    UefiCpuPkg/DxeMpLib: Rename MpInitExitBootServicesCallback()
    
    Rename MpInitExitBootServicesCallback() to MpInitChangeApLoopCallback() because
    it will not only be invoked on Exit Boot Service Event, but also will be invoked
    on Legacy Ready To Boot Event.
    
    https://bugzilla.tianocore.org/show_bug.cgi?id=210
    
    Cc: Laszlo Ersek <lersek@redhat.com>
    Cc: Paolo Bonzini <pbonzini@redhat.com>
    Cc: Feng Tian <feng.tian@intel.com>
    Cc: Jiewen Yao <jiewen.yao@intel.com>
    Cc: Michael D Kinney <michael.d.kinney@intel.com>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Jeff Fan <jeff.fan@intel.com>
    Reviewed-by: Feng Tian <feng.tian@intel.com>

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

                 reply	other threads:[~2016-11-14 11:25 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-68033-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.