-
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
[wasm] Bump emscripten to 2.0.23 #53603
[wasm] Bump emscripten to 2.0.23 #53603
Conversation
Tagging subscribers to this area: @carlossanlop Issue Details
|
Tagging subscribers to 'arch-wasm': @lewing Issue Details
|
The failing System.Net.Primitives.Unit.Tests.CookieContainerTest.SetCookies_Success is #53931 |
The fix for FS bug, where it ignores permissions didn't make it into 2.0.23, even if it looks like it from the commit history. I still see this in
Context: emscripten-core/emscripten@a56817a |
Do we know why the AOT tests are failing? |
Some of them are timing out, due to the recent increase in build time. We should bump the timeout, to we can at least get the tests running, and not miss any regressions. I would add diff --git a/src/libraries/sendtohelixhelp.proj b/src/libraries/sendtohelixhelp.proj
index 84c140a2182..1dd6716f2e8 100644
--- a/src/libraries/sendtohelixhelp.proj
+++ b/src/libraries/sendtohelixhelp.proj
@@ -29,6 +29,7 @@
<_workItemTimeout Condition="'$(Scenario)' == '' and '$(_workItemTimeout)' == '' and ('$(TargetArchitecture)' == 'arm64' or '$(TargetArchitecture)' == 'arm')">00:45:00</_workItemTimeout>
<_workItemTimeout Condition="'$(Scenario)' != '' and '$(_workItemTimeout)' == '' and ('$(TargetArchitecture)' == 'arm64' or '$(TargetArchitecture)' == 'arm')">01:00:00</_workItemTimeout>
<_workItemTimeout Condition="'$(Scenario)' == 'BuildWasmApps' and '$(_workItemTimeout)' == ''">01:00:00</_workItemTimeout>
+ <_workItemTimeout Condition="'$(TargetOS)' == 'Browser' and '$(NeedsToBuildWasmAppsOnHelix)' == 'true'">01:00:00</_workItemTimeout>
<_workItemTimeout Condition="'$(Scenario)' == '' and '$(_workItemTimeout)' == ''">00:15:00</_workItemTimeout>
<_workItemTimeout Condition="'$(Scenario)' != '' and '$(_workItemTimeout)' == ''">00:30:00</_workItemTimeout> |
To be able to use this image before dotnet/runtime#53603 is finished
8 libraries are failing with AOT. Some are timing out, some with emcc getting killed with:
|
In the last run there are 7 test jobs failing, only 1 of them receiving signal SIGKILL, On linux helix machine, the limits are set like this:
and the system has cca 8GB of memory and 128GB of storage space for |
Looks like the I tried to build the first library test, which timeouts - Note: the local build might be behaving differently compared to helix, I see 81 assemblies AOT'ed after linking vs 61 on helix. |
I tried to change |
The |
cc @marek-safar |
…ipten-2-0-23-bump
This reverts commit 67dd775.
It might be the new string tail merging in wasm-ld:
Let see if the |
Merging current I have opened emscripten-core/emscripten#14485 and will try to dig deeper to see if I can spot what might be causing the higher memory usage. |
To be sure it behaves the same as in local build
Lukas Lansky opened a ticket for us to get more memory (and cores as side effect) https://github.com/dotnet/core-eng/issues/13425 |
It looks like it reduces the memory load a lot
Nice to see this green, please get in mergeable condition so we can land it. |
browser failure is #53957 |
CoreCLR Pri0 Runtime Tests Run windows arm64 checked - failure is the same seen in #54053 and doesn't contain logs |
…bugger2 * origin/main: (107 commits) Disable MacCatalyst arm64 PR test runs on staging pipeline (dotnet#54678) [WASM] Fix async/await in config loading (dotnet#54652) Fix for heap_use_after_free flagged by sanitizer (dotnet#54679) [wasm] Bump emscripten to 2.0.23 (dotnet#53603) Fix compiler references when building inside VS (dotnet#54614) process more TLS frames at one when available (dotnet#50815) Add PeriodicTimer (dotnet#53899) UdpClient with span support (dotnet#53429) exclude fragile tests (dotnet#54671) get last error before calling a method that might fail as well (dotnet#54667) [FileStream] add tests for device and UNC paths (dotnet#54545) Fix sporadic double fd close (dotnet#54660) Remove Version.Clone from AssemblyName.Clone (dotnet#54621) [wasm] Enable fixed libraries tests (dotnet#54641) [wasm] Fix blazor/aot builds (dotnet#54651) [mono][wasm] Fix compilation error on wasm (dotnet#54659) Fix telemetry for Socket connects to Dns endpoints (dotnet#54071) [wasm] Build static components; include hot_reload in runtime (dotnet#54568) [wasm][debugger] Reuse debugger-agent on wasm debugger (dotnet#52300) Put Crossgen2 in sync with dotnet#54235 (dotnet#54438) ...
No description provided.