diff options
| author | Brian Sullivan <briansul@microsoft.com> | 2017-06-13 13:57:33 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-06-13 13:57:33 -0700 |
| commit | 25bc371325b21a4bed9e0337192dd04ad7051b54 (patch) | |
| tree | c07451e1992e23e0b89055c80367024437d06c2c /Documentation/building | |
| parent | 7e8cb3efb7556eea02ad43292b8baa8651e14e79 (diff) | |
| download | coreclr-25bc371325b21a4bed9e0337192dd04ad7051b54.tar.gz coreclr-25bc371325b21a4bed9e0337192dd04ad7051b54.tar.bz2 coreclr-25bc371325b21a4bed9e0337192dd04ad7051b54.zip | |
Added the checked CORE_ROOT path to this
Diffstat (limited to 'Documentation/building')
| -rw-r--r-- | Documentation/building/windows-test-instructions.md | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/Documentation/building/windows-test-instructions.md b/Documentation/building/windows-test-instructions.md index 3e03254623..709b301dd2 100644 --- a/Documentation/building/windows-test-instructions.md +++ b/Documentation/building/windows-test-instructions.md @@ -57,7 +57,7 @@ This will generate a report named as `TestRun_<arch>_<flavor>.html` (e.g. `TestR Upon completing a test run, you may find one or more tests have failed. -The output of the Test will be available in Test reports directory, but the default the directory would be something like is `<repo_root>\bin\tests\x64\Windows_NT.x64.Checked\Reports\Exceptions\Finalization`. +The output of the Test will be available in Test reports directory, but the default the directory would be something like is `<repo_root>\bin\tests\Windows_NT.x64.Checked\Reports\Exceptions\Finalization`. There are 2 files of interest: @@ -68,12 +68,13 @@ There are 2 files of interest: If you wish to re-run a failed test, please follow the following steps: -1. Set an environment variable, `CORE_ROOT`, pointing to the path to product binaries that was passed to runtest.cmd. The command to set this environment variable is also specified in the test report for a failed test. +1. Set an environment variable, `CORE_ROOT`, pointing to the path to product binaries that was passed to runtest.cmd. +For example using a checked build the location would be: `<repo_root>\bin\tests\Windows_NT.x64.Checked\Tests\Core_Root` + 2. Next, run the failed test, the command to which is also present in the test report for a failed test. It will be something like `<repo_root>\binaries\tests\x64\debug\Exceptions\Finalization\Finalizer.cmd`. If you wish to run the test under a debugger (e.g. [WinDbg](http://msdn.microsoft.com/en-us/library/windows/hardware/ff551063(v=vs.85).aspx)), append `-debug <debuggerFullPath>` to the test command. For example: - <repo_root>\binaries\tests\x64\debug\Exceptions\Finalization\Finalizer.cmd -debug <debuggerFullPath> **Modifying a test** |