-
Notifications
You must be signed in to change notification settings - Fork 16
chore(crashtracking): cfg child helper function with the same conditions as its parent test_crasht_tracking_validate_callstack
#1431
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
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
test_crasht_tracking_validate_callstack
aee24bf to
a8e4a81
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1431 +/- ##
==========================================
- Coverage 71.38% 71.38% -0.01%
==========================================
Files 411 411
Lines 66110 66110
==========================================
- Hits 47192 47191 -1
- Misses 18918 18919 +1
🚀 New features to boost your workflow:
|
BenchmarksComparisonBenchmark execution time: 2026-01-06 21:54:43 Comparing candidate commit a8e4a81 in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 57 metrics, 2 unstable metrics. CandidateCandidate benchmark detailsGroup 1
Group 2
Group 3
Group 4
Group 5
Group 6
Group 7
Group 8
Group 9
Group 10
Group 11
Group 12
Group 13
Group 14
Group 15
Group 16
Group 17
Group 18
Group 19
BaselineOmitted due to size. |
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|

What does this PR do?
test_crasht_tracking_validate_callstackis disabled on aarch64 musl and libc. We should disabletest_crash_tracking_callstackunder the same conditions to clean up clippy warnings. Comment added so that we know to remove both cfgs when this is revisitedMotivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
How to test the change?
Describe here in detail how the change can be validated.