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

ruifengz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/spark.git


The following commit(s) were added to refs/heads/master by this push:
     new cb857243662a [SPARK-54051][INFRA][PYTHON] Keep coverage data when 
running pip tests
cb857243662a is described below

commit cb857243662ace88ae440cf0686a663ee4f2760d
Author: Tian Gao <[email protected]>
AuthorDate: Wed Oct 29 08:34:48 2025 +0800

    [SPARK-54051][INFRA][PYTHON] Keep coverage data when running pip tests
    
    ### What changes were proposed in this pull request?
    
    Skip removing `python/coverage.xml` in `run-pip-tests`
    
    ### Why are the changes needed?
    
    `run-pip-tests` will clear existing coverage data from previous tests. For 
example: 
https://github.com/apache/spark/actions/runs/16342241585/job/46167521633 has no 
coverage data uploaded because the file is removed after the test.
    
    ### Does this PR introduce _any_ user-facing change?
    
    No
    
    ### How was this patch tested?
    
    This is a script change, should reflect in github actions.
    
    ### Was this patch authored or co-authored using generative AI tooling?
    
    No
    
    Closes #51552 from gaogaotiantian/keep-coverage-data.
    
    Authored-by: Tian Gao <[email protected]>
    Signed-off-by: Ruifeng Zheng <[email protected]>
---
 dev/run-pip-tests | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/dev/run-pip-tests b/dev/run-pip-tests
index 426ec329d915..233eaed7ff24 100755
--- a/dev/run-pip-tests
+++ b/dev/run-pip-tests
@@ -28,8 +28,9 @@ cd "$FWDIR"
 # Clean ignored/untracked files that do not need
 # for pip packaging test. Machines in GitHub Action do not have
 # enough space, see also SPARK-44557.
+# We need to keep the coverage file from previous tests in coverage runs.
 if [[ ! -z "${GITHUB_ACTIONS}" ]]; then
-  git clean -d -f -x -e assembly
+  git clean -d -f -x -e assembly -e python/coverage.xml
 fi
 
 echo "Constructing virtual env for testing"


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

Reply via email to