Tarantool development patches archive
 help / color / mirror / Atom feed
From: Igor Munkin via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Sergey Bronnikov <estetus@gmail.com>
Cc: max.kokryashkin@gmail.com, tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH 0/2 v2] Add code coverage support
Date: Mon, 21 Aug 2023 11:05:46 +0000	[thread overview]
Message-ID: <ZONFCkAsMbA8rofY@tarantool.org> (raw)
In-Reply-To: <cover.1690915289.git.sergeyb@tarantool.org>

Sergey,

I've checked the patchset into all long-term branches in
tarantool/luajit and bumped a new version in master, release/2.11 and
release/2.10.

On 01.08.23, Sergey Bronnikov via Tarantool-patches wrote:
> From: Sergey Bronnikov <sergeyb@tarantool.org>
> 
> Patch-series adds code coverage support to LuaJIT build infrastructure
> and Github Actions.
> 
> Changes v2:
> - addressed comments from Max Kokryashkin and Sergey Kaplun
> - added integration with Coveralls
> 
> Branch: https://github.com/tarantool/luajit/tree/ligurio/code-coverage
> Coveralls: https://coveralls.io/github/tarantool/luajit
> Patch v1: https://lists.tarantool.org/tarantool-patches/58297844-8590-cf70-b3d5-3ed8908aef9a@tarantool.org/T/#t
> 
> Sergey Bronnikov (2):
>   cmake: add code coverage support
>   ci: support coveralls
> 
>  .github/actions/setup-linux/action.yml |  1 +
>  .github/workflows/coverage.yml         | 60 ++++++++++++++++++++++++++
>  CMakeLists.txt                         |  9 ++++
>  cmake/CodeCoverage.cmake               | 45 +++++++++++++++++++
>  test/CMakeLists.txt                    |  7 +++
>  test/tarantool-c-tests/CMakeLists.txt  |  6 ++-
>  6 files changed, 127 insertions(+), 1 deletion(-)
>  create mode 100644 .github/workflows/coverage.yml
>  create mode 100644 cmake/CodeCoverage.cmake
> 
> -- 
> 2.34.1
> 

-- 
Best regards,
IM

      parent reply	other threads:[~2023-08-21 11:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01 18:46 Sergey Bronnikov via Tarantool-patches
2023-08-01 18:46 ` [Tarantool-patches] [PATCH 1/2 v2] cmake: add " Sergey Bronnikov via Tarantool-patches
2023-08-02  8:06   ` Maxim Kokryashkin via Tarantool-patches
2023-08-02  8:18     ` Sergey Bronnikov via Tarantool-patches
2023-08-06 11:35       ` Sergey Kaplun via Tarantool-patches
2023-08-07 13:39         ` Sergey Bronnikov via Tarantool-patches
2023-08-15  8:41           ` Maxim Kokryashkin via Tarantool-patches
2023-08-01 18:46 ` [Tarantool-patches] [PATCH 2/2 v2] ci: support coveralls Sergey Bronnikov via Tarantool-patches
2023-08-02  8:18   ` Maxim Kokryashkin via Tarantool-patches
2023-08-02  8:20     ` Sergey Bronnikov via Tarantool-patches
2023-08-06 11:41     ` Sergey Kaplun via Tarantool-patches
2023-08-07 11:32       ` Sergey Bronnikov via Tarantool-patches
2023-08-21 11:05 ` Igor Munkin via Tarantool-patches [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZONFCkAsMbA8rofY@tarantool.org \
    --to=tarantool-patches@dev.tarantool.org \
    --cc=estetus@gmail.com \
    --cc=imun@tarantool.org \
    --cc=max.kokryashkin@gmail.com \
    --subject='Re: [Tarantool-patches] [PATCH 0/2 v2] Add code coverage support' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox