[Xen-devel] [ovmf baseline-only test] 68383: tolerable trouble: blocked/broken

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

This run is configured for baseline tests only.

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

Failures :-/ but no regressions.

Regressions which are regarded as allowable (not blocking):
 build-i386                    3 host-install(3)       broken baseline untested
 build-amd64                   3 host-install(3)       broken baseline untested
 build-i386-pvops              3 host-install(3)       broken baseline untested
 build-i386-xsm                3 host-install(3)       broken baseline untested
 build-amd64-pvops             3 host-install(3)       broken baseline untested
 build-amd64-xsm               3 host-install(3)       broken baseline untested

Tests which did not succeed, but are not blocking:
 test-amd64-amd64-xl-qemuu-ovmf-amd64  1 build-check(1)             blocked n/a
 build-amd64-libvirt           1 build-check(1)               blocked  n/a
 test-amd64-i386-xl-qemuu-ovmf-amd64  1 build-check(1)              blocked n/a
 build-i386-libvirt            1 build-check(1)               blocked  n/a

version targeted for testing:
 ovmf                 315d9d08fd77db1024ccc5307823da8aaed85e2f
baseline version:
 ovmf                 2b631390f9f5f6971c3c8a7f0f47160b80cf072b

Last test of basis    68381  2017-01-17 08:46:09 Z    0 days
Testing same since    68383  2017-01-17 14:46:21 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Gary Lin <glin@xxxxxxxx>
  Laszlo Ersek <lersek@xxxxxxxxxx>

jobs:
 build-amd64-xsm                                              broken  
 build-i386-xsm                                               broken  
 build-amd64                                                  broken  
 build-i386                                                   broken  
 build-amd64-libvirt                                          blocked 
 build-i386-libvirt                                           blocked 
 build-amd64-pvops                                            broken  
 build-i386-pvops                                             broken  
 test-amd64-amd64-xl-qemuu-ovmf-amd64                         blocked 
 test-amd64-i386-xl-qemuu-ovmf-amd64                          blocked 


------------------------------------------------------------
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

broken-step build-i386 host-install(3)
broken-step build-amd64 host-install(3)
broken-step build-i386-pvops host-install(3)
broken-step build-i386-xsm host-install(3)
broken-step build-amd64-pvops host-install(3)
broken-step build-amd64-xsm host-install(3)

Push not applicable.

------------------------------------------------------------
commit 315d9d08fd77db1024ccc5307823da8aaed85e2f
Author: Gary Lin <glin@xxxxxxxx>
Date:   Tue Jan 17 12:52:32 2017 +0800

    OvmfPkg: pull in TLS modules with -D TLS_ENABLE (also enabling HTTPS)
    
    This commit introduces a new build option, TLS_ENABLE, to pull in the
    TLS-related modules. If HTTP_BOOT_ENABLE and TLS_ENABLE are enabled at
    the same time, the HTTP driver locates the TLS protocols automatically
    and thus HTTPS is enabled.
    
    To build OVMF with HTTP Boot:
    
    $ ./build.sh -D HTTP_BOOT_ENABLE
    
    To build OVMF with HTTPS Boot:
    
    $ ./build.sh -D HTTP_BOOT_ENABLE -D TLS_ENABLE
    
    Cc: Laszlo Ersek <lersek@xxxxxxxxxx>
    Cc: Justen Jordan L <jordan.l.justen@xxxxxxxxx>
    Cc: Wu Jiaxin <jiaxin.wu@xxxxxxxxx>
    Cc: Long Qin <qin.long@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Gary Lin <glin@xxxxxxxx>
    Reviewed-by: Wu Jiaxin <jiaxin.wu@xxxxxxxxx>
    Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx>

commit 32e22f20c985b6053fe286ef95882ded73b8b398
Author: Gary Lin <glin@xxxxxxxx>
Date:   Tue Jan 17 12:52:31 2017 +0800

    OvmfPkg: correct the IScsiDxe module included for the IPv6 stack
    
    Always use IScsiDxe from NetworkPkg when IPv6 is enabled since it provides
    the complete ISCSI support.
    
    NOTE: This makes OpenSSL a hard requirement when NETWORK_IP6_ENABLE is
          true.
    
    (Based on Jiaxin's suggestion)
    
    Cc: Laszlo Ersek <lersek@xxxxxxxxxx>
    Cc: Justen Jordan L <jordan.l.justen@xxxxxxxxx>
    Cc: Wu Jiaxin <jiaxin.wu@xxxxxxxxx>
    Cc: Long Qin <qin.long@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Gary Lin <glin@xxxxxxxx>
    Reviewed-by: Wu Jiaxin <jiaxin.wu@xxxxxxxxx>
    Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    [lersek@xxxxxxxxxx: update subject line]
    Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx>

commit 6d0f8941bdc2900085e7c1ab06df5549c10b91dd
Author: Gary Lin <glin@xxxxxxxx>
Date:   Tue Jan 17 12:52:30 2017 +0800

    OvmfPkg: always resolve OpenSslLib, IntrinsicLib and BaseCryptLib
    
    This commit provides unconditional library resolutions for the OpenSslLib,
    IntrinsicLib and BaseCryptLib classes, regardless of whether those classes
    are actually used by any module.
    
    Although those libraries depends on OpenSSL, they won't be built unless
    a module really uses them. Thus, missing OpenSSL from the tree won't
    cause any build failure as long as SECURE_BOOT_ENABLE is false.
    
    (Based on Jiaxin's patch and Laszlo's suggestion)
    
    Cc: Laszlo Ersek <lersek@xxxxxxxxxx>
    Cc: Justen Jordan L <jordan.l.justen@xxxxxxxxx>
    Cc: Wu Jiaxin <jiaxin.wu@xxxxxxxxx>
    Cc: Long Qin <qin.long@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Gary Lin <glin@xxxxxxxx>
    Reviewed-by: Wu Jiaxin <jiaxin.wu@xxxxxxxxx>
    Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx>

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