Gtest's EXPECT calls whole lot of libc functions
(mem*, malloc) even when EXPECT does not fail.
This does not play well with tsan runtime unit tests
b/c e.g. we call some EXPECTs with runtime mutexes locked.
Details
Details
- Reviewers
vitalybuka melver - Commits
- rGf50cee2f4bad: tsan: switch sync test from EXPECT to CHECK
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
The other tests can keep using EXPECT because they're not end-to-end?
Because they don't hold runtime locks around EXPECTs (this will in the next changes).
Should we s/EXPECT/CHECK/ wholesale?
Comment Actions
You can do it in later changes once it becomes necessary. I assume you already have a commit with that?