Skip to content
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][icu][libraries] Load full ICU in library tests only when it's necessary #82619

Merged
merged 7 commits into from
Mar 1, 2023

Conversation

ilonatommy
Copy link
Member

Fixes #82592.

@ghost
Copy link

ghost commented Feb 24, 2023

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

Fixes #82592.

Author: ilonatommy
Assignees: ilonatommy
Labels:

arch-wasm, area-Infrastructure-libraries

Milestone: -

@@ -35,6 +32,11 @@
<_BundleAOTTestWasmAppForHelixDependsOn>$(_BundleAOTTestWasmAppForHelixDependsOn);PrepareForWasmBuildApp;_PrepareForAOTOnHelix</_BundleAOTTestWasmAppForHelixDependsOn>
</PropertyGroup>

<!-- trimming tests InvariantGlobalizationFalse require full ICU data -->
<PropertyGroup Condition="'$(TestTrimming)' == 'true'">
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why only when 'TestTrimming' ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's the story:
I made this PR to reduce the number of tests that run with this flag set to true to minimum. However, I was not able to make InvariantGlobalizationFalse.cs in trimming tests pass - even setting the Property straight in that test d1f019b was not woring - when we were entering WasmApp.targets the value was already trimmed.
I came up with the workaround: I won't set the flag for all the tests in tests.browser.targets but only for the trimming ones, to make InvariantGlobalizationFalse.cs pass.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You also need '$(IsTrimmingTestProject)' == 'true'. $(TestTrimming) would be set for the whole build, but it is relevant only for trimming projects which will have $(IsTrimmingTestProject) set. At least based on reading the code:)

Copy link
Member Author

@ilonatommy ilonatommy Feb 28, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changing it to IsTrimmingTestProject breaks the test again. It has to be connected with the order of MsBuild files evaluation, because for the discussed test both flags: IsTrimmingTestProject and TestTrimming are true in the binlog. So it must be that we are reading test.browser.targets before we read Directory.Build.props where IsTrimmingTestProject value is set. TestTrimming is set in src/libraries/tests.proj and is already availabe in the line quoted.
Conclusion: the condition has to stay as it is.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm confused about it. Do all combinations 4 of trimming and invariant work for native rebuild ?
Is this just issue with unit testing ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We took it offline with Pavel and it's not about trimming but about these files being used in different builds. That is why values set in one of them are not reflected in the other.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is nested MSBuild which didn't receive WasmIncludeFullIcuData from System.Runtime.TrimmingTests.proj

image

And then full file is not there!

image

@radical
Copy link
Member

radical commented Feb 27, 2023

/azp run runtime-wasm-libtests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@ilonatommy
Copy link
Member Author

Failures unrelated.

@radical
Copy link
Member

radical commented Mar 1, 2023

/azp run runtime-wasm

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[browser][icu] Load full ICU in library tests only when it's necessary
3 participants