Skip to content

Conversation

@totalgee
Copy link
Contributor

  • also add unit tests to cover some broken (now fixed) cases.

Issue this pull request references: #376

- also add unit tests to cover some broken (now fixed) cases.
@totalgee
Copy link
Contributor Author

How does one figure out what the error was? I built everything and ran the unit tests, and there were no errors, nor were there with most of the CI builds/tests. But here, it says one of the fuzz tests (only when compiling with GCC v6) had a segmentation fault, but I don't even know what it was testing:

        Start 2907: fuzz.MINIMIZED/fc5434a62691cb7f3ba4e327d713bb84024ce265
2907/3370 Test #2907: fuzz.MINIMIZED/fc5434a62691cb7f3ba4e327d713bb84024ce265 ...................***Exception: SegFault  0.27 sec

[...]

99% tests passed, 1 tests failed out of 3370

Total Test time (real) = 451.70 sec

The following tests FAILED:
	2907 - fuzz.MINIMIZED/fc5434a62691cb7f3ba4e327d713bb84024ce265 (SEGFAULT)
Errors while running CTest

@totalgee
Copy link
Contributor Author

@lefticus I know you've been busy with your various C++ conference presentations... (-; Any tips on how to figure out what the above fuzz-testing error was? Thanks.

@lefticus lefticus merged commit 7f822be into ChaiScript:develop Nov 21, 2017
@lefticus
Copy link
Member

I have been busy, but I'm just going to go ahead and merge this and sort out the details of why that test was failing. It was a test that was automatically created with a fuzzer, so if the nature of the test changes because of correctness - that's OK.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants