The GitHub Actions job "Tests (AMD)" on airflow.git/v3-3-test has failed.
Run started by GitHub user potiuk (triggered by potiuk).

Head commit for run:
58d6c813f89e369799ba737e40d6bfbb970a383a / Jason(Zhe-You) Liu 
<[email protected]>
[v3-3-test] Drop colored logging from the Go SDK edge worker (#70824) (#70908)

* Drop colored logging from the Go SDK edge worker

The Go SDK edge worker was the only Edge Worker that colorized its console
logs. The Python Edge Worker (edge3 provider) does not support colored
logging, so the Go side aligns with it and drops the feature rather than
maintaining coloring the rest of the Edge Worker surface does not offer.

Dropping colored logging removes the sole use of the github.com/MatusOllah/
slogcolor dependency; the edge worker now logs via the standard library slog
text handler, preserving log levels including the custom TRACE level. The
lang-SDK Go example module, which resolves the SDK via a replace directive,
is re-tidied to drop the now-unused indirect slogcolor entry.

* Reconcile lang-SDK Go example go.sum before building the bundle

The K8S Lang-SDK test always builds the Go bundle from upstream main's
go-sdk, while go_example is a branch fixture whose go.sum is tidied against
the in-repo go-sdk. When a branch changes go-sdk's dependency graph the two
go-sdks diverge, and Go refuses to build the bundle on the resulting go.sum
drift ("missing go.sum entry ..."), turning the bundle-build step red on the
pull request. Re-tidy the scratch go_example against the go-sdk it is actually
compiled against before packing so the build reconciles the drift itself; the
committed go.sum is left untouched and stays guarded by the
check-go-example-mod-tidy prek hook.
(cherry picked from commit 802ffa7b3c6ea34a69dd7df0f42c9dc26d5bb883)

Report URL: https://github.com/apache/airflow/actions/runs/30703688578

With regards,
GitHub Actions via GitBox


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

Reply via email to