Skip to content

Test failures on cygwin #41

Closed
Closed

Description

@amai2012

Running the tests as of b50ced8 in cygwin (64bit) results in:

$ make test
g++ -fsyntax-only simplecpp.cpp && ./testrunner && python run-tests.py
TODO -E testsuite/clang-preprocessor-tests/c99-6_10_3_4_p5.c
TODO -E testsuite/clang-preprocessor-tests/c99-6_10_3_4_p6.c
FAILED -E testsuite/clang-preprocessor-tests/clang_headers.c
TODO -DA=1 -E testsuite/clang-preprocessor-tests/cxx_compl.cpp
TODO -E testsuite/clang-preprocessor-tests/cxx_oper_keyword_ms_compat.cpp
TODO -E testsuite/clang-preprocessor-tests/expr_usual_conversions.c
FAILED -E testsuite/clang-preprocessor-tests/has_attribute.cpp
TODO -E -Dfoo='bar\' testsuite/clang-preprocessor-tests/macro_backslash.c
TODO -E testsuite/clang-preprocessor-tests/macro_expand.c
TODO -E testsuite/clang-preprocessor-tests/macro_fn_comma_swallow.c
TODO -E testsuite/clang-preprocessor-tests/macro_fn_comma_swallow2.c
TODO -E -DNAMED testsuite/clang-preprocessor-tests/macro_fn_comma_swallow2.c
TODO -E testsuite/clang-preprocessor-tests/macro_fn_disable_expand.c
TODO -E testsuite/clang-preprocessor-tests/macro_fn_lparen_scan.c
TODO -E testsuite/clang-preprocessor-tests/macro_paste_commaext.c
TODO -E testsuite/clang-preprocessor-tests/macro_paste_hard.c
TODO -E testsuite/clang-preprocessor-tests/macro_rescan_varargs.c
TODO -E testsuite/clang-preprocessor-tests/stdint.c
TODO -E -Dint=a -Duint=b -D_t=c -DINT=d -DUINT=e -D_MIN=f -D_MAX=g testsuite/clang-preprocessor-tests/stdint.c
TODO -E -DTEST1 testsuite/clang-preprocessor-tests/stringize_misc.c
TODO -E testsuite/gcc-preprocessor-tests/diagnostic-pragma-1.c
FAILED -E testsuite/gcc-preprocessor-tests/normalize-3.c
TODO -E testsuite/gcc-preprocessor-tests/pr45457.c
TODO -E testsuite/gcc-preprocessor-tests/pr57580.c
FAILED -E testsuite/gcc-preprocessor-tests/pr63831-1.c
FAILED -E testsuite/gcc-preprocessor-tests/pr63831-2.c
FAILED -E testsuite/gcc-preprocessor-tests/pr65238-1.c
FAILED -E testsuite/gcc-preprocessor-tests/ucnid-2011-1.c
FIXED pr58844-1.c
FIXED pr58844-2.c
Number of tests: 176
Number of skipped: 15
Number of todos: 21
Number of failed: 7

I assume the FAILURES are all unexpected?

Activity

  1. amai2012 commented on Sep 8, 2016

    @amai2012
    ContributorAuthor

    Can this be related to http://trac.cppcheck.net/ticket/7725 "Include in source directory not found?!"?

  2. danmar commented on Sep 10, 2016

    @danmar
    Collaborator

    I assume the FAILURES are all unexpected?

    Yes they are unexpected.

    Also those "FIXED" are unexpected. They don't work in Linux.

  3. amai2012 commented on Sep 12, 2016

    @amai2012
    ContributorAuthor

    Are there any flags to produce a more verbose output?

  4. danmar commented on Sep 13, 2016

    @danmar
    Collaborator

    no .. but feel free to add such flag.

  5. amai2012 commented on Oct 27, 2016

    @amai2012
    ContributorAuthor

    Do those tests work for you on Windows? I wonder if that is a platform issue.

  6. danmar commented on Oct 29, 2016

    @danmar
    Collaborator

    hmm.. I get FIXED now on Linux too.

  7. danmar commented on Oct 29, 2016

    @danmar
    Collaborator

    I took care of those FIXED : see 6c55e17

    The testscript will now make sure they PASS. Otherwise it will say FAILED.

  8. amai2012 commented on Oct 31, 2016

    @amai2012
    ContributorAuthor

    Confirmed.
    Now 7 FAILED remaining:

    FAILED -E testsuite/clang-preprocessor-tests/clang_headers.c
    FAILED -E testsuite/clang-preprocessor-tests/has_attribute.cpp
    FAILED -E testsuite/gcc-preprocessor-tests/normalize-3.c
    FAILED -E testsuite/gcc-preprocessor-tests/pr63831-1.c
    FAILED -E testsuite/gcc-preprocessor-tests/pr63831-2.c
    FAILED -E testsuite/gcc-preprocessor-tests/pr65238-1.c
    FAILED -E testsuite/gcc-preprocessor-tests/ucnid-2011-1.c

  9. self-assigned this
    on Jun 22, 2017
  10. danmar commented on Jun 22, 2017

    @danmar
    Collaborator

    gcc in linux and cygwin generates somewhat different output. It might be because I have different gcc versions or because gcc was compiled with different settings.

    The clang_headers.c failed because <limits.h> was different in linux and cygwin. I skip that test.

    in my linux box gcc does not handle __has_attribute(). Therefore simplecpp pass in linux but fails in cygwin when that is used. For now I will skip these but maybe it would be best to handle __has_attribute().

    in my linux box the code "\u00a0" generates a "\u00a0" token. however in cygwin I get "\u000000a0". I assume these are the same. But simplecpp always outputs "\u00a0" so it will fail in cygwin. I will skip these tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions