You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since VS update 2, executing our test suite of around 5000 tests takes much longer than before. The problem seems to be at two places:
After Google test finished test execution, the process executing the tests seems to be very busy for another 2-3 minutes; the test adapter code "hangs" at while (!process.StandardOutput.EndOfStream) of file Core/Helpers/ProcessLauncher.cs for that time (and afterwards continues normally)
Even worse, after the test adapter's code has finished its tasks (i.e., after TestEnvironment.LogInfo("Test execution completed.") of file Core/GoogleTestExecutor.cs has been executed), it takes 15-20 minutes until test results are finally displayed in VS's test explorer, and during this time, VS is rather busy (as Windows' task manager shows).
We can reproduce this behavior on VS 2015 Enterprise Edition update 2, and we can see that it does not happen with update 1.
The text was updated successfully, but these errors were encountered:
Since the MS Connect webpage swallows files (i.e., it reports success after upload, but they never show up at the issue), here are the excel sheets showing the regression in terms of test execution time.
It seems like the perfomance regression has been fixed with VS update 3 - I have tested with its RC (Community edition), and it seems to work just fine.
Since VS update 2, executing our test suite of around 5000 tests takes much longer than before. The problem seems to be at two places:
while (!process.StandardOutput.EndOfStream)
of fileCore/Helpers/ProcessLauncher.cs
for that time (and afterwards continues normally)TestEnvironment.LogInfo("Test execution completed.")
of fileCore/GoogleTestExecutor.cs
has been executed), it takes 15-20 minutes until test results are finally displayed in VS's test explorer, and during this time, VS is rather busy (as Windows' task manager shows).We can reproduce this behavior on VS 2015 Enterprise Edition update 2, and we can see that it does not happen with update 1.
The text was updated successfully, but these errors were encountered: