dd-trace-php icon indicating copy to clipboard operation
dd-trace-php copied to clipboard

test(CI): upload junit reports to datadog

Open Leiyks opened this issue 3 weeks ago • 2 comments

Description

Reviewer checklist

  • [ ] Test coverage seems ok.
  • [ ] Appropriate labels assigned.

Leiyks avatar Dec 08 '25 15:12 Leiyks

Codecov Report

:white_check_mark: All modified and coverable lines are covered by tests. :white_check_mark: Project coverage is 61.60%. Comparing base (867b36c) to head (c4d3680). :warning: 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.

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

codecov-commenter avatar Dec 08 '25 15:12 codecov-commenter

Benchmarks [ tracer ]

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

Comparing candidate commit c4d3680f23135fdffb0c379a20f119219907d708 in PR branch leiyks/feat-upload-junit-report-to-datadog with baseline commit 867b36cac82bbfcdf2e1aaf37393f721a010e37f 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%]

pr-commenter[bot] avatar Dec 08 '25 16:12 pr-commenter[bot]