-
Notifications
You must be signed in to change notification settings - Fork 9
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
[crashtracker] Small style improvements to 754 #759
Conversation
BenchmarksComparisonBenchmark execution time: 2024-11-26 19:45:56 Comparing candidate commit 72a94ce in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 51 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
BaselineOmitted due to size. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #759 +/- ##
=======================================
Coverage 70.53% 70.53%
=======================================
Files 297 297
Lines 43487 43484 -3
=======================================
Hits 30673 30673
+ Misses 12814 12811 -3
|
@@ -228,29 +223,27 @@ fn run_receiver_child(uds_parent: RawFd, uds_child: RawFd, stderr: RawFd, stdout | |||
} | |||
} | |||
|
|||
/// true if successful wait, false if timeout occurred. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is returning an error on timeout not a good idea here?
What does this PR do?
Addresses some PR comments I'd made on #754 754
Motivation
David was so fast he merged before I posted the comments.
Additional Notes
Anything else we should know when reviewing?
How to test the change?
Describe here in detail how the change can be validated.