-
Notifications
You must be signed in to change notification settings - Fork 196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
testing/regression/* not used by CMake/CTest #741
Comments
Just noticed that some of these aren't meant to be executed and just check that compilation succeeds, e.g: I can't find an existing build system for these, so I'm not sure which are meant to be run (if any). @brycelelbach do you recall if these are all intended to be compile only tests? |
Some of them are, some are meant to be run. It was an idea that never really came to fruition. |
We should incorporate the ones that run into the existing unit tests and remove this directory, since it's experimental / unused. |
There's some overlap here with #807 -- once we have proper compile test support we could use that to check the "expected build failure" tests. |
Naively trying to add these tests caused issues on windows due to CMAKE_OBJECT_PATH_MAX -- the paths to the object files exceed a system-dependent maximum number of characters. We should find a way to add these.
We could shorten the names, but it might be best to just integrate them with the other unit tests in
testing/
ortesting/<backend>
and put bug metadata in comments.The text was updated successfully, but these errors were encountered: