24181767299
80%
master: 80%

Ran 09 Apr 2026 09:01AM UTC

Jobs 1

Files 34

Run time 1min

Badge

Embed ▾

Committed 09 Apr 2026 08:59AM UTC coverage: 80.459%. Remained the same

Build # 24181767299

Build Type

push

github

Committed by

web-flow

Commit Message

message-forwrding: keep backtraces when reraising an exception (#6995)

A few functions in message_forwarding need to do some cleanup when
encountering an exception, but in doing so, the original backtrace is
lost. This makes it difficult to track down the original location that
raised
 the exception.

I've considered other options instead of calling Backtrace.is_important:
- Call `Backtrace.reraise e e`: this is more expensive than it needs to
  be.
- Create a new function that can be easily used: This is awkward to
  backport, and in my attempts the resulting code was not great to read.

So I ended up with the compromise of using Backtrace.is_important, which
does exactly what's needed here, even though it's difficult to enforce
correctly across the codebase.

Coverage Stats

3504 of 4355 relevant lines covered (80.46%)

0.8 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	python3.11 - 24181767299.1	09 Apr 2026 09:01AM UTC	34	80.46	GitHub Action Run

xapi-project / xen-api / 24181767299
80%
master: 80%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 24181767299

xapi-project / xen-api / 24181767299 80% master: 80%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 24181767299

xapi-project / xen-api / 24181767299
80%
master: 80%

README BADGES
x