Skip to content
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

Test discovery fails with very large number of test cases #225

Closed
4 tasks done
hkaimio opened this issue Oct 8, 2020 · 5 comments
Closed
4 tasks done

Test discovery fails with very large number of test cases #225

hkaimio opened this issue Oct 8, 2020 · 5 comments

Comments

@hkaimio
Copy link

hkaimio commented Oct 8, 2020

Checklist

  • The issue is about this extension and NOT about a fork.
  • Check the known issues list.
  • The latest version of the extension was used.
  • It is not related to remote-vscode or I checked the following issue

I have a GTest executable with very large number (~150000) tests (actually most of them are different parameter combinations for a single parameterized test). Test explorer just shows the rotating "reload tests" arrow but nothing happens. If I build the test executable without this particular test, it works just find.

To Reproduce

Create a test exectauble with a test with 150000 parameterized variants
Try to use it in VScode

Desktop

  • Extension Version: 3.4.2
  • VS Code Version: 1.50 insider
  • Catch2 / Google Test / DOCTest Version: Googletest 1.7
  • OS Type and Version: Ubuntu 20.04
  • Using remote-ssh/docker/wsl?: no

Log (optional but recommended)

The log file ends with this line (I can provide full log via email if needed)
[2020-10-07 13:52:57.292] [INFO] Couldn't parse output file. Possibly it is an older version of Google Test framework. It is trying to parse the output

@matepek
Copy link
Owner

matepek commented Oct 8, 2020

Hello,

Please fill the Catch2 / Google Test / DOCTest Version: information.

I need more information..

Please run you executable with --gtest_list_tests --gtest_output=xml:tests.xml > stdout.txt 2>stderr.txt and send me the generated 2 or 3 files.

@hkaimio
Copy link
Author

hkaimio commented Oct 8, 2020

we are using gtest 1.7.
I sent the stdout.txt tou you via email (stderr.txt was empty and tests.xml was not produced)

@matepek
Copy link
Owner

matepek commented Oct 9, 2020

I haven't received any emails. 🤷‍♂️
Try sending it on gitter as PM.

@matepek
Copy link
Owner

matepek commented Oct 10, 2020

Hello,

I test it. It actually works just takes a lot of time to parse it.

@matepek matepek closed this as completed Oct 13, 2020
@matepek
Copy link
Owner

matepek commented Nov 14, 2020

Hey,
Any news on this? I did some small optimisation. I would like to hear your feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants