tarantool
/
luajit
/
13947733880
93%
tarantool/master: 93%
tarantool/master: 93%
|
Ran
|
Jobs
1
|
Files
89
|
Run time
1min
|
Badge
Embed ▾
README BADGES
|
coverage: 92.929% (-0.09%) from 93.02%
push
github
BuristanAvoid unpatching bytecode twice after a trace flush. Reported by Sergey Kaplun. (cherry picked from commit 85c3f2fb6) When flushing the already flushed trace, it is possible that another trace is recorded for the same bytecode as the first trace. In that case, the assertion fails in `trace_unpatch()`. This patch fixes it by unpatching the trace only in the case if it persists in the trace chain. Also, it deletes the dead code for the trace unpatching logic, since the root trace can't start from `BC_JMP` and the child traces are handled differently. Sergey Kaplun: * added the description and the test for the problem Part of tarantool/tarantool#11055
5699 of 6039 branches covered (94.37%)
Branch coverage included in aggregate %.
21715 of 23461 relevant lines covered (92.56%)
2962812.3 hits per line
Coverage Regressions
| Lines | Coverage | ∆ | File |
|---|---|---|---|
| 10 |
77.8 |
-1.01% | src/lj_api.c |
| 7 |
87.15 |
-0.66% | src/lj_crecord.c |
| 7 |
96.01 |
-0.47% | src/lj_record.c |
| 2 |
99.16 |
-0.34% | src/lj_gc.c |
| 2 |
92.0 |
-0.44% | src/luajit.c |
| 1 |
78.42 |
0.0% | src/lj_opt_fold.c |
| 1 |
97.42 |
-0.18% | src/lj_trace.c |
Jobs
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 13947733880.1 | 89 |
92.93 |
GitHub Action Run |
