chore(ci): Prototype: SMP client-side report rendering - #2324
Conversation
c4803f8 to
8948e88
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8948e88e8b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| when: always | ||
| script: | ||
| - python3 ./ci/tooling/build-smp-report.py | ||
| - ./smp report render |
There was a problem hiding this comment.
Make the SMP binary available to the report job
On every development-branch pipeline, report-benchmarks-adp starts in a fresh container and invokes ./smp, but the SMP CI image does not install that binary and the upstream job's artifact list contains only submission_metadata and the two report files. The binary downloaded by run-benchmarks-adp therefore does not reach this job, so this command exits with “No such file or directory” before generating or posting the condensed report, causing the reporting job—and otherwise successful pipelines—to fail. Download smp here or publish it as an artifact needed by this job.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
The standalone report job cannot invoke the new renderer because its fresh workspace receives only report artifacts and the CI image does not include smp; every PR benchmark report therefore stops before posting its condensed comment.
🤖 Datadog Autotest · Commit 8948e88 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest
| when: always | ||
| script: | ||
| - python3 ./ci/tooling/build-smp-report.py | ||
| - ./smp report render |
There was a problem hiding this comment.
Acquire
smp in the standalone report job
Every development-branch benchmark report job fails before rendering, so PR authors receive no condensed benchmark comment even after a successful benchmark sync.
Assertion details
- Input: Any development-branch pipeline that schedules the separate
report-benchmarks-adpjob. - Expected: The reporting job should acquire the pinned SMP binary before invoking
smp report render, then publish the condensed PR comment. - Actual:
report-benchmarks-adpinvokes./smp, but neither the job image nor the artifacts downloaded throughneedscontain that executable.
| - ./smp report render | |
| - *setup-smp-env | |
| - ./ci/tooling/configure-smp-aws-credentials.sh | |
| - aws --profile ${AWS_NAMED_PROFILE} s3 cp s3://smp-cli-releases/${SMP_VERSION}/x86_64-unknown-linux-musl/smp smp && chmod +x smp | |
| - ./smp report render |
Was this helpful? React 👍 or 👎
🤖 Datadog Autotest · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest
Binary Size Analysis (Agent Data Plane)Baseline: ca31d5f · Comparison: d570b7f · diff ✅ Binary size difference within thresholdChanges by Module
Detailed Symbol Changes |
8948e88 to
45c414a
Compare
Regression Detector (Agent Data Plane)this test report is locally rendered Optimization Goals: ✅ No significant changes detectedFine details of change detection per experiment (5)Experiments configured
Bounds Checks: ✅ Passed (5)
ExplanationA change is flagged as a regression when |Δ mean %| > 5.00% in the regressing direction for its optimization goal AND SMP marks the experiment as a regression ( |
Summary
Use a
SMPbinary generated by https://github.com/DataDog/single-machine-performance/pull/4693/sChange Type