🐛 FIX: Check fuzz test name collision by checking the name against HashSet #114
Conversation
This file contains 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
Collaborator
lukacan
commented
Feb 1, 2024
lukacan
commented
- Fix fuzz test name collision based on the example in the Jira Task.
- Wdyt about this solution?
Ikrk
requested changes
Feb 5, 2024
Ikrk
force-pushed
the
fix/fuzz_add_names_collision
branch
from
638506a
to
b04bc63
Compare
Ikrk
force-pushed
the
fix/fuzz_add_names_collision
branch
from
b04bc63
to
98caeb2
Compare
Ikrk
approved these changes
Feb 8, 2024
lukacan
added a commit
that referenced
this pull request
May 20, 2024
…shSet (#114) * 🐛 FIX: Check fuzz test name collision by checking the name against HashSet * ✏️ review fix
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.