Ran
|
Jobs
1
|
Files
89
|
Run time
19s
|
Badge
README BADGES
|
push
github
test: adjust lua-Harness test error assertion The current pattern in 303-package.t for the test case loading invalid Lua script is too tight for the following reasons revealed by Tarantool testing: * The platform might prepend the common prefix to all Lua errors, so anchoring the pattern to the beginning of the error message is too strict for matching the particular errors. * The platform might canonicalize module names (i.e., use absolute paths) for searchers and loaders, so matching the current working directory via "./" is too straight-forward. Hence, this patch removes the starting anchor from the pattern and fixes the last part of it to match only the "basename" of the module being loaded. As a result, the check is not too strict and Lua-specific but rather starts following common sense. Reviewed-by: Sergey Kaplun <skaplun@tarantool.org> Signed-off-by: Igor Munkin <imun@tarantool.org> (cherry picked from commit 487eeb0b5)
5349 of 5969 branches covered (0.0%)
Branch coverage included in aggregate %.
20510 of 23267 relevant lines covered (88.15%)
698430.97 hits per line
Lines | Coverage | ∆ | File |
---|---|---|---|
3 |
72.64 |
-0.25% | src/lj_crecord.c |
6 |
76.45 |
-0.47% | src/lj_opt_fold.c |
7 |
94.74 |
-4.78% | src/lj_str.c |
ID | Job ID | Ran | Files | Coverage | |
---|---|---|---|---|---|
1 | 7272782336.1 | 89 |
88.45 |
GitHub Action Run |
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line | Branch Hits | Branch Misses |
---|