You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since assert is a necessary part of the tests' control flow, compiling with NDEBUG defined globally (e.g. via config.cc.poptions+=-DNDEBUG) causes the tests to fail.
Forcibly undefining NDEBUG in each test driver before including <cassert> looks like one way to fix this:
Cool, it looks like this was addressed in 7a4fc37. I was even able to cherry-pick it back to 0.13 (excluding any newly-added tests) and all tests are passing with global -DNDEBUG now. Thanks @karen-arutyunov!
Since
assert
is a necessary part of the tests' control flow, compiling withNDEBUG
defined globally (e.g. viaconfig.cc.poptions+=-DNDEBUG
) causes the tests to fail.Forcibly undefining
NDEBUG
in each test driver before including<cassert>
looks like one way to fix this:If this looks like an appropriate solution, I'm happy to open a PR.
The text was updated successfully, but these errors were encountered: