Problems building the current master

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

Problems building the current master

Tamara Mendt
Hello,

I am getting errors when trying to build the current master and I wonder if
anyone has had the same problem or could help me figure it out.

@aalexandrov says he is having the same issue.

I am using
Maven Version: 3.0.5
Java version: 1.8.0_45

When I try to compile I get following Errors and the build fails:

[ERROR] error:
[INFO]      while compiling: YarnTaskManager.scala
...
[ERROR] error: File name too long
...
[ERROR] Failed to execute goal
net.alchim31.maven:scala-maven-plugin:3.1.4:compile (scala-compile-first)
on project flink-yarn: wrap: org.apache.commons.exec.ExecuteException:
Process exited with an error: 1 (Exit value: 1) -> [Help 1]

Cheers,

Tamara
Reply | Threaded
Open this post in threaded view
|

Re: Problems building the current master

Chiwan Park
Hi.

I think that you are building in encrypted file system such as ecryptfs.
Some encrypted file systems do not support long file name, but scala classes have long file name frequently.

You can choose two options to solve this problem.

1. Build in non-encrypted file system.
2. Add `-Xmax-classfile-name` args into configuration of scald-maven-plugin in pom.xml to restrict file name length. Following is example:

<arg>-Xmax-classfile-name</arg>
<arg>128</arg>


Regards.
Chiwan Park (Sent with iPhone)


> On May 19, 2015, at 11:53 PM, Tamara Mendt <[hidden email]> wrote:
>
> Hello,
>
> I am getting errors when trying to build the current master and I wonder if
> anyone has had the same problem or could help me figure it out.
>
> @aalexandrov says he is having the same issue.
>
> I am using
> Maven Version: 3.0.5
> Java version: 1.8.0_45
>
> When I try to compile I get following Errors and the build fails:
>
> [ERROR] error:
> [INFO]      while compiling: YarnTaskManager.scala
> ...
> [ERROR] error: File name too long
> ...
> [ERROR] Failed to execute goal
> net.alchim31.maven:scala-maven-plugin:3.1.4:compile (scala-compile-first)
> on project flink-yarn: wrap: org.apache.commons.exec.ExecuteException:
> Process exited with an error: 1 (Exit value: 1) -> [Help 1]
>
> Cheers,
>
> Tamara

Reply | Threaded
Open this post in threaded view
|

Re: Problems building the current master

Stephan Ewen
Chiwan proposed a good workaround.

I think that, as a long term fix, we should rewrite the code a bit such
that it does not generate such long names.



On Tue, May 19, 2015 at 5:37 PM, Chiwan Park <[hidden email]> wrote:

> Hi.
>
> I think that you are building in encrypted file system such as ecryptfs.
> Some encrypted file systems do not support long file name, but scala
> classes have long file name frequently.
>
> You can choose two options to solve this problem.
>
> 1. Build in non-encrypted file system.
> 2. Add `-Xmax-classfile-name` args into configuration of
> scald-maven-plugin in pom.xml to restrict file name length. Following is
> example:
>
> <arg>-Xmax-classfile-name</arg>
> <arg>128</arg>
>
>
> Regards.
> Chiwan Park (Sent with iPhone)
>
>
> > On May 19, 2015, at 11:53 PM, Tamara Mendt <[hidden email]> wrote:
> >
> > Hello,
> >
> > I am getting errors when trying to build the current master and I wonder
> if
> > anyone has had the same problem or could help me figure it out.
> >
> > @aalexandrov says he is having the same issue.
> >
> > I am using
> > Maven Version: 3.0.5
> > Java version: 1.8.0_45
> >
> > When I try to compile I get following Errors and the build fails:
> >
> > [ERROR] error:
> > [INFO]      while compiling: YarnTaskManager.scala
> > ...
> > [ERROR] error: File name too long
> > ...
> > [ERROR] Failed to execute goal
> > net.alchim31.maven:scala-maven-plugin:3.1.4:compile (scala-compile-first)
> > on project flink-yarn: wrap: org.apache.commons.exec.ExecuteException:
> > Process exited with an error: 1 (Exit value: 1) -> [Help 1]
> >
> > Cheers,
> >
> > Tamara
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Problems building the current master

Robert Metzger
We could actually add a check into the tools/qa-check.sh script. That way
we'll see at least a warning in pull requests introducing too long lines.

On Tue, May 19, 2015 at 6:03 PM, Stephan Ewen <[hidden email]> wrote:

> Chiwan proposed a good workaround.
>
> I think that, as a long term fix, we should rewrite the code a bit such
> that it does not generate such long names.
>
>
>
> On Tue, May 19, 2015 at 5:37 PM, Chiwan Park <[hidden email]>
> wrote:
>
> > Hi.
> >
> > I think that you are building in encrypted file system such as ecryptfs.
> > Some encrypted file systems do not support long file name, but scala
> > classes have long file name frequently.
> >
> > You can choose two options to solve this problem.
> >
> > 1. Build in non-encrypted file system.
> > 2. Add `-Xmax-classfile-name` args into configuration of
> > scald-maven-plugin in pom.xml to restrict file name length. Following is
> > example:
> >
> > <arg>-Xmax-classfile-name</arg>
> > <arg>128</arg>
> >
> >
> > Regards.
> > Chiwan Park (Sent with iPhone)
> >
> >
> > > On May 19, 2015, at 11:53 PM, Tamara Mendt <[hidden email]>
> wrote:
> > >
> > > Hello,
> > >
> > > I am getting errors when trying to build the current master and I
> wonder
> > if
> > > anyone has had the same problem or could help me figure it out.
> > >
> > > @aalexandrov says he is having the same issue.
> > >
> > > I am using
> > > Maven Version: 3.0.5
> > > Java version: 1.8.0_45
> > >
> > > When I try to compile I get following Errors and the build fails:
> > >
> > > [ERROR] error:
> > > [INFO]      while compiling: YarnTaskManager.scala
> > > ...
> > > [ERROR] error: File name too long
> > > ...
> > > [ERROR] Failed to execute goal
> > > net.alchim31.maven:scala-maven-plugin:3.1.4:compile
> (scala-compile-first)
> > > on project flink-yarn: wrap: org.apache.commons.exec.ExecuteException:
> > > Process exited with an error: 1 (Exit value: 1) -> [Help 1]
> > >
> > > Cheers,
> > >
> > > Tamara
> >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Problems building the current master

aalexandrov
I had a different issue related to the fact that
flink-language-binding-generic was not able to find (a potentially
outdated) flink-compiler dependency. I had to wipe out the local flink
artifacts from my .m2/repository to make this work.

2015-05-19 18:06 GMT+02:00 Robert Metzger <[hidden email]>:

> We could actually add a check into the tools/qa-check.sh script. That way
> we'll see at least a warning in pull requests introducing too long lines.
>
> On Tue, May 19, 2015 at 6:03 PM, Stephan Ewen <[hidden email]> wrote:
>
> > Chiwan proposed a good workaround.
> >
> > I think that, as a long term fix, we should rewrite the code a bit such
> > that it does not generate such long names.
> >
> >
> >
> > On Tue, May 19, 2015 at 5:37 PM, Chiwan Park <[hidden email]>
> > wrote:
> >
> > > Hi.
> > >
> > > I think that you are building in encrypted file system such as
> ecryptfs.
> > > Some encrypted file systems do not support long file name, but scala
> > > classes have long file name frequently.
> > >
> > > You can choose two options to solve this problem.
> > >
> > > 1. Build in non-encrypted file system.
> > > 2. Add `-Xmax-classfile-name` args into configuration of
> > > scald-maven-plugin in pom.xml to restrict file name length. Following
> is
> > > example:
> > >
> > > <arg>-Xmax-classfile-name</arg>
> > > <arg>128</arg>
> > >
> > >
> > > Regards.
> > > Chiwan Park (Sent with iPhone)
> > >
> > >
> > > > On May 19, 2015, at 11:53 PM, Tamara Mendt <[hidden email]>
> > wrote:
> > > >
> > > > Hello,
> > > >
> > > > I am getting errors when trying to build the current master and I
> > wonder
> > > if
> > > > anyone has had the same problem or could help me figure it out.
> > > >
> > > > @aalexandrov says he is having the same issue.
> > > >
> > > > I am using
> > > > Maven Version: 3.0.5
> > > > Java version: 1.8.0_45
> > > >
> > > > When I try to compile I get following Errors and the build fails:
> > > >
> > > > [ERROR] error:
> > > > [INFO]      while compiling: YarnTaskManager.scala
> > > > ...
> > > > [ERROR] error: File name too long
> > > > ...
> > > > [ERROR] Failed to execute goal
> > > > net.alchim31.maven:scala-maven-plugin:3.1.4:compile
> > (scala-compile-first)
> > > > on project flink-yarn: wrap:
> org.apache.commons.exec.ExecuteException:
> > > > Process exited with an error: 1 (Exit value: 1) -> [Help 1]
> > > >
> > > > Cheers,
> > > >
> > > > Tamara
> > >
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Problems building the current master

aalexandrov
I think that these two should be renamed to flink-optimizer, no?

./flink-staging/flink-language-binding/flink-python/pom.xml:
<artifactId>flink-compiler</artifactId>
./flink-staging/flink-language-binding/flink-language-binding-generic/pom.xml:
<artifactId>flink-compiler</artifactId>

2015-05-19 21:07 GMT+02:00 Alexander Alexandrov <
[hidden email]>:

> I had a different issue related to the fact that
> flink-language-binding-generic was not able to find (a potentially
> outdated) flink-compiler dependency. I had to wipe out the local flink
> artifacts from my .m2/repository to make this work.
>
> 2015-05-19 18:06 GMT+02:00 Robert Metzger <[hidden email]>:
>
>> We could actually add a check into the tools/qa-check.sh script. That way
>> we'll see at least a warning in pull requests introducing too long lines.
>>
>> On Tue, May 19, 2015 at 6:03 PM, Stephan Ewen <[hidden email]> wrote:
>>
>> > Chiwan proposed a good workaround.
>> >
>> > I think that, as a long term fix, we should rewrite the code a bit such
>> > that it does not generate such long names.
>> >
>> >
>> >
>> > On Tue, May 19, 2015 at 5:37 PM, Chiwan Park <[hidden email]>
>> > wrote:
>> >
>> > > Hi.
>> > >
>> > > I think that you are building in encrypted file system such as
>> ecryptfs.
>> > > Some encrypted file systems do not support long file name, but scala
>> > > classes have long file name frequently.
>> > >
>> > > You can choose two options to solve this problem.
>> > >
>> > > 1. Build in non-encrypted file system.
>> > > 2. Add `-Xmax-classfile-name` args into configuration of
>> > > scald-maven-plugin in pom.xml to restrict file name length. Following
>> is
>> > > example:
>> > >
>> > > <arg>-Xmax-classfile-name</arg>
>> > > <arg>128</arg>
>> > >
>> > >
>> > > Regards.
>> > > Chiwan Park (Sent with iPhone)
>> > >
>> > >
>> > > > On May 19, 2015, at 11:53 PM, Tamara Mendt <[hidden email]>
>> > wrote:
>> > > >
>> > > > Hello,
>> > > >
>> > > > I am getting errors when trying to build the current master and I
>> > wonder
>> > > if
>> > > > anyone has had the same problem or could help me figure it out.
>> > > >
>> > > > @aalexandrov says he is having the same issue.
>> > > >
>> > > > I am using
>> > > > Maven Version: 3.0.5
>> > > > Java version: 1.8.0_45
>> > > >
>> > > > When I try to compile I get following Errors and the build fails:
>> > > >
>> > > > [ERROR] error:
>> > > > [INFO]      while compiling: YarnTaskManager.scala
>> > > > ...
>> > > > [ERROR] error: File name too long
>> > > > ...
>> > > > [ERROR] Failed to execute goal
>> > > > net.alchim31.maven:scala-maven-plugin:3.1.4:compile
>> > (scala-compile-first)
>> > > > on project flink-yarn: wrap:
>> org.apache.commons.exec.ExecuteException:
>> > > > Process exited with an error: 1 (Exit value: 1) -> [Help 1]
>> > > >
>> > > > Cheers,
>> > > >
>> > > > Tamara
>> > >
>> > >
>> >
>>
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Problems building the current master

Stephan Ewen
Yes, those should definitely be renamed.

It is amazing that maven actually compiles this. I am a bit puzzled there...

On Tue, May 19, 2015 at 9:09 PM, Alexander Alexandrov <
[hidden email]> wrote:

> I think that these two should be renamed to flink-optimizer, no?
>
> ./flink-staging/flink-language-binding/flink-python/pom.xml:
> <artifactId>flink-compiler</artifactId>
>
> ./flink-staging/flink-language-binding/flink-language-binding-generic/pom.xml:
> <artifactId>flink-compiler</artifactId>
>
> 2015-05-19 21:07 GMT+02:00 Alexander Alexandrov <
> [hidden email]>:
>
> > I had a different issue related to the fact that
> > flink-language-binding-generic was not able to find (a potentially
> > outdated) flink-compiler dependency. I had to wipe out the local flink
> > artifacts from my .m2/repository to make this work.
> >
> > 2015-05-19 18:06 GMT+02:00 Robert Metzger <[hidden email]>:
> >
> >> We could actually add a check into the tools/qa-check.sh script. That
> way
> >> we'll see at least a warning in pull requests introducing too long
> lines.
> >>
> >> On Tue, May 19, 2015 at 6:03 PM, Stephan Ewen <[hidden email]> wrote:
> >>
> >> > Chiwan proposed a good workaround.
> >> >
> >> > I think that, as a long term fix, we should rewrite the code a bit
> such
> >> > that it does not generate such long names.
> >> >
> >> >
> >> >
> >> > On Tue, May 19, 2015 at 5:37 PM, Chiwan Park <[hidden email]>
> >> > wrote:
> >> >
> >> > > Hi.
> >> > >
> >> > > I think that you are building in encrypted file system such as
> >> ecryptfs.
> >> > > Some encrypted file systems do not support long file name, but scala
> >> > > classes have long file name frequently.
> >> > >
> >> > > You can choose two options to solve this problem.
> >> > >
> >> > > 1. Build in non-encrypted file system.
> >> > > 2. Add `-Xmax-classfile-name` args into configuration of
> >> > > scald-maven-plugin in pom.xml to restrict file name length.
> Following
> >> is
> >> > > example:
> >> > >
> >> > > <arg>-Xmax-classfile-name</arg>
> >> > > <arg>128</arg>
> >> > >
> >> > >
> >> > > Regards.
> >> > > Chiwan Park (Sent with iPhone)
> >> > >
> >> > >
> >> > > > On May 19, 2015, at 11:53 PM, Tamara Mendt <[hidden email]>
> >> > wrote:
> >> > > >
> >> > > > Hello,
> >> > > >
> >> > > > I am getting errors when trying to build the current master and I
> >> > wonder
> >> > > if
> >> > > > anyone has had the same problem or could help me figure it out.
> >> > > >
> >> > > > @aalexandrov says he is having the same issue.
> >> > > >
> >> > > > I am using
> >> > > > Maven Version: 3.0.5
> >> > > > Java version: 1.8.0_45
> >> > > >
> >> > > > When I try to compile I get following Errors and the build fails:
> >> > > >
> >> > > > [ERROR] error:
> >> > > > [INFO]      while compiling: YarnTaskManager.scala
> >> > > > ...
> >> > > > [ERROR] error: File name too long
> >> > > > ...
> >> > > > [ERROR] Failed to execute goal
> >> > > > net.alchim31.maven:scala-maven-plugin:3.1.4:compile
> >> > (scala-compile-first)
> >> > > > on project flink-yarn: wrap:
> >> org.apache.commons.exec.ExecuteException:
> >> > > > Process exited with an error: 1 (Exit value: 1) -> [Help 1]
> >> > > >
> >> > > > Cheers,
> >> > > >
> >> > > > Tamara
> >> > >
> >> > >
> >> >
> >>
> >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Problems building the current master

Robert Metzger
Probably all Flink dev's have the "flink-compiler" jar in their local ".m2"
directory.
Also on travis, we are caching the ".m2" directory to improve build times.
Maybe it would make sense to disable that on travis to detect those issues
in the future.
I'll try it out to see how it affects the build time.

On Tue, May 19, 2015 at 9:21 PM, Stephan Ewen <[hidden email]> wrote:

> Yes, those should definitely be renamed.
>
> It is amazing that maven actually compiles this. I am a bit puzzled
> there...
>
> On Tue, May 19, 2015 at 9:09 PM, Alexander Alexandrov <
> [hidden email]> wrote:
>
> > I think that these two should be renamed to flink-optimizer, no?
> >
> > ./flink-staging/flink-language-binding/flink-python/pom.xml:
> > <artifactId>flink-compiler</artifactId>
> >
> >
> ./flink-staging/flink-language-binding/flink-language-binding-generic/pom.xml:
> > <artifactId>flink-compiler</artifactId>
> >
> > 2015-05-19 21:07 GMT+02:00 Alexander Alexandrov <
> > [hidden email]>:
> >
> > > I had a different issue related to the fact that
> > > flink-language-binding-generic was not able to find (a potentially
> > > outdated) flink-compiler dependency. I had to wipe out the local flink
> > > artifacts from my .m2/repository to make this work.
> > >
> > > 2015-05-19 18:06 GMT+02:00 Robert Metzger <[hidden email]>:
> > >
> > >> We could actually add a check into the tools/qa-check.sh script. That
> > way
> > >> we'll see at least a warning in pull requests introducing too long
> > lines.
> > >>
> > >> On Tue, May 19, 2015 at 6:03 PM, Stephan Ewen <[hidden email]>
> wrote:
> > >>
> > >> > Chiwan proposed a good workaround.
> > >> >
> > >> > I think that, as a long term fix, we should rewrite the code a bit
> > such
> > >> > that it does not generate such long names.
> > >> >
> > >> >
> > >> >
> > >> > On Tue, May 19, 2015 at 5:37 PM, Chiwan Park <[hidden email]
> >
> > >> > wrote:
> > >> >
> > >> > > Hi.
> > >> > >
> > >> > > I think that you are building in encrypted file system such as
> > >> ecryptfs.
> > >> > > Some encrypted file systems do not support long file name, but
> scala
> > >> > > classes have long file name frequently.
> > >> > >
> > >> > > You can choose two options to solve this problem.
> > >> > >
> > >> > > 1. Build in non-encrypted file system.
> > >> > > 2. Add `-Xmax-classfile-name` args into configuration of
> > >> > > scald-maven-plugin in pom.xml to restrict file name length.
> > Following
> > >> is
> > >> > > example:
> > >> > >
> > >> > > <arg>-Xmax-classfile-name</arg>
> > >> > > <arg>128</arg>
> > >> > >
> > >> > >
> > >> > > Regards.
> > >> > > Chiwan Park (Sent with iPhone)
> > >> > >
> > >> > >
> > >> > > > On May 19, 2015, at 11:53 PM, Tamara Mendt <
> [hidden email]>
> > >> > wrote:
> > >> > > >
> > >> > > > Hello,
> > >> > > >
> > >> > > > I am getting errors when trying to build the current master and
> I
> > >> > wonder
> > >> > > if
> > >> > > > anyone has had the same problem or could help me figure it out.
> > >> > > >
> > >> > > > @aalexandrov says he is having the same issue.
> > >> > > >
> > >> > > > I am using
> > >> > > > Maven Version: 3.0.5
> > >> > > > Java version: 1.8.0_45
> > >> > > >
> > >> > > > When I try to compile I get following Errors and the build
> fails:
> > >> > > >
> > >> > > > [ERROR] error:
> > >> > > > [INFO]      while compiling: YarnTaskManager.scala
> > >> > > > ...
> > >> > > > [ERROR] error: File name too long
> > >> > > > ...
> > >> > > > [ERROR] Failed to execute goal
> > >> > > > net.alchim31.maven:scala-maven-plugin:3.1.4:compile
> > >> > (scala-compile-first)
> > >> > > > on project flink-yarn: wrap:
> > >> org.apache.commons.exec.ExecuteException:
> > >> > > > Process exited with an error: 1 (Exit value: 1) -> [Help 1]
> > >> > > >
> > >> > > > Cheers,
> > >> > > >
> > >> > > > Tamara
> > >> > >
> > >> > >
> > >> >
> > >>
> > >
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Problems building the current master

Robert Metzger
Okay .. it seems that maven is downloading the flink-compiler artifacts
from a snapshots repository:

[INFO] ------------------------------------------------------------------------
[INFO] Building flink-language-binding-generic 0.9-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] Downloading:
https://oss.sonatype.org/content/repositories/snapshots/org/apache/flink/flink-compiler/0.9-SNAPSHOT/maven-metadata.xml
[INFO] Downloading:
https://repository.apache.org/snapshots/org/apache/flink/flink-compiler/0.9-SNAPSHOT/maven-metadata.xml
[INFO] Downloading:
http://repository.apache.org/snapshots/org/apache/flink/flink-compiler/0.9-SNAPSHOT/maven-metadata.xml
[INFO] Downloading:
https://nexus.codehaus.org/snapshots/org/apache/flink/flink-compiler/0.9-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded:
http://repository.apache.org/snapshots/org/apache/flink/flink-compiler/0.9-SNAPSHOT/maven-metadata.xml
(2 KB at 4.9 KB/sec)
[INFO] Downloaded:
https://repository.apache.org/snapshots/org/apache/flink/flink-compiler/0.9-SNAPSHOT/maven-metadata.xml
(2 KB at 3.0 KB/sec)
[INFO] Downloading:
https://oss.sonatype.org/content/repositories/snapshots/org/apache/flink/flink-compiler/0.9-SNAPSHOT/flink-compiler-0.9-20150313.122611-190.pom
[INFO] Downloading:
https://repository.apache.org/snapshots/org/apache/flink/flink-compiler/0.9-SNAPSHOT/flink-compiler-0.9-20150313.122611-190.pom
[INFO] Downloaded:
https://repository.apache.org/snapshots/org/apache/flink/flink-compiler/0.9-SNAPSHOT/flink-compiler-0.9-20150313.122611-190.pom
(4 KB at 6.2 KB/sec)
[INFO] Downloading:
https://repository.apache.org/snapshots/org/apache/flink/flink-compiler/0.9-SNAPSHOT/flink-compiler-0.9-20150313.122611-190.jar
[INFO] Downloaded:
https://repository.apache.org/snapshots/org/apache/flink/flink-compiler/0.9-SNAPSHOT/flink-compiler-0.9-20150313.122611-190.jar
(2660 KB at 2499.9 KB/sec)


So maven can build because "flink-compiler:0.9-SNAPSHOT" is online
available.
I'm trying to see whether adding --no-snapshot-updates [1] will fail the
build on travis. Once I've verified that, I'll push a fix.



[1]https://jira.codehaus.org/browse/MNG-5064

On Tue, May 19, 2015 at 9:26 PM, Robert Metzger <[hidden email]> wrote:

> Probably all Flink dev's have the "flink-compiler" jar in their local
> ".m2" directory.
> Also on travis, we are caching the ".m2" directory to improve build times.
> Maybe it would make sense to disable that on travis to detect those issues
> in the future.
> I'll try it out to see how it affects the build time.
>
> On Tue, May 19, 2015 at 9:21 PM, Stephan Ewen <[hidden email]> wrote:
>
>> Yes, those should definitely be renamed.
>>
>> It is amazing that maven actually compiles this. I am a bit puzzled
>> there...
>>
>> On Tue, May 19, 2015 at 9:09 PM, Alexander Alexandrov <
>> [hidden email]> wrote:
>>
>> > I think that these two should be renamed to flink-optimizer, no?
>> >
>> > ./flink-staging/flink-language-binding/flink-python/pom.xml:
>> > <artifactId>flink-compiler</artifactId>
>> >
>> >
>> ./flink-staging/flink-language-binding/flink-language-binding-generic/pom.xml:
>> > <artifactId>flink-compiler</artifactId>
>> >
>> > 2015-05-19 21:07 GMT+02:00 Alexander Alexandrov <
>> > [hidden email]>:
>> >
>> > > I had a different issue related to the fact that
>> > > flink-language-binding-generic was not able to find (a potentially
>> > > outdated) flink-compiler dependency. I had to wipe out the local flink
>> > > artifacts from my .m2/repository to make this work.
>> > >
>> > > 2015-05-19 18:06 GMT+02:00 Robert Metzger <[hidden email]>:
>> > >
>> > >> We could actually add a check into the tools/qa-check.sh script. That
>> > way
>> > >> we'll see at least a warning in pull requests introducing too long
>> > lines.
>> > >>
>> > >> On Tue, May 19, 2015 at 6:03 PM, Stephan Ewen <[hidden email]>
>> wrote:
>> > >>
>> > >> > Chiwan proposed a good workaround.
>> > >> >
>> > >> > I think that, as a long term fix, we should rewrite the code a bit
>> > such
>> > >> > that it does not generate such long names.
>> > >> >
>> > >> >
>> > >> >
>> > >> > On Tue, May 19, 2015 at 5:37 PM, Chiwan Park <
>> [hidden email]>
>> > >> > wrote:
>> > >> >
>> > >> > > Hi.
>> > >> > >
>> > >> > > I think that you are building in encrypted file system such as
>> > >> ecryptfs.
>> > >> > > Some encrypted file systems do not support long file name, but
>> scala
>> > >> > > classes have long file name frequently.
>> > >> > >
>> > >> > > You can choose two options to solve this problem.
>> > >> > >
>> > >> > > 1. Build in non-encrypted file system.
>> > >> > > 2. Add `-Xmax-classfile-name` args into configuration of
>> > >> > > scald-maven-plugin in pom.xml to restrict file name length.
>> > Following
>> > >> is
>> > >> > > example:
>> > >> > >
>> > >> > > <arg>-Xmax-classfile-name</arg>
>> > >> > > <arg>128</arg>
>> > >> > >
>> > >> > >
>> > >> > > Regards.
>> > >> > > Chiwan Park (Sent with iPhone)
>> > >> > >
>> > >> > >
>> > >> > > > On May 19, 2015, at 11:53 PM, Tamara Mendt <
>> [hidden email]>
>> > >> > wrote:
>> > >> > > >
>> > >> > > > Hello,
>> > >> > > >
>> > >> > > > I am getting errors when trying to build the current master
>> and I
>> > >> > wonder
>> > >> > > if
>> > >> > > > anyone has had the same problem or could help me figure it out.
>> > >> > > >
>> > >> > > > @aalexandrov says he is having the same issue.
>> > >> > > >
>> > >> > > > I am using
>> > >> > > > Maven Version: 3.0.5
>> > >> > > > Java version: 1.8.0_45
>> > >> > > >
>> > >> > > > When I try to compile I get following Errors and the build
>> fails:
>> > >> > > >
>> > >> > > > [ERROR] error:
>> > >> > > > [INFO]      while compiling: YarnTaskManager.scala
>> > >> > > > ...
>> > >> > > > [ERROR] error: File name too long
>> > >> > > > ...
>> > >> > > > [ERROR] Failed to execute goal
>> > >> > > > net.alchim31.maven:scala-maven-plugin:3.1.4:compile
>> > >> > (scala-compile-first)
>> > >> > > > on project flink-yarn: wrap:
>> > >> org.apache.commons.exec.ExecuteException:
>> > >> > > > Process exited with an error: 1 (Exit value: 1) -> [Help 1]
>> > >> > > >
>> > >> > > > Cheers,
>> > >> > > >
>> > >> > > > Tamara
>> > >> > >
>> > >> > >
>> > >> >
>> > >>
>> > >
>> > >
>> >
>>
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Problems building the current master

Stephan Ewen
Thanks for investigating this, Robert!

On Tue, May 19, 2015 at 10:08 PM, Robert Metzger <[hidden email]>
wrote:

> Okay .. it seems that maven is downloading the flink-compiler artifacts
> from a snapshots repository:
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building flink-language-binding-generic 0.9-SNAPSHOT
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Downloading:
>
> https://oss.sonatype.org/content/repositories/snapshots/org/apache/flink/flink-compiler/0.9-SNAPSHOT/maven-metadata.xml
> [INFO] Downloading:
>
> https://repository.apache.org/snapshots/org/apache/flink/flink-compiler/0.9-SNAPSHOT/maven-metadata.xml
> [INFO] Downloading:
>
> http://repository.apache.org/snapshots/org/apache/flink/flink-compiler/0.9-SNAPSHOT/maven-metadata.xml
> [INFO] Downloading:
>
> https://nexus.codehaus.org/snapshots/org/apache/flink/flink-compiler/0.9-SNAPSHOT/maven-metadata.xml
> [INFO] Downloaded:
>
> http://repository.apache.org/snapshots/org/apache/flink/flink-compiler/0.9-SNAPSHOT/maven-metadata.xml
> (2 KB at 4.9 KB/sec)
> [INFO] Downloaded:
>
> https://repository.apache.org/snapshots/org/apache/flink/flink-compiler/0.9-SNAPSHOT/maven-metadata.xml
> (2 KB at 3.0 KB/sec)
> [INFO] Downloading:
>
> https://oss.sonatype.org/content/repositories/snapshots/org/apache/flink/flink-compiler/0.9-SNAPSHOT/flink-compiler-0.9-20150313.122611-190.pom
> [INFO] Downloading:
>
> https://repository.apache.org/snapshots/org/apache/flink/flink-compiler/0.9-SNAPSHOT/flink-compiler-0.9-20150313.122611-190.pom
> [INFO] Downloaded:
>
> https://repository.apache.org/snapshots/org/apache/flink/flink-compiler/0.9-SNAPSHOT/flink-compiler-0.9-20150313.122611-190.pom
> (4 KB at 6.2 KB/sec)
> [INFO] Downloading:
>
> https://repository.apache.org/snapshots/org/apache/flink/flink-compiler/0.9-SNAPSHOT/flink-compiler-0.9-20150313.122611-190.jar
> [INFO] Downloaded:
>
> https://repository.apache.org/snapshots/org/apache/flink/flink-compiler/0.9-SNAPSHOT/flink-compiler-0.9-20150313.122611-190.jar
> (2660 KB at 2499.9 KB/sec)
>
>
> So maven can build because "flink-compiler:0.9-SNAPSHOT" is online
> available.
> I'm trying to see whether adding --no-snapshot-updates [1] will fail the
> build on travis. Once I've verified that, I'll push a fix.
>
>
>
> [1]https://jira.codehaus.org/browse/MNG-5064
>
> On Tue, May 19, 2015 at 9:26 PM, Robert Metzger <[hidden email]>
> wrote:
>
> > Probably all Flink dev's have the "flink-compiler" jar in their local
> > ".m2" directory.
> > Also on travis, we are caching the ".m2" directory to improve build
> times.
> > Maybe it would make sense to disable that on travis to detect those
> issues
> > in the future.
> > I'll try it out to see how it affects the build time.
> >
> > On Tue, May 19, 2015 at 9:21 PM, Stephan Ewen <[hidden email]> wrote:
> >
> >> Yes, those should definitely be renamed.
> >>
> >> It is amazing that maven actually compiles this. I am a bit puzzled
> >> there...
> >>
> >> On Tue, May 19, 2015 at 9:09 PM, Alexander Alexandrov <
> >> [hidden email]> wrote:
> >>
> >> > I think that these two should be renamed to flink-optimizer, no?
> >> >
> >> > ./flink-staging/flink-language-binding/flink-python/pom.xml:
> >> > <artifactId>flink-compiler</artifactId>
> >> >
> >> >
> >>
> ./flink-staging/flink-language-binding/flink-language-binding-generic/pom.xml:
> >> > <artifactId>flink-compiler</artifactId>
> >> >
> >> > 2015-05-19 21:07 GMT+02:00 Alexander Alexandrov <
> >> > [hidden email]>:
> >> >
> >> > > I had a different issue related to the fact that
> >> > > flink-language-binding-generic was not able to find (a potentially
> >> > > outdated) flink-compiler dependency. I had to wipe out the local
> flink
> >> > > artifacts from my .m2/repository to make this work.
> >> > >
> >> > > 2015-05-19 18:06 GMT+02:00 Robert Metzger <[hidden email]>:
> >> > >
> >> > >> We could actually add a check into the tools/qa-check.sh script.
> That
> >> > way
> >> > >> we'll see at least a warning in pull requests introducing too long
> >> > lines.
> >> > >>
> >> > >> On Tue, May 19, 2015 at 6:03 PM, Stephan Ewen <[hidden email]>
> >> wrote:
> >> > >>
> >> > >> > Chiwan proposed a good workaround.
> >> > >> >
> >> > >> > I think that, as a long term fix, we should rewrite the code a
> bit
> >> > such
> >> > >> > that it does not generate such long names.
> >> > >> >
> >> > >> >
> >> > >> >
> >> > >> > On Tue, May 19, 2015 at 5:37 PM, Chiwan Park <
> >> [hidden email]>
> >> > >> > wrote:
> >> > >> >
> >> > >> > > Hi.
> >> > >> > >
> >> > >> > > I think that you are building in encrypted file system such as
> >> > >> ecryptfs.
> >> > >> > > Some encrypted file systems do not support long file name, but
> >> scala
> >> > >> > > classes have long file name frequently.
> >> > >> > >
> >> > >> > > You can choose two options to solve this problem.
> >> > >> > >
> >> > >> > > 1. Build in non-encrypted file system.
> >> > >> > > 2. Add `-Xmax-classfile-name` args into configuration of
> >> > >> > > scald-maven-plugin in pom.xml to restrict file name length.
> >> > Following
> >> > >> is
> >> > >> > > example:
> >> > >> > >
> >> > >> > > <arg>-Xmax-classfile-name</arg>
> >> > >> > > <arg>128</arg>
> >> > >> > >
> >> > >> > >
> >> > >> > > Regards.
> >> > >> > > Chiwan Park (Sent with iPhone)
> >> > >> > >
> >> > >> > >
> >> > >> > > > On May 19, 2015, at 11:53 PM, Tamara Mendt <
> >> [hidden email]>
> >> > >> > wrote:
> >> > >> > > >
> >> > >> > > > Hello,
> >> > >> > > >
> >> > >> > > > I am getting errors when trying to build the current master
> >> and I
> >> > >> > wonder
> >> > >> > > if
> >> > >> > > > anyone has had the same problem or could help me figure it
> out.
> >> > >> > > >
> >> > >> > > > @aalexandrov says he is having the same issue.
> >> > >> > > >
> >> > >> > > > I am using
> >> > >> > > > Maven Version: 3.0.5
> >> > >> > > > Java version: 1.8.0_45
> >> > >> > > >
> >> > >> > > > When I try to compile I get following Errors and the build
> >> fails:
> >> > >> > > >
> >> > >> > > > [ERROR] error:
> >> > >> > > > [INFO]      while compiling: YarnTaskManager.scala
> >> > >> > > > ...
> >> > >> > > > [ERROR] error: File name too long
> >> > >> > > > ...
> >> > >> > > > [ERROR] Failed to execute goal
> >> > >> > > > net.alchim31.maven:scala-maven-plugin:3.1.4:compile
> >> > >> > (scala-compile-first)
> >> > >> > > > on project flink-yarn: wrap:
> >> > >> org.apache.commons.exec.ExecuteException:
> >> > >> > > > Process exited with an error: 1 (Exit value: 1) -> [Help 1]
> >> > >> > > >
> >> > >> > > > Cheers,
> >> > >> > > >
> >> > >> > > > Tamara
> >> > >> > >
> >> > >> > >
> >> > >> >
> >> > >>
> >> > >
> >> > >
> >> >
> >>
> >
> >
>