nchammas opened a new pull request, #58526:
URL: https://github.com/apache/spark/pull/58526

   ### What changes were proposed in this pull request?
   
   It's useful to know what skip flags are active when the documentation build 
runs. Instead of `echo`-ing them in the places where we want to know, the build 
script now prints them itself when it runs.
   
   ### Why are the changes needed?
   
   Helps troubleshoot builds when we want to know what exactly was supposed to 
run.
   
   The new method to print flags is naive in that it prints all flags that 
begin with `SKIP_`, even if they have no special meaning to the script. It's a 
minor tradeoff that lets us avoid repeating the names of every "real" skip flag.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No.
   
   ### How was this patch tested?
   
   I ran the doc build locally.
   
   ```
   $ SKIP_API=1 SKIP_SCALADOC=1 SKIP_PYTHONDOC=1 bundle exec jekyll build
   Configuration file: .../spark/docs/_config.yml
   
   **********************
   * Skip flags enabled *
   **********************
   SKIP_API
   SKIP_PYTHONDOC
   SKIP_SCALADOC
   
   ************************
   * Building error docs. *
   ************************
   Generated: docs/_generated/error-conditions.html
               Source: .../spark/docs
          Destination: .../spark/docs/_site
    Incremental build: disabled. Enable with --incremental
         Generating... 
                       done in 7.553 seconds.
    Auto-regeneration: disabled. Use --watch to enable.
   ```
   
   ### Was this patch authored or co-authored using generative AI tooling?
   
   No.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

Reply via email to