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

HyukjinKwon pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/spark-connect-rust.git


The following commit(s) were added to refs/heads/master by this push:
     new e0fcefbb [SPARK-61224][CONNECT][INFRA][TESTS] Run the live tests of 
array_literal, execute_plan_hook, raw_relation and types_roundtrip against the 
server in CI
e0fcefbb is described below

commit e0fcefbb0989003f50cf93c828c3840ed50080cf
Author: Hyukjin Kwon <[email protected]>
AuthorDate: Mon Nov 9 17:07:14 2026 +0900

    [SPARK-61224][CONNECT][INFRA][TESTS] Run the live tests of array_literal, 
execute_plan_hook, raw_relation and types_roundtrip against the server in CI
    
    ### What changes were proposed in this pull request?
    
    [SPARK-61224](https://issues.apache.org/jira/browse/SPARK-61224): Run the 
server tests of `array_literal.rs`, `execute_plan_hook.rs`, `raw_relation.rs` 
and `types_roundtrip.rs` against the live server in CI.
    
    These files of `crates/spark-connect/tests` run their server tests only 
when `SPARK_REMOTE` is set. The step "Rust behavioral e2e tests (against the 
live server)" of `build_python_connect.yml` runs only the test files it names, 
the coverage job's live pass names other files, and the plain `cargo test` 
steps run without a server. This adds the four files to the live step, as 
`arrow_map_input` was added in SPARK-61212.
    
    - `array_literal.rs`: the element type of array literals of the Rust core 
(SPARK-61119).
    - `execute_plan_hook.rs`: the hooks called before each execution 
(SPARK-61117).
    - `raw_relation.rs`: relations and commands of messages built outside the 
client (SPARK-61111).
    - `types_roundtrip.rs`: the round trip of DDL comments with backslashes and 
quotes (SPARK-61206).
    
    ### Why are the changes needed?
    
    Their server tests never ran in CI, so a regression of these paths against 
a real server would not fail CI.
    
    ### Does this PR introduce _any_ user-facing change?
    
    No, CI only.
    
    ### How was this patch tested?
    
    These four files passed against a local Spark 4.3.0 Connect server in the 
full Rust suite of the trial merge of the current master (790 passed, 0 
failed). CI of this PR runs them in its live step.
    
    ### Was this patch authored or co-authored using generative AI tooling?
    
    Generated-by: Claude Opus 5.5
    
    This pull request and its description were written by Isaac.
    
    Closes #401 from HyukjinKwon/SPARK-61224-ci-live-tests.
    
    Authored-by: Hyukjin Kwon <[email protected]>
    Signed-off-by: Hyukjin Kwon <[email protected]>
---
 .github/workflows/build_python_connect.yml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/.github/workflows/build_python_connect.yml 
b/.github/workflows/build_python_connect.yml
index e6f8815b..9c3930f2 100644
--- a/.github/workflows/build_python_connect.yml
+++ b/.github/workflows/build_python_connect.yml
@@ -392,7 +392,8 @@ jobs:
           cargo test -p apache-spark-connect \
             --test e2e_functions --test e2e_columns --test e2e_dataframe \
             --test e2e_coverage --test e2e_linear_svc --test 
e2e_linear_regression --test e2e_integration \
-            --test arrow_map_input \
+            --test arrow_map_input --test array_literal --test 
execute_plan_hook --test raw_relation \
+            --test types_roundtrip \
             -- --test-threads=1
 
       - name: Rust WASM UDF e2e test (against the live server)


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

Reply via email to