test/upgrade: Test multiple upgrade path in Ubuntu #787
Conversation
This file contains 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
Originally, we tested only precise->saucy, through non-LTS releases. Now, we test quantal->saucy->trusty (this skips raring, as it was EOL before quantal), raring->saucy, and LTS upgrade precise->trusty. precise->quantal is broken (upstream problem due to, at least, libxi6 needing to be downgraded), but I don't see why anyone would still want to do that now that trusty has been released. Finally, the test only runs if `-R` is not specified on the command line: we do not want to check against SUPPORTED_RELEASES as this test intentionally tries out releases that are marked as unsupported.
dnschneid
added a commit
that referenced
this pull request
Apr 21, 2014
test/upgrade: Test multiple upgrade path in Ubuntu
|
Awesome. Thanks for improving the testing! |
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.
Originally, we tested only precise->saucy, through non-LTS releases, but this got broken when we marked raring as unsupported.
Now, we test quantal->saucy->trusty (this skips raring, as it was EOL before quantal), raring->saucy, and LTS upgrade precise->trusty.
precise->quantal is broken (upstream problem due to, at least,
libxi6needing to be downgraded), but I don't see why anyone would still want to do that now that trusty has been released.Finally, the test only runs if
-Ris not specified on the command line: we do not want to check against$SUPPORTED_RELEASESas this test intentionally tries out releases that are marked as unsupported.Tested in
2014-04-20_11-38-30_drinkcat_chroagh_upgrade-test_18(nothing broke!)