This particular exception in Dispose is masking a real failure in our suite...
This particular exception in Dispose is masking a real failure in our suite runs. This particular scenario can only happen, based on my code reading, if an exception happens trying to create the RuntimeAssemblyManager instance. In that case domain != null && assemblyManager == null. That exception propagates out the calling code which has HostedRuntimeEnvironment in a using block hence it goes to Dispose. The Dispose method thinks this combination is invalid and throws a new exception thus hiding the real and original problem. Removing the check in Dispose so the real exception will make it into our xUnit logs and we can track down the flaky behavior. (changeset 1407359)
Showing
想要评论请 注册 或 登录