-
Notifications
You must be signed in to change notification settings - Fork 13
fix(ddcommon): fix build on i686 #1144
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
base: main
Are you sure you want to change the base?
Conversation
Artifact Size Benchmark Reportaarch64-alpine-linux-musl
aarch64-unknown-linux-gnu
libdatadog-x64-windows
libdatadog-x86-windows
x86_64-alpine-linux-musl
x86_64-unknown-linux-gnu
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1144 +/- ##
==========================================
+ Coverage 71.30% 71.51% +0.21%
==========================================
Files 343 343
Lines 52471 52848 +377
==========================================
+ Hits 37412 37792 +380
+ Misses 15059 15056 -3
🚀 New features to boost your workflow:
|
@@ -64,9 +64,9 @@ pub fn alt_fork() -> libc::pid_t { | |||
}; | |||
|
|||
// The max value of a PID is configurable, but within an i32, so the failover | |||
if res > pid_t::MAX as i64 { | |||
if (res as i64) > (pid_t::MAX as i64) { |
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.
Nit: probably it would be better to use res
as a c_long
since the syscall is supposed to return that exact type and then cast pid_t
to c_long
just to cover the case the where the platform is 64bit
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.
Not sure it's an issue as we don't support bsd but syscall doesn't always return a c_long 😩
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.
I saw that but decided to ignore since, as you said, I don't think we will target bsd. Anyway I'll let you decide what's the cleanest way to do it.
fbe5ccd
to
7aac992
Compare
BenchmarksComparisonBenchmark execution time: 2025-07-16 12:32:49 Comparing candidate commit 7aac992 in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 52 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
BaselineOmitted due to size. |
/merge |
View all feedbacks in Devflow UI.
The expected merge time in Use ⏳ Processing |
What does this PR do?
Build is broken on i686 due to
c_long
(return value fromsyscall
) being an i32 instead of a i64 see this jobMotivation
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.