I fixed that failure with some Git magic. Gary
On Wed, Sep 27, 2017 at 12:32 AM, Benedikt Ritter <brit...@apache.org> wrote: > > > Am 27.09.2017 um 00:16 schrieb Gary Gregory <garydgreg...@gmail.com>: > > > > This test fails on Windows: > > Can’t we just drop Windows support? :( > > Do you have some time to investigate this? > > Cheers, > Benedikt > > > > > org.apache.commons.io.FileUtilsTestCase > > > > FileUtilsTestCase > > org.apache.commons.io.FileUtilsTestCase > > testContentEqualsIgnoreEOL(org.apache.commons.io.FileUtilsTestCase) > > java.lang.AssertionError > > > > at org.junit.Assert.fail(Assert.java:86) > > > > at org.junit.Assert.assertTrue(Assert.java:41) > > > > at org.junit.Assert.assertFalse(Assert.java:64) > > > > at org.junit.Assert.assertFalse(Assert.java:74) > > > > at > > org.apache.commons.io.FileUtilsTestCase.testContentEqualsIgnoreEOL( > FileUtilsTestCase.java:681) > > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > > > at > > sun.reflect.NativeMethodAccessorImpl.invoke( > NativeMethodAccessorImpl.java:57) > > > > at > > sun.reflect.DelegatingMethodAccessorImpl.invoke( > DelegatingMethodAccessorImpl.java:43) > > > > at java.lang.reflect.Method.invoke(Method.java:606) > > > > at > > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall( > FrameworkMethod.java:50) > > > > at > > org.junit.internal.runners.model.ReflectiveCallable.run( > ReflectiveCallable.java:12) > > > > at > > org.junit.runners.model.FrameworkMethod.invokeExplosively( > FrameworkMethod.java:47) > > > > at > > org.junit.internal.runners.statements.InvokeMethod. > evaluate(InvokeMethod.java:17) > > > > at > > org.junit.internal.runners.statements.RunBefores. > evaluate(RunBefores.java:26) > > > > at > > org.junit.internal.runners.statements.RunAfters.evaluate( > RunAfters.java:27) > > > > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > > > > at > > org.junit.runners.BlockJUnit4ClassRunner.runChild( > BlockJUnit4ClassRunner.java:78) > > > > at > > org.junit.runners.BlockJUnit4ClassRunner.runChild( > BlockJUnit4ClassRunner.java:57) > > > > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > > > > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > > > > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > > > > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > > > > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > > > > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > > > > at > > org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run( > JUnit4TestReference.java:86) > > > > at > > org.eclipse.jdt.internal.junit.runner.TestExecution. > run(TestExecution.java:38) > > > > at > > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner. > runTests(RemoteTestRunner.java:539) > > > > at > > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner. > runTests(RemoteTestRunner.java:761) > > > > at > > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner. > run(RemoteTestRunner.java:461) > > > > at > > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner. > main(RemoteTestRunner.java:207) > > > > > > Gary > > > > On Tue, Sep 26, 2017 at 2:48 PM, Benedikt Ritter <brit...@apache.org> > wrote: > > > >> Hey, > >> > >> I’m going through the list of components I happen to work with and make > >> them ready for Java 9. Since I’m blocked in the release process of > >> collections because of the Windows test failures, I’m going to cut a RC > for > >> IO 2.6 probably tomorrow night. > >> > >> Regards, > >> Benedikt > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > >> For additional commands, e-mail: dev-h...@commons.apache.org > >> > >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
