-
Notifications
You must be signed in to change notification settings - Fork 10
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
Fix builder cmake target directory. #776
Conversation
BenchmarksComparisonBenchmark execution time: 2024-12-03 10:52:58 Comparing candidate commit 9e24825 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 #776 +/- ##
==========================================
- Coverage 70.55% 70.52% -0.04%
==========================================
Files 297 297
Lines 43528 43533 +5
==========================================
- Hits 30712 30701 -11
- Misses 12816 12832 +16
|
builder/src/crashtracker.rs
Outdated
@@ -22,11 +22,15 @@ pub struct CrashTracker { | |||
impl CrashTracker { | |||
fn gen_binaries(&self) -> Result<()> { | |||
if arch::BUILD_CRASHTRACKER { | |||
let mut datadog_root = project_root(); | |||
datadog_root.push(self.target_dir.as_ref()); | |||
println!("ROOT: {}", datadog_root.to_str().unwrap()); |
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.
nitt: Is it for logging or is it a debug print that was forgotten ?
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.
the latter, thanks for noticing
ea72e53
to
9e24825
Compare
What does this PR do?
Fix cmake target directory during the artifact generation.
Motivation
The builder could fail on certain scenarios.
How to test the change?
Builder can be triggered by:
cargo run --bin release --features profiling,telemetry,symbolizer,crashtracker,data-pipeline --release -- --out <path>
After that it can be checked that all required artifacts should be in the desired output path