There is no need to run linter checks (such as luacheck) in scope of the
testing workflows, since there is a separate one for this. Hence, only
<LuaJIT-test> target should be used in these workflows.
Signed-off-by: Igor Munkin <
imun@tarantool.org>
---
.github/workflows/exotic-builds-testing.yml | 2 +-
.github/workflows/testing.yml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/.github/workflows/exotic-builds-testing.yml b/.github/workflows/exotic-builds-testing.yml
index 67ab9cc3..62b83931 100644
--- a/.github/workflows/exotic-builds-testing.yml
+++ b/.github/workflows/exotic-builds-testing.yml
@@ -74,5 +74,5 @@ jobs:
run: cmake --build . --parallel
working-directory: ${{ env.BUILDDIR }}
- name: test
- run: cmake --build . --parallel --target test
+ run: cmake --build . --parallel --target LuaJIT-test
working-directory: ${{ env.BUILDDIR }}
diff --git a/.github/workflows/testing.yml b/.github/workflows/testing.yml
index b7a6cfe2..8300c443 100644
--- a/.github/workflows/testing.yml
+++ b/.github/workflows/testing.yml
@@ -74,7 +74,7 @@ jobs:
run: cmake --build . --parallel
working-directory: ${{ env.BUILDDIR }}
- name: test
- run: cmake --build . --parallel --target test
+ run: cmake --build . --parallel --target LuaJIT-test
working-directory: ${{ env.BUILDDIR }}
--
2.30.2