Skip to content

Conversation

@dotnet-maestro
Copy link
Contributor

@dotnet-maestro dotnet-maestro bot commented Sep 10, 2024

This pull request updates the following dependencies

From https://github.com/dotnet/emsdk

  • Subscription: f85f62c8-5e7d-4706-1003-08dcbc30275f
  • Build: 20240914.3
  • Date Produced: September 14, 2024 11:52:59 AM UTC
  • Commit: c3d83d0ea894e5ee537bfc591fd48e06af8d9166
  • Branch: refs/heads/release/9.0

…09.5

Microsoft.SourceBuild.Intermediate.emsdk , Microsoft.NET.Workload.Emscripten.Current.Manifest-9.0.100.Transport
 From Version 9.0.0-rc.2.24455.1 -> To Version 9.0.0-rc.2.24459.5
…11.2

Microsoft.SourceBuild.Intermediate.emsdk , Microsoft.NET.Workload.Emscripten.Current.Manifest-9.0.100.Transport
 From Version 9.0.0-rc.2.24459.5 -> To Version 9.0.0-rc.2.24461.2
@carlossanlop
Copy link
Contributor

The test failure looks bad. Could it be related to this deps flow, @lewing?

Job: https://dev.azure.com/dnceng-public/public/_build/results?buildId=806363&view=logs&j=63c2d0c8-fec2-5788-81c8-f3ac95e8841f&t=744baa8c-2e26-50b3-27ca-51a0d84eca60&l=80
Log file: https://helixre107v0xd1eu3ibi6ka.blob.core.windows.net/dotnet-runtime-refs-pull-107610-merge-85b59b965bdf427baf/WasmTestOnFirefox-MT-System.Xml.XmlSerializer.ReflectionOnly.Tests/1/console.08535e4c.log?helixlogtype=result

[14:14:53] fail: System.BadImageFormatException: Could not resolve field token 0x04000100, due to: Could not load type of field 'System.Runtime.InteropServices.JavaScript.JSSynchronizationContext:Queue' (2) due to: Could not load file or assembly 'System.Runtime, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. assembly:System.Runtime.InteropServices.JavaScript.dll type:JSSynchronizationContext member:(null)
[14:14:53] fail: File name: 'System.Runtime.InteropServices.JavaScript'
[14:14:53] fail: [0x012ad6f0-dpty 14:14:53.534] [MONO] System.BadImageFormatException: Could not resolve field token 0x04000100, due to: Could not load type of field 'System.Runtime.InteropServices.JavaScript.JSSynchronizationContext:Queue' (2) due to: Could not load file or assembly 'System.Runtime, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. assembly:System.Runtime.InteropServices.JavaScript.dll type:JSSynchronizationContext member:(null)
                 File name: 'System.Runtime.InteropServices.JavaScript'
                 Fl<@mono_wasm_invoke_jsexport (http://127.0.0.1:42097/_framework/dotnet.runtime.js:3:197185
                 @http://127.0.0.1:42097/_framework/dotnet.native.wasm:wasm-function[194]:0x15525)
                 createDotnetRuntime</</Module._mono_wasm_invoke_jsexport@http://127.0.0.1:42097/_framework/dotnet.native.js:8:133139
                 Fl</</ot.proxyGCHandle<@http://127.0.0.1:42097/_framework/dotnet.runtime.js:3:206322
                 Fl</<@http://127.0.0.1:42097/_framework/dotnet.runtime.js:3:206495
[14:14:53] info: [0x012ad6f0-dpty 14:14:53.584] MONO_WASM: Dumping web worker info as seen by UI thread, it could be stale:
[14:14:53] info: 001 | 0x012ad6f0-dpty: isRunning: true isAttached: true isEventLoop:false reuseCount:  1 -
[14:14:53] fail: [0x012ad6f0-dpty 14:14:53.585] MONO_WASM: install_main_synchronization_context failed RuntimeError: Aborted(co@mono_wasm_invoke_jsexport (http://127.0.0.1:42097/_framework/dotnet.js:3:27212
                 lo@http://127.0.0.1:42097/_framework/dotnet.js:3:26825
                 abort@http://127.0.0.1:42097/_framework/dotnet.native.js:8:9945
                 _abort@http://127.0.0.1:42097/_framework/dotnet.native.js:8:104230
                 @http://127.0.0.1:42097/_framework/dotnet.native.wasm:wasm-function[194]:0x15528)
                 createDotnetRuntime</</Module._mono_wasm_invoke_jsexport@http://127.0.0.1:42097/_framework/dotnet.native.js:8:133139
                 Fl</</ot.proxyGCHandle<@http://127.0.0.1:42097/_framework/dotnet.runtime.js:3:206322
                 Fl</<@http://127.0.0.1:42097/_framework/dotnet.runtime.js:3:206495
                 ). Build with -sASSERTIONS for more info.
[14:14:53] fail: [0x012ad6f0-dpty 14:14:53.585] MONO_WASM: mono_wasm_start_deputy_thread_async() failed RuntimeError: Aborted(co@mono_wasm_invoke_jsexport (http://127.0.0.1:42097/_framework/dotnet.js:3:27212
                 lo@http://127.0.0.1:42097/_framework/dotnet.js:3:26825
                 abort@http://127.0.0.1:42097/_framework/dotnet.native.js:8:9945
                 _abort@http://127.0.0.1:42097/_framework/dotnet.native.js:8:104230
                 @http://127.0.0.1:42097/_framework/dotnet.native.wasm:wasm-function[194]:0x15528)
                 createDotnetRuntime</</Module._mono_wasm_invoke_jsexport@http://127.0.0.1:42097/_framework/dotnet.native.js:8:133139
                 Fl</</ot.proxyGCHandle<@http://127.0.0.1:42097/_framework/dotnet.runtime.js:3:206322
                 Fl</<@http://127.0.0.1:42097/_framework/dotnet.runtime.js:3:206495
                 ). Build with -sASSERTIONS for more info.

…14.3

Microsoft.SourceBuild.Intermediate.emsdk , Microsoft.NET.Workload.Emscripten.Current.Manifest-9.0.100.Transport
 From Version 9.0.0-rc.2.24461.2 -> To Version 9.0.0-rc.2.24464.3
@lewing
Copy link
Member

lewing commented Sep 16, 2024

@carlossanlop green now

@carlossanlop carlossanlop merged commit dbb28df into release/9.0 Sep 16, 2024
@carlossanlop carlossanlop deleted the darc-release/9.0-9727522e-87a7-483e-b808-62b71b33a47a branch September 16, 2024 22:40
@github-actions github-actions bot locked and limited conversation to collaborators Oct 17, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

area-codeflow for labeling automated codeflow Servicing-approved Approved for servicing release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants