[
https://issues.apache.org/jira/browse/FLINK-24455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17424652#comment-17424652
]
Aitozi commented on FLINK-24455:
--------------------------------
Finally, It turns out that it's my fault lead to this (I change the
workingDirectory to the parent dir) before {{copy-dependencies}}, so it add
more unrelated jar to submodule classpath :(
But I still have one concern here.
1. It's default use the {{mvn}} command to execute, I have an alias for this,
so I encountered this problem, may be we could add a check exitcode after
execute {{copy-dependencies}} ?
2. Why use {{copy-dependencies}} instead of mvn clean package to build a fat
jar?
Please take a look when you are free cc [~chesnay]
> Flink runtime test can't work with FallbackAkkaRpcSystemLoader
> --------------------------------------------------------------
>
> Key: FLINK-24455
> URL: https://issues.apache.org/jira/browse/FLINK-24455
> Project: Flink
> Issue Type: Bug
> Components: Tests
> Reporter: Aitozi
> Priority: Major
> Attachments: image-2021-10-06-00-27-19-848.png,
> image-2021-10-06-02-26-25-670.png, screenshot-1.png
>
>
> After [FLINK-24367|https://github.com/apache/flink/pull/17385/files], a
> {{FallbackAkkaRpcSystemLoader}} is provided, which should make it possible to
> run test directly without execute {{mvn package -pl
> flink-rpc/flink-rpc-akka,flink-rpc/flink-rpc-akka-loader}} in command line,
> but I still meet the exception
> !image-2021-10-06-00-27-19-848.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
