[Bugfix][Failing Test] Fix test_events.py

[rabi]

Fixes tests/distributed/test_events.py::test_topic_filtering

FIX: #18458

[github-actions]

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can either: Add ready label to the PR or enable auto-merge.

🚀

[markmc]

Thanks @rabi !

It looks like in #16750 we never added this new test to a CI job - could you find a suitable place for it in .buildkite/test-pipeline.yaml?

cc @alec-flowers

[hmellor]

Ok this bug stems from the fact that KVEventsConfig is no longer a pydantic.BaseModel (it was standardised to be a dataclass like the other configs).

The default scope of pytest.fixture is function (docs) so we should simply be able to remove the line cfg = publisher_config.model_copy(). Tests are allowed to mutate the fixture because it is not reused for multiple tests.

[rabi]

The default scope of pytest.fixture is function (docs)

done, Thanks!

[hmellor]

Could you add this file to the source_file_dependencies above with test_utils and test_pynccl?

[hmellor]

Thanks! Let's see if the test suite passes