|
Ran
|
Jobs
1
|
Files
89
|
Run time
5s
|
Badge
README BADGES
|
push
github
Always exit after machine code page protection change fails. Reported by Sergey Kaplun. (cherry picked from commit c50232eb3) Unfortunately, <exit> call had been missing for a long time for the case when <mprotect> fails within <mcode_protect>. Though the patch per se is quite trivial, the test is not at all. It exploits the fact, that <mprotect> is used only for protecting area for mcode or callback function pointers. Hence, if the test doesn't use FFI at all, it is guaranteed that the only <mprotect> called in LuaJIT runtime locates in <mcode_protect> (that is not true for Tarantool, so the test is disabled for integration testing routine). Furthermore, overloading <mprotect> on macOS occurs to be not an easy ride either, so running the test on macOS is disabled, since this is the common part for all platforms and everything can be checked on Linux in a much more easier way. Igor Munkin: * added the description and the test for the problem Part of tarantool/tarantool#8825
5329 of 5969 branches covered (0.0%)
Branch coverage included in aggregate %.
2 of 2 new or added lines in 1 file covered. (100.0%)
20428 of 23287 relevant lines covered (87.72%)
1294965.74 hits per line
| Lines | Coverage | ∆ | File |
|---|---|---|---|
| 1 |
72.22 |
0.08% | src/lj_crecord.c |
| 1 |
95.64 |
-0.05% | src/lj_record.c |
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 6049318845.1 | 89 |
88.04 |
GitHub Action Run |
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line | Branch Hits | Branch Misses |
|---|