HotFix: Remove accidental pdb.set_trace() call from test file #804
Conversation
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
TimoImhof
changed the title
|
Was then included in #802 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR removes a hidden pdb.set_trace() call in test_adapter_composition.py:
Problem
This line caused the test runner (pytest) to pause execution and wait for user input during test discovery or execution. Since it's not in an interactive terminal (especially when running via VS Code or CI), it appears as if the tests are hanging or failing silently.
It looks like this was a leftover debugging breakpoint that was accidentally committed.
Fix
The line has been removed to allow the test suite to run normally without interactive interruption.
After removing this, test discovery and execution complete successfully.