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] 67612: all pass
Date: Wed, 31 Aug 2016 09:19:30 +0100	[thread overview]
Message-ID: <osstest-67612-mainreport@xen.org> (raw)

This run is configured for baseline tests only.

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

Perfect :-)
All tests in this flight passed as required
version targeted for testing:
 ovmf                 965268ea6df485d78b982d00270bd4ce7f673820
baseline version:
 ovmf                 5f53a7aa59d4df1fe4326af18a9240d4dfebc129

Last test of basis    67608  2016-08-30 10:48:34 Z    0 days
Testing same since    67612  2016-08-31 06:23:03 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Hao Wu <hao.a.wu@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 965268ea6df485d78b982d00270bd4ce7f673820
Author: Hao Wu <hao.a.wu@intel.com>
Date:   Tue Aug 30 09:59:02 2016 +0800

    SecurityPkg: Use IsZeroGuid API for zero GUID checking
    
    Instead of comparing a GUID with gZeroGuid via the CompareGuid API, the
    commit uses the IsZeroGuid API to check if the given GUID is a zero GUID.
    
    Cc: Chao Zhang <chao.b.zhang@intel.com>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Hao Wu <hao.a.wu@intel.com>
    Reviewed-by: Chao Zhang <chao.b.zhang@intel.com>

commit 39cde03cc5efd67c11dc75cd5ba5e8ccf55c5594
Author: Hao Wu <hao.a.wu@intel.com>
Date:   Tue Aug 30 09:57:59 2016 +0800

    MdeModulePkg: Use IsZeroGuid API for zero GUID checking
    
    Instead of comparing a GUID with gZeroGuid via the CompareGuid API, the
    commit uses the IsZeroGuid API to check if the given GUID is a zero GUID.
    
    Cc: Feng Tian <feng.tian@intel.com>
    Cc: Star Zeng <star.zeng@intel.com>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Hao Wu <hao.a.wu@intel.com>
    Reviewed-by: Feng Tian <feng.tian@Intel.com>

commit dc2109946df2522974a058b0bca5530befdea1cd
Author: Hao Wu <hao.a.wu@intel.com>
Date:   Tue Aug 30 09:51:40 2016 +0800

    IntelFrameworkModulePkg: Use IsZeroGuid API for zero GUID checking
    
    Instead of comparing a GUID with gZeroGuid via the CompareGuid API, the
    commit uses the IsZeroGuid API to check if the given GUID is a zero GUID.
    
    Cc: Jeff Fan <jeff.fan@intel.com>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Hao Wu <hao.a.wu@intel.com>
    Reviewed-by: Jeff Fan <jeff.fan@intel.com>

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

                 reply	other threads:[~2016-08-31  8:19 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-67612-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.