|
Ran
|
Jobs
1
|
Files
89
|
Run time
1min
|
Badge
README BADGES
|
push
github
Fix predict_next() in parser (for real now). Reported by Sergey Kaplun. (cherry picked from commit f602f0154) Before the patch `predict_next()` uses the pc allocation limit (`fs->bclim`) instead of the real limit of the defined bytecodes (`fs->pc`). This leads to the use of undefined value and possible crash. This patch fixes the check. Sergey Kaplun: * added the description and the test for the problem Part of tarantool/tarantool#10709
5696 of 6033 branches covered (94.41%)
Branch coverage included in aggregate %.
1 of 1 new or added line in 1 file covered. (100.0%)
5 existing lines in 3 files now uncovered.21708 of 23438 relevant lines covered (92.62%)
2963948.88 hits per line
| Lines | Coverage | ∆ | File |
|---|---|---|---|
| 1 |
99.04 |
1.44% | src/lj_str.c |
| 2 |
78.42 |
-0.16% | src/lj_opt_fold.c |
| 2 |
94.08 |
0.0% | src/lj_ir.c |
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 13026640110.1 | 89 |
92.99 |
GitHub Action Run |
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line | Branch Hits | Branch Misses |
|---|