The GitHub Actions job "Tests" on airflow.git/ghaeli/callback-remote-logging has failed. Run started by GitHub user seanghaeli (triggered by seanghaeli).
Head commit for run: ab18dff3bb07f8601018f9e61127dfa8f9c3a638 / Sean Ghaeli <[email protected]> Add remote log upload support for callback subprocesses Enable callback logs (deadline alerts, SLA notifications, etc.) to be uploaded to remote storage (S3, GCS, etc.) so they are visible in the Airflow UI when remote logging is configured. Key change: make `ti` optional in `RemoteLogIO.upload()` protocol and `upload_to_remote()` since callbacks don't have a task instance. The 7 providers that ignore `ti` (S3, GCS, CloudWatch, WASB, OSS, HDFS, Alibaba) work immediately. Elasticsearch and OpenSearch use `ti` for log ID rendering and will need a follow-up to handle the `ti=None` case — until then, callback log upload failures for those providers are caught and logged without affecting callback execution. - Make `ti` optional (`RuntimeTI | None = None`) in `RemoteLogIO.upload()` protocol and `upload_to_remote()` - Add `_upload_logs()` to `CallbackSubprocess.wait()`, delegating to `upload_to_remote` with error handling that swallows failures - Wire up `_remote_logging_conn(client)` in `_configure_logging()` so remote log handler processors are initialized during logging setup - Move logging setup inside `_ensure_client()` context in `supervise_callback()` so the client is available for `_configure_logging()` Report URL: https://github.com/apache/airflow/actions/runs/25345657479 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
