You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2020/05/27 09:04:00 UTC
[jira] [Closed] (FLINK-17938) Cannot run mvn clean verify
flink-yarn-tests
[ https://issues.apache.org/jira/browse/FLINK-17938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Rohrmann closed FLINK-17938.
---------------------------------
Resolution: Fixed
Fixed via
master: e1989bf3b598a565501f4d040ef9627aa34e3ded
1.11.0: 8b8ed695714d878fe69ca3dad8e7540b41c5d4e7
> Cannot run mvn clean verify flink-yarn-tests
> --------------------------------------------
>
> Key: FLINK-17938
> URL: https://issues.apache.org/jira/browse/FLINK-17938
> Project: Flink
> Issue Type: Bug
> Components: Deployment / YARN, Tests
> Affects Versions: 1.11.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Critical
> Labels: pull-request-available
> Fix For: 1.11.0
>
>
> As part of FLINK-11086, we introduced the setting of the yarn class path in a static initializer of {{YarnTestBase.java:199}}. The yarn class path file will be generated by the {{maven-dependency-plugin}} in the {{package}} phase. Due to this, the {{yarn.classpath}} file won't be accessible to all users of the {{YarnTestBase}} class which are run in a previous phase (e.g. {{UtilsTest.testUberjarLocator}}).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)