potiuk opened a new pull request, #69411:
URL: https://github.com/apache/airflow/pull/69411

   The Multi-Lang KubernetesExecutor system test (#68709) builds a Go bundle 
and a Java jar inside throwaway toolchain containers. On a dev host the Go 
module/build cache, the Gradle distribution and the dependency caches persist 
between runs, but CI runners are ephemeral and nothing cached them — so every 
scheduled run re-pulled the `golang`/`eclipse-temurin` images and re-downloaded 
the Gradle distribution and all dependencies. That added ~10 min to each of the 
six `KubernetesExecutor` + standard-naming-off variants (the only ones that run 
the test), which the daily CI duration-trend alert flagged.
   
   This builds the artifacts with the **host toolchain** in CI instead, 
provisioned and cached through `actions/setup-go` and `actions/setup-java` (the 
same pattern the sibling *Go SDK tests* / *Java SDK tests* jobs already use). A 
new `LANG_SDK_NATIVE_TOOLCHAIN=true` env, set only for that variant, makes 
breeze invoke the host `go` / `./gradlew` rather than `docker run`. Local runs 
keep the containerised build, so a dev host still needs neither Go nor a JDK 
installed.
   
   Measured on run `28635348211`: the parallel provisioning block was ~5m36s, 
almost entirely toolchain-image pulls + cold Gradle/Maven/Go dependency 
downloads. Removing the image pulls and warming the caches should cut that to 
~1–1.5 min (~4 min/job); the subsequent helm upgrade and the test itself are 
unaffected.
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Claude Code (Opus 4.8)
   
   Generated-by: Claude Code (Opus 4.8) following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)


-- 
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]

Reply via email to