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] 68034: all pass
Date: Mon, 14 Nov 2016 14:08:49 +0000	[thread overview]
Message-ID: <osstest-68034-mainreport@xen.org> (raw)

This run is configured for baseline tests only.

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

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

Last test of basis    68033  2016-11-14 09:16:38 Z    0 days
Testing same since    68034  2016-11-14 12:18:33 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Feng Tian <feng.tian@intel.com>
  Richard Thomaiyar <richard.marian.thomaiyar@intel.com>
  Thomaiyar, Richard Marian <richard.marian.thomaiyar@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 b17d5507cfdfd10c4f1f5911ffe75fdc49fafa37
Author: Feng Tian <feng.tian@intel.com>
Date:   Mon Nov 7 15:46:16 2016 +0800

    MdeModulePkg/UsbMass: Revert changes of removing retry logic
    
    This patch is used to revert changes done in commit 17f3e942
    bc527fbd75068d2d5752b6af54917487 - "MdeModulePkg/UsbMass: Not
    retry if usb bot transfer execution fail"
    
    It's because Usb Floppy will report DEVICE_ERROR for the first
    several cmds when it need spin up. so retry logic makes sense.
    
    Cc: Star Zeng <star.zeng@intel.com>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Feng Tian <feng.tian@intel.com>
    Reviewed-by: Star Zeng <star.zeng@intel.com>

commit f56ae7bf82bf32dd0ec9cafb9f632511813c823e
Author: Thomaiyar, Richard Marian <richard.marian.thomaiyar@intel.com>
Date:   Tue Nov 8 17:45:25 2016 +0800

    IntelFsp2Pkg: Support to return error status from FSP API done
    
    Added FspMemoryInitDone2, FspTempRamExitDone2, FspSiliconInitDone2
    to return error status to Boot Loader for FSP API calls.
    To maintain backward compatibility existing functions
    (FspMemoryInitDone, FspTempRamExitDone, FspSiliconInitDone)
    declaration left untouched.
    
    Cc: Maurice Ma <maurice.ma@intel.com>
    Cc: Jiewen Yao <jiewen.yao@intel.com>
    Cc: Giri P Mudusuru <giri.p.mudusuru@intel.com>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Richard Thomaiyar <richard.marian.thomaiyar@intel.com>
    Reviewed-by: Jiewen Yao <jiewen.yao@intel.com>
    Reviewed-by: Giri P Mudusuru <giri.p.mudusuru@intel.com>

commit d18f9699e7c98bf63f9d92f8e111bb3a6b3d0882
Author: Feng Tian <feng.tian@intel.com>
Date:   Thu Nov 10 13:16:14 2016 +0800

    MdePkg: Fix spec mismatch in string representation of EMMC dev node
    
    Cc: Eric Jin <eric.jin@intel.com>
    Cc: Liming Gao <liming.gao@intel.com>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Feng Tian <feng.tian@intel.com>
    Reviewed-by: Ruiyu Ni <ruiyu.ni@intel.com>

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

                 reply	other threads:[~2016-11-14 14:08 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-68034-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).