This is an archive of the discontinued LLVM Phabricator instance.

tsan: switch sync test from EXPECT to CHECK
ClosedPublic

Authored by dvyukov on Oct 27 2021, 2:02 AM.

Details

Summary

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.

Diff Detail

Event Timeline

dvyukov requested review of this revision.Oct 27 2021, 2:02 AM
dvyukov created this revision.
Herald added a project: Restricted Project. · View Herald TranscriptOct 27 2021, 2:02 AM
Herald added a subscriber: Restricted Project. · View Herald Transcript
melver accepted this revision.Oct 27 2021, 2:18 AM

The other tests can keep using EXPECT because they're not end-to-end?

This revision is now accepted and ready to land.Oct 27 2021, 2:18 AM

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?

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?

You can do it in later changes once it becomes necessary. I assume you already have a commit with that?

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?

You can do it in later changes once it becomes necessary. I assume you already have a commit with that?

No, I didn't do it yet/don't have commit.

This revision was automatically updated to reflect the committed changes.