24137293824
80%
master: 78%

Ran 08 Apr 2026 01:15PM UTC

Jobs 0

Files 0

Run time –

Badge

Embed ▾

pending completion

cancel

Build # 24137293824

Build Type

push

github

Committed by

psafont

Commit Message

message-forwrding: keep backtraces when reraising an exception

A few functions in message_forwarding need to do some cleanup when
encountering an exception, but in doing so, the original backtrace is
being 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.

Signed-off-by: Pau Ruiz Safont <pau.safont@vates.tech>

Coverage Stats

Source Files on build 24137293824

Detailed source file information is not available for this build.

psafont / xen-api / 24137293824
80%
master: 78%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on build 24137293824

psafont / xen-api / 24137293824 80% master: 78%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on build 24137293824

psafont / xen-api / 24137293824
80%
master: 78%

README BADGES
x