e2e: add DPS leak checks - #1263
Merged
Merged
Conversation
Run strict SDK and Paho leak tracking after every DPS registration test. Share tracker construction with the IoT Hub suite while preserving its existing false-positive filter. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Remove the shared tracker factory and leave the existing IoT Hub setup untouched. The DPS conftest now configures its LeakTracker directly. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Carter Tinney (cartertinney)
requested review from
Avishek (avishekpant) and
olivakar
September 3, 2026 17:26
Avishek (avishekpant)
approved these changes
Sep 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
DPS registration creates MQTT pipelines and background resources but previously had no leak coverage. Successful
register()calls implicitly shut down their pipeline, so a strict post-test check can detect resources that survive registration without needing IoT Hub's separate pre/post-shutdown trackers.DPS uses no replacement-object suppression: every DPS client is created after the baseline, so suppressing one replacement object would hide a real leak.
Validation
uv run --no-sync pytest tests(5,448 passed, 6 skipped)git diff --checkpassedLive DPS registration requires CI credentials and is delegated to the DPS E2E pipeline.