|
Ran
|
Jobs
1
|
Files
310
|
Run time
34s
|
Badge
README BADGES
|
push
travis-ci
<a href="https://github.com/tarantool/tarantool/commit/<a class=hub.com/tarantool/tarantool/commit/074b73fb1505501dd6eb86e6ac6079bc45cdc697">074b73fb1<a href="https://github.com/tarantool/tarantool/commit/074b73fb1505501dd6eb86e6ac6079bc45cdc697">">test: update test-run Store *.reject files in ${BUILD}/test/var/rejects/&lt;...&gt;/ instead of ${SOURCE}/test/&lt;...&gt;/. The past approach leads to problems with testing, when the out of source build is used and sources are on a read-only filesystem. The main problem is when a test fails, but it is marked as fragile and should be run again. The test fail assumes storing of the .reject file and the testing fails on attempt to write to the read-only filesystem. The re-run is not performed so. Side effect for the in-source build: since the test/var/ directory is gitignored, the *.reject files will not shown in `git status` output anymore. https://github.com/tarantool/test-run/pull/209 Follows up #4874 (cherry picked from commit </a><a class="double-link" href="https://github.com/tarantool/tarantool/commit/<a class="double-link" href="https://github.com/tarantool/tarantool/commit/8a0d45f278ede5c3c6f0a12c3ab4056bfa6befba">8a0d45f27</a>">8a0d45f27</a><a href="https://github.com/tarantool/tarantool/commit/074b73fb1505501dd6eb86e6ac6079bc45cdc697">)
42759 of 51624 relevant lines covered (82.83%)
954567.86 hits per line
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 3 | 25319.3 (TARGET=coverage) | 0 |
82.83 |
Travis Job 25319.3 |