-
Notifications
You must be signed in to change notification settings - Fork 449
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
VSCode CTest Google Test complains non-existing DartConfiguration.tcl
AND poor performance!
#3917
Comments
@khteh Thank you for your github issue! If you want to disable CTest, you can follow these steps:
|
This works for me. What's the issue with |
@khteh Also, we have settings that allow you to enable parallel execution for tests, which should significantly increase the speed of tests running. Besides that possibility, it would require more investigation to understand perf differences between us and them. As for the |
Doesn't help! I have How to enable parallel execution of |
DartConfiguration.tcl
DartConfiguration.tcl
AND poor performance!
@khteh We're sorry to get back to you so late, is your problem reproducible at this time? If it is still reproducible could you give us a specific reproduction recording and build information? It would be very helpful for us to investigate this issue! Thank you in advance! |
Didn't I respond 2 weeks ago that it doesn't help? There is no build config which refers to the missing file. This is C++ build. Why does it complain to about |
We have a couple of settings that might help you have tests run in parallel:
|
It's kind of hard to read, but this link seems to help someone who has a similar warning about the DartConfiguration.tcl file: https://cmake.org/pipermail/cmake/2015-January/059742.html |
Output:
|
|
@khteh What version of the extension are you using? Could you try the most recent pre-release? I recognize the Regular expression bug and believe we put a fix into the extension in pre-release. Thanks. |
|
@khteh Could you show me screenshots of the official release channel versus the pre-release? Looking at the changelog of the most recent pre-release, nothing should be changed that doesn't allow it to show up in the Test Explorer. |
|
@khteh Got it, to recap. I think we've fixed the DartConfiguration issue?
For the regex issue, I implemented this #3814 in June. It is possible that there is a bug, or that we missed an edge case. What is your scenario? How are you running the command? From the test explorer "Run all" button? Or are you highlighting all of your tests? |
Why is the reconfiguration necessary? Does it make sense? It doesn't happen with I run the tests by a mouse click on the play ("Run Test") button. |
The only way to know what tests are present are if we configure your CMake project. There could be some improvement where we keep state from the last instance or last configuration, however, there is the chance that this is out of date, so it would be an improvement request to better use the past state. |
I get the same CMakeLists.txt
|
Hi @juscghwe, as we can see from the comments above, this doc: https://cmake.org/pipermail/cmake/2015-January/059742.html may be help you for the DartConfiguration issue. Also, only from above CMakeLists.txt file, we get some files missing error as following after
For this unrelated issue, could you please file a new issue, we will track it there, thank you in advanced! |
Hi @Amy-Li03 . I switched to pre-release and it still occured. I followed the document you provided and added |
@juscghwe , we are very happy your issue has been resolved. Happy coding! |
Brief Issue Summary
I hit the following bogus error in VSCode running CTest with GoogleTest for my C++ app:
Why do I need
DartConfiguration.tcl
? How to fix this bogus "error" message?In addition, I have
TestMate C++
extension installed in my VSCode and it relatively runs much faster (4.3s) than CTest (23.6s). I am not sure if this bogus error message is the root cause. How do I disable CTest?CMake Tools Diagnostics
No response
Debug Log
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: