-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Improve downgrade-upgrade integration test #53775
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
Improve downgrade-upgrade integration test #53775
Conversation
| ], workingDirectory: parentDirectory.path, trace: true); | ||
| expect(exitCode, 0); | ||
|
|
||
| // Step 2. Switch to the dev branch. |
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.
These comments refer to dev branch anyway :)
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.
Ahh ... yes
jonahwilliams
left a comment
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.
LGTM
* Support old and new git release tag formats (#53715) * Improve downgrade-upgrade integration test (#53775) * Fix diagnostics crash in profile mode (#53878) * Prevent diagnostics crash in profile mode * Prevent diagnostics crash in profile mode Co-authored-by: Christopher Fujino <[email protected]> Co-authored-by: Ferhat <[email protected]>
Description
Before this PR, the
downgrade_upgrade_integration_test.dartwas failing during fast forward, however the test swallowed the tool exit. The fast forward would fail because the upgrade command'sresetChanges()method, intended to roll back from a hotfix commit back to the last published dev tag (e.g. fromv1.9.1+hotfix.6 -> v1.9.1), however, in this test it was actually jumping forward from the temp repo's hotfix tag (e.g.v1.9.1+hotfix.6) to the source repo's last dev tag (e.g.v1.6.4), and then trying to fast forward resulted in a merge conflict, causing thegit pull -ffto fail.This PR gets rid of the merge conflict by starting from the dev branch, so that the reset is to a tag that is on the current branch, making a fast forward valid. It also checks the exit code of each step, to protect against regression.
Related Issues
Part of #53688.
Tests
This improves an existing test.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]). This will ensure a smooth and quick review process.///).flutter analyze --flutter-repo) does not report any problems on my PR.Breaking Change
Did any tests fail when you ran them? Please read [Handling breaking changes].