I don't know if this is the test runner or something worse, but the "Discover test" portion of the test runner is taking a very long time. I'm trying to run one single test. This test discovers (using --gtest_list_tests) and executes instantly on the command line.
This is a copy/paste of a fast discovery "Tests" output:
------ Discover test started ------
Found 1 tests in executable D:\path\to\my\test.exe
========== Discover test finished: 1 found (0:00:20.5250523) ==========
------ Run test started ------
Found 1 tests in executable D:\path\to\my\test.exe
Running 1 tests...
Executing tests on 1 threads
Test execution completed.
========== Run test finished: 1 run (0:00:07.5687568) ==========
Discovery takes between 20 and 37 seconds. Execution takes between 2 and 20 seconds. I don't really have any idea what to do at this point, but this is killing my ability to do TDD. The guy sitting right next to me discovers a single test in <1 second.
I looked at process monitor and it appears NotifyChangeDirectory can take up to 30 seconds sometimes. I've been at this 3 hours and I can't seem to figure it out. The crazy thing is it was working fine up until 3 hours ago.
I've tried everything I can think of to no avail:
- I rechecked out the repo
- cleared temp directories
- downgraded the extension to 0.3.0
- run VS as admin
Have you ever run into this issue?
I don't know if this is the test runner or something worse, but the "Discover test" portion of the test runner is taking a very long time. I'm trying to run one single test. This test discovers (using --gtest_list_tests) and executes instantly on the command line.
This is a copy/paste of a fast discovery "Tests" output:
Discovery takes between 20 and 37 seconds. Execution takes between 2 and 20 seconds. I don't really have any idea what to do at this point, but this is killing my ability to do TDD. The guy sitting right next to me discovers a single test in <1 second.
I looked at process monitor and it appears NotifyChangeDirectory can take up to 30 seconds sometimes. I've been at this 3 hours and I can't seem to figure it out. The crazy thing is it was working fine up until 3 hours ago.
I've tried everything I can think of to no avail:
Have you ever run into this issue?