Thanks. I upgraded to 2.3.0rc1 so I could use cr_skip_test, and I see that —pattern is now —filter and —no-early-exit is now deprecated. I used to make use of pattern and no-early-exit for inspecting leaks with valgrind. How do I accomplish that now?
Valgrind output is always clean (even though I know that this test has a memory leak)
well they shouldn’t fail, i put that stuff in setup/teardown because it’s boilerplate that a whole suite will share. but sometimes it’s useful to be able to error if something in setup/teardown fails. i think it makes sense for abort to be the most obvious choice
yeah, sounds good to me. they shouldn’t fail, if they did then something has gone wrong