-
-
Notifications
You must be signed in to change notification settings - Fork 382
review: test: Fixed nondeterministic failures in ContractOnSettersParametrizedTest.data() #6499
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
yonghanlin
wants to merge
2
commits into
INRIA:master
Choose a base branch
from
yonghanlin:fix/ContractOnSettersParametrizedTest-nondeterminism
base: master
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.
Open
Changes from all commits
Commits
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
Oops, something went wrong.
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.
Could you add a fat comment of what you do here and why we need it?
It's unclear how this relates to the problem described in the PR description.
Thanks!
Uh oh!
There was an error while loading. Please reload this page.
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.
Thank you for your review! The code below filters out invalid (receiver, method, argument) combinations before invoking setters via reflection in
ContractOnSettersParametrizedTest. This test generates candidate combinations, and the order of these candidates depends on iteration over unordered collections. When NonDex randomizes iteration order, some seeds produce combinations that violate Spoon's API contracts, which leads to nondeterministic test failures.For IMPORT_REFERENCE, the parameter type is a
CtReference, but Spoon only accepts four specific subtypes:CtTypeReference,CtExecutableReference,CtFieldReference, andCtPackageReference. WhencreateCompatibleObject()produced otherCtReferencesubtypes, the reflective call triggered contract violations. The code below explicitly checks for these four allowed types and skip all other arguments.For pattern arguments, the generator sometimes produces a
CtUnnamedPatternas the value for this parameter. However,CtCasePatterncannot directly take aCtUnnamedPatternas its pattern. It is only valid when nested inside a record pattern. When this invalid combination appears under certain NonDex seeds, the reflective call fails. The code below therefore skips this specific combination.Please let me know if you need any more details. Thank you again for pointing out the unclear part.