Skip to content

Conversation

@Leiyks
Copy link
Contributor

@Leiyks Leiyks commented Dec 8, 2025

Description

Reviewer checklist

  • Test coverage seems ok.
  • Appropriate labels assigned.

@codecov-commenter
Copy link

codecov-commenter commented Dec 8, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 61.60%. Comparing base (867b36c) to head (c4d3680).
⚠️ Report is 25 commits behind head on master.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #3521      +/-   ##
==========================================
- Coverage   61.74%   61.60%   -0.14%     
==========================================
  Files         142      142              
  Lines       12975    12975              
  Branches     1700     1700              
==========================================
- Hits         8011     7993      -18     
- Misses       4204     4222      +18     
  Partials      760      760              

see 4 files with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 867b36c...c4d3680. Read the comment docs.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@pr-commenter
Copy link

pr-commenter bot commented Dec 8, 2025

Benchmarks [ tracer ]

Benchmark execution time: 2025-12-17 13:34:10

Comparing candidate commit c4d3680 in PR branch leiyks/feat-upload-junit-report-to-datadog with baseline commit 867b36c in branch master.

Found 3 performance improvements and 3 performance regressions! Performance is the same for 187 metrics, 1 unstable metrics.

scenario:MessagePackSerializationBench/benchMessagePackSerialization

  • 🟩 execution_time [-5.933µs; -4.367µs] or [-5.315%; -3.912%]

scenario:MessagePackSerializationBench/benchMessagePackSerialization-opcache

  • 🟩 execution_time [-4.416µs; -2.264µs] or [-3.920%; -2.010%]

scenario:PHPRedisBench/benchRedisBaseline

  • 🟥 execution_time [+5.685µs; +6.928µs] or [+4.213%; +5.134%]

scenario:SamplingRuleMatchingBench/benchGlobMatching1

  • 🟥 execution_time [+47.311ns; +112.689ns] or [+2.162%; +5.149%]

scenario:SpanBench/benchOpenTelemetryAPI-opcache

  • 🟥 mem_peak [+1.700MB; +1.704MB] or [+4.418%; +4.430%]

scenario:TraceSerializationBench/benchSerializeTrace

  • 🟩 execution_time [-40.634µs; -27.466µs] or [-9.109%; -6.157%]

@Leiyks Leiyks force-pushed the leiyks/feat-upload-junit-report-to-datadog branch 11 times, most recently from b0268f7 to f764fc8 Compare December 15, 2025 13:47
Signed-off-by: Alexandre Rulleau <alexandre.rulleau@datadoghq.com>
@Leiyks Leiyks force-pushed the leiyks/feat-upload-junit-report-to-datadog branch from f764fc8 to c4d3680 Compare December 17, 2025 12:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants