-
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
[mono] Android x64: No pending exception expected: java.lang.ClassNotFoundException #92000
Comments
Tagging subscribers to 'arch-android': @steveisok, @akoeplinger Issue DetailsOccurred on Build InformationBuild: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=402917 Error MessageFill the error message using step by step known issues guidance. {
"ErrorMessage": "Abort message: 'No pending exception expected: java.lang.ClassNotFoundException: throw",
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}
|
removing blocking-clean-ci as it has not failed in 30 days
|
Occurred on
Build android-x64 Release AllSubsets_Mono_RuntimeTests minijit
andandroid-x64 Release AllSubsets_Mono_RuntimeTests_Interp monointerpreter
.Log: https://helixre107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-pull-91925-merge-14240024556a44e6be/PayloadGroup0/1/console.18bcda7f.log?helixlogtype=result
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=402917
Build error leg or test failing: baseservices/exceptions/unhandled/unhandled/unhandled.sh
Pull request: #91925
Error Message
Fill the error message using step by step known issues guidance.
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=402917
Error message validated:
Abort message: 'No pending exception expected: java.lang.ClassNotFoundException: throw
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 9/13/2023 12:21:14 PM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: