ci/e2e: disable upgrade tests #673
Merged
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
Upgrade tests scenarii should be changed. As they are not relevant anymore and sporadically fail it better to disable them. This commit also remove the manual upgrade test with Elemental CLI, as this is not supported. Signed-off-by: Loic Devulder <ldevulder@suse.com>
juadk
approved these changes
Feb 16, 2023
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.
Upgrade tests scenarii should be changed. As they are not relevant anymore and sporadically fail it better to disable them.
This commit also remove the manual upgrade test with Elemental CLI, as this is not supported. And anyway the others upgrade methods are using the same API for the upgrade as the CLI. It could also be added in elemental-toolkit if needed.
Should fix #668 and #669.
NOTE: upgrade test in UI is kept, as it does a test do the latest version built and check the generated OS list from YAML, so still useful for now.
Verification runs: