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] 68571: all pass
Date: Fri, 17 Feb 2017 07:53:49 +0000	[thread overview]
Message-ID: <osstest-68571-mainreport@xen.org> (raw)

This run is configured for baseline tests only.

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

Perfect :-)
All tests in this flight passed as required
version targeted for testing:
 ovmf                 b173ad78519b2ade309019614b52e1453727e20d
baseline version:
 ovmf                 fd12acdeff7a04ad34ccb95103eb6204b8901749

Last test of basis    68568  2017-02-16 15:17:39 Z    0 days
Testing same since    68571  2017-02-17 00:50:59 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Haojian Zhuang <haojian.zhuang@linaro.org>
  Jiaxin Wu <jiaxin.wu@intel.com>
  Ruiyu Ni <ruiyu.ni@intel.com>
  Wu Jiaxin <jiaxin.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 b173ad78519b2ade309019614b52e1453727e20d
Author: Jiaxin Wu <jiaxin.wu@intel.com>
Date:   Wed Feb 15 14:32:14 2017 +0800

    NetworkPkg/HttpBootDxe: Update to check specified media type
    
    IANA has approved below new media type for EFI http(s) boot usage:
      application/vnd.efi.img
      application/vnd.efi.iso
    
    HTTP boot driver should be updated to check the above media type
    from Content-Type header field.
    
    Cc: Ye Ting <ting.ye@intel.com>
    Cc: Fu Siyuan <siyuan.fu@intel.com>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Wu Jiaxin <jiaxin.wu@intel.com>
    Reviewed-by: Fu Siyuan <siyuan.fu@intel.com>
    Reviewed-by: Ye Ting <ting.ye@intel.com>

commit 6c6452c6e23a89be0e565501500e83c136e3fcbd
Author: Jiaxin Wu <jiaxin.wu@intel.com>
Date:   Thu Feb 16 09:15:11 2017 +0800

    NetworkPkg/HttpBootDxe: Declare the functions as EFIAPI to pass the GCC build
    
    Cc: Laszlo Ersek <lersek@redhat.com>
    Cc: Gerd Hoffmann <kraxel@redhat.com>
    Cc: Ye Ting <ting.ye@intel.com>
    Cc: Fu Siyuan <siyuan.fu@intel.com>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Wu Jiaxin <jiaxin.wu@intel.com>
    Reviewed-by: Laszlo Ersek <lersek@redhat.com>
    Build-tested-by: Laszlo Ersek <lersek@redhat.com>

commit d176bb3c5c28e0c89ae86995ecd6b9e21b4e0b9f
Author: Haojian Zhuang <haojian.zhuang@linaro.org>
Date:   Mon Feb 13 15:53:00 2017 +0800

    ArmPlatformPkg/PL061Gpio: fix the offset value in Get function
    
    When call PL061GetPins() or PL061SetPins(), should use GPIO_PIN_MASK(offset)
    as parameter, not offset.
    
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Haojian Zhuang <haojian.zhuang@linaro.org>
    Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>

commit d164a0e31bf8aa5bc8f9a184a02648585ff4f0d7
Author: Haojian Zhuang <haojian.zhuang@linaro.org>
Date:   Mon Feb 13 15:52:59 2017 +0800

    ArmPlatformPkg/PL061: remove duplicated PL061_GPIO_DATA_REG
    
    PL061_GPIO_DATA_REG offset is referenced in PL061EffectiveAddress ()
    already. So remove the duplicated reference when invoke PL061GetPins ()
    or PL061SetPins ().
    
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Haojian Zhuang <haojian.zhuang@linaro.org>
    Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>

commit 31d7be0135b8e8b95508daa6484bebba6280af15
Author: Ruiyu Ni <ruiyu.ni@intel.com>
Date:   Thu Feb 9 17:24:05 2017 +0800

    ShellPkg/pci: Report error when invalid value is specified for "-ec"
    
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Ruiyu Ni <ruiyu.ni@intel.com>
    Reviewed-by: Jaben Carsey <jaben.carsey@intel.com>

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

                 reply	other threads:[~2017-02-17  7:53 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-68571-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).