Closed elmarb closed 4 years ago
Same issue. We have rolled back to 16.5.0
Same issue. Now, I use spesific version "16.6.0-preview-20200310-03". Previous versions has no probrems to run UnitTest program.
Same issue. The previous run on 16.5.0 has no problem.
The tests using Test Assembly works fine with 16.6.0
But the tests using Test Plan testSelector: 'testPlan'
just cannot make it. It happened to both of our pipelines using test plan.
Thanks for the report, I unlisted the 16.6.0 package while we investigate this.
@vritant24 could you jump on this please?
FYI:
I see 16.6.0 is unlisted on nuget.org
Unfortunalty Dependabot is pushing 16.6.0:
@304NotModified Thanks for the info, the fakes change should be limited to TestPlatform package, so this one should be safe to re-list (and it's dependencies). Validating that.
@304NotModified Re-listed, please let me know if you see more problems.
It works well now. thank you for your support.
2020年4月21日(火) 18:53 Jakub Jareš notifications@github.com:
@304NotModified https://github.com/304NotModified Re-listed, please let me know if you see more problems.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/microsoft/vstest/issues/2408#issuecomment-617077878, or unsubscribe https://github.com/notifications/unsubscribe-auth/AG7XBCDHHVIGFO77JBRB4CLRNVUKFANCNFSM4MMTVVMQ .
Fixed in #2417
Hi Our TFS DB has been increased 4 times in size during infinite loop. How can I safely clean it to reduce it's size to previous value?
@ShreyasRmsft do you have an answer for @vitalyve question please?
@vitalyve setting up a retention policy to clean up older builds should free up the size naturally. This is the recommended way.
Description
Our Azure DevOps server pipeline hangs with endless repetitions of
System.Reflection.AmbiguousMatchException
in the "Visual Studio Test" task ever since 16.6.0 came out. We're trying to run Coded UI tests on Windows 10 machines (that don't do anything else). I realize it's easily worked around by fixing our "Visual Studio test platform installer" task at 16.5.0 rather than "latest stable".Diagnostic logs
Environment