From: Igor Munkin via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Sergey Kaplun <skaplun@tarantool.org>,
Sergey Bronnikov <sergeyb@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH luajit 0/3] Integration testing and tiny fixes in CI
Date: Wed, 13 Jul 2022 13:09:21 +0300 [thread overview]
Message-ID: <Ys6Z0Wx0WU/+4qaV@tarantool.org> (raw)
In-Reply-To: <cover.1655911291.git.imun@tarantool.org>
I've checked the patchset into all long-term branches in
tarantool/luajit and bumped a new version in master, 2.10 and 1.10.
On 22.06.22, Igor Munkin wrote:
> After reusable workflow is merged into tarantool/tarantool master
> branch[1], we can proceed with LuaJIT integration testing patchset. The
> changeset contains a couple of CI-related fixes and introduces Tarantool
> integration testing in LuaJIT repository. You can find more verbose
> descriptions in the corresponding commit messages.
>
> Branch: https://github.com/tarantool/luajit/tree/imun/ci-tarantool-tests
> CI: https://github.com/tarantool/luajit/commit/0b72879
>
> [1]: https://github.com/tarantool/tarantool/pull/7276
>
> Igor Munkin (3):
> ci: fix --parallel argument for MacOS runners
> ci: remove GC64 matrix entries for ARM64 workflows
> ci: add Tarantool integration testing
>
> .github/workflows/linux-aarch64.yml | 28 ++++++++++++++---
> .github/workflows/linux-x86_64.yml | 43 ++++++++++++++++++++++++--
> .github/workflows/macos-m1.yml | 32 +++++++++++++++-----
> .github/workflows/macos-x86_64.yml | 47 ++++++++++++++++++++++++++---
> 4 files changed, 130 insertions(+), 20 deletions(-)
>
> --
> 2.34.0
>
--
Best regards,
IM
prev parent reply other threads:[~2022-07-13 10:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 15:33 Igor Munkin via Tarantool-patches
2022-06-22 15:33 ` [Tarantool-patches] [PATCH luajit 1/3] ci: fix --parallel argument for MacOS runners Igor Munkin via Tarantool-patches
2022-06-23 8:19 ` Sergey Kaplun via Tarantool-patches
2022-06-29 22:17 ` Igor Munkin via Tarantool-patches
2022-07-01 13:12 ` Sergey Bronnikov via Tarantool-patches
2022-07-04 7:05 ` Igor Munkin via Tarantool-patches
2022-07-05 17:20 ` Sergey Bronnikov via Tarantool-patches
2022-07-05 21:25 ` Igor Munkin via Tarantool-patches
2022-06-22 15:33 ` [Tarantool-patches] [PATCH luajit 2/3] ci: remove GC64 matrix entries for ARM64 workflows Igor Munkin via Tarantool-patches
2022-06-23 8:29 ` Sergey Kaplun via Tarantool-patches
2022-06-29 22:17 ` Igor Munkin via Tarantool-patches
2022-07-01 13:21 ` Sergey Bronnikov via Tarantool-patches
2022-07-04 7:05 ` Igor Munkin via Tarantool-patches
2022-06-22 15:33 ` [Tarantool-patches] [PATCH luajit 3/3] ci: add Tarantool integration testing Igor Munkin via Tarantool-patches
2022-06-23 8:45 ` Sergey Kaplun via Tarantool-patches
2022-06-29 22:17 ` Igor Munkin via Tarantool-patches
2022-07-04 10:24 ` Sergey Kaplun via Tarantool-patches
2022-07-01 13:39 ` Sergey Bronnikov via Tarantool-patches
2022-07-04 7:07 ` Igor Munkin via Tarantool-patches
2022-07-04 10:09 ` Sergey Bronnikov via Tarantool-patches
2022-07-13 10:09 ` 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=Ys6Z0Wx0WU/+4qaV@tarantool.org \
--to=tarantool-patches@dev.tarantool.org \
--cc=imun@tarantool.org \
--cc=sergeyb@tarantool.org \
--cc=skaplun@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH luajit 0/3] Integration testing and tiny fixes in CI' \
/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