From: Maxim Kokryashkin via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: "Sergey Bronnikov" <sergeyb@tarantool.org>
Cc: "Sergey Bronnikov" <estetus@gmail.com>,
max.kokryashkin@gmail.com, tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH] cmake: add code coverage support
Date: Mon, 14 Aug 2023 10:46:34 +0300 [thread overview]
Message-ID: <1691999194.276493289@f154.i.mail.ru> (raw)
In-Reply-To: <d2756c2b-3121-5191-a06d-58e74839ad2a@tarantool.org>
[-- Attachment #1: Type: text/plain, Size: 1628 bytes --]
Hi, Sergey!
Thanks for the fixes!
LGTM
--
Best regards,
Maxim Kokryashkin
>
>>Sergey,
>>
>>
>>On 8/8/23 13:47, Sergey Kaplun wrote:
>>
>>
>><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].
>>>
>>> <snipped>
>>
>>Fixed, thanks!
>>
>>
>>--- a/.github/workflows/coverage.yml
>>+++ b/.github/workflows/coverage.yml
>>@@ -51,7 +51,7 @@ jobs:
>> run: cmake --build . --parallel
>> working-directory: ${{ env.BUILDDIR }}
>> - name: run regression tests
>>- run: cmake --build ${{ env.BUILDDIR }} --parallel --target test
>>+ run: cmake --build ${{ env.BUILDDIR }} --parallel --target
>>LuaJIT-test
>> - name: generate code coverage report
>> run: cmake --build ${{ env.BUILDDIR }} --parallel --target
>>LuaJIT-coverage
>> - name: send code coverage to coveralls.io
>
[-- Attachment #2: Type: text/html, Size: 2775 bytes --]
prev parent reply other threads:[~2023-08-14 7:46 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
2023-08-08 19:25 ` Sergey Bronnikov via Tarantool-patches
2023-08-14 7:46 ` Maxim Kokryashkin 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=1691999194.276493289@f154.i.mail.ru \
--to=tarantool-patches@dev.tarantool.org \
--cc=estetus@gmail.com \
--cc=m.kokryashkin@tarantool.org \
--cc=max.kokryashkin@gmail.com \
--cc=sergeyb@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