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

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

This run is configured for baseline tests only.

flight 75398 ovmf real [real]

Failures and problems with tests :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 build-amd64-xsm                 <job status>                 broken
 build-i386                      <job status>                 broken
 build-amd64-pvops               <job status>                 broken
 build-i386-xsm                  <job status>                 broken
 build-amd64                     <job status>                 broken
 build-i386-pvops                <job status>                 broken

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
 build-amd64                   4 host-install(4)       broken baseline untested
 build-i386-pvops              4 host-install(4)       broken baseline untested
 build-i386                    4 host-install(4)       broken baseline untested
 build-amd64-xsm               4 host-install(4)       broken baseline untested
 build-i386-xsm                4 host-install(4)       broken baseline untested
 build-amd64-pvops             4 host-install(4)       broken baseline untested

version targeted for testing:
 ovmf                 8122c6bc8b6f1fde31f2af6c1560ec552204980d
baseline version:
 ovmf                 b9c055f72b9dbc9cef3a65b9a4932ad6e4f403e0

Last test of basis    75394  2018-10-11 10:20:15 Z    0 days
Testing same since    75398  2018-10-12 00:20:37 Z    0 days    1 attempts

People who touched revisions under test:
  Dongao Guo <dongao.guo@xxxxxxxxx>
  Guo, Dongao <dongao.guo@xxxxxxxxx>

 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

Test harness code can be found at

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

Push not applicable.

commit 8122c6bc8b6f1fde31f2af6c1560ec552204980d
Author: Guo, Dongao <dongao.guo@xxxxxxxxx>
Date:   Mon Oct 8 15:56:48 2018 +0800

    MdeModulePkg/RegularExpressionDxe:omit unused variable
    comment unused variable to avoid warning,and modify inf build option.
    Cc: Liming Gao <liming.gao@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Dongao Guo <dongao.guo@xxxxxxxxx>
    Reviewed-by: Liming Gao <liming.gao@xxxxxxxxx>

commit 4ee787cc1b158566145d23be941aa2abb5c29c7c
Author: Guo, Dongao <dongao.guo@xxxxxxxxx>
Date:   Wed Oct 10 15:39:03 2018 +0800

    MdeModulePkg/RegularExpressionDxe:disable wraning to pass gcc4.8 build
    There are three warnings reported by GCC 4.8 and the later GCC release
    are workaround with them.
    And all the three warnings are invalid,so I just disable warnings rather
    than fix them at now.
    Following is the analysis from Laszlo Ersek.
    > MdeModulePkg/Universal/RegularExpressionDxe/Oniguruma/regcomp.c: In
    > function 'compile_length_tree':
    > MdeModulePkg/Universal/RegularExpressionDxe/Oniguruma/regcomp.c:1516:7:
    > warning: 'len' may be used uninitialized in this function
    > [-Wmaybe-uninitialized]
    >    int len;
    >        ^
    I think this is an invalid warning; the type of the controlling expression
    (node->type) is enum GimmickType, and the case labels cover all values of
    the enum. An assert(0) could be added, I guess, but again, upstream
    Oniguruma would be justified to reject the idea.
    > MdeModulePkg/Universal/RegularExpressionDxe/Oniguruma/regparse.c: In
    > function 'parse_callout_args.isra.10.constprop.30':
    > MdeModulePkg/Universal/RegularExpressionDxe/Oniguruma/regparse.c:6753:25:
    > warning: 'rl' may be used uninitialized in this function
    > [-Wmaybe-uninitialized]
    >   vals[n].l = rl;
    >               ^
    This warning is invalid, given:
      6749    if (cn > 0) {
      6750      long rl;
      6751      r = parse_long(enc, buf, bufend, 1, LONG_MAX, &rl);
      6752      if (r == ONIG_NORMAL) {
      6753        vals[n].l = rl;
    Because parse_long() only returns ONIG_NORMAL after it sets (*rl).
    > MdeModulePkg/Universal/RegularExpressionDxe/Oniguruma/regparse.c: In
    > function 'parse_callout_of_name.constprop.29':
    > MdeModulePkg/Universal/RegularExpressionDxe/Oniguruma/regparse.c:6861:38:
    > warning: 'tag_end' may be used uninitialized in this function
    > [-Wmaybe-uninitialized]
    >      if (! is_allowed_callout_tag_name(enc, tag_start, tag_end))
    This warning is also invalid, given:
      6852    if (c == '[') {
      6853      if (PEND) return ONIGERR_END_PATTERN_IN_GROUP;
      6854      tag_start = p;
      6855      while (! PEND) {
      6856        if (PEND) return ONIGERR_END_PATTERN_IN_GROUP;
      6857        tag_end = p;
      6858        PFETCH_S(c);
      6859        if (c == ']') break;
      6860      }
      6861      if (! is_allowed_callout_tag_name(enc, tag_start, tag_end))
      6862        return ONIGERR_INVALID_CALLOUT_TAG_NAME;
    To see that, first we should note:
     #define PEND         (p < end ?  0 : 1)
    therefore PEND doesn't change if neither "p" nor "end" change.
    Second, when we reach line 6855 (the "while") for the very first time,
    (!PEND) is certainly true (i.e., PEND is false), because otherwise we
    would have bailed at line 6853. Therefore we reach line 6857, and assign
    "tag_end". Regardless of whether we iterate zero or more *additional*
    times around the loop, "tag_end" will have been set, whenever we reach
    line 6861.
    Cc: Liming Gao <liming.gao@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Dongao Guo <dongao.guo@xxxxxxxxx>
    Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx>

Xen-devel mailing list



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