Re: Filename too long

As a guideline I recommend my fellow developers to not have reduntant names in the directory paths of a repository. In your example I counted 4 times hadoop-yarn which is 3 times too many. Unfortunately windows in the year 2018 still has a fixed path limit of something along 260 characters. -- Dom

Re: Filename too long

Never mind. Figured out the solution. Ralph > On Dec 1, 2018, at 11:06 PM, Ralph Goers wrote: > > Gary, when I clone the git repo to my Windows VM I am getting the error > message > > error: unable to create file > log4j-1.2-api/src/test/resources/config-1.2/hadoop/hadoop-yarn-project/hadoop

Filename too long

Gary, when I clone the git repo to my Windows VM I am getting the error message error: unable to create file log4j-1.2-api/src/test/resources/config-1.2/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-unmanaged-am-launcher/src/test/resources/log4j.properti

Re: Jenkins build became unstable: Log4j 2 2.x #3753

No, it means that the fix for 1906 still isn’t perfect. Ralph > On Dec 1, 2018, at 6:21 PM, Gary Gregory wrote: > > Is this failure related to the recent file close issue in the tests? > > Gary > > -- Forwarded message - > From: Apache Jenkins Server > Date: Sat, Dec 1, 2018

Fwd: Jenkins build became unstable: Log4j 2 2.x #3753

Is this failure related to the recent file close issue in the tests? Gary -- Forwarded message - From: Apache Jenkins Server Date: Sat, Dec 1, 2018 at 3:53 PM Subject: Jenkins build became unstable: Log4j 2 2.x #3753 To: See