Run lang-SDK K8s system test once in a dedicated job instead of 6x#69500
Merged
Conversation
potiuk
requested review from
amoghrajesh,
ashb,
bugraoz93,
gopidesupavan,
jason810496 and
jscheffl
as code owners
boring-cyborg
Bot
added
area:dev-tools
area:kubernetes-tests
backport-to-v3-3-test
The Multi-Lang KubernetesExecutor coordinator system test was gated on KubernetesExecutor + use-standard-naming==false, but that condition is true once per kubernetes-combo, so it ran redundantly across all six Python/K8s combos on ci-amd (and again on ci-arm) - adding ~4 minutes of Go/Java build and coordinator run to each of those six system-test jobs and pushing them to ~20 minutes, well above the rest of the matrix. The test is executor/naming/version-independent, so run it once instead: a dedicated tests-kubernetes-lang-sdk job on a single default Python-Kubernetes combo that provisions the native Go/Java toolchains (cached) and runs only the lang-SDK test (-k test_lang_sdk_combined_dag_succeeds), not the full suite or the upgrade path. The regular system-test matrix no longer runs it at all, so those six jobs drop back to ~15 minutes. Also scope the Go/Java build caches by runner.arch: the previous key used only runner.os (Linux), which would collide between amd64 and arm64 runners now that the dedicated job runs on both.
potiuk
force-pushed
the
lang-sdk-dedicated-k8s-job
branch
from
ad1fdd6 to
6ce612a
Compare
Lee-W
approved these changes
Jul 7, 2026
Contributor
Backport failed to create: v3-3-test. View the failure log Run detailsNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
You can attempt to backport this manually by running: cherry_picker 586e658 v3-3-testThis should apply the commit to the v3-3-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continueIf you don't have cherry-picker installed, see the installation guide. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Multi-Lang KubernetesExecutor coordinator system test (added in #68709)
was gated on
KubernetesExecutor+use-standard-naming == false— but thatcondition is true once per
kubernetes-combo, so it ran redundantly across allsix Python/K8s combos on ci-amd (and again on ci-arm). Each of those six
system-test jobs paid ~4 extra minutes of Go/Java build + coordinator run,
pushing them to ~20 min — well above the rest of the matrix, and the source of
the recurring "K8S System:KubernetesExecutor-*-false" CI duration-trend alerts.
The test is executor/naming/version-independent, so this runs it once: a
dedicated
tests-kubernetes-lang-sdkjob on a single default Python-Kubernetescombo that provisions the native Go/Java toolchains (cached) and runs only the
lang-SDK test (
-k test_lang_sdk_combined_dag_succeeds) — not the full suite,and no
--upgrade. The regular system-test matrix no longer runs it at all, sothose six jobs drop back to ~15 min.
Also scopes the Go/Java build caches by
runner.arch: the previous key usedonly
runner.os(Linux), which would collide between amd64 and arm64 now thatthe dedicated job runs on both.
Follow-up to #69411 (native lang-SDK toolchain build + caching).
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.8) following the guidelines