[Xen-devel] [ovmf baseline-only test] 71974: all pass

[Platform Team regression test user <citrix-osstest@xxxxxxxxxxxxxx>]

This run is configured for baseline tests only.

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

Perfect :-)
All tests in this flight passed as required
version targeted for testing:
 ovmf                 0024172d909ec73a9ce9ffdfc9fdd4382080e110
baseline version:
 ovmf                 79de8c79cdef26e5578050b7f1a206745c6cff14

Last test of basis    71973  2017-08-14 07:50:11 Z    0 days
Testing same since    71974  2017-08-14 18:17:16 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Andrew Fish <afish@xxxxxxxxx>
  Hao Wu <hao.a.wu@xxxxxxxxx>
  Jiaxin Wu <jiaxin.wu@xxxxxxxxx>
  Wu Jiaxin <jiaxin.wu@xxxxxxxxx>

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 0024172d909ec73a9ce9ffdfc9fdd4382080e110
Author: Andrew Fish <afish@xxxxxxxxx>
Date:   Mon Aug 7 11:26:05 2017 +0800

    BaseTools: Fix Segmentation fault: 11 when build AppPkg with XCODE5
    
    it is a bug in mtoc setting the size of the debug directory entry to
    the size of the .debug section, not the size of the
    EFI_IMAGE_DEBUG_DIRECTORY_ENTRY. It was causing a loop to iterate and
    get bogus EFI_IMAGE_DEBUG_DIRECTORY_ENTRY data and pass that to
    memset() and boom.
    
    Cc: Liming Gao <liming.gao@xxxxxxxxx>
    Cc: Michael D Kinney <michael.d.kinney@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Andrew Fish <afish@xxxxxxxxx>
    Reviewed-by: Liming Gao <liming.gao@xxxxxxxxx>

commit 7b1dbd15ea00d09f5e8b1fe0f6c97f1eba0f7efe
Author: Jiaxin Wu <jiaxin.wu@xxxxxxxxx>
Date:   Mon Jan 23 10:18:30 2017 +0800

    NetworkPkg/HttpBootDxe: Update device path node to include DNS information
    
    Cc: Ye Ting <ting.ye@xxxxxxxxx>
    Cc: Fu Siyuan <siyuan.fu@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Wu Jiaxin <jiaxin.wu@xxxxxxxxx>
    Reviewed-by: Ye Ting <ting.ye@xxxxxxxxx>

commit 67e0bbd6c34942a238c8381d14aa984b30f27f0c
Author: Jiaxin Wu <jiaxin.wu@xxxxxxxxx>
Date:   Tue Jan 24 11:51:01 2017 +0800

    MdeModulePkg/UefiBootManagerLib: Support DNS device path description
    
    This patch is to update UEFI Boot manager to support DNS device path
    for HTTP(S) network boot.
    
    Cc: Ye Ting <ting.ye@xxxxxxxxx>
    Cc: Fu Siyuan <siyuan.fu@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Wu Jiaxin <jiaxin.wu@xxxxxxxxx>
    Reviewed-by: Ye Ting <ting.ye@xxxxxxxxx>

commit 9b9d0655c1547384c2b34cea94eab4b8b83bd1b9
Author: Jiaxin Wu <jiaxin.wu@xxxxxxxxx>
Date:   Tue Jul 25 11:08:16 2017 +0800

    MdePkg/UefiDevicePathLib: Add DevPathFromTextDns and DevPathToTextDns 
libraries
    
    V3:
    * Fix the bug in DevPathFromTextDns()
    
    V2:
    * Add no IP instance case check.
    
    Cc: Ye Ting <ting.ye@xxxxxxxxx>
    Cc: Fu Siyuan <siyuan.fu@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Wu Jiaxin <jiaxin.wu@xxxxxxxxx>
    Reviewed-by: Fu Siyuan <siyuan.fu@xxxxxxxxx>
    Reviewed-by: Ye Ting <ting.ye@xxxxxxxxx>

commit ecbabb7f8bf435c69bac97dee22899471294319b
Author: Jiaxin Wu <jiaxin.wu@xxxxxxxxx>
Date:   Mon Jan 23 10:17:58 2017 +0800

    MdePkg/DevicePath.h: Add DNS Device Path definition
    
    This patch adds the DNS device path node definition.
    
    Cc: Ye Ting <ting.ye@xxxxxxxxx>
    Cc: Fu Siyuan <siyuan.fu@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Wu Jiaxin <jiaxin.wu@xxxxxxxxx>
    Reviewed-by: Ye Ting <ting.ye@xxxxxxxxx>

commit b92efc9fe5aebf4115e076c3ef44c82b21da4e20
Author: Hao Wu <hao.a.wu@xxxxxxxxx>
Date:   Tue Aug 8 16:34:43 2017 +0800

    MdeModulePkg/EmmcDxe: Make sure no extra data is erased by EraseBlocks
    
    V3 changes:
    Add debug messages for new return path when successfully erase the
    specified blocks. Refine logic for calculating the size for writing
    zeros to device.
    
    V2 changes:
    
    The Trim command is not supported on all eMMC devices. For those devices
    that do not support such command, add codes to handle the scenario.
    
    Commit message:
    
    The current implementation of the Erase Block Protocol service
    EraseBlocks() uses the erase command. According to spec eMMC Electrical
    Standard 5.1, Section 6.6.9:
    
    The erasable unit of the eMMC is the "Erase Group"; Erase group is
    measured in write blocks that are the basic writable units of the Device.
    ...
    When the Erase is executed it will apply to all write blocks within an
    erase group.
    
    However, code logic in function EmmcEraseBlocks() does not check whether
    the blocks to be erased form complete erase groups. Missing such checks
    will lead to erasing extra data on the device.
    
    This commit will:
    a. If the device support the Trim command, use the Trim command to
    perform the erase operations for eMMC devices.
    
    According to the spec:
    Unlike the Erase command, the Trim function applies the erase operation to
    write blocks instead of erase groups.
    
    b. If the device does not support the Trim command, use the Erase command
    to erase the data in the erase groups. And write zeros to those blocks
    that cannot form a complete erase group.
    
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Hao Wu <hao.a.wu@xxxxxxxxx>
    Reviewed-by: Star Zeng <star.zeng@xxxxxxxxx>

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