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

Executing lots of tests takes MUCH longer since VS update 2 #52

Closed
csoltenborn opened this issue May 26, 2016 · 3 comments
Closed

Executing lots of tests takes MUCH longer since VS update 2 #52

csoltenborn opened this issue May 26, 2016 · 3 comments

Comments

@csoltenborn
Copy link
Owner

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.

@csoltenborn
Copy link
Owner Author

Here's the according bug report.

@csoltenborn
Copy link
Owner Author

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.

TestExecutionTimes.zip

@csoltenborn
Copy link
Owner Author

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.

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

No branches or pull requests

1 participant