Skip to content
This repository has been archived by the owner on Jan 23, 2023. It is now read-only.

Update Unicode data to version 11 #20529

Merged
merged 4 commits into from
Oct 24, 2018
Merged

Update Unicode data to version 11 #20529

merged 4 commits into from
Oct 24, 2018

Conversation

tarekgh
Copy link
Member

@tarekgh tarekgh commented Oct 22, 2018

No description provided.

@tarekgh tarekgh requested a review from krwq October 22, 2018 23:18
@tarekgh tarekgh self-assigned this Oct 22, 2018
@tarekgh tarekgh added this to the 3.0 milestone Oct 22, 2018
@tarekgh
Copy link
Member Author

tarekgh commented Oct 22, 2018

I am going to update the tests on corefx too.

CC @GrabYourPitchforks

@tarekgh
Copy link
Member Author

tarekgh commented Oct 22, 2018

Copy link
Member

@krwq krwq left a 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

@jkotas
Copy link
Member

jkotas commented Oct 22, 2018

@dotnet-bot test this please

@GrabYourPitchforks
Copy link
Member

GrabYourPitchforks commented Oct 23, 2018

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.
(And such an API would really be a separate issue from this one, anyway.)

@tarekgh
Copy link
Member Author

tarekgh commented Oct 23, 2018

System.Globalization.Tests.CharUnicodeInfoGetUnicodeCategoryTests.GetUnicodeCategory is expected to fail in this PR. I already have other PR in corefx for fixing this test.

@jkotas
Copy link
Member

jkotas commented Oct 23, 2018

Disable the affected tests in https://github.com/dotnet/coreclr/blob/master/tests/CoreFX/CoreFX.issues.json . We want to keep the CI green.

@jkotas
Copy link
Member

jkotas commented Oct 23, 2018

Should we move this file to shared CoreLib partition as part of this and update the data in CoreRT/ProjectN as well?

@tarekgh
Copy link
Member Author

tarekgh commented Oct 23, 2018

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" />
Copy link
Member

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?

Copy link
Member Author

@tarekgh tarekgh Oct 23, 2018

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.

@jkotas
Copy link
Member

jkotas commented Oct 23, 2018

Disable the affected tests in https://github.com/dotnet/coreclr/blob/master/tests/CoreFX/CoreFX.issues.json

You will need to do this before merging this PR...

@tarekgh
Copy link
Member Author

tarekgh commented Oct 23, 2018

@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.

@jkotas
Copy link
Member

jkotas commented Oct 23, 2018

The CI picks up a fixed snapshot that is several weeks old. Your fix won't propagate into this snapshot anytime soon.

@tarekgh
Copy link
Member Author

tarekgh commented Oct 24, 2018

@dotnet/dnceng do you know how I can restart "Windows_NT arm Cross Checked Innerloop Build and Test " leg?

@mmitche
Copy link
Member

mmitche commented Oct 24, 2018

@dotnet-bot test Windows_NT arm Cross Checked Innerloop Build and Test

@tarekgh
Copy link
Member Author

tarekgh commented Oct 24, 2018

@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 :-)

@mmitche
Copy link
Member

mmitche commented Oct 24, 2018

@dotnet-bot is just a convention, not required. It's generally just "test "

@tarekgh
Copy link
Member Author

tarekgh commented Oct 24, 2018

I am pretty sure I tried "test" a couple of times with this leg and didn't work.

@tarekgh tarekgh merged commit 11c5d6c into dotnet:master Oct 24, 2018
dotnet-maestro-bot pushed a commit to dotnet-maestro-bot/corefx that referenced this pull request Oct 24, 2018
* 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>
dotnet-maestro-bot pushed a commit to dotnet-maestro-bot/corert that referenced this pull request Oct 24, 2018
* 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>
tarekgh added a commit to dotnet/corefx that referenced this pull request Oct 24, 2018
* 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>
tarekgh added a commit to tarekgh/coreclr that referenced this pull request Oct 25, 2018
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.
tarekgh added a commit to dotnet/corert that referenced this pull request Oct 25, 2018
* 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>
jkotas pushed a commit that referenced this pull request Oct 25, 2018
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.
A-And pushed a commit to A-And/coreclr that referenced this pull request Nov 20, 2018
* Update Unicode data to version 11

* Move CharUnicodeInfoData.cs to the hsared folder

* Delete un-needed file

* Disable the failed test
A-And pushed a commit to A-And/coreclr that referenced this pull request Nov 20, 2018
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.
@tarekgh tarekgh deleted the Unicode11 branch March 25, 2019 15:29
picenka21 pushed a commit to picenka21/runtime that referenced this pull request Feb 18, 2022
* 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
picenka21 pushed a commit to picenka21/runtime that referenced this pull request Feb 18, 2022
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
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants