Skip to content

Fix remote task log pollution leaking out of S3 log handler test - #69539

Merged
vincbeck merged 1 commit into
apache:mainfrom
jason810496:fix/tests/log-handler-remote-task-log-pollution
Jul 7, 2026
Merged

Fix remote task log pollution leaking out of S3 log handler test#69539
vincbeck merged 1 commit into
apache:mainfrom
jason810496:fix/tests/log-handler-remote-task-log-pollution

Conversation

@jason810496

Copy link
Copy Markdown
Member

Why

test_read_remote_logs_with_real_s3_remote_log_io assigns _ActiveLoggingConfig.remote_task_log directly and never restores it, so any log-reading test collected afterwards (e.g. test_log_reader.py when run after test_log_handlers.py) tries to fetch logs from the long-gone mocked S3 bucket and fails with InvalidAccessKeyId.

What

  • Set _ActiveLoggingConfig.remote_task_log via monkeypatch.setattr so it is restored after the test.

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

test_read_remote_logs_with_real_s3_remote_log_io assigned
_ActiveLoggingConfig.remote_task_log directly and never restored it, so
any log-reading test collected afterwards tried to fetch logs from the
long-gone mocked S3 bucket and failed with InvalidAccessKeyId.
@jason810496 jason810496 self-assigned this Jul 7, 2026
@jason810496
jason810496 requested review from Lee-W, gopidesupavan, jscheffl and potiuk and removed request for jscheffl July 7, 2026 11:28
@vincbeck
vincbeck merged commit 8bedde1 into apache:main Jul 7, 2026
148 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants