On Wed, Aug 14, 2019 at 9:48 AM Stanislav Fomichev <sdf@xxxxxxxxxx> wrote: > > Otherwise they can bring the whole process down. > > Cc: Andrii Nakryiko <andriin@xxxxxx> > Signed-off-by: Stanislav Fomichev <sdf@xxxxxxxxxx> > --- This is probably why you added all that extra logging in __test__fail(), right? So had a low-priority TODO item to add another CHECK()-like macro that would only report failure (but won't bump/log success). Seems like this is something that would be useful for these asserts? What do you think about either QCHECK() (for "quiet" check) or surely we can also do ASSERT (but it's less obvious that it won't log success and it's also not obvious that it won't actually terminate test immediately). Then inside that QCHECK() you can log file:line number, similar to CHECK(), but only for failure case. Thoughts?
