-
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
tracing/eventpipe/providervalidation/providervalidation/providervalidation.cmd test failure #101759
Comments
Test output from failing test in case it is useful
|
The error message regex pattern I ran providervalidation locally, and wasn't able to immediately repro the error Tom provided. |
From looking at the past 9 build console logs, it looks like the All of the 9 logs' thread 1 stacks call So it seems mono specific. Is it possible to highlight the actual reason for the crash from the @carlossanlop did you create a different tracking issue for #87444, or should we just create error message matching at the Managed stacktrace level? |
Closing for the same reason as #87444, Instead, issues for CI failures should try to match part of the managed stack trace instead if the Native stacktrace is unknown and the External Debugger dump points towards "futex-internal" |
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=661154
Build error leg or test failing: tracing/eventpipe/providervalidation/providervalidation/providervalidation.cmd
Pull request: #101715
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=661154
Error message validated:
[./nptl/futex-internal.c: No such file or directory
]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 5/1/2024 8:59:40 AM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: