dev/core#2073 Remove memory leak in heavily tested (merge) code #18692
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.
Overview
dev/core#2073 Remove memory leak in heavily tested (merge) code
Before
Use of
$dao->query($query);
- which is a legacy pattern previously to cause memory leaksAfter
Technical Details
There are dozens of tests that pass through these lines - I used api_v3_JobTest:testBatchMerge to step through it
Comments
Example tests
message: 'Failure in api call for relationship create: yep it is tested'
severity: fail
...
not ok 1970 - Failure: api_v3_RelationshipTest::testRelationshipCreateDuplicateWithCustomFields
message: 'Failure in api call for relationship create: yep it is tested'
severity: fail
...
not ok 1971 - Failure: api_v3_RelationshipTest::testRelationshipCreateDuplicateWithCustomFields2
message: 'Failure in api call for relationship create: yep it is tested'
severity: fail