build failes for commons-io

2018-10-15 Thread Aleksander Ściborek
Hi, I had forked commons-io and pulled it from github and later on I run mvn clean package. I've got 9 failures - One from FileUtilsTestCase and more from IOUtilsTestCase. Aleksander

Re: build failes for commons-io

2018-10-15 Thread sebb
On Mon, 15 Oct 2018 at 21:11, Aleksander Ściborek wrote: > > Hi, > I had forked commons-io and pulled it from github and later on I run mvn > clean package. I've got 9 failures - One from FileUtilsTestCase and more > from IOUtilsTestCase. It works for me using the following software. Apache Mave

Re: build failes for commons-io

2018-10-15 Thread Aleksander Ściborek
Ok. soon I will add more information, but actually you can see that it fails on github: https://travis-ci.org/apache/commons-io On Mon, 15 Oct 2018 at 22:51, sebb wrote: > On Mon, 15 Oct 2018 at 21:11, Aleksander Ściborek > wrote: > > > > Hi, > > I had forked commons-io and pulled it from githu

Re: build failes for commons-io

2018-10-15 Thread sebb
On Mon, 15 Oct 2018 at 21:56, Aleksander Ściborek wrote: > > Ok. soon I will add more information, but actually you can see that it > fails on github: https://travis-ci.org/apache/commons-io Those appear to be Checkstyle errors, not test errors. > On Mon, 15 Oct 2018 at 22:51, sebb wrote: > > >

Re: build failes for commons-io

2018-10-15 Thread Aleksander Ściborek
Ok, so this is list of errors: FileUtilsTestCase.testContentEqualsIgnoreEOL:672 IOUtilsTestCase.testResourceToByteArray_ExistingResourceAtRootPackage:1251 expected:<0> but was:<1705> IOUtilsTestCase.testResourceToByteArray_ExistingResourceAtRootPackage_WithClassLoader:1258 expected:<0> but was:

Re: build failes for commons-io

2018-10-15 Thread sebb
On Mon, 15 Oct 2018 at 22:44, Aleksander Ściborek wrote: > > Ok, so this is list of errors: > FileUtilsTestCase.testContentEqualsIgnoreEOL:672 > IOUtilsTestCase.testResourceToByteArray_ExistingResourceAtRootPackage:1251 > expected:<0> but was:<1705> What is the size of the following file: src/

Re: build failes for commons-io

2018-10-15 Thread Aleksander Ściborek
Github indicates 1.67 KB, on my computer it shows 1,7 KB but this is probably just rounded value On Mon, 15 Oct 2018 at 23:54, sebb wrote: > On Mon, 15 Oct 2018 at 22:44, Aleksander Ściborek > wrote: > > > > Ok, so this is list of errors: > > FileUtilsTestCase.testContentEqualsIgnoreEOL:672 >

Re: build failes for commons-io

2018-10-15 Thread sebb
On Mon, 15 Oct 2018 at 23:04, Aleksander Ściborek wrote: > > Github indicates 1.67 KB, on my computer it shows 1,7 KB but this is > probably just rounded value That looks OK. However, the assertion message means that the code detected a size of 0. No idea why that should be. I think you will h

Re: build failes for commons-io

2018-10-15 Thread Aleksander Ściborek
I think I've found actually reasos for my problems, it's seems it was caused by long path and spaces in directories names - I run mvn clean package in tmp folder and everything has passed On Tue, 16 Oct 2018 at 00:29, sebb wrote: > On Mon, 15 Oct 2018 at 23:04, Aleksander Ściborek > wrote: > >

Re: build failes for commons-io

2018-10-16 Thread sebb
On Tue, 16 Oct 2018 at 00:43, Aleksander Ściborek wrote: > > I think I've found actually reasos for my problems, it's seems it was > caused by long path and spaces in directories names - I run mvn clean > package in tmp folder and everything has passed Ah, thanks for letting us know. However, th

Re: build failes for commons-io

2018-10-16 Thread sebb
I've raised a bug (IO-589) and fixed it, so thanks again for finding the error. It was a bug in the test code. On Tue, 16 Oct 2018 at 15:36, sebb wrote: > > On Tue, 16 Oct 2018 at 00:43, Aleksander Ściborek > wrote: > > > > I think I've found actually reasos for my problems, it's seems it was > >

Re: build failes for commons-io

2018-10-16 Thread Aleksander Ściborek
I've just updated my fork and everything is ok. Thank you very much :) On Wed, Oct 17, 2018, 01:11 sebb wrote: > I've raised a bug (IO-589) and fixed it, so thanks again for finding the > error. > It was a bug in the test code. > > > --