|
Ran
|
Jobs
1
|
Files
525
|
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)
70714 of 118964 branches covered (59.44%)
106325 of 121279 relevant lines covered (87.67%)
1361694.09 hits per line
| Lines | Coverage | ∆ | File |
|---|---|---|---|
| 6 |
92.51 |
-0.22% | src/box/vinyl.c |
| 4 |
93.31 |
-1.27% | src/lib/swim/swim_io.c |
| 2 |
96.2 |
-0.09% | src/box/iproto.cc |
| 2 |
88.02 |
-0.07% | src/box/vy_run.c |
| 1 |
90.77 |
-0.03% | src/box/box.cc |
| 1 |
99.1 |
-0.3% | src/box/lua/iproto.c |
| 1 |
86.09 |
0.09% | src/box/xlog.c |
| 1 |
92.93 |
-0.1% | src/lib/core/fiber.c |
| 1 |
96.3 |
-3.7% | src/lib/digest/crc32_hw_impl.c |
| 1 |
96.95 |
-0.1% | src/lib/msgpuck/msgpuck.h |
| 1 |
75.85 |
-0.24% | src/main.cc |
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 25099237341.1 | 525 |
87.67 |
GitHub Action Run |
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line | Branch Hits | Branch Misses |
|---|