Tarantool development patches archive
 help / color / mirror / Atom feed
From: Sergey Kaplun via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Sergey Bronnikov <sergeyb@tarantool.org>
Cc: Sergey Bronnikov <estetus@gmail.com>,
	tarantool-patches@dev.tarantool.org, max.kokryashkin@gmail.com
Subject: Re: [Tarantool-patches] [PATCH] cmake: add code coverage support
Date: Tue, 8 Aug 2023 13:47:36 +0300	[thread overview]
Message-ID: <ZNIdSBmg0oN0syIV@root> (raw)
In-Reply-To: <696ac7ac-b93d-84ff-3285-f1a848c6bdde@tarantool.org>

Hi, Sergey!
Thanks for the fixes!
LGTM, except the last minor nit ;).

On 08.08.23, Sergey Bronnikov wrote:
> Hello,

<snipped>

> 
> 
> diff --git a/.github/workflows/coverage.yml b/.github/workflows/coverage.yml
> index 78abf2e1..13ea6c5b 100644
> --- a/.github/workflows/coverage.yml
> +++ b/.github/workflows/coverage.yml
> @@ -50,8 +50,10 @@ jobs:
>         - name: build
>           run: cmake --build . --parallel
>           working-directory: ${{ env.BUILDDIR }}
> -      - name: test and generate code coverage report
> -        run: cmake --build ${{ env.BUILDDIR }} --parallel --target coverage
> +      - name: run regression tests
> +        run: cmake --build ${{ env.BUILDDIR }} --parallel --target test

I suppose it should be LuaJIT-test, since we don't want to run linters
here. See also [1].

> +      - name: generate code coverage report
> +        run: cmake --build ${{ env.BUILDDIR }} --parallel --target LuaJIT-coverage
>         - name: send code coverage to coveralls.io
>           run: |
>             curl -LO https://coveralls.io/coveralls-linux.tar.gz

<snipped>

> >   

[1]: https://github.com/tarantool/luajit/actions/runs/5794532687/job/15704307515#step:7:46

-- 
Best regards,
Sergey Kaplun

  reply	other threads:[~2023-08-08 10:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25 13:52 Sergey Bronnikov via Tarantool-patches
2023-07-26 15:02 ` Sergey Kaplun via Tarantool-patches
2023-07-27  8:42   ` Sergey Bronnikov via Tarantool-patches
2023-07-30 12:55     ` Maxim Kokryashkin via Tarantool-patches
2023-07-30 13:34     ` Maxim Kokryashkin via Tarantool-patches
2023-08-01 15:25       ` Sergey Bronnikov via Tarantool-patches
2023-08-08  8:16 ` Sergey Bronnikov via Tarantool-patches
2023-08-08 10:47   ` Sergey Kaplun via Tarantool-patches [this message]
2023-08-08 19:25     ` Sergey Bronnikov via Tarantool-patches
2023-08-14  7:46       ` Maxim Kokryashkin via Tarantool-patches

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=ZNIdSBmg0oN0syIV@root \
    --to=tarantool-patches@dev.tarantool.org \
    --cc=estetus@gmail.com \
    --cc=max.kokryashkin@gmail.com \
    --cc=sergeyb@tarantool.org \
    --cc=skaplun@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH] cmake: 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