|
Ran
|
Jobs
1
|
Files
89
|
Run time
4s
|
Badge
README BADGES
|
push
github
test: fix fix-mips64-spare-side-exit-patching This test may be flaky due to a sparse filling of the vector with traces. Hence, `misc.getmetrics().jit_trace_num` (which is the total number of traces) is not the last trace number, so there is no mcode for it. This patch fixes flakyness from two sides: * The `fillmcode()` function now starts a search from the given trace itself, so there is no possible inconsistency with the growing vector. * The finding of the last trace number in the aforementioned test is now more bulletproof: we scan all numbers from the metrics value to the maxtrace value. The last number with an existing mcode is chosen as the resulting last trace number. Reviewed-by: Maxim Kokryashkin <m.kokryashkin@tarantool.org> Reviewed-by: Igor Munkin <imun@tarantool.org> Signed-off-by: Igor Munkin <imun@tarantool.org> (cherry picked from commit 7d5901dda)
5300 of 5952 branches covered (0.0%)
Branch coverage included in aggregate %.
20342 of 23201 relevant lines covered (87.68%)
692941.49 hits per line
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 6317466575.1 | 89 |
87.96 |
GitHub Action Run |
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line | Branch Hits | Branch Misses |
|---|