This is an automated email from the ASF dual-hosted git repository.

chaokunyang pushed a commit to branch releases-0.11
in repository https://gitbox.apache.org/repos/asf/fury.git


The following commit(s) were added to refs/heads/releases-0.11 by this push:
     new 6ff12af7 fix(kotlin): merge kotlin ci to 0.11 (#2178)
6ff12af7 is described below

commit 6ff12af70011929ac15d612dd62a4a0ddbf645a9
Author: PAN <[email protected]>
AuthorDate: Thu Apr 24 14:57:12 2025 +0800

    fix(kotlin): merge kotlin ci to 0.11 (#2178)
    
    <!--
    **Thanks for contributing to Fury.**
    
    **If this is your first time opening a PR on fury, you can refer to
    
[CONTRIBUTING.md](https://github.com/apache/fury/blob/main/CONTRIBUTING.md).**
    
    Contribution Checklist
    
    - The **Apache Fury (incubating)** community has restrictions on the
    naming of pr titles. You can also find instructions in
    [CONTRIBUTING.md](https://github.com/apache/fury/blob/main/CONTRIBUTING.md).
    
    - Fury has a strong focus on performance. If the PR you submit will have
    an impact on performance, please benchmark it first and provide the
    benchmark result here.
    -->
    
    ## What does this PR do?
    
    <!-- Describe the purpose of this PR. -->
    
    ## Related issues
    
    <!--
    Is there any related issue? Please attach here.
    
    - #xxxx0
    - #xxxx1
    - #xxxx2
    -->
    
    ## Does this PR introduce any user-facing change?
    
    <!--
    If any user-facing interface changes, please [open an
    issue](https://github.com/apache/fury/issues/new/choose) describing the
    need to do so and update the document if necessary.
    -->
    
    - [ ] Does this PR introduce any public API change?
    - [ ] Does this PR introduce any binary protocol compatibility change?
    
    ## Benchmark
    
    <!--
    When the PR has an impact on performance (if you don't know whether the
    PR will have an impact on performance, you can submit the PR first, and
    if it will have impact on performance, the code reviewer will explain
    it), be sure to attach a benchmark data here.
    -->
    
    ---------
    
    Co-authored-by: Shawn Yang <[email protected]>
---
 .github/workflows/ci.yml | 20 ++++++++++++++++++++
 ci/run_ci.sh             | 15 +++++++++++++++
 2 files changed, 35 insertions(+)

diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index c1238531..b1819f29 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -136,6 +136,26 @@ jobs:
         shell: bash
         run: ./ci/run_ci.sh graalvm_test
 
+  kotlin:
+    name: Kotlin CI
+    runs-on: ubuntu-latest
+    env:
+      MY_VAR: "PATH"
+    strategy:
+      matrix:
+        java-version: ["8"]
+    steps:
+      - uses: actions/checkout@v4
+      - name: Set up JDK ${{ matrix.java-version }}
+        uses: actions/setup-java@v4
+        with:
+          java-version: ${{ matrix.java-version }}
+          distribution: "temurin"
+      - name: Install fury java
+        run: cd java && mvn -T10 --no-transfer-progress clean install 
-DskipTests && cd -
+      - name: Run Kotlin CI
+        run: ./ci/run_ci.sh kotlin
+
   scala:
     name: Scala CI
     runs-on: ubuntu-latest
diff --git a/ci/run_ci.sh b/ci/run_ci.sh
index 9a4b7bea..936a1feb 100755
--- a/ci/run_ci.sh
+++ b/ci/run_ci.sh
@@ -162,6 +162,18 @@ jdk17_plus_tests() {
   echo "Executing latest_jdk_tests succeeds"
 }
 
+kotlin_tests() {
+  echo "Executing fury kotlin tests"
+  cd "$ROOT/kotlin"
+  set +e
+  mvn -T16 --batch-mode --no-transfer-progress test -DfailIfNoTests=false
+  testcode=$?
+  if [[ $testcode -ne 0 ]]; then
+    exit $testcode
+  fi
+  echo "Executing fury kotlin tests succeeds"
+}
+
 windows_java21_test() {
   java -version
   echo "Executing fury java tests"
@@ -205,6 +217,9 @@ case $1 in
     java21)
       jdk17_plus_tests
     ;;
+    kotlin)
+      kotlin_tests
+    ;;
     windows_java21)
       windows_java21_test
     ;;


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to