-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Conversation
I am going to update the tests on corefx too. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't really tell if the data is right but the process seems reasonable from offline conversation
@dotnet-bot test this please |
I'd love for us to add an API to get the version of the Unicode spec that's burned in to the product. Otherwise LGTM. |
System.Globalization.Tests.CharUnicodeInfoGetUnicodeCategoryTests.GetUnicodeCategory is expected to fail in this PR. I already have other PR in corefx for fixing this test. |
Disable the affected tests in https://github.com/dotnet/coreclr/blob/master/tests/CoreFX/CoreFX.issues.json . We want to keep the CI green. |
Should we move this file to shared CoreLib partition as part of this and update the data in CoreRT/ProjectN as well? |
I think this will be a good idea. I'll try to modify the code to do that. and we can update the CoreRT when we get the change mirrored. |
@@ -372,7 +372,6 @@ | |||
<Compile Include="$(BclSourcesRoot)\System\Reflection\Metadata\AssemblyExtensions.cs" /> | |||
</ItemGroup> | |||
<ItemGroup> | |||
<Compile Include="$(BclSourcesRoot)\System\Globalization\CharUnicodeInfoData.cs" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you please delete this file as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
interesting, I did move command in PS window and I thought it deleted the original file but it didn't. anyway, I'll fix that. Thanks for the catch.
You will need to do this before merging this PR... |
@jkotas does CI pick the tests from corefx repro master? or it pick it up from some other place? I am asking because I have fixed the test on corefx which should work fine now. |
The CI picks up a fixed snapshot that is several weeks old. Your fix won't propagate into this snapshot anytime soon. |
@dotnet/dnceng do you know how I can restart "Windows_NT arm Cross Checked Innerloop Build and Test " leg? |
@dotnet-bot test Windows_NT arm Cross Checked Innerloop Build and Test |
@mmitche thanks for help. just wondering why I can start other legs without specifying "@dotnet-bot" while I cannot do it for "Windows_NT arm Cross Checked Innerloop Build and Test". I am just curious to know :-) |
@dotnet-bot is just a convention, not required. It's generally just "test " |
I am pretty sure I tried "test" a couple of times with this leg and didn't work. |
* Update Unicode data to version 11 * Move CharUnicodeInfoData.cs to the hsared folder * Delete un-needed file * Disable the failed test Signed-off-by: dotnet-bot <dotnet-bot@microsoft.com>
* Update Unicode data to version 11 * Move CharUnicodeInfoData.cs to the hsared folder * Delete un-needed file * Disable the failed test Signed-off-by: dotnet-bot <dotnet-bot@microsoft.com>
* Update Unicode data to version 11 * Move CharUnicodeInfoData.cs to the hsared folder * Delete un-needed file * Disable the failed test Signed-off-by: dotnet-bot <dotnet-bot@microsoft.com>
In the PR dotnet#20529 we have used the old existing data when we moved the file CharunicodeInfoData.cs to shared folder. This change is to restore the actual updated file.
* Update Unicode data to version 11 * Move CharUnicodeInfoData.cs to the hsared folder * Delete un-needed file * Disable the failed test Signed-off-by: dotnet-bot <dotnet-bot@microsoft.com>
In the PR #20529 we have used the old existing data when we moved the file CharunicodeInfoData.cs to shared folder. This change is to restore the actual updated file.
* Update Unicode data to version 11 * Move CharUnicodeInfoData.cs to the hsared folder * Delete un-needed file * Disable the failed test
In the PR dotnet#20529 we have used the old existing data when we moved the file CharunicodeInfoData.cs to shared folder. This change is to restore the actual updated file.
* Update Unicode data to version 11 * Move CharUnicodeInfoData.cs to the hsared folder * Delete un-needed file * Disable the failed test Commit migrated from dotnet/coreclr@11c5d6c
In the PR dotnet/coreclr#20529 we have used the old existing data when we moved the file CharunicodeInfoData.cs to shared folder. This change is to restore the actual updated file. Commit migrated from dotnet/coreclr@bbf0902
No description provided.