-
-
Notifications
You must be signed in to change notification settings - Fork 973
Fix flaky grails-views-gson tests caused by shared static test state #16033
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
borinquenkid
wants to merge
2
commits into
8.0.x
Choose a base branch
from
fix/flaky-json-view-gson-shared-state
base: 8.0.x
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.
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.
This is the part of the PR I'd keep — an unqualified same-package reference silently binding to another spec's
@Entityclasses is a real trap, and givingExpandSpecits own fixtures is the right shape of fix.But it's applied to one of four specs doing exactly this, and not to the two with the worst numbers in #16030.
TeamandPlayerare declared once, inJsonViewHelperSpec.groovy:663and:672, and after this PR they are still registered into three other independently-builtKeyValueMappingContextinstances:IncludeAssociationsSpec—import grails.plugin.json.view.*plusaddPersistentEntities(Player, Team)HalEmbeddedSpec— same-package unqualified reference,addPersistentEntities(Team, Player)IterableRenderSpec— same-package unqualified reference,addPersistentEntities(Player, Team), in five separate featuresThe same pattern holds for two other classes:
grails.plugin.json.view.api.Authoris declared inapi/JsonApiSpec.groovy:449and also registered byapi/JsonApiHandleAssociationsSpec(addPersistentEntities(Author, PublishedBook, Publisher))Personis declared inEmbeddedAssociationsSpec.groovy:180and also registered byHalEmbeddedSpec(addPersistentEntities(Person, Parent))Per the dashboard the two worst specs are
JsonViewHelperSpec(8 methods, 20 failures) andJsonApiSpec(7 methods, 20 failures) — and both still share entity classes with another spec after this change.ExpandSpec(19 failures) is the only one decoupled. So if class-keyed GORM state is the root cause, the flakiness should survive this PR.Could you extend the same treatment to those specs? Given
Team/Playerare wanted by four specs, a shared read-only fixture file plus one mapping context, or per-spec copies as done here, would both work — the important thing is that no two independently-built mapping contexts see the sameClass. A dedicated fixture source file would also make the ownership obvious and stop the next spec from picking them up by accident.