W dniu 08.11.2012 21:43, Sérgio Basto pisze:
> On Dom, 2012-10-28 at 16:42 +0000, Sérgio Basto wrote:
>> On Dom, 2012-10-28 at 07:38 +0100, Julian Sikorski wrote:
>>
>>
>>> It built, but the process took 600 minutes. This is still a bit slow
>>> IMO. I'll just build the missing mame-0.147 for F-18 and hold on with
>>> u-releases until we get more memory for the buildsys.
>>
>>
>> 14860 (mame): Build on target fedora-18-rpmfusion_nonfree succeeded.
>>
>>
>> i686:
builder1.rpmfusion.org Status: done/done Build Time: 85 minutes
>> x86_64:
builder1.rpmfusion.org Status: done/done Build Time: 210
>> minutes
>>
>> My bet is a problem only with rawhide (F19) build system.
>>
>>
http://buildsys.rpmfusion.org/logs/fedora-development-rpmfusion_nonfree/1...
>> we can see in this link that we have lots of "Cannot allocate memory"
,
>> while on F18 we don't have .
>>
>> I remember see a failed build log with VirtualBox on F19 like "Memory
>> exhausted" , but never in F18
>
> Comparing building mame-0_147u2 on F16, F17 , F18 and Rawhide
>
>
http://buildsys.rpmfusion.org/build-status/job.psp?uid=14967
>
>
http://buildsys.rpmfusion.org/build-status/job.psp?uid=14966
>
>
http://buildsys.rpmfusion.org/build-status/job.psp?uid=14976
>
>
http://buildsys.rpmfusion.org/build-status/job.psp?uid=14907
>
> F16 Build Time =~ 96 minutes
> F17 Build Time =~ 107 minutes
> but F18 Build Time =~ 1250 minutes !?!
> and F19 Build Time =~ 676 minutes
>
> So my guess was totally wrong , So what is the the problem ? is from
> new releases ?
>
>
>
Just for comparison, here is how long it took on my machine (yum and
root cache fully updated, no ccache):
F-17 x86_64: 38 minutes 0 seconds
F-18 x86_64: 40 minutes 58 seconds
devel x86_64: 44 minutes 51 seconds
So, it seems there is nothing that much different cpu-time-wise. I asked
on the devel ML how to get some memory usage stats, will report back
once I have them.
Hi,
mame-0_147u4-1
build in less of 130 minutes in all branches F19, F18, F17 and F16 .
this is problem is fixed ? if yes let close the bug
Thanks,
--
Sérgio M. B.