|
Ran
|
Jobs
1
|
Files
89
|
Run time
4min
|
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 6032 branches covered (94.43%)
Branch coverage included in aggregate %.
1 of 1 new or added line in 1 file covered. (100.0%)
7 existing lines in 2 files now uncovered.21692 of 23429 relevant lines covered (92.59%)
2935313.58 hits per line
| Lines | Coverage | ∆ | File |
|---|---|---|---|
| 2 |
99.16 |
-0.34% | src/lj_gc.c |
| 5 |
78.42 |
-0.31% | src/lj_opt_fold.c |
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 12804709872.1 | 89 |
92.96 |
GitHub Action Run |
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line | Branch Hits | Branch Misses |
|---|