[jason810496]

• closes: E2E and Breeze coverage for the executable coordinator path (Go SDK) #66943
• depends on Go SDK: airflow-go-pack tool for self-contained bundle binaries #67156 get merged first
• early review diff: jason810496/airflow@refactor/go-sdk/airflow-go-pack...jason810496:refactor/go-sdk/e2e-tests

What

Airflow e2e test to verify Go-SDK starting from building Go artifact, setup coordinator and corresponding worker, then trigger DagRun.

Verify Task state, XCom, Logging from Airflow REST API following the same pattern of Java-SDK.

Verification

---

Was generative AI tooling used to co-author this PR?

• Yes, with help of Claude Opus 4.8 following the guidelines

[phanikumv]

lgtm, and this mirrors the existing Java SDK test pattern. We just need to wait for #67156 to be merged before this

[uranusjr]

Actually… do we even have E2E CI jobs set up for Java SDK currently? I remember adding the tests but don’t recall if I wired up CI.

[phanikumv]

Actually… do we even have E2E CI jobs set up for Java SDK currently? I remember adding the tests but don’t recall if I wired up CI.

I saw run_java_sdk_tests, then may be we need a follow up PR to add java sdk CI tests then.

[jason810496]

Actually… do we even have E2E CI jobs set up for Java SDK currently? I remember adding the tests but don’t recall if I wired up CI.

I wired the E2E for Java SDK up in

• Fix Java-SDK e2e test registration #67993

[jason810496]

https://github.com/apache/airflow/actions/runs/27116260260/job/80026835010?pr=67956

I just rebased in top of dependent PR and the Go-SDK e2e test passed. The fail and pending tests are not related, merging this.