Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
lwm1986
roslyn
提交
e45806ce
R
roslyn
项目概览
lwm1986
/
roslyn
与 Fork 源项目一致
从无法访问的项目Fork
通知
1
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
DevOps
流水线
流水线任务
计划
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
R
roslyn
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
DevOps
DevOps
流水线
流水线任务
计划
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
流水线任务
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
未验证
提交
e45806ce
编写于
9月 30, 2019
作者:
G
Gen Lu
提交者:
GitHub
9月 30, 2019
浏览文件
操作
浏览文件
下载
差异文件
Merge pull request #38952 from nnpcYvIVl/spelling-16
Spelling fixes
上级
9b987ced
3a6cee87
变更
8
隐藏空白更改
内联
并排
Showing
8 changed file
with
13 addition
and
13 deletion
+13
-13
src/Features/Core/Portable/EditAndContinue/DebuggingSession.cs
...eatures/Core/Portable/EditAndContinue/DebuggingSession.cs
+1
-1
src/Test/Utilities/Portable/Assert/ConditionalFactAttribute.cs
...est/Utilities/Portable/Assert/ConditionalFactAttribute.cs
+4
-4
src/Test/Utilities/Portable/Compilation/ThrowingAnalyzerAssemblyLoader.cs
...es/Portable/Compilation/ThrowingAnalyzerAssemblyLoader.cs
+1
-1
src/Test/Utilities/Portable/Metadata/IlasmUtilities.cs
src/Test/Utilities/Portable/Metadata/IlasmUtilities.cs
+1
-1
src/Test/Utilities/Portable/ObjectReference.cs
src/Test/Utilities/Portable/ObjectReference.cs
+2
-2
src/Test/Utilities/Portable/TargetFrameworkUtil.cs
src/Test/Utilities/Portable/TargetFrameworkUtil.cs
+2
-2
src/Tools/Source/RunTests/ITestExecutor.cs
src/Tools/Source/RunTests/ITestExecutor.cs
+1
-1
src/Tools/Source/RunTests/Program.cs
src/Tools/Source/RunTests/Program.cs
+1
-1
未找到文件。
src/Features/Core/Portable/EditAndContinue/DebuggingSession.cs
浏览文件 @
e45806ce
...
...
@@ -75,7 +75,7 @@ internal sealed class DebuggingSession : IDisposable
/// <summary>
/// The solution captured when the debugging session entered run mode (application debugging started),
/// or the solution which the last changes commited to the debuggee at the end of edit session were calculated from.
/// or the solution which the last changes commit
t
ed to the debuggee at the end of edit session were calculated from.
/// The solution reflecting the current state of the modules loaded in the debugee.
/// </summary>
internal
Solution
LastCommittedSolution
{
get
;
private
set
;
}
...
...
src/Test/Utilities/Portable/Assert/ConditionalFactAttribute.cs
浏览文件 @
e45806ce
...
...
@@ -51,8 +51,8 @@ public static class ConditionalSkipReason
public
class
ConditionalFactAttribute
:
FactAttribute
{
/// <summary>
/// This prop
re
ty exists to prevent users of ConditionalFact from accidentally putting documentation
/// in the Skip prop
re
ty instead of Reason. Putting it into Skip would cause the test to be unconditionally
/// This prop
er
ty exists to prevent users of ConditionalFact from accidentally putting documentation
/// in the Skip prop
er
ty instead of Reason. Putting it into Skip would cause the test to be unconditionally
/// skipped vs. conditionally skipped which is the entire point of this attribute.
/// </summary>
[
Obsolete
(
"ConditionalFact should use Reason or AlwaysSkip"
,
error
:
true
)]
...
...
@@ -91,8 +91,8 @@ public ConditionalFactAttribute(params Type[] skipConditions)
public
class
ConditionalTheoryAttribute
:
TheoryAttribute
{
/// <summary>
/// This prop
re
ty exists to prevent users of ConditionalFact from accidentally putting documentation
/// in the Skip prop
re
ty instead of Reason. Putting it into Skip would cause the test to be unconditionally
/// This prop
er
ty exists to prevent users of ConditionalFact from accidentally putting documentation
/// in the Skip prop
er
ty instead of Reason. Putting it into Skip would cause the test to be unconditionally
/// skipped vs. conditionally skipped which is the entire point of this attribute.
/// </summary>
[
Obsolete
(
"ConditionalTheory should use Reason or AlwaysSkip"
)]
...
...
src/Test/Utilities/Portable/Compilation/ThrowingAnalyzerAssemblyLoader.cs
浏览文件 @
e45806ce
...
...
@@ -8,7 +8,7 @@
namespace
Microsoft.CodeAnalysis.Test.Utilities
{
/// <summary>
/// Used when a non-runtime specific loader is needed that is never inten
t
ed to be used.
/// Used when a non-runtime specific loader is needed that is never inten
d
ed to be used.
/// </summary>
internal
sealed
class
ThrowingAnalyzerAssemblyLoader
:
AnalyzerAssemblyLoader
{
...
...
src/Test/Utilities/Portable/Metadata/IlasmUtilities.cs
浏览文件 @
e45806ce
...
...
@@ -23,7 +23,7 @@ private static string GetIlasmPath()
{
if
(
ExecutionConditionUtil
.
IsWindowsDesktop
)
{
// The des
tk
op ilasm is still necessary because a number of our tests depend on being able to
// The des
kt
op ilasm is still necessary because a number of our tests depend on being able to
// emit PDB files for net modules. That feature is not available on coreclr ilasm.
return
Path
.
Combine
(
Path
.
GetDirectoryName
(
RuntimeUtilities
.
GetAssemblyLocation
(
typeof
(
object
))),
...
...
src/Test/Utilities/Portable/ObjectReference.cs
浏览文件 @
e45806ce
...
...
@@ -96,7 +96,7 @@ private void ReleaseAndGarbageCollect()
}
/// <summary>
/// Provides the underlying strong refernce to the given action. This method is marked not be inlined, to ensure that no temporaries are left
/// Provides the underlying strong refer
e
nce to the given action. This method is marked not be inlined, to ensure that no temporaries are left
/// on the stack that might still root the strong reference. The caller must not "leak" the object out of the given action for any lifetime
/// assertions to be safe.
/// </summary>
...
...
@@ -107,7 +107,7 @@ public void UseReference(Action<T> action)
}
/// <summary>
/// Provides the underlying strong refernce to the given function. This method is marked not be inlined, to ensure that no temporaries are left
/// Provides the underlying strong refer
e
nce to the given function. This method is marked not be inlined, to ensure that no temporaries are left
/// on the stack that might still root the strong reference. The caller must not "leak" the object out of the given action for any lifetime
/// assertions to be safe.
/// </summary>
...
...
src/Test/Utilities/Portable/TargetFrameworkUtil.cs
浏览文件 @
e45806ce
...
...
@@ -23,7 +23,7 @@ public enum TargetFramework
/// <summary>
/// Eventually this will be deleted and replaced with NetStandard20. Short term this creates the "standard"
/// API set across des
tk
op and coreclr
/// API set across des
kt
op and coreclr
/// </summary>
Standard
,
StandardLatest
,
...
...
@@ -145,7 +145,7 @@ public static ImmutableArray<MetadataReference> GetReferences(TargetFramework tf
// Check to see if there are any duplicate references. This guards against tests inadvertently passing multiple copies of
// say System.Core to the tests and implicitly depending on the higher one to win. The few tests which actually mean to
// pass multiple ver
is
ons of a DLL should manually construct the reference list and not use this helper.
// pass multiple ver
si
ons of a DLL should manually construct the reference list and not use this helper.
void
checkForDuplicateReferences
()
{
var
nameSet
=
new
HashSet
<
string
>(
getNames
(
references
),
StringComparer
.
OrdinalIgnoreCase
);
...
...
src/Tools/Source/RunTests/ITestExecutor.cs
浏览文件 @
e45806ce
...
...
@@ -39,7 +39,7 @@ internal TestExecutionOptions(string xunitPath, ProcDumpInfo? procDumpInfo, stri
/// <remarks>
/// The difference between <see cref="TestResultInfo"/> and <see cref="TestResult"/> is the former
/// is specifically for the actual test execution results while the latter can contain extra metadata
/// about the results. For example whether it was cached, or had diag
on
stic, output, etc ...
/// about the results. For example whether it was cached, or had diag
no
stic, output, etc ...
/// </remarks>
internal
readonly
struct
TestResultInfo
{
...
...
src/Tools/Source/RunTests/Program.cs
浏览文件 @
e45806ce
...
...
@@ -203,7 +203,7 @@ async Task DumpProcess(Process targetProcess, string procDumpExeFilePath, string
var
processOutput
=
await
processInfo
.
Result
;
// The exit code for procdump doesn't obey standard windows rules. It will return non-zero
// for succesful cases (possibly returning the count of dumps that were written). Best
// for succes
s
ful cases (possibly returning the count of dumps that were written). Best
// backup is to test for the dump file being present.
if
(
File
.
Exists
(
dumpFilePath
))
{
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录