-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Optimization: Avoid quadratic behavior in IdMaker.make_unique_parameterset_ids #14739
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
NoxiousTab
wants to merge
5
commits into
pytest-dev:main
Choose a base branch
from
NoxiousTab:optimize-idmaker-dedup
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+43
−2
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
06f6de9
Avoid quadratic behavior in IdMaker.make_unique_parameterset_ids
NoxiousTab 1f0cfd8
Add changelog entry for #14739
NoxiousTab 9d5c200
Merge branch 'main' into optimize-idmaker-dedup
NoxiousTab 2f4e877
Address review: free renamed-away ids from used_ids, add regression test
NoxiousTab 278dafd
Merge branch 'main' into optimize-idmaker-dedup
NoxiousTab File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| IdMaker.make_unique_parameterset_ids (used to generate ids for @pytest.mark.parametrize) no longer scales quadratically with the number of parameter sets when many of them produce colliding ids, significantly speeding up collection for large parametrized test suites with many duplicate ids. |
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This only half-updates the parallel set:
resolved_ids[index]is replaced, but the old id is never removed fromused_idswhen it no longer occurs in the list.That is not just an invariant smell — it changes assigned ids whenever a later candidate equals a fully-renamed-away earlier id.
Simplified counter-example (same algorithm as this loop):
After both
"a10"entries are renamed, main frees"a10"for the 11th"a". Here"a10"stays reserved forever, so the last id becomes"a11".Please keep
used_idsin sync, e.g. with a remaining-count:There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done, using a
remaining_id_countscopy ofid_countsdecremented per rename, discarding once it hits zero. kinda the same idea as your sketch. Traced through the counter example of["a10","a10"]+["a"]*11and confirmed in the code that it correctly produces "a10" as the last id.