|
Ran
|
Jobs
1
|
Files
89
|
Run time
7s
|
Badge
README BADGES
|
push
github
Handle table unsinking in the presence of IRFL_TAB_NOMM. Reported by Sergey Kaplun. (cherry-picked from commit 0ef51b495) Table `NEWREF` storage for non-constant keys also emits `FREF` IR with `IRFL_TAB_NOMM` to invalidate the metamethod cache. When table creation and `NEWREF` are sinked, the corresponding `FSTORE` is sinked too and should be restored on trace exit. However, `snap_unsink()` doesn't expect anything except `IRFL_TAB_META` as the second operand of `FREF`, so the corresponding assertion fails. This patch adds a switch-case statement to handle the `IRFL_TAB_NOMM` case. Since `FREF` with `IRFL_TAB_NOMM` always follows some hash store, we can avoid a duplication of the cache invalidation, so this case just does nothing. Sergey Kaplun: * added the description and the test for the problem Part of tarantool/tarantool#8825 Reviewed-by: Maxim Kokryashkin <m.kokryashkin@tarantool.org> Reviewed-by: Sergey Bronnikov <sergeyb@tarantool.org> Signed-off-by: Igor Munkin <imun@tarantool.org> (cherry picked from commit e56c6d400)
5300 of 5952 branches covered (0.0%)
Branch coverage included in aggregate %.
20334 of 23201 relevant lines covered (87.64%)
676053.34 hits per line
| Lines | Coverage | ∆ | File |
|---|---|---|---|
| 1 |
92.76 |
-0.33% | src/lj_ir.c |
| 1 |
99.04 |
1.44% | src/lj_str.c |
| 2 |
75.77 |
-0.16% | src/lj_opt_fold.c |
| 6 |
82.22 |
-2.67% | src/lj_sysprof.c |
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 6312339812.1 | 89 |
87.93 |
GitHub Action Run |
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line | Branch Hits | Branch Misses |
|---|