From: Maxim Kokryashkin 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 2/2 v2] ci: support coveralls
Date: Wed, 2 Aug 2023 11:18:07 +0300 [thread overview]
Message-ID: <trbesdgl3ad5y4iyu4jnalvngp62e3p3i6t36urufvirhbymc2@gpjys54hltis> (raw)
In-Reply-To: <6535409abb0242a342285f683db945f54b01e5d2.1690915289.git.sergeyb@tarantool.org>
Hi, Sergey!
Thanks for the patch!
LGTM, except for a few nits regarding the commit message.
Best regards,
Maxim Kokryashkin
On Tue, Aug 01, 2023 at 09:46:10PM +0300, Sergey Bronnikov via Tarantool-patches wrote:
> From: Sergey Bronnikov <sergeyb@tarantool.org>
>
> The patch adds a workflow that runs regression test suites, produces a
> summary about current code coverage and send code coverage data to
Typo: s/about/of/
Typo: s/send code/sends code/
> Coveralls. Coveralls is a web-service that lets you inspect every detail
Typo: s/web-service/web service/
> of your coverage. See Tarantool's LuaJIT page on Coveralls [1].
>
> 1. https://coveralls.io/github/tarantool/luajit
> ---
> .github/actions/setup-linux/action.yml | 1 +
> .github/workflows/coverage.yml | 60 ++++++++++++++++++++++++++
> 2 files changed, 61 insertions(+)
> create mode 100644 .github/workflows/coverage.yml
>
> diff --git a/.github/actions/setup-linux/action.yml b/.github/actions/setup-linux/action.yml
> index f0171b83..71619a60 100644
> --- a/.github/actions/setup-linux/action.yml
> +++ b/.github/actions/setup-linux/action.yml
> @@ -16,4 +16,5 @@ runs:
> run: |
> apt -y update
> apt -y install cmake gcc make ninja-build perl
> + pip3 install gcovr
> shell: bash
> diff --git a/.github/workflows/coverage.yml b/.github/workflows/coverage.yml
> new file mode 100644
> index 00000000..9fff06c7
> --- /dev/null
> +++ b/.github/workflows/coverage.yml
> @@ -0,0 +1,60 @@
> +name: Code coverage
> +
> +on:
> + push:
> + branches-ignore:
> + - '**-notest'
> + - 'upstream-**'
> + tags-ignore:
> + - '**'
> +
> +concurrency:
> + # An update of a developer branch cancels the previously
> + # scheduled workflow run for this branch. However, the default
> + # branch, and long-term branch (tarantool/release/2.11,
> + # tarantool/release/2.10, etc) workflow runs are never canceled.
> + #
> + # We use a trick here: define the concurrency group as 'workflow
> + # run ID' + # 'workflow run attempt' because it is a unique
> + # combination for any run. So it effectively discards grouping.
> + #
> + # XXX: we cannot use `github.sha` as a unique identifier because
> + # pushing a tag may cancel a run that works on a branch push
> + # event.
> + group: ${{ startsWith(github.ref, 'refs/heads/tarantool/')
> + && format('{0}-{1}', github.run_id, github.run_attempt)
> + || format('{0}-{1}', github.workflow, github.ref) }}
> + cancel-in-progress: true
> +
> +jobs:
> + coverage:
> + strategy:
> + fail-fast: false
> + runs-on: [self-hosted, regular, x86_64, Linux]
> + steps:
> + - uses: actions/checkout@v3
> + with:
> + fetch-depth: 0
> + submodules: recursive
> + - name: setup Linux
> + uses: ./.github/actions/setup-linux
> + - name: configure
> + run: >
> + cmake -S . -B ${{ env.BUILDDIR }}
> + -G Ninja
> + -DCMAKE_BUILD_TYPE=RelWithDebInfo
> + -DLUAJIT_ENABLE_COVERAGE=ON
> + -DLUAJIT_ENABLE_GC64=ON
> + - 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: send code coverage to coveralls.io
> + run: |
> + curl -LO https://coveralls.io/coveralls-linux.tar.gz
> + tar xvzf coveralls-linux.tar.gz
> + ./coveralls -f ./coverage/luajit.xml
> + working-directory: ${{ env.BUILDDIR }}
> + env:
> + COVERALLS_REPO_TOKEN: ${{ secrets.GITHUB_TOKEN }}
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-08-02 8:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 18:46 [Tarantool-patches] [PATCH 0/2 v2] Add code coverage support 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 [this message]
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 ` [Tarantool-patches] [PATCH 0/2 v2] Add code coverage support Igor Munkin 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=trbesdgl3ad5y4iyu4jnalvngp62e3p3i6t36urufvirhbymc2@gpjys54hltis \
--to=tarantool-patches@dev.tarantool.org \
--cc=estetus@gmail.com \
--cc=m.kokryashkin@tarantool.org \
--cc=max.kokryashkin@gmail.com \
--subject='Re: [Tarantool-patches] [PATCH 2/2 v2] ci: support coveralls' \
/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