-
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][AOT] Xunit.Sdk.ReflectionAttributeInfo.GetNamedArgument Exception #49770
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsThere is an ongoing effort to better understand the failures encountered when running wasm library tests with AOT compilation on CI. In the past week, this error #49717 began surfacing. In an attempt to reproduce #49717 and figuring out the scope, now this error is being hit. This error has been seen in Error
ReproRunning library tests on Browser wasm based on 4e3deb5
|
We found that this error started occurring after #49072 was merged in to master. |
Do methods with filters run with interp even in aot case ? Or just the filter clause is interpreted ? Or what's the catch here ? |
…et#49072)" This reverts commit 686f752. Reverting this for now, as a workaround to get the AOT library tests working again. Running library tests with AOT+EnableAggressiveTrimming broke with: ``` info: Arguments: --run,WasmTestRunner.dll,System.Buffers.Tests.dll,-notrait,category=OuterLoop,-notrait,category=failing info: Initializing..... fail: System.AggregateException: AggregateException_ctor_DefaultMessage (Arg_NullReferenceException) ---> System.NullReferenceException: Arg_NullReferenceException at Xunit.Sdk.ReflectionAttributeInfo.GetNamedArgument[Int32](String argumentName) --- End of stack trace from previous location --- at Xunit.Sdk.ReflectionAttributeInfo.GetNamedArgument[Int32](String argumentName) --- End of stack trace from previous location --- at Xunit.Sdk.ReflectionAttributeInfo.GetNamedArgument[Int32](String argumentName) Exception_EndOfInnerExceptionStack info: Discovering: System.Buffers.Tests.dll (method display = ClassAndMethod, method display options = None) info: WASM EXIT 1 fail: Application has finished with exit code TESTS_FAILED but 0 was expected ``` More info: dotnet#49770
There is an ongoing effort to better understand the failures encountered when running wasm library tests with AOT compilation on CI. In the past week, this error #49717 began surfacing. In an attempt to reproduce #49717 and figuring out the scope, now this error is being hit.
This error has been seen in
System.Buffers.Tests.csproj
,Common.Tests.csproj
, andSystem.ComponentModel.TypeConverter.Tests.csproj
withRunAOTCompilation=true
(regardless of the value ofEnableAggressiveTrimming
). WhenRunAOTCompilation=false
(regardless of the value ofEnableAggressiveTrimming
, the tests run to completion with no failures.Error
Repro
Running library tests on Browser wasm based on 4e3deb5
Make the following changes to prevent linking out xunit related assemblies and skip an exception filter error with AOT compilation.
./build.sh -os Browser -arch wasm -c Release
./dotnet.sh build /t:Test /p:TargetOS=Browser /p:TargetArchitecture=wasm /p:Configuration=Release /p:EnableAggressiveTrimming=true /p:RunAOTCompilation=true src/libraries/System.Buffers/tests/System.Buffers.Tests.csproj
The text was updated successfully, but these errors were encountered: