Repository navigation
ci: shard coverage and upload report to S3 - #504
Merged
Merged
Conversation
p0rtale
force-pushed
the
add-s3-coverage-upload
branch
6 times, most recently
from
July 16, 2026 10:49
370c5d8 to
71b147c
Compare
vakhov
reviewed
Jul 16, 2026
p0rtale
force-pushed
the
add-s3-coverage-upload
branch
from
July 16, 2026 11:27
71b147c to
0fe4a89
Compare
p0rtale
force-pushed
the
add-s3-coverage-upload
branch
2 times, most recently
from
July 16, 2026 13:10
565bd51 to
7ba90c4
Compare
p0rtale
force-pushed
the
add-s3-coverage-upload
branch
3 times, most recently
from
July 29, 2026 08:11
1f0a348 to
57c1b8e
Compare
p0rtale
force-pushed
the
add-s3-coverage-upload
branch
from
September 14, 2026 12:17
57c1b8e to
72429fd
Compare
p0rtale
changed the title
p0rtale
force-pushed
the
add-s3-coverage-upload
branch
from
September 14, 2026 20:36
72429fd to
321e8c7
Compare
vakhov
approved these changes
Sep 15, 2026
p0rtale
force-pushed
the
add-s3-coverage-upload
branch
from
September 21, 2026 08:22
321e8c7 to
1977535
Compare
- Upload the luacov report to S3 on master pushes and tag releases. - Run CE and EE coverage in parallel sharded jobs and merge the per-shard luacov stats in a dedicated job before generating the report. CE runs on Tarantool master, EE on Tarantool Enterprise 3.6. - Make server wait timeouts configurable via LUATEST_SERVER_WAIT_TIMEOUT and set it to 180 in coverage jobs.
- Retry vshard.storage.buckets_info in get_other_storage_bucket_id to avoid next() on a nil result when storage is slow under coverage. - Use LUATEST_SERVER_WAIT_TIMEOUT instead of a hardcoded 60s timeout for bucket wait helpers and the double-buckets rebalancing retries.
p0rtale
force-pushed
the
add-s3-coverage-upload
branch
from
September 22, 2026 18:21
3d0e93c to
f30a7d5
Compare
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
vakhov
self-requested a review
September 23, 2026 09:19
a1div0
approved these changes
Sep 23, 2026
Write a trailing space after the last counter, otherwise luacov skips it and reports the last line as uncovered.
vakhov
approved these changes
Sep 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Coverage reports are now uploaded to S3 on pushes to
masterand tag releases.Since a single coverage job took too long, the coverage run is sharded across 6 parallel jobs: CE coverage on Tarantool master and EE coverage on Tarantool Enterprise 3.6, each split into 3 shards. Each job runs a subset of the test files with luacov and publishes its
luacov.stats*.outas an artifact, then a dedicated job merges them withtest/luacov-merger.luaand uploads the generated report.Also server wait timeouts became configurable via
LUATEST_SERVER_WAIT_TIMEOUT(set to 180 in coverage jobs) to accommodate the slower luacov-instrumented storage.Additionally,
get_other_storage_bucket_idnow retriesvshard.storage.buckets_infountil it responds or the deadline expires, instead of callingnext()on anilresult when the storage times out under coverage.