Added test for issue #1046 & fix proposition#1136
Merged
JakeGinnivan merged 5 commits intoGitTools:masterfrom Feb 25, 2017
Merged
Added test for issue #1046 & fix proposition#1136JakeGinnivan merged 5 commits intoGitTools:masterfrom
JakeGinnivan merged 5 commits intoGitTools:masterfrom
Conversation
Contributor
Author
|
There was problem with very long version calculating after my change, so I optimized this fix. Now calculation time is similiar to beta009 version. |
Contributor
|
This all looks pretty reasonable to me, nice investigation and work! |
Contributor
|
Investigating build failure.. and 0_o |
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
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.
Hi,
I tried to fix issue #1046. I added test for it and I did some investigation.
Here's image describing structure of commits in this test:
I did fix for this, but after my changes two tests was failing:
ReleaseBranchScenarios.WhenReleaseBranchIsMergedIntoMasterHighestVersionIsTakenWithItandDevelopScenarios.InheritVersionFromReleaseBranch.I changed asserts in failing tests, because looks like this tests had same issue as described in #1046. I don't know if it is proper solution. I didn't find this in documentation. Looks like corner cases.
Could someone check this is ok?
Short description of problem:
This line returned
release 2commit for arguments:release after mergeanddevelop after merge.Then calculated parent for
develop after mergewasMerge branch 'release-2.0.0' into develop. This commits have same merge base - returnedmergeBasewas alsorelease 2(look at image).Because
findMergeBaseequalsmergeBase, then loop stopped executing. It shouldn't stop becausemergeBaseWasForwardMergecondition was still met.Solution
commitToFindCommonBaseshould be moved up until there is no other merge bases withcommit(current branch tip).