-
Notifications
You must be signed in to change notification settings - Fork 13.8k
[FLINK-10665] [tests] Remove legacy test YARNSessionFIFOITCase#testJavaAPI #6917
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
Conversation
|
|
@zentol thanks for the review, add a hotfix :-) |
|
|
@zentol thanks and sorry I should have paid more attention |
|
@zentol I have resolved travis issue. Could you review this when you're free? There are little changes though. |
|
cc @GJL would you like to give a glance at this thread? it's not quite complex imo. |
| * Test the YARN Java API. | ||
| */ | ||
| @Test | ||
| public void testJavaAPI() throws Exception { |
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.
How about we delete testJavaAPI? This test only starts a session cluster and tests whether the ClusterConnectionInfo and the URL of the web UI are not null. I don't see how this is related to Yarn's FIFO scheduler, i.e., the test does not belong here. Retrieving the ClusterConnectionInfo and URL of the web ui is already covered by other tests [1][2]. Lastly, the ported version in this PR does not have the same assertions as before. Let me know what you think, @tisonkun.
[1]
flink/flink-clients/src/test/java/org/apache/flink/client/cli/DefaultCLITest.java
Line 71 in 0a54983
| final LeaderConnectionInfo clusterConnectionInfo = clusterClient.getClusterConnectionInfo(); |
[2] https://github.com/apache/flink/blob/0a54983ca0207444477cfe991dbee1b611496204/flink-clients/src/main/java/org/apache/flink/client/program/rest/RestClusterClient.java
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.
Thanks for your investigation. I've checkout it and agree with you, adding a follow-up to address your comment.
As a following consideration, we should properly test FLINK on YARN in the future. Current status is not quite robust and elegant IMO (ó﹏ò。)
What is the purpose of the change
Remove legacy test
YARNSessionFIFOITCase#testJavaAPI. Since the functions are covered byDefaultCLITestVerifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:
(Evolving): (no)Documentation
cc @tillrohrmann