[
https://issues.apache.org/jira/browse/SPARK-9608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Owen updated SPARK-9608:
-----------------------------
Priority: Minor (was: Major)
Yes, just did a quick test and you're right. Do you want to make a PR?
> Incorrect zinc -status check in build/mvn
> -----------------------------------------
>
> Key: SPARK-9608
> URL: https://issues.apache.org/jira/browse/SPARK-9608
> Project: Spark
> Issue Type: Bug
> Components: Build
> Affects Versions: 1.4.1
> Reporter: Ryan Williams
> Priority: Minor
>
> {{build/mvn}} [uses a {{-z `zinc -status`}}
> test|https://github.com/apache/spark/blob/5a23213c148bfe362514f9c71f5273ebda0a848a/build/mvn#L138]
> to determine whether a {{zinc}} process is running.
> However, {{zinc -status}} checks port {{3030}} by default.
> This means that if a {{$ZINC_PORT}} env var is set to some value besides
> {{3030}}, and an existing {{zinc}} process is running on port {{3030}},
> {{build/mvn}} will skip starting a {{zinc}} process, thinking that a suitable
> one is running.
> Subsequent compilations will look for a {{zinc}} at port {{$ZINC_PORT}} and
> not find one.
> The {{zinc -status}} call should get the flag {{-port "$ZINC_PORT"}} added to
> it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
