-
Notifications
You must be signed in to change notification settings - Fork 336
Endless loop of AmbiguousMatchException with 16.6.0 #2408
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
Comments
Same issue. We have rolled back to 16.5.0 |
Same issue. Now, I use spesific version "16.6.0-preview-20200310-03". |
Same issue. The previous run on 16.5.0 has no problem. The tests using Test Assembly works fine with 16.6.0 |
Thanks for the report, I unlisted the 16.6.0 package while we investigate this. @vritant24 could you jump on this please? |
@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
<#2408 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AG7XBCDHHVIGFO77JBRB4CLRNVUKFANCNFSM4MMTVVMQ>
.
|
Fixed in #2417 |
Hi |
@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
Server: Azure DevOps Server Version Dev17.M153.5
Agent:
The text was updated successfully, but these errors were encountered: