-
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
[mono][ios] Eventpipe gcdump test failing on apple mobile platforms #90012
Comments
Just following the steps above will leave the diagnostic tracing component disabled as well as not setting the needed env variable to startup the diagnostic server. Making sure we link @kotlarmilos could you retry your repro making sure we got the needed pre-reqs in place (linking to the none stub version of the diagnostics_tracing component as well as setting up the diagnostic server) and see if it still repros. |
@kotlarmilos, did you have a chance to try this test with the above? |
Thanks for the heads up, I didn't have capacity before the RC1 snap, but I will follow-up this week. I think the components are not properly initialized locally. I will try to reproduce it without stubs. |
I managed to reproduce it on a device. Try to add snippet below to the target in Lines 348 to 351 in a3a0f5c
The app fails with the following log:
|
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=363106
Build error leg or test failing: tracing/eventpipe/gcdump.dll
Pull request: #89726
Error Message
Fill the error message using step by step known issues guidance.
Test log:
Repro steps
Note: You may need to provide a correct path to the cross compiler in the AppleBuild.targets.
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=363106
Error message validated:
Application has finished with exit code 255 but 100 was expected
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 8/4/2023 11:24:17 AM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: