The GitHub Actions job "Tests (ARM)" on airflow.git/main has succeeded. Run started by GitHub user potiuk (triggered by potiuk).
Head commit for run: d24297f6582265f9b14a210853b8966284caf62f / KidAmnesiac1 <[email protected]> Change log level from info to debug for Edge job fetch (#68736) * Change log level from info to debug for Edge job fetch This changes the log level of the "No new job to process" message in `fetch_and_run_job()` from `logger.info` to `logger.debug`. *Why*: An idle edge worker emits this message every job_poll_interval seconds for as long as no work is queued. In many deployments, workers spend the majority of their time idle — that's by design, since edge workers are often provisioned for bursty or on-demand workloads. The result is that this single message dominates the worker logs, drowning out genuinely useful INFO-level entries like job starts, completions, state changes, and heartbeat events. Per Python's logging conventions, INFO should communicate "confirmation that things are working as expected" — meaningful milestones and state transitions. An idle worker having nothing to do is the expected steady state, not a notable event. By contrast, DEBUG is the correct level for routine operational chatter useful only when actively troubleshooting. For comparison, the line immediately above it already uses the right level: logger.debug("Attempting to fetch a new job..."). The "no job found" outcome is the other half of the same operation and should match. Impact: No behaviour change. Operators who want to see these messages can still set the edge worker log level to DEBUG. Everyone else gets cleaner logs at the default INFO level. * Update log message in docs Report URL: https://github.com/apache/airflow/actions/runs/29119895569 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
