[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



This run is configured for baseline tests only.

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

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                 19ca06bb84cafd661f7da34e9ca3c7ec6add1135
baseline version:
 ovmf                 5ab0ffc9f64f5a539a9bdb50446b7fbf92b845d6

Last test of basis    68398  2017-01-19 17:19:17 Z    1 days
Testing same since    68404  2017-01-20 09:16:30 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Dandan Bi <dandan.bi@xxxxxxxxx>
  Star Zeng <star.zeng@xxxxxxxxx>
  Thomas Huth <thuth@xxxxxxxxxx>
  Zhang Lubo <lubo.zhang@xxxxxxxxx>

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 19ca06bb84cafd661f7da34e9ca3c7ec6add1135
Author: Thomas Huth <thuth@xxxxxxxxxx>
Date:   Thu Jan 19 10:17:37 2017 +0100

    OvmfPkg: Remove superfluous return statements.
    
    If the code eventually returns "Status" anyway, it does not make
    sense to explicitely return "Status" in case of an error, too.
    
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Thomas Huth <thuth@xxxxxxxxxx>
    Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx>

commit 266746561d454d3d35938886e61a02b1ee1abaff
Author: Zhang Lubo <lubo.zhang@xxxxxxxxx>
Date:   Fri Jan 6 17:15:27 2017 +0800

    ShellPkg: Add check logic for the gateway validity.
    
    if we set a static IP using command
    'ifconfig -s eth0 static 192.168.0.121 255.255.255.0 0.0.0.0'
    The system says 'Failed to set address.' but using
    'ifconfig -l', the static IP can be assigned successfully.
    so we need to check the gateway validity before setting manual
    address to keep the ifconfig -s command more consistent.
    
    Signed-off-by: Zhang Lubo <lubo.zhang@xxxxxxxxx>
    Cc: Santhapur Naveen <naveens@xxxxxxxxxxxxxx>
    Cc: Ye Ting <ting.ye@xxxxxxxxx>
    Cc: Fu Siyuan <siyuan.fu@xxxxxxxxx>
    Cc: Wu Jiaxin <jiaxin.wu@xxxxxxxxx>
    Reviewed-by: Wu Jiaxin <jiaxin.wu@xxxxxxxxx>
    Reviewed-by: Ye Ting <ting.ye@xxxxxxxxx>
    Reviewed-by: Fu Siyuan <siyuan.fu@xxxxxxxxx>

commit eabc6e59b9a718a44ab292f7e5c447c4c06d21c4
Author: Zhang Lubo <lubo.zhang@xxxxxxxxx>
Date:   Thu Dec 8 19:26:24 2016 +0800

    NetworkPkg: Add dns support for target URL configuration in ISCSI.
    
    v2:
    *1. Add IScsiDnsIsConfigured function in IScsiSupported to check
    attempt using DNS protocol or not.2. Fix wrongs typos in IScsiDns.c
    and .uni file.3. define a macro for the length of target URL.4.
    update the Copyright to 2017.
    
    Add DNS support for target URL directly configuration in UI.
    
    Besides, When we enable the option (Get target info via DHCP) ,
    the dhcp server will return target info include the  rootpath,
    like the format
    "iscsi:"<servername>":"<protocol>":"<port>":"<LUN>":"<targetname>
    According to the RFC 4173,the server name region is expressed as
    IPv4(192.168.10.20 )or IPv6 ([2000:bbbb::3]) or domain name,
    but currently we only support the IP address format.
    To enable this feature, we can support both.
    
    Another enhancement is that we can deal with the data received from
    the iSCSI login response with an target redirection status,
    in which contains the Target Address in the format
    domainname[:port][,portal-group-tag] required by RFC 3720.
    
    Cc: Ye Ting <ting.ye@xxxxxxxxx>
    Cc: Fu Siyuan <siyuan.fu@xxxxxxxxx>
    Cc: Wu Jiaxin <jiaxin.wu@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Zhang Lubo <lubo.zhang@xxxxxxxxx>
    Reviewed-by: Wu Jiaxin <jiaxin.wu@xxxxxxxxx>
    Reviewed-by: Ye Ting <ting.ye@xxxxxxxxx>
    Reviewed-by: Fu Siyuan <siyuan.fu@xxxxxxxxx>

commit a409875592d984fdc412675e93884556eb6635d0
Author: Dandan Bi <dandan.bi@xxxxxxxxx>
Date:   Thu Jan 12 20:25:40 2017 +0800

    MdeModulePkg/FileExplorer: Enable functionality of creating new file/folder
    
    https://bugzilla.tianocore.org/show_bug.cgi?id=324
    
    Enhance the FileExplorerlib so that user can create a new file/folder
    through the UI page.
    
    Cc: Eric Dong <eric.dong@xxxxxxxxx>
    Cc: Liming Gao <liming.gao@xxxxxxxxx>
    Cc: Jiewen Yao <jiewen.yao@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Dandan Bi <dandan.bi@xxxxxxxxx>
    Reviewed-by: Eric Dong <eric.dong@xxxxxxxxx>

commit 9cf1aa29cf4036c21a69b6faeebd4d91dd50b12e
Author: Dandan Bi <dandan.bi@xxxxxxxxx>
Date:   Thu Jan 12 18:49:40 2017 +0800

    MdeModulePkg/FileExplorer: Update QuesrionId when Updating FileExplore form
    
    https://bugzilla.tianocore.org/show_bug.cgi?id=342
    
    When user select and enter a directory, File Explorer will update the
    form based on the new folders and files in the directory. But when
    creating question opcodes, the question id is same with previous one
    and this will cause browser to show the highlight menu incorrectly.
    
    Cc: Eric Dong <eric.dong@xxxxxxxxx>
    Cc: Liming Gao <liming.gao@xxxxxxxxx>
    Cc: Jiewen Yao <jiewen.yao@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Dandan Bi <dandan.bi@xxxxxxxxx>
    Reviewed-by: Eric Dong <eric.dong@xxxxxxxxx>

commit d9b64abbdf70e42f8e20bd372aaf9605cb20b725
Author: Dandan Bi <dandan.bi@xxxxxxxxx>
Date:   Tue Jan 10 13:17:28 2017 +0800

    MdeModulePkg/FileExplorer: Remove the codes of searching load file protocol
    
    https://bugzilla.tianocore.org/show_bug.cgi?id=323
    
    FileExplorer no need to search load file protocol to show files.
    Now remove the codes.
    
    Cc: Eric Dong <eric.dong@xxxxxxxxx>
    Cc: Liming Gao <liming.gao@xxxxxxxxx>
    Cc: Jiewen Yao <jiewen.yao@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Dandan Bi <dandan.bi@xxxxxxxxx>
    Reviewed-by: Eric Dong <eric.dong@xxxxxxxxx>

commit a08cdd228a3ec593c28e1d445cd92cee8e17535b
Author: Dandan Bi <dandan.bi@xxxxxxxxx>
Date:   Mon Jan 16 09:58:47 2017 +0800

    ShellPkg/HandleParsingLib: Fix coding style issue
    
    Cc: Jaben Carsey <jaben.carsey@xxxxxxxxx>
    Cc: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Dandan Bi <dandan.bi@xxxxxxxxx>
    Reviewed-by: Jaben Carsey <jaben.carsey@xxxxxxxxx>

commit c326e0780a12f912bc6cb7a37ea0f6b201a7567c
Author: Star Zeng <star.zeng@xxxxxxxxx>
Date:   Thu Jan 12 18:21:29 2017 +0800

    ShellPkg SmbiosView: Add missing decoding of SMBIOS spec 3.0.0
    
    REF: https://bugzilla.tianocore.org/show_bug.cgi?id=345
    
    When I am adding SMBIOS spec 3.1.0 support, I found the decoding
    of SMBIOS spec 3.0.0 for some definitions is missing.
    
    Cc: Jaben Carsey <jaben.carsey@xxxxxxxxx>
    Cc: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Star Zeng <star.zeng@xxxxxxxxx>
    Reviewed-by: Jaben Carsey <jaben.carsey@xxxxxxxxx>

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.