This makes its role clearer. It's plausible that one may want to manually
define TEST_IS_SLOW when running the tests in some environments - in
particular, it seems to be necessary to use the higher tolerance timeouts
if running the tests on Windows runners on Github Actions.
Details
Details
- Reviewers
ldionne - Group Reviewers
Restricted Project - Commits
- rG63d88ed5bfcf: [libcxx] [test] Split the TEST_HAS_SANITIZERS define into…
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
libcxx/test/support/test_macros.h | ||
---|---|---|
196 | I think the name TEST_IS_SLOW is a bit generic, we have slow tests that don't use this. (*cough* format) |
libcxx/test/support/test_macros.h | ||
---|---|---|
196 | Right, that makes sense. That macro sure is a mouthful, but it doesn’t need to be super convenient, so it’s probably fine. I can update the patch with that name later tonight. |
I think the name TEST_IS_SLOW is a bit generic, we have slow tests that don't use this. (*cough* format)
How about TEST_IS_EXECUTED_IN_A_SLOW_ENVIRONMENT or something along these lines?