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

dongjoon 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 6da54d9a1a42 [SPARK-53666][INFRA][FOLLOWUP] Use absolute output path 
for `generate-llms-txt.py`
6da54d9a1a42 is described below

commit 6da54d9a1a42be9fbbe512788dd5007c8ec940c5
Author: Dongjoon Hyun <[email protected]>
AuthorDate: Thu Nov 6 22:47:19 2025 -0800

    [SPARK-53666][INFRA][FOLLOWUP] Use absolute output path for 
`generate-llms-txt.py`
    
    ### What changes were proposed in this pull request?
    
    This PR aims to use an absolute output path (`"$SELF/_site/llms.txt"`) 
instead of a relative path (`_site/llms.txt`) when 
`dev/create-release/release-build.sh` uses `generate-llms-txt.py`.
    
    
https://github.com/apache/spark/blob/47a8d2a2ce58c9a28fbbeaf8af38717895ae01a6/dev/create-release/release-build.sh#L839-L841
    
    ### Why are the changes needed?
    
    Currently, Apache Spark release CI has been broken. 
(https://github.com/apache/spark/actions/workflows/release.yml)
    This is a release blocker for Apache Spark 4.1.0.
    
      - https://github.com/apache/spark/actions/runs/19060666797 (2025-11-03)
    ```
    + echo 'Generating llms.txt...'
    Generating llms.txt...
    + python /opt/spark-rm/generate-llms-txt.py --docs-path . --output 
_site/llms.txt --version 4.2.0-SNAPSHOT
    Traceback (most recent call last):
      File "/opt/spark-rm/generate-llms-txt.py", line 206, in <module>
        main()
      File "/opt/spark-rm/generate-llms-txt.py", line 202, in main
        generate_llms_txt(docs_path, output_path, args.version)
      File "/opt/spark-rm/generate-llms-txt.py", line 159, in generate_llms_txt
        with open(output_path, "w", encoding="utf-8") as f:
    FileNotFoundError: [Errno 2] No such file or directory: '/_site/llms.txt'
    ```
    
      - https://github.com/apache/spark/actions/runs/19094119034 (2025-11-04)
    
    ```
    + echo 'Generating llms.txt...'
    Generating llms.txt...
    + python /opt/spark-rm/generate-llms-txt.py --docs-path . --output 
_site/llms.txt --version 4.2.0-SNAPSHOT
    Traceback (most recent call last):
      File "/opt/spark-rm/generate-llms-txt.py", line 206, in <module>
        main()
      File "/opt/spark-rm/generate-llms-txt.py", line 202, in main
        generate_llms_txt(docs_path, output_path, args.version)
      File "/opt/spark-rm/generate-llms-txt.py", line 159, in generate_llms_txt
        with open(output_path, "w", encoding="utf-8") as f:
    FileNotFoundError: [Errno 2] No such file or directory: '/_site/llms.txt'
    ```
    
    ### Does this PR introduce _any_ user-facing change?
    
    No behavior change because this is a release script.
    
    ### How was this patch tested?
    
    Manual test.
    
    ```
    $ mkdir /tmp/SPARK-53666
    $ dev/create-release/do-release-docker.sh -t SPARK-53666 -d 
/tmp/SPARK-53666 -n -s docs
    ...
    = Building spark-rm image with tag SPARK-53666...
    ...
    ```
    
    ### Was this patch authored or co-authored using generative AI tooling?
    
    No.
    
    Closes #52934 from dongjoon-hyun/SPARK-53666.
    
    Authored-by: Dongjoon Hyun <[email protected]>
    Signed-off-by: Dongjoon Hyun <[email protected]>
---
 dev/create-release/release-build.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev/create-release/release-build.sh 
b/dev/create-release/release-build.sh
index 73ea87cfe6ac..6c4ab8006aab 100755
--- a/dev/create-release/release-build.sh
+++ b/dev/create-release/release-build.sh
@@ -838,7 +838,7 @@ if [[ "$1" == "docs" ]]; then
   echo "Generating llms.txt..."
   python "$SELF/generate-llms-txt.py" \
     --docs-path . \
-    --output _site/llms.txt \
+    --output "$SELF/_site/llms.txt" \
     --version "$SPARK_VERSION"
 
   cd ..


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

Reply via email to