-
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
System.Memory.Tests.Span.StringSearchValuesTests failing with "Exit code was 1 but it should have been 42" #90945
Comments
Tagging subscribers to this area: @dotnet/area-system-memory Issue DetailsBuild InformationBuild: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=382187 Error MessageTwo tests failing:
Fill the error message using step by step known issues guidance. {
"ErrorMessage": "at System.Memory.Tests.Span.StringSearchValuesTests.",
"ErrorPattern": ""
}
|
cc @MihaZupan Related to #88394 |
All failures in Kusto are on Seems related to #66147, which already disabled similar |
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=382187
Build error leg or test failing: GC_API.WorkItemExecution
Pull request: #90796
Error Message
Two tests failing:
Exit code was 1 but it should have been 42
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=382187
Error message validated:
at System.Memory.Tests.Span.StringSearchValuesTests.
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 8/22/2023 6:40:32 PM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: