-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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] Tracking AOT wasm library test failures #48079
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsTo see where the wasm library tests stand with AOT compilation with respect to how many pass/fail, what the failures are, how many hang, the 268 test suites were ran locally. Dropbox paper with findings Suites that did not produce
|
Author: | mdh1418 |
---|---|
Assignees: | - |
Labels: |
|
Milestone: | - |
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to this area: @CoffeeFlux Issue DetailsTo see where the wasm library tests stand with AOT compilation with respect to how many pass/fail, what the failures are, how many hang, the 268 test suites were ran locally. Dropbox paper with findings Suites that did not produce
|
Author: | mdh1418 |
---|---|
Assignees: | - |
Labels: |
|
Milestone: | - |
It would be nice to compare this with currently known failures with the interpreter, so we can tell what is AOT-specific. |
I ran all the libraries for Browser wasm here. There were only 5 test failures overall, belonging to two different test suites. However, there were a number of suites that had 0 tests run most likely due to skips. To compare the failures found from running tests in AOT mode, the test names themselves were compared and out of the tests ran (Not skipped) in interp mode (non AOT), 5275 of the 10974 tests failing in AOT Mode were ran on interp mode. The rest (5699) are likely tests that are skipped on interp mode. The 5275 tests that failed on AOT yet passing on Interp overall belong to 79 different test suites under |
Can the changes be merged, even if turned off by default, so these failures are easier to debug ? |
I (@fanyang-mono ) am working on the issue |
Closing this, as this predates the newer set of aot test issues that are tracked with |
To see where the wasm library tests stand with AOT compilation with respect to how many pass/fail, what the failures are, how many hang, the 268 test suites were ran locally.
Dropbox paper with findings
All CI Results
Among all the test suites failing on CI, the following are the main unique test failures observed.
Unique Test Failures based on CI logs
Assert.True() Failure
[Wasm][AOT]Assert.True() failure
#49246System.ExecutionEngineException : AOT Compilation failed for method
wasm AOT library test failure - AOT Compilation failed for method #49219System.ExecutionEngineException : Attempting to JIT compile method
wasm AOT library test failure - Attempting to JIT compile method #46708console.error: RuntimeError: memory access out of bounds
wasm AOT library test failure - memory access out of bounds #46700System.NotImplementedException : The method or operation is not implemented.
[Wasm][AOT] System.NotImplementedException : The method or operation is not implemented. #49229System.ExecutionEngineException : AOT Compilation failed for method 'void System.Threading.CancellationTokenSource:ExecuteCallbackHandlers (bool)'.
wasm AOT library test failure - AOT Compilation failed for method #49219System.ExecutionEngineException : AOT Compilation failed for method 'bool Microsoft.Extensions.Internal.ParameterDefaultValue:TryGetDefaultValue (System.Reflection.ParameterInfo,object&)'.
wasm AOT library test failure - AOT Compilation failed for method #49219System.ExecutionEngineException : Attempting to JIT compile method '(wrapper dynamic-method) object Microsoft.Extensions.DependencyInjection.ServiceLookup.ILEmitResolverBuilder:ResolveService (Microsoft.Extensions.DependencyInjection.ServiceLookup.ILEmitResolverBuilder/ILEmitResolverBuilderRuntimeContext,Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope)' while running in aot-only mode. See https://docs.microsoft.com/xamarin/ios/internals/limitations for more information.
wasm AOT library test failure - Attempting to JIT compile method #46708System.ExecutionEngineException : Attempting to JIT compile method '(wrapper dynamic-method) object object:lambda_method
wasm AOT library test failure - Attempting to JIT compile method #46708AOT Compilation failed for method 'object Microsoft.Extensions.DependencyInjection.ActivatorUtilities/ConstructorMatcher:CreateInstance (System.IServiceProvider)'.
wasm AOT library test failure - AOT Compilation failed for method #49219System.ExecutionEngineException : AOT Compilation failed for method 'System.Threading.Tasks.Task System.Net.Http.HttpContent:LoadIntoBufferAsync (long,System.Threading.CancellationToken)'.
wasm AOT library test failure - AOT Compilation failed for method #49219EventName and ExceptionJson is supposed to be null but it isn't.
[Wasm][AOT] Microsoft.Extensions.Logging.EventSource.Tests failures #49240LoggerName is supposed to be null but it isn't.
[Wasm][AOT] Microsoft.Extensions.Logging.EventSource.Tests failures #49240console.error: RuntimeError: invalid index into function table
wasm AOT library test failure - invalid index into function table #46731System.Composition.Hosting.CompositionFailedException : No export was found for the contract
[Wasm][AOT] System.Composition.Hosting.CompositionFailedException #49230System.Composition.Hosting.CompositionFailedException : No importing constructor was found on type
[Wasm][AOT] System.Composition.Hosting.CompositionFailedException #49230System.ExecutionEngineException : AOT Compilation failed for method 'void System.Data.DataColumnCollection:BaseAdd (System.Data.DataColumn)'.
wasm AOT library test failure - AOT Compilation failed for method #49219System.ExecutionEngineException : AOT Compilation failed for method 'void System.Data.DataRow:set_Item (System.Data.DataColumn,object)'
wasm AOT library test failure - AOT Compilation failed for method #49219System.IO.DirectoryNotFoundException : Could not find a part of the path
orSystem.IO.FileNotFoundException : Could not find file
[Wasm][AOT] System.IO.DirectoryNotFoundException And System.IO.FileNotFoundException #49232 (@fanyang-mono working on this)Assert.NotEmpty() Failure
[Wasm][AOT] System.Diagnostics.TraceSource.Tests failures #49241Assert.Contains() Failure
[Wasm][AOT] System.Diagnostics.TraceSource.Tests failures #49241System.ExecutionEngineException : AOT Compilation failed for method 'void System.IO.MemoryMappedFiles.Tests.MemoryMappedFileTests_CreateFromFile
wasm AOT library test failure - AOT Compilation failed for method #49219System.ExecutionEngineException : AOT Compilation failed for method 'void System.Net.Http.HttpContent:CopyTo (System.IO.Stream,System.Net.TransportContext,System.Threading.CancellationToken)'.
wasm AOT library test failure - AOT Compilation failed for method #49219Special case (Invariant.Tests)
System.ExecutionEngineException : AOT Compilation failed for method 'void System.Net.Mime.ContentType:ParseValue ()'.
wasm AOT library test failure - AOT Compilation failed for method #49219[byte difference]
[Wasm][AOT] System.Reflection.Metadata.Tests failures #49245System.InvalidOperationException : Failed to compare two elements in the array.
wasm AOT library test failure - System.InvalidOperationException #46759Assert.Throws() Failure
[Wasm][AOT] System.Runtime.CompilerServices.Unsafe.Tests failures #49242console.error: RuntimeError: function signature mismatch
wasm AOT library test failure - function signature mismatch #46761 logSystem.NullReferenceException : Object reference not set to an instance of an object.
[Wasm][AOT] System.NullReferenceException : Object reference not set to an instance of an object. #49234System.ExecutionEngineException : AOT Compilation failed for method 'void System.Numerics.Tests.divremTest:VerifyDivRemString (string)'.
wasm AOT library test failure - AOT Compilation failed for method #49219Assertion at /__w/1/s/src/mono/mono/metadata/class-init.c:2746, condition '<disabled>' not met
wasm AOT library test failure - condition<disabled>
not met #46698 logAssertion: should not be reached at /__w/1/s/src/mono/mono/metadata/class-accessors.c:86
[Wasm][AOT] Assertion: should not be reached at src/mono/mono/metadata/class-accessors.c:83 #45304Assertion at /__w/1/s/src/mono/mono/mini/mini-generic-sharing.c:2168, condition '<disabled>' not met
wasm AOT library test failure - condition<disabled>
not met #46698 logProcess 24507 didn't exit within 00:15:00 and will be killed
[Wasm][AOT] System.Threading.Tasks.Dataflow.Tests failures #49243Assertion at /__w/1/s/src/mono/mono/mini/mini-exceptions.c:3965, condition '<disabled>' not met
wasm AOT library test failure - condition<disabled>
not met #46698 logconsole.error: Unhandled exception in _finalize_startup Error: FS error
[Wasm][AOT] System.IO.FileSystem.Tests failures #49244Assertion: should not be reached at /__w/1/s/src/mono/mono/mini/../sgen/sgen-scan-object.h:91
[Wasm][AOT] Assertion: should not be reached at /__w/1/s/src/mono/mono/mini/../sgen/sgen-scan-object.h:91 #49225EnableAggressiveTrimming related failures
r)
System.ArgumentException : Type Moq.Internals.InterfaceProxy is not valid base type for interface proxy, because it does not have accessible parameterless constructor. Only a non-sealed class with non-private default constructor can be used as base type for interface proxy. Please use some other valid type.
#46760 logs)
System.InvalidOperationException : Sequence contains no matching element
#46759t)
System.ArgumentNullException : Value cannot be null. (Parameter 'method')
#46758 (@naricc working on this)af)
System.NotSupportedException : Use of ResourceManager for custom types is disabled. Set the MSBuild Property CustomResourceTypesSupport to true in order to enable it.
ah)
console.error: System.AggregateException: One or more errors occurred. (Object reference not set to an instance of an object.) ---> System.NullReferenceException: Object reference not set to an instance of an object.
ai)
Could not load file or assembly 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies
logThe Unique failures may appear across several test suites. Each test suite below has failed on CI, and are tagged with the corresponding failure by the alphabetical tag.
Suites that did not produce test results
Error: Failed to load method 0x6000001
Suites that failed with 1 or more test failures
Kæ￿ $@#�'ã†�ìŽ A5
not AOT relatedTests failing in CI
The text was updated successfully, but these errors were encountered: