CoreCLR tests are flaky #21937
Assignees
Labels
Comments
agocke
added a commit
to agocke/roslyn
that referenced
this issue
Sep 7, 2017
The testing instructure for CoreCLR currently runs all assemblies in parallel in a single process, so resources, which are static and lazy initialized, must have thread synchronization. Otherwise, tests which depend on object or symbol identity could fail if they retrieve different copies of the same resource. Fixes dotnet#21937
agocke
added a commit
that referenced
this issue
Sep 10, 2017
The testing instructure for CoreCLR currently runs all assemblies in parallel in a single process, so resources, which are static and lazy initialized, must have thread synchronization. Otherwise, tests which depend on object or symbol identity could fail if they retrieve different copies of the same resource. Fixes #21937
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Failure seen in: https://ci.dot.net/job/dotnet_roslyn/job/master/job/ubuntu_16_debug_prtest/6104/ for #21928.
@agocke has observed we have some races producing metadata references in tests and is fixing them now.
The text was updated successfully, but these errors were encountered: