Open dpoeschl opened 4 years ago
Both failures have the same root cause. GetDocumentTextChangesAsync
is a trivial test - it just calls SyntaxTree.GetChanges
. From the output it seems that this compiler API sometimes returns a different result, which is very odd - I briefly looked at the implementation and don't see any obvious non-determinism. Both the expected and the actual results are valid edit scripts, but it's not clear why we get the "expected" most of the time and "actual" this time around.
@agocke @jcouv Any ideas?
I don't see how this test could fail this way. Moving to backlog in case we see it again.
Test results here: https://dev.azure.com/dnceng/public/_build/results?buildId=416558&view=ms.vss-test-web.build-test-results-tab&runId=13087564&resultId=131526&paneView=debug
BreakMode_ModuleDisallowsEditAndContinue
GetDocumentTextChangesAsync