Description
Some recently merged change made FSI multi-emit tests flaky:
https://dev.azure.com/dnceng-public/public/_build/results?buildId=1003058&view=ms.vss-test-web.build-test-results-tab&runId=26764208&resultId=104454&paneView=debug
[xUnit.net 00:11:53.04] Scripting\Interactive.fs(61,0): at Scripting.Interactive tests.Evaluation of multiple sessions should succeed(Boolean useMultiEmit)
Failed Scripting.Interactive tests.Evaluation of multiple sessions should succeed(useMultiEmit: True) [8 s]
Error Message:
System.TypeLoadException : Could not load type 'Test2' from assembly 'FSI-ASSEMBLY, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null'.
Stack Trace:
at FSharp.Test.ScriptHelpers.TestHelpers.getValue(FSharpResult`2 value, FSharpDiagnostic[] errors) in D:\a_work\1\s\tests\FSharp.Test.Utilities\ScriptHelpers.fs:line 101
at Scripting.Interactive tests.Evaluation of multiple sessions should succeed(Boolean useMultiEmit) in D:\a_work\1\s\tests\FSharp.Compiler.ComponentTests\Scripting\Interactive.fs:line 61
Repro steps
Run Scripting
tests in VS Test Explorer in parallel. Tests with useMultiEmit: true
will fail.
This apparently happens when running multiple evaluation sessions concurrently when one of the sessions is single-emit, so impact is low.
Metadata
Metadata
Assignees
Type
Projects
Status