Ran
|
Jobs
1
|
Files
89
|
Run time
9s
|
Badge
Embed ▾
README BADGES
|
push
github
Avoid assertion in case of stack overflow from stitched trace. Reported by Sergey Bronnikov. Fixed by Sergey Kaplun. (cherry-picked from commit 1d75cd4d7) When we exit from a stitched trace due to the Lua stack overflow error, we cannot determine the bytecode position properly, and because of that, we get the incorrect bytecode instruction in `debug_framepc`. This patch fixes this behavior, so the `debug_framepc` now returns `NO_BCPOS` for this case. Maxim Kokryashkin: * added the description and the test for the problem Part of tarantool/tarantool#9145 Reviewed-by: Sergey Bronnikov <sergeyb@tarantool.org> Reviewed-by: Sergey Kaplun <skaplun@tarantool.org> Signed-off-by: Igor Munkin <imun@tarantool.org>
5419 of 6013 branches covered (90.12%)
Branch coverage included in aggregate %.
20752 of 23406 relevant lines covered (88.66%)
2801269.14 hits per line
ID | Job ID | Ran | Files | Coverage | |
---|---|---|---|---|---|
1 | 7886114042.1 | 89 |
88.96 |
GitHub Action Run |
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line | Branch Hits | Branch Misses |
---|