Skip to content

Fix flaky test_overflow_queue in history websocket tests#171766

Open
bdraco wants to merge 2 commits into
devfrom
fix-test-overflow-queue-flake
Open

Fix flaky test_overflow_queue in history websocket tests#171766
bdraco wants to merge 2 commits into
devfrom
fix-test-overflow-queue-flake

Conversation

@bdraco
Copy link
Copy Markdown
Member

@bdraco bdraco commented May 21, 2026

Proposed change

test_overflow_queue compared the full bus listener dictionary before and after, which flakes when unrelated components asynchronously add or remove EVENT_STATE_CHANGED listeners during the test. Replace the inline assert with a context manager assert_no_listener_leak that captures listeners before and after and ignores state_changed. To still verify the live stream subscription is cleaned up on overflow, spy on async_track_state_change_event so the test directly asserts the unsubscribe callable is invoked when the queue overflows.

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Deprecation (breaking change to happen in the future)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

  • This PR fixes or closes issue: fixes #
  • This PR is related to issue:
  • Link to documentation pull request:
  • Link to developer documentation pull request:
  • Link to frontend pull request:

Checklist

  • I understand the code I am submitting and can explain how it works.
  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • I have followed the perfect PR recommendations
  • The code has been formatted using Ruff (ruff format homeassistant tests)
  • Tests have been added to verify that the new code works.
  • Any generated code has been carefully reviewed for correctness and compliance with project standards.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • For the updated dependencies a diff between library versions and ideally a link to the changelog/release notes is added to the PR description.

To help with the load of incoming pull requests:

Comparing the full bus listener dict can fail when unrelated components
asynchronously add or remove EVENT_STATE_CHANGED listeners during the
test; capture listeners before and after via a context manager that
excludes state_changed.
@home-assistant
Copy link
Copy Markdown
Contributor

Hey there @home-assistant/core, mind taking a look at this pull request as it has been labeled with an integration (history) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of history can trigger bot actions by commenting:

  • @home-assistant close Closes the pull request.
  • @home-assistant mark-draft Mark the pull request as draft.
  • @home-assistant ready-for-review Remove the draft status from the pull request.
  • @home-assistant rename Awesome new title Renames the pull request.
  • @home-assistant reopen Reopen the pull request.
  • @home-assistant unassign history Removes the current integration label and assignees on the pull request, add the integration domain after the command.
  • @home-assistant update-branch Update the pull request branch with the base branch.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) to the pull request.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the pull request.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR aims to make test_overflow_queue in the History websocket API test suite less flaky by changing how it asserts that event bus listeners are not leaked during the test.

Changes:

  • Add an assert_no_listener_leak context manager to snapshot bus listeners before/after a block.
  • Update test_overflow_queue to use the new context manager and ignore EVENT_STATE_CHANGED listener changes to reduce unrelated flakiness.

Comment thread tests/components/history/test_websocket_api.py
@bdraco bdraco closed this May 21, 2026
@bdraco bdraco deleted the fix-test-overflow-queue-flake branch May 21, 2026 19:18
@bdraco
Copy link
Copy Markdown
Member Author

bdraco commented May 21, 2026

need to rethink this

Add a spy on async_track_state_change_event so the test directly
asserts the live stream's unsubscribe callable is invoked when the
queue overflows, instead of relying on the (unreliable) shared
EVENT_STATE_CHANGED bus listener count.
@bdraco bdraco reopened this May 21, 2026
@bdraco bdraco marked this pull request as ready for review May 21, 2026 20:10
@bdraco bdraco requested a review from a team as a code owner May 21, 2026 20:10
Copilot AI review requested due to automatic review settings May 21, 2026 20:10
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants