-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[browser] Added an optional HybridGlobalization run of libraries #95324
Conversation
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsFixes #95282. Runs on:
|
/azp run runtime-wasm-hg-tests |
No pipelines are associated with this pull request. |
@radical, am I missing something to be able to trigger the template's job? |
You will need to ask FR to add a corresponding pipeline. Maybe add this to |
/azp run runtime-wasm-libtests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-libtests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-libtests |
Azure Pipelines successfully started running 1 pipeline(s). |
Locally, running with node v20.8.0 |
/azp run runtime-wasm-libtests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-libtests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-libtests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-libtests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-libtests |
Azure Pipelines successfully started running 1 pipeline(s). |
@@ -84,6 +84,12 @@ | |||
<ProjectExclusions Include="$(MSBuildThisFileDirectory)System.Runtime\tests\System.Globalization.Tests\Hybrid\System.Globalization.Hybrid.WASM.Tests.csproj" /> | |||
</ItemGroup> | |||
|
|||
<!-- invariant project cannot be tested in hybrid mode; projects using functions that throw PNSE too often to block separate tests (HashCode, CompareOptions) --> |
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.
projects using functions that throw PNSE too often to block separate tests (HashCode, CompareOptions)
- can you explain this? And is there an issue for it?
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.
It's not an issue, it's by design, here is the doc
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.
As a follow-up job, I should add the APIs from tests that I blocked in this PR to the doc (into "Affected public APIs" sections).
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.
The CI related changes LGTM 👍
Co-authored-by: Ankit Jain <[email protected]>
Fixes #95282.
Runs on:
- rolling buildadd it in a few weeks in a follow-up PR, when we decide that it is stable/azp run runtime-wasm-libtests
We have a few not supported operations, e.g.
GetHashCode
orCompare
with certain sets ofStringComparison
options. Tests that use them were blocked. Some tests need further investigation, connected issues:#95503
#95471
#95473
#95594
#95623