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

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

This run is configured for baseline tests only.

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

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

Last test of basis    74836  2018-06-09 13:00:09 Z    1 days
Testing same since    74839  2018-06-10 07:54:36 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
  Kinney, Michael D <michael.d.kinney@xxxxxxxxx>
  Michael D Kinney <michael.d.kinney@xxxxxxxxx>
  Ruiyu Ni <ruiyu.ni@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 eb5943134630292db2c14346b5d94eab0b72314f
Author: Kinney, Michael D <michael.d.kinney@xxxxxxxxx>
Date:   Thu Mar 29 08:35:07 2018 -0700

    SignedCapsulePkg/SystemFirmwareUpdateDxe: Use progress API
    
    https://bugzilla.tianocore.org/show_bug.cgi?id=801
    
    Use PlatformFlashWriteWithProgress() instead of PlatformFLashWrite()
    so the user can be informed of the progress as a capsule is used
    to update a firmware image in a firmware device.
    
    Cc: Jiewen Yao <jiewen.yao@xxxxxxxxx>
    Signed-off-by: Michael D Kinney <michael.d.kinney@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Tested-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
    Reviewed-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
    Reviewed-by: Star Zeng <star.zeng@xxxxxxxxx>

commit 574761065744238440d2baf426d2ccc5912db13a
Author: Kinney, Michael D <michael.d.kinney@xxxxxxxxx>
Date:   Thu Feb 15 14:02:06 2018 -0800

    MdeModulePkg/DxeCapsuleLibFmp: Add progress bar support
    
    https://bugzilla.tianocore.org/show_bug.cgi?id=801
    
    Based on content from the following branch/commits:
    https://github.com/Microsoft/MS_UEFI/tree/share/MsCapsuleSupport
    
    * Change Update_Image_Progress() to UpdateImageProcess()
    * Call DisplayUpdateProgressLib from UpdateImageProgress().
    * Split out a boot service and runtime version of
      UpdateImageProgress() so the DisplayUpdateProgressLib is
      not used at runtime.
    * If gEdkiiFirmwareManagementProgressProtocolGuid is present,
      then use its progress bar color and watchdog timer value.
    * If gEdkiiFirmwareManagementProgressProtocolGuid is not present,
      then use default progress bar color and 5 min watchdog timer.
    * Remove Print() calls during capsule processing.  Instead,
      the DisplayUpdateProgressLib is used to inform the user
      of progress during a capsule update.
    
    Cc: Star Zeng <star.zeng@xxxxxxxxx>
    Cc: Eric Dong <eric.dong@xxxxxxxxx>
    Cc: Jiewen Yao <jiewen.yao@xxxxxxxxx>
    Cc: Sean Brogan <sean.brogan@xxxxxxxxxxxxx>
    Signed-off-by: Michael D Kinney <michael.d.kinney@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Tested-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
    Reviewed-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
    Reviewed-by: Star Zeng <star.zeng@xxxxxxxxx>

commit f3100a1a2f575e1a0ce4744cb2722e780135b1cf
Author: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
Date:   Tue May 29 18:12:51 2018 +0800

    MdeModulePkg/Ata/AtaAtapiPassThru: Enable/disable DEVSLP per policy
    
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
    Reviewed-by: Chasel Chiu <chasel.chiu@xxxxxxxxx>
    Reviewed-by: Hao A Wu <hao.a.wu@xxxxxxxxx>
    Reviewed-by: Star Zeng <star.zeng@xxxxxxxxx>

commit 06766c0e19092eed5563caeb94576f0d4ac65fd1
Author: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
Date:   Tue May 29 13:08:21 2018 +0800

    MdeModulePkg/AtaAtapiPassThru: enable/disable PUIS per policy
    
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
    Reviewed-by: Star Zeng <star.zeng@xxxxxxxxx>
    Reviewed-by: Chasel Chiu <chasel.chiu@xxxxxxxxx>
    Reviewed-by: Hao A Wu <hao.a.wu@xxxxxxxxx>

commit f87a1e4158994b4d16ae09ea0bc41831292dc94c
Author: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
Date:   Tue May 29 13:07:32 2018 +0800

    MdeModulePkg: Add AtaAtapiPolicy protocol definition
    
    The patch adds AtaAtapiPolicy protocol which is produced by platform
    and consumed by AtaAtapiPassThruDxe driver.
    
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
    Reviewed-by: Star Zeng <star.zeng@xxxxxxxxx>

commit 8d3c4b552f81ff7aafbe50e555032a83aef1b0d8
Author: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
Date:   Tue May 29 10:51:25 2018 +0800

    MdeModulePkg/AtaAtapiPassThru: Spin up Power up in Standby devices
    
    The patch adds support to certain devices that support PUIS (Power
    up in Standby).
    For those devices that supports SET_FEATURE spin up, SW needs to
    send SET_FEATURE subcommand to spin up the devices.
    For those devices that doesn't support SET_FEATURE spin up, SW needs
    to send read sectors command to spin up the devices.
    
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
    Reviewed-by: Chasel Chiu <chasel.chiu@xxxxxxxxx>
    Reviewed-by: Hao A Wu <hao.a.wu@xxxxxxxxx>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel