-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
Some tests are not displayed #103
Comments
Can you run your test executable manually with |
Yes, it produces standart google test --help output |
How long does it take to produce that? If shorter than 5 sec I have no idea. Can you send me the exec? What kind of os. ... |
Let me know if you still have the issue |
The issue still remains. The exec is super fast <1s, I can send it to you |
It is welcomed |
linux? |
yes, Ubuntu 18 |
I finally found why this was happening. The code outside of google testing was sending the exception and crashed the executable, so the catch2 script thought it wasn't an executable. |
Also the exception was sent because of not getting the environment variables that cannot be set with "env", could this also be implemented? See details: #116 |
Sorry, but my linux VM is deep inside cupboard. :) Check my comment on the issue you mentioned. Let me know if you have any questions. |
I think I mixed too many things here, will create a new, more clear version) |
When I refresh the tests toolbar, it doesn't show all tests I have in the specified folder.
My settings are:
The logpanel output for the not found tests is the following:
The text was updated successfully, but these errors were encountered: