[
https://issues.apache.org/jira/browse/SPARK-9607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14654249#comment-14654249
]
Ryan Williams commented on SPARK-9607:
--------------------------------------
Not sure I have the right bash terminology, but the {{cd}} in the sub-shell
that you quoted doesn't change the current working directory of the parent
script ({{build/mvn}}). You can put some {{pwd}} commands in {{build/mvn}} to
check.
This bug definitely interacts with SPARK-9608 but I don't think either is
really caused by the other.
I'll send a PR for this shortly as well.
> Incorrect zinc check in build/mvn
> ---------------------------------
>
> Key: SPARK-9607
> URL: https://issues.apache.org/jira/browse/SPARK-9607
> Project: Spark
> Issue Type: Bug
> Components: Build
> Affects Versions: 1.4.1
> Reporter: Ryan Williams
> Priority: Minor
>
> [This
> check|https://github.com/apache/spark/blob/5a23213c148bfe362514f9c71f5273ebda0a848a/build/mvn#L84-L85]
> in {{build/mvn}} attempts to determine whether {{zinc}} has been installed,
> but it fails to add the prefix {{build/}} to the path, so it always thinks
> that {{zinc}} is not installed, sets {{ZINC_INSTALL_FLAG}} to {{1}}, and
> attempts to install {{zinc}}.
> This error manifests later because [the {{zinc -shutdown}} and {{zinc
> -start}}
> commands|https://github.com/apache/spark/blob/5a23213c148bfe362514f9c71f5273ebda0a848a/build/mvn#L140-L143]
> are always run, even if zinc was not installed and is running.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
