|
Ran
|
Jobs
1
|
Files
520
|
Run time
2min
|
Badge
README BADGES
|
push
github
test: fix the signal sender PID logging test It used to start Tarantool after sending a signal. It might so happen that the previous instance haven't finished when the new instance is started, which will lead to the locked WAL dir error. Let's fix that. Follows-up #12477 NO_DOC=test NO_CHANGELOG=test (cherry picked from commit 1603435a5)
68826 of 116355 branches covered (59.15%)
103567 of 118234 relevant lines covered (87.59%)
1645518.79 hits per line
| Lines | Coverage | ∆ | File |
|---|---|---|---|
| 16 |
90.74 |
-0.52% | src/box/box.cc |
| 8 |
92.43 |
-0.32% | src/box/vinyl.c |
| 6 |
97.05 |
-0.61% | src/lib/msgpuck/msgpuck.h |
| 4 |
93.31 |
-1.27% | src/lib/swim/swim_io.c |
| 2 |
94.22 |
-0.3% | src/box/memtx_space.c |
| 2 |
89.72 |
-0.1% | src/box/xrow.c |
| 2 |
85.61 |
-0.72% | src/lib/core/coio.c |
| 2 |
94.22 |
-0.39% | src/lua/fiber.c |
| 1 |
84.35 |
-0.03% | src/box/xlog.c |
| 1 |
96.3 |
-3.7% | src/cpu_feature.c |
| 1 |
90.38 |
-1.77% | src/lib/core/trigger.cc |
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 25099257270.1 | 520 |
87.59 |
GitHub Action Run |
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line | Branch Hits | Branch Misses |
|---|