Ran
|
Jobs
1
|
Files
89
|
Run time
14s
|
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
5339 of 5972 branches covered (0.0%)
Branch coverage included in aggregate %.
20483 of 23293 relevant lines covered (87.94%)
2736173.25 hits per line
Lines | Coverage | ∆ | File |
---|---|---|---|
1 |
95.91 |
-0.18% | src/lj_opt_mem.c |
2 |
95.59 |
-0.11% | src/lj_record.c |
3 |
97.61 |
-1.44% | src/lj_str.c |
ID | Job ID | Ran | Files | Coverage | |
---|---|---|---|---|---|
1 | 6303180813.1 | 89 |
88.24 |
GitHub Action Run |
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line | Branch Hits | Branch Misses |
---|