Skip to content

lua: support code coverage - #15915

Open
ligurio wants to merge 1 commit into
google:masterfrom
ligurio:ligurio/fix-lua-code-coverage
Open

lua: support code coverage#15915
ligurio wants to merge 1 commit into
google:masterfrom
ligurio:ligurio/fix-lua-code-coverage

Conversation

@ligurio

@ligurio ligurio commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Follows up tarantool/tarantool#11250
Follows up #14656
Closes #14859

@github-actions

Copy link
Copy Markdown

ligurio is either the primary contact or is in the CCs list of projects/tarantool.
ligurio has previously contributed to projects/tarantool. The previous PR was #15831
ligurio is either the primary contact or is in the CCs list of projects/lua-example.
ligurio has previously contributed to projects/lua-example. The previous PR was #15384
ligurio is either the primary contact or is in the CCs list of projects/lua.
ligurio has previously contributed to projects/lua. The previous PR was #15849

@ligurio
ligurio force-pushed the ligurio/fix-lua-code-coverage branch from aa32549 to 1e00c18 Compare July 28, 2026 09:31
@ligurio

ligurio commented Jul 28, 2026

Copy link
Copy Markdown
Contributor Author

@jonathanmetzman could you take a look?

@DavidKorczynski

Copy link
Copy Markdown
Collaborator

/gcbrun trial_build.py htslib json-c lua tarantool --fuzzing-engines libfuzzer --sanitizers coverage

@DavidKorczynski

Copy link
Copy Markdown
Collaborator

the above all runs failed due to production builds failing and thus skipping. It's a bit counter-intuitive because this should at least enable the build for some of them.

@DavidKorczynski

Copy link
Copy Markdown
Collaborator

/gcbrun trial_build.py jq jsoncpp jsoncons lua tarantool --fuzzing-engines libfuzzer --sanitizers coverage

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support C/C++ coverage for Lua tests

2 participants