xapi-project
/
xen-api
/
24460003757
80%
master: 79%
master: 79%
|
Ran
|
Jobs
1
|
Files
34
|
Run time
1min
|
Badge
Embed ▾
README BADGES
|
coverage: 80.459%. Remained the same
push
github
web-flowmessage-forwrding: keep backtraces when reraising an exception (26.1-lcm) (#6996) 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. (cherry picked from commit https://github.com/xapi-project/xen-api/commit/1268943a9)
3504 of 4355 relevant lines covered (80.46%)
0.8 hits per line
Jobs
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | python3.11 - 24460003757.1 | 34 |
80.46 |
GitHub Action Run |
