Menu

#105 test issues on SunOS

v1.0 (example)
closed-invalid
nobody
None
5
2015-06-08
2015-06-06
No

Running the test suite I notice numerous issues on SunOS i386 (compiled in pkgsrc with gcc4.9.2)

example extract:

Running suite(s): Check Servant
Running suite(s):100%: Checks: 0, Failures: 0, Errors: 0
check.c:496: Bad status in set_fork_status
Check Servant2
27%: Checks: 146, Failures: 58, Errors: 48
...

test output log attached...

Any hints on how to proceed?

1 Attachments

Discussion

  • Branden Archer

    Branden Archer - 2015-06-08

    Although perhaps not intuitive, the attached log indicates that all test suites passed:

    ==================
    All 7 tests passed
    ==================

    As part of the unit tests, there are tests which check that Check can properly fail if an assertion fails. This results in many failures in the logs. However, those failures are expected, and some test suites in Check are checking that there are failures when expected. So, if one of those failures did not occur as expected, the a test suite would fail, which would indicate that something went wrong.

    In short, everything worked out as expected. Sorry for the confusion.

     
  • Branden Archer

    Branden Archer - 2015-06-08
    • status: open --> closed-invalid
     
  • Richard PALO

    Richard PALO - 2015-06-08

    yes, 'check.c:496: Bad status in set_fork_status' is particularly disconcerting.

     

Log in to post a comment.

MongoDB Logo MongoDB