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] 67999: all pass
Date: Sat, 5 Nov 2016 08:34:58 +0000	[thread overview]
Message-ID: <osstest-67999-mainreport@xen.org> (raw)

This run is configured for baseline tests only.

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

Perfect :-)
All tests in this flight passed as required
version targeted for testing:
 ovmf                 fdaf78424da45b34ef515119cd308ffa8cd43d54
baseline version:
 ovmf                 669b6cc60bf610bbee32e79ed165ca604764c169

Last test of basis    67997  2016-11-04 16:17:17 Z    0 days
Testing same since    67999  2016-11-05 00:51:50 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Ard Biesheuvel <ard.biesheuvel@linaro.org>
  Jiewen Yao <jiewen.yao@intel.com>
  Laszlo Ersek <lersek@redhat.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 fdaf78424da45b34ef515119cd308ffa8cd43d54
Author: Jiewen Yao <jiewen.yao@intel.com>
Date:   Sat Oct 29 20:51:56 2016 +0800

    BaseTools/Pkcs7: Add readme.md
    
    Add readme.md to describe the X.509 certificate generation.
    
    Cc: Yonghong Zhu <yonghong.zhu@intel.com>
    Cc: Liming Gao <liming.gao@intel.com>
    Cc: Michael D Kinney <michael.d.kinney@intel.com>
    Cc: Qin Long <qin.long@intel.com>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Jiewen Yao <jiewen.yao@intel.com>
    Reviewed-by: Qin Long <qin.long@intel.com>

commit 12a37b2ae19b1edabf390c0744ae0af9bb9d2b9a
Author: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Date:   Thu Nov 3 17:29:01 2016 +0000

    MdePkg/BaseMemoryLib*: check for zero length in ZeroMem ()
    
    Unlike other string functions in this library, ZeroMem () does not
    return early when the length of the input buffer is 0. So add the
    same to ZeroMem () as well, for all implementations of BaseMemoryLib
    living under MdePkg/
    
    This fixes an issue with the ARM implementation of BaseMemoryLibOPtDxe,
    whose InternalMemZeroMem code does not expect a length of 0, and always
    writes at least a single byte.
    
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
    Acked-by: Laszlo Ersek <lersek@redhat.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-11-05  8:34 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-67999-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).