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

[Lincoln Baxter, III]

The problem was that there was not enough memory being allocated for some
of the very expensive operations that Forge performs in the test suite.
Like booting up multiple forge instances in a test, etc. Increasing the
Surefire Heap space did the trick. Thanks for that suggestion!

~Lincoln

On Wed, Nov 30, 2011 at 5:07 AM, Max Rydahl Andersen <
max.andersen at redhat.com> 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 at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/forge-dev
>
> /max
> http://about.me/maxandersen
>
>
>
>
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>



-- 
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20111130/85d9de17/attachment.html