From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from [87.239.111.99] (localhost [127.0.0.1]) by dev.tarantool.org (Postfix) with ESMTP id 6F0EFBE02FB; Sat, 9 Mar 2024 17:41:47 +0300 (MSK) DKIM-Filter: OpenDKIM Filter v2.11.0 dev.tarantool.org 6F0EFBE02FB DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tarantool.org; s=dev; t=1709995307; bh=M7v4+UDgeYknDCH86qoCILrwiwUmD0Q5PQyoUI5a4N0=; h=To:Date:Subject:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:From:Reply-To:From; b=xzs7lunfIiM761Po4wexNFlRtKQkhYvRmr29E81MhGWEeZE8xmnXn0Ix0E36wjtGm GnfiPdJzXJFrZ3wu9A5kO+Q3qYJdx/cfPhpR0BsZPFNx6BUdqyFZHHPoTZJCigAjoH +W8id1H2ruz3SsyqJWm/h+VOZklNX48wSnRVtNmY= Received: from mail-lf1-f53.google.com (mail-lf1-f53.google.com [209.85.167.53]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id 55B4DBE02F5 for ; Sat, 9 Mar 2024 17:41:45 +0300 (MSK) DKIM-Filter: OpenDKIM Filter v2.11.0 dev.tarantool.org 55B4DBE02F5 Received: by mail-lf1-f53.google.com with SMTP id 2adb3069b0e04-5133bd7eb47so3606135e87.3 for ; Sat, 09 Mar 2024 06:41:45 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709995304; x=1710600104; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=eZsDnbMgZiIexEbDov1YFlkF5jCm//MrF7yOmykH6og=; b=v4FQrY6yuEL3zpHOeM77EnOWrb2s/w0ddcVbjA9k1TXTilMiCI85XUGzMq+pDKJ18n 5G5VhMbDHdNydYWMdT6hCskL71ltnEHoIXHnNgb4EZOgkoPJpxrbrH2SlxAaR1Wx+sdN fXsSxB1yOIaXPyT7pVVuJVfjeODfqDdl0pBN+wL2PHtO2v6rpgjMOF5cRggQIx4Iuf+F +nFxRLFHahf8hzHTD4e5IdboOvFyfGJWDo+T9S81IF2GzV3MFpHkEsinn8kE5JOGwBG3 UlqglwxoulIF10pSTI1B2r7oVczM4mfD5mo0W5tKje3/RCpnfAgCyoF1ItoyiLVb2LD7 nX2Q== X-Gm-Message-State: AOJu0YzxQkEP6OAsR/KFALHkeAYTF+Q0ruZwdxtKrRQsKMjDrv0IIBj3 NferQ/ecu1FqpqH7zGgfHQTrvUbCeqkFk3tpwwaANDFUgLJFEL6ZMK195W57LO0= X-Google-Smtp-Source: AGHT+IEU9d72eCRgtyt/0Egm6SZgFWBFzvEgoLCLnY+mdG1HHmB4foP59BeiO7c5jNhoOG9ssXSZag== X-Received: by 2002:a05:6512:360a:b0:513:588a:2612 with SMTP id f10-20020a056512360a00b00513588a2612mr981810lfs.28.1709995303948; Sat, 09 Mar 2024 06:41:43 -0800 (PST) Received: from localhost.localdomain (95-24-11-149.broadband.corbina.ru. [95.24.11.149]) by smtp.gmail.com with ESMTPSA id b4-20020a056512024400b00513026abb06sm339318lfo.88.2024.03.09.06.41.43 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 09 Mar 2024 06:41:43 -0800 (PST) X-Google-Original-From: Maxim Kokryashkin To: tarantool-patches@dev.tarantool.org, skaplun@tarantool.org, sergeyb@tarantool.org Date: Sat, 9 Mar 2024 17:41:40 +0300 Message-ID: <20240309144140.78635-1-m.kokryashkin@tarantool.org> X-Mailer: git-send-email 2.43.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [Tarantool-patches] [PATCH luajit v4] ci: extend tarantool integration testing X-BeenThere: tarantool-patches@dev.tarantool.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Maxim Kokryashkin via Tarantool-patches Reply-To: Maxim Kokryashkin Errors-To: tarantool-patches-bounces@dev.tarantool.org Sender: "Tarantool-patches" This patch makes use of reusable workflows from the Tarantool repository, so now LuaJIT CI tests integration in all relevant workflows. Also, this patch disables MacOS testing for Tarantool integration since those runs were made nightly in the Tarantool repo. As noted in the documentation [1], it is impossible for a single workflow call tree to include more than 20 workflows. To overcome this limitation, workflows are started in a bunch of separate files. This makes it impossible to depend on LuaJIT-only jobs for integration workflows such as `tarantool-ecosystem.yml` or `tarantool-exotic.yml` since it is impossible to make cross-dependencies between workflow files. The name of a callee workflow cannot be substituted using a matrix [2], so workflow calls are copied and pasted instead. Table below shows which workflows are enabled and why. Workflow name |+/-| Reason ----------------------------------------------------------------- codeql | - | Not relevant to LuaJIT. coverage | + | Long tests for profilers. coverity | - | Cron workflow. debug | + | Tarantool debug build. debug_aarch64 | + | Tarantool debug build. debug_asan_clang | + | Tarantool debug build. default_gcc_centos_7 | + | Old gcc version (7). freebsd | - | Nightly build. fuzzing | - | Impossible to bump LuaJIT. integration | + | Tarantool ecosystem. jepsen-cluster-txm | - | Manual workflow. jepsen-cluster | - | Manual workflow. jepsen-single-instance-txm | - | Cron workflow. jepsen-single-instance | - | Cron workflow. lango-stale-reviews | - | Cron workflow. lint | - | LuaJIT has its own lint. luajit-integration | + | Run tests under Tarantool. memtx_allocator_based_on_malloc | - | Not relevant to LuaJIT. osx | - | Nightly build. out_of_source | + | Out of source build. packaging | - | No LuaJIT-relevant variety. perf_cbench | - | Not enabled for PRs. perf_linkbench_ssd | - | Not enabled for PRs. perf_micro | - | Not relevant to LuaJIT. perf_nosqlbench_hash | - | Not enabled for PRs. perf_nosqlbench_tree | - | Not enabled for PRs. perf_sysbench | - | Not enabled for PRs. perf_tpcc | - | Not enabled for PRs. perf_tpch | - | Not enabled for PRs. perf_ycsb_hash | - | Not enabled for PRs. perf_ycsb_tree | - | Not enabled for PRs. publish-module-api-doc | - | No Doxygen in LuaJIT. release | + | Tarantool release build. release_asan_clang | + | Tarantool release build. release_clang | + | Tarantool release build. release_lto | + | Tarantool release build. release_lto_clang | + | Tarantool release build. reusable_build | - | Utility for integration. source | - | Not enabled for PRs. static_build | + | Tarantool static build. static_build_cmake_linux | - | Just an OOS static build. static_build_pack_test_deploy | - | Utility for packaging. submodule_update | - | Not enabled for PRs. [1]: https://docs.github.com/en/actions/using-workflows/reusing-workflows#limitations [2]: https://github.com/orgs/community/discussions/45342#discussioncomment-4779360 --- Changes in v4: - Fixed comments as per review by Sergey Kaplun - Integration jobs are now separate from the LuaJIT testing. - Yaroslav introduced etcd client testing, but he did not account for our integration CI, so secrets are broken for it. I'll ask him to resolve the issue. .../integration-tarantool-ecosystem.yml | 40 ++++++ .github/workflows/integration-tarantool.yml | 118 ++++++++++++++++++ .github/workflows/testing.yml | 9 ++ 3 files changed, 167 insertions(+) create mode 100644 .github/workflows/integration-tarantool-ecosystem.yml create mode 100644 .github/workflows/integration-tarantool.yml diff --git a/.github/workflows/integration-tarantool-ecosystem.yml b/.github/workflows/integration-tarantool-ecosystem.yml new file mode 100644 index 00000000..b93e0c78 --- /dev/null +++ b/.github/workflows/integration-tarantool-ecosystem.yml @@ -0,0 +1,40 @@ +# XXX: A single call tree for reusable workflows can't exceed the +# total of 20 workflows, as stated in the documentation [1]. +# This workflow file was created to avoid this limitation. +# +# [1]: https://docs.github.com/en/actions/using-workflows/reusing-workflows#limitations +name: 'Integration / Tarantool ecosystem' + +on: + push: + branches-ignore: + - '**-notest' + - '**-nointegration' + - '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: + test-tarantool-integration: + uses: tarantool/tarantool/.github/workflows/integration.yml@master + with: + submodule: luajit + revision: ${{ github.sha }} diff --git a/.github/workflows/integration-tarantool.yml b/.github/workflows/integration-tarantool.yml new file mode 100644 index 00000000..cf5c7fb5 --- /dev/null +++ b/.github/workflows/integration-tarantool.yml @@ -0,0 +1,118 @@ +# XXX: A single call tree for reusable workflows can't exceed the +# total of 20 workflows, as stated in the documentation [1]. +# This workflow file was created to avoid this limitation. +# +# [1]: https://docs.github.com/en/actions/using-workflows/reusing-workflows#limitations +name: 'Integration / Tarantool' + +on: + push: + branches-ignore: + - '**-notest' + - '**-nointegration' + - '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: + test-tarantool-coverage: + name: coverage + uses: tarantool/tarantool/.github/workflows/coverage.yml@master + with: + submodule: luajit + revision: ${{ github.sha }} + + test-tarantool-debug: + name: debug + uses: tarantool/tarantool/.github/workflows/debug.yml@master + with: + submodule: luajit + revision: ${{ github.sha }} + + test-tarantool-debug_aarch64: + name: debug aarch64 + uses: tarantool/tarantool/.github/workflows/debug_aarch64.yml@master + with: + submodule: luajit + revision: ${{ github.sha }} + + test-tarantool-debug_asan_clang: + name: debug ASAN clang + uses: tarantool/tarantool/.github/workflows/debug_asan_clang.yml@master + with: + submodule: luajit + revision: ${{ github.sha }} + + test-tarantool-default_gcc_centos_7: + name: gcc centos 7 + uses: tarantool/tarantool/.github/workflows/default_gcc_centos_7.yml@master + with: + submodule: luajit + revision: ${{ github.sha }} + + test-tarantool-out_of_source: + name: out of source + uses: tarantool/tarantool/.github/workflows/out_of_source.yml@master + with: + submodule: luajit + revision: ${{ github.sha }} + + test-tarantool-release: + name: release + uses: tarantool/tarantool/.github/workflows/release.yml@master + with: + submodule: luajit + revision: ${{ github.sha }} + + test-tarantool-release_asan_clang: + name: release ASAN clang + uses: tarantool/tarantool/.github/workflows/release_asan_clang.yml@master + with: + submodule: luajit + revision: ${{ github.sha }} + + test-tarantool-release_clang: + name: release clang + uses: tarantool/tarantool/.github/workflows/release_clang.yml@master + with: + submodule: luajit + revision: ${{ github.sha }} + + test-tarantool-release_lto: + name: release lto + uses: tarantool/tarantool/.github/workflows/release_lto.yml@master + with: + submodule: luajit + revision: ${{ github.sha }} + + test-tarantool-release_lto_clang: + name: release lto clang + uses: tarantool/tarantool/.github/workflows/release_lto_clang.yml@master + with: + submodule: luajit + revision: ${{ github.sha }} + + test-tarantool-static_build: + name: static build + uses: tarantool/tarantool/.github/workflows/static_build.yml@master + with: + submodule: luajit + revision: ${{ github.sha }} diff --git a/.github/workflows/testing.yml b/.github/workflows/testing.yml index cb4ba57b..1581c8fc 100644 --- a/.github/workflows/testing.yml +++ b/.github/workflows/testing.yml @@ -1,3 +1,11 @@ +# XXX: A single call tree for reusable workflows can't exceed the +# total of 20 workflows, as stated in the documentation [1]. +# Some other jobs are started in separate workflow files to +# overcome the limitation. The jobs are Tarantool ecosystem +# integration testing (tarantool-ecosystem.yml) and exotic +# Tarantool builds (tarantool-exotic.yml). +# +# [1]: https://docs.github.com/en/actions/using-workflows/reusing-workflows#limitations name: Testing on: @@ -108,6 +116,7 @@ jobs: ${{ matrix.BUILDTYPE }} GC64:${{ matrix.GC64 }} needs: test-luajit + # XXX: Only LuaJIT-tests are running in this workflow. uses: tarantool/tarantool/.github/workflows/luajit-integration.yml@master with: CMAKE_EXTRA_PARAMS: > -- 2.43.2