On Fri, 14 Feb 2014 17:16:48 +0100, Richard W.M. Jones wrote:
> Can you choose it based on something like the output of `free -m`
> and/or `grep -i bogomips /proc/cpuinfo` ?
That would not be great, it would make build results unreproducible
(=the testsuite results) on different build hosts.
Jan
On Fri, Feb 14, 2014 at 10:29:38PM +, Matthew Garrett wrote:
> On Fri, Feb 14, 2014 at 04:00:09PM -0600, Mátyás Selmeci wrote:
>
> > This may be a stupid question, but can you solve this by putting
> > more swap on those builders?
>
> It depends. If the system is sufficiently resource constra
On Fri, Feb 14, 2014 at 04:00:09PM -0600, Mátyás Selmeci wrote:
> This may be a stupid question, but can you solve this by putting
> more swap on those builders?
It depends. If the system is sufficiently resource constrained that
malloc() is actually telling you that you're not going to the moon
On Fri, 14 Feb 2014 16:00:09 -0600
Mátyás Selmeci wrote:
> This may be a stupid question, but can you solve this by putting more
> swap on those builders?
Possibly so yeah. Currently they have 4GB mem and 4GB swap.
Ideally it would be good to fix in the package or tools though, so
people with
On 02/14/2014 02:53 PM, Dmitry Butskoy wrote:
Dennis Gilmore wrote:
The arm builders all have 4gb of ram. how much ram should the tests
need?
BTW, some "big" application -- seamonkey (former mozilla/netscape
suite) -- fails to build on arm due to the same reason -- not enough
memory on the b
Dennis Gilmore wrote:
The arm builders all have 4gb of ram. how much ram should the tests
need?
BTW, some "big" application -- seamonkey (former mozilla/netscape suite)
-- fails to build on arm due to the same reason -- not enough memory on
the build host.
~buc
--
devel mailing list
devel
On 02/14/2014 05:30 PM, Jerry James wrote:
But memory, now, that's an issue. All I know for sure is that the
x86_64 and i686 builds succeeded, so those boxes had "enough" memory;
the ARM build failed, so that box did not have "enough" memory.
Based on the data presented so far, it could also
On Fri, Feb 14, 2014 at 9:16 AM, Richard W.M. Jones wrote:
> It sounds rather ill-defined :-) What counts as large amounts of
> memory or CPU?
>
Yes, I really don't know. CPU isn't so much the concern, anyway. Let
those builder churn away for long periods of time. Bwahahahaha!
But memory, no
On Fri, Feb 14, 2014 at 09:10:23AM -0700, Jerry James wrote:
> On Fri, Feb 14, 2014 at 8:54 AM, Jerry James wrote:
>
> > There's no parallel make involved. Drat. Well, I'll figure out which
> > test(s) are eating up the memory and disable it/them on ARM, I guess.
> > Thanks for the replies, ev
On Fri, Feb 14, 2014 at 8:54 AM, Jerry James wrote:
> There's no parallel make involved. Drat. Well, I'll figure out which
> test(s) are eating up the memory and disable it/them on ARM, I guess.
> Thanks for the replies, everybody.
>
A little bit of digging into the sources shows that I just
On Fri, Feb 14, 2014 at 1:59 AM, Dan Horák wrote:
> I think it was g++ (or the ld linker) what went out of memory, not
> unexpected with 4GB memory plus some swap, 4 CPUs and parallel make.
> Jerry, can you retry with parallel make disabled?
>
Actually, the failure occurred while running %check
On Thu, Feb 13, 2014 at 01:47:51PM -0700, Jerry James wrote:
> What do I do about this?
>
> http://koji.fedoraproject.org/koji/taskinfo?taskID=6526911
>
> [While building and running tests]:
>
> CC ../build/flintxx/test/t-traits
> CC ../build/flintxx/test/t-fmpzxx
> virtual memory ex
On Fri, 14 Feb 2014 02:51:36 -0600
Dennis Gilmore wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Thu, 13 Feb 2014 13:47:51 -0700
> Jerry James wrote:
>
> > What do I do about this?
> >
> > http://koji.fedoraproject.org/koji/taskinfo?taskID=6526911
> >
> > [While building and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 13 Feb 2014 13:47:51 -0700
Jerry James wrote:
> What do I do about this?
>
> http://koji.fedoraproject.org/koji/taskinfo?taskID=6526911
>
> [While building and running tests]:
>
> CC ../build/flintxx/test/t-traits
> CC ../build
What do I do about this?
http://koji.fedoraproject.org/koji/taskinfo?taskID=6526911
[While building and running tests]:
CC ../build/flintxx/test/t-traits
CC ../build/flintxx/test/t-fmpzxx
virtual memory exhausted: Cannot allocate memory
make[1]: *** [../build/flintxx/test/t-fmpzxx] E
15 matches
Mail list logo
