• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

xapi-project / xen-api / 17642309023 / 1
80%
master: 80%

Build:
Build:
LAST BUILD BRANCH: asv/revert_stream_vdi
DEFAULT BRANCH: master
Ran 11 Sep 2025 10:59AM UTC
Files 34
Run time 1s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

11 Sep 2025 10:55AM UTC coverage: 80.368%. Remained the same
17642309023.1

push

github

web-flow
CP-308811: Add an option to limit the span depth in tracing (#6607)

Adds a new span.depth key to the trace context baggage, and a
configurable max_span_depth. This defaults to 100 and so will not limit
traces (the traces I've seen with the most depth are ~40 depth e.g.
https://jaeger.kfd.eng.citrite.net/trace/ea5ddca5509b3ae1102bc7279092652d),
but is useful when wanting to analyse large traces which can often
become slow if all the spans are recorded in a trace.

This isn't perfect, the span.depth seems to get lost sometimes between
xapi and xenops, resulting in a greater depth than that listed, but I
have created ticket CP-308999 for this and this works well enough to
greatly reduce the number of spans in a trace when needed, which is the
intention. As an example, a host evacuate trace with max_span_depth 10
goes down to ~1000 spans rather than the 34k+ withou a depth limit.

3496 of 4350 relevant lines covered (80.37%)

0.8 hits per line

Source Files on job python3.11 - 17642309023.1
  • Tree
  • List 34
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 17642309023
  • e3d4f34b on github
  • Prev Job for on gh-readonly-queue/master/pr-6607-2bef63a7063fc01a23bb66017b47f76fd51e8564 (#17638733496.1)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc