[Xen-devel] [ovmf baseline-only test] 71613: tolerable FAIL

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

This run is configured for baseline tests only.

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

Failures :-/ but no regressions.

Regressions which are regarded as allowable (not blocking):
 build-i386-libvirt            5 libvirt-build                fail   like 71610
 build-amd64-libvirt           5 libvirt-build                fail   like 71610

version targeted for testing:
 ovmf                 1fb805b1eb5b6039cb12375f8594aba65bf60a44
baseline version:
 ovmf                 157fb7bf29eea497b22025f53b5547e4748b6c2d

Last test of basis    71610  2017-06-27 21:50:21 Z    1 days
Testing same since    71613  2017-06-29 03:17:33 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>

jobs:
 build-amd64-xsm                                              pass    
 build-i386-xsm                                               pass    
 build-amd64                                                  pass    
 build-i386                                                   pass    
 build-amd64-libvirt                                          fail    
 build-i386-libvirt                                           fail    
 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 1fb805b1eb5b6039cb12375f8594aba65bf60a44
Author: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
Date:   Fri Jun 23 14:50:53 2017 +0000

    MdeModulePkg/AtaAtapiPassThru: relax PHY detect timeout
    
    The SATA spec mandates that link detection by the PHY completes within
    10 ms after receiving a reset signal. However, there is no obligation
    to uphold this requirement at the driver end as strictly as we do, and
    as it turns out, some combinations of host and device (e.g., Samsung
    850 EVO connected to a LeMaker Cello) are only borderline compliant,
    which means the device is not detected reliably.
    
    So let's allow for a bit of margin, and increase the PHY detect timeout
    value to 15 ms.
    
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
    Reviewed-by: Star Zeng <star.zeng@xxxxxxxxx>

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