[Improve] e2e.yml improvement #4144
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
|
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.
[Improve] e2e.yml improvement
What changes were proposed in this pull request
Since the introduction of e2e testing, the quality of our project has significantly improved. However, due to limited github build resources and the many items that need to be tested in our e2e test case, almost every submission results in test failures (e.g: #4143 those related to deployment mode jobs. This situation necessitates that PMC members manually rerun the tests, severely impacting the project’s progress and collaboration efficiency.
To address this issue, we will temporarily retain only the test cases related to Flink 1.18, while removing those associated with versions 1.16 and 1.17. This adjustment aims to improve the pass rate of e2e tests and enhance the overall efficiency of developer collaboration.
Brief change log
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
Does this pull request potentially affect one of the following parts