Re: [forge-dev] Forge build back to Stable (Hack away!)

You could always spin up a job on the JBoss Jenkins server to build this on Windows for you …. On Nov 30, 2011, at 9:49 AM, Lincoln Baxter, III wrote: Hey Koen, Could I ask you to look in to this? I am not at a place where I have access to windows, and I don't see that error on OSX. Thanks! ~Lincoln On Wed, Nov 30, 2011 at 7:12 AM, Koen Aers <koen.aers(a)gmail.com&gt; wrote: > I was able to build, test and run without issues on OSX. On Windows (XP) > the build stopped after the following failing test. I didn't investigate > any further. > > Cheers, > Koen > > > ------------------------------------------------------------------------------- > Test set: org.jboss.forge.test.parser.java.JavaClassTest > > ------------------------------------------------------------------------------- > Tests run: 25, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.078 > sec <<< FAILURE! > testFormattingIsNotChanged(org.jboss.forge.test.parser.java.JavaClassTest) > Time elapsed: 0.015 sec <<< FAILURE! > java.lang.AssertionError: > at org.junit.Assert.fail(Assert.java:91) > at org.junit.Assert.assertTrue(Assert.java:43) > at org.junit.Assert.assertTrue(Assert.java:54) > at > org.jboss.forge.test.parser.java.JavaClassTest.testFormattingIsNotChanged(JavaClassTest.java:77) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at > org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:59) > at > org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:115) > at > org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:102) > at org.apache.maven.surefire.Surefire.run(Surefire.java:180) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:350) > at > org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021) > > > > > > On Wed, Nov 30, 2011 at 11:10 AM, Richard Kennard < > richard(a)kennardconsulting.com&gt; wrote: > >> Lincoln, >> >> The build seems to run, and there are no lingering test failures, but on >> Windows the distribution fails to start up? It just hangs at the command >> prompt, >> without printing 'Forge' in ASCII text or anything. It appears to be >> waiting for keyboard input, as if I press ENTER the cursor moves down once, >> but then >> it too stops. >> >> I have grown so used to Forge telling me I'm an idiot for running >> Windows, but now it won't even do that :) >> >> Regards, >> >> Richard. >> >> On 30/11/2011 9:07 PM, Max Rydahl Andersen wrote: >> > What was the problem in the end ? >> > >> > My guess was a memory leak in forge or the testsuite - did I win ? >> > >> > /max >> > >> > On Nov 29, 2011, at 22:16, Lincoln Baxter, III wrote: >> > >> >> Please feel free to run the full build on any operating system, >> without the aggravation of lingering test failures! >> >> >> >> -- >> >> Lincoln Baxter, III >> >> http://ocpsoft.com >> >> http://scrumshark.com >> >> "Keep it Simple" >> >> _______________________________________________ >> >> forge-dev mailing list >> >> forge-dev(a)lists.jboss.org >> >> https://lists.jboss.org/mailman/listinfo/forge-dev >> > /max >> > http://about.me/maxandersen >> > >> > >> > >> > >> > _______________________________________________ >> > forge-dev mailing list >> > forge-dev(a)lists.jboss.org >> > https://lists.jboss.org/mailman/listinfo/forge-dev >> > >> > >> >> _______________________________________________ >> forge-dev mailing list >> forge-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/forge-dev >> > > > _______________________________________________ > forge-dev mailing list > forge-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev > > -- Lincoln Baxter, III http://ocpsoft.com http://scrumshark.com "Keep it Simple" _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev