2012/10/10 Julian Sikorski <belegdol-Re5JQEeQqe8AvxtiuMwx3w(a)public.gmane.org&gt;: > W dniu 2012-10-10 12:22, Leigh Scott pisze: >> >> Hi Julian, >> >> >>> If I could somehow force only one build at a >>> time, this could help. Otherwise we might need to bump the builder >>> memory - how much does it have now? That's the point, the builder is lacking memory, but only during link time of a given build. I've reproduced the problem on a similar builder. I will try to reproduce using a f18 target. Please do not submit any mame jobs for now. Thx Nicolas (kwizart)

W dniu 11.10.2012 07:28, Julian Sikorski pisze: > W dniu 11.10.2012 00:27, Nicolas Chauvet pisze: >> 2012/10/10 Julian Sikorski <

>>> W dniu 2012-10-10 12:22, Leigh Scott pisze: >>>> >>>> Hi Julian, >>>> >>>> >>>>> If I could somehow force only one build at a >>>>> time, this could help. Otherwise we might need to bump the builder >>>>> memory - how much does it have now? >> That's the point, the builder is lacking memory, but only during link >> time of a given build. >> I've reproduced the problem on a similar builder. I will try to >> reproduce using a f18 target. >> >> Please do not submit any mame jobs for now. >> Thx >> >> Nicolas (kwizart) >> > Sure, no problem. If the memory is the only issue, I can consider > donating some. Let me know what your tests show and what type of memory > is needed. > > Julian > Where do we stand on this? If RPM Fusion is no longer able to supply up-to-date mame packages, I need to look for another solution. Regards, Julian

Nicolas Chauvet píše v So 27. 10. 2012 v 12:40 +0200: > Yesterday. > Le 27 oct. 2012 10:43, "Julian Sikorski" <belegdol(a)gmail.com&gt; a écrit : > > > > W dniu 11.10.2012 07:28, Julian Sikorski pisze: > > > W dniu 11.10.2012 00:27, Nicolas Chauvet pisze: > > >> 2012/10/10 Julian Sikorski < > belegdol-Re5JQEeQqe8AvxtiuMwx3w-XMD5yJDbdMReXY1tMh2IBg(a)public.gmane.org&gt;: > > >>> W dniu 2012-10-10 12:22, Leigh Scott pisze: > > >>>> > > >>>> Hi Julian, > > >>>> > > >>>> > > >>>>> If I could somehow force only one build at a > > >>>>> time, this could help. Otherwise we might need to bump the builder > > >>>>> memory - how much does it have now? > > >> That's the point, the builder is lacking memory, but only during link > > >> time of a given build. > > >> I've reproduced the problem on a similar builder. I will try to > > >> reproduce using a f18 target. > > >> > > >> Please do not submit any mame jobs for now. > > >> Thx > > >> > > >> Nicolas (kwizart) > > >> > > > Sure, no problem. If the memory is the only issue, I can consider > > > donating some. Let me know what your tests show and what type of memory > > > is needed. > > > > > > Julian > > > > > Where do we stand on this? If RPM Fusion is no longer able to supply > > up-to-date mame packages, I need to look for another solution. > > > > Regards, > > Julian > > Hi Julian, > > I was only able to test a f18 target > Yesterday. And it has failed the same as f19. > > There are actions ongoing to solve this from the infra side. > > Btw. Is there a way to lower the memory usage needed at link time until the > problem is solved ? the trick used in Fedora on s390/ppc/arm for some packages (webkit, ...) was to switch from -g to -g1 (generates less debuginfos) and use "-Wl,--no-keep-memory -Wl,--reduce-memory-overheads" options for the linker

W dniu 27.10.2012 12:52, Dan Horák pisze: > Dan Horák píše v So 27. 10. 2012 v 12:48 +0200: >> Nicolas Chauvet píše v So 27. 10. 2012 v 12:40 +0200: >>> Yesterday. >>> Le 27 oct. 2012 10:43, "Julian Sikorski" <belegdol-Re5JQEeQqe8AvxtiuMwx3w-XMD5yJDbdMReXY1tMh2IBg(a)public.gmane.org&gt; a écrit : >>>> >>>> W dniu 11.10.2012 07:28, Julian Sikorski pisze: >>>>> W dniu 11.10.2012 00:27, Nicolas Chauvet pisze: >>>>>> 2012/10/10 Julian Sikorski < >>> belegdol-Re5JQEeQqe8AvxtiuMwx3w-XMD5yJDbdMReXY1tMh2IBg-XMD5yJDbdMSQIYZ4X/+iSw-XMD5yJDbdMReXY1tMh2IBh2eb7JE58TQ(a)public.gmane.org&gt;: >>>>>>> W dniu 2012-10-10 12:22, Leigh Scott pisze: >>>>>>>> >>>>>>>> Hi Julian, >>>>>>>> >>>>>>>> >>>>>>>>> If I could somehow force only one build at a >>>>>>>>> time, this could help. Otherwise we might need to bump the builder >>>>>>>>> memory - how much does it have now? >>>>>> That's the point, the builder is lacking memory, but only during link >>>>>> time of a given build. >>>>>> I've reproduced the problem on a similar builder. I will try to >>>>>> reproduce using a f18 target. >>>>>> >>>>>> Please do not submit any mame jobs for now. >>>>>> Thx >>>>>> >>>>>> Nicolas (kwizart) >>>>>> >>>>> Sure, no problem. If the memory is the only issue, I can consider >>>>> donating some. Let me know what your tests show and what type of memory >>>>> is needed. >>>>> >>>>> Julian >>>>> >>>> Where do we stand on this? If RPM Fusion is no longer able to supply >>>> up-to-date mame packages, I need to look for another solution. >>>> >>>> Regards, >>>> Julian >>> >>> Hi Julian, >>> >>> I was only able to test a f18 target >>> Yesterday. And it has failed the same as f19. >>> >>> There are actions ongoing to solve this from the infra side. >>> >>> Btw. Is there a way to lower the memory usage needed at link time until the >>> problem is solved ? >> >> the trick used in Fedora on s390/ppc/arm for some packages (webkit, ...) >> was to switch from -g to -g1 (generates less debuginfos) and use >> "-Wl,--no-keep-memory -Wl,--reduce-memory-overheads" >> options for the linker > > and it looks like this: > > %build > %ifarch s390 %{arm} > # Use linker flags to reduce memory consumption on low-mem architectures > %global optflags %{optflags} -Wl,--no-keep-memory -Wl,--reduce-memory-overheads > %endif > %ifarch s390 > # Decrease debuginfo verbosity to reduce memory consumption even more > %global optflags %(echo %{optflags} | sed 's/-g/-g1/') > %endif > > > > Dan > I have now submitted a build with first of the workarounds enabled. Let's see if it helps. Julian

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 So I will submit new VirtaulBox release on F18 first . Best regards and thanks,

Keep in mind that it was 0.147u1 which was built for rawhide, and 0.147 for F-18.

W dniu 29.10.2012 00:54, Sérgio Basto pisze: > On Dom, 2012-10-28 at 21:42 +0100, Julian Sikorski wrote: >> Keep in mind that it was 0.147u1 which was built for rawhide, and >> 0.147 >> for F-18. > > You haven't test 0.147u1 or other than 0.147 on F-18 builder > http://buildsys.rpmfusion.org/logs/fedora-18-rpmfusion_nonfree/ . > > I don't understand if you are saying that 0.147u1 have a specific > problem that makes "memory exhausted", that 0.147 doesn't ? I am not saying that, I am saying that we are not comparing the same thing here, so we should be cautious when drawing conclusions. > > If not, what bigger test build 0.147u1 to F-18 to see if just take about > 190 minutes. I will do it once mame-0.147 gets pushed to F-18 stable. It got missed before which leads to dependency problems. > > Other suggestion is limit the builder to build one package each time. > > Thanks and best regards, > Regards, Julian

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 ?

On Sáb, 2012-11-10 at 11:57 +0100, Julian Sikorski wrote: > 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 https://bugzilla.rpmfusion.org/show_bug.cgi?id=2554 Thanks,