/srv/irclogs.ubuntu.com/2014/08/29/#launchpad.txt

pnormanI'm a maintainer on a PPA which keeps getting virtual memory exhausted errors when it tries to build a package. This isn't surprising, given the huge codebase of heavily templated C++ code that takes half an hour to build. We're looking at switching from g++ to clang++ which might fix this, but in the mean time, is it possible to supply our own VM for building the package so we can get a more recent version up?02:22
wgrantpnorman: It's not possible to do that. But if you're getting VM exhaustion errors it sounds like you're running out of 32-bit address space, not running out of RAM.02:26
wgrantA bigger virtual machine won't help won't help on 32-bit architectures if you can't compile within 4GiB of address space.02:27
wgrantWe normally see such problems during linking rather than compilation, though. Are you really managing to exhaust the address space in a single compilation unit?02:30
pnormanYou're right, that was from the 32 bit build. Let me find an error for the 64 bit02:33
pnormanhttps://launchpad.net/~mapnik/+archive/ubuntu/nightly-trunk/+build/6304351 is an amd64 and I see virtual memory exhausted: Cannot allocate memory towards the end02:36
wgrantpnorman: Are you sure something's not very wrong? The builders all now have twice the RAM they did a month ago; this could never have built before then.02:39
pnormanI'm building a more recent commit at work. Let me check when last build is (the one in the PPA)02:41
pnormanLet me try that failing build on my server02:53
=== s8321414_ is now known as s8321414
pnormanbuilding, but with -j6 so it shouldn't take the hour that the builders do03:37
pnormanWell 10 minutes in and it's using ~6GB of RAM. How much RAM do the builders have?03:48
wgrantpnorman: 4GB plus some swap.04:33
wgrantI don't recall how much swap.04:33
wgrantBut that seems like an implausibly large amount of RAM for a single compilation unit to require, even if it's horrid C++.04:34
pnormanclang++ does it in about 2.5GB05:07
pnormanMy build log inclues the message clang: error: unable to execute command: Killed and tells me to file a debian bug (https://launchpadlibrarian.net/183499083/buildlog_ubuntu-trusty-i386.mapnik_3.0.0%2Bdev20140829.git.8faa358-2~trusty1_FAILEDTOBUILD.txt.gz)07:20
wgrantpnorman: It probably got OOM-killed.07:23
pnormanI also have an amd64 build that's apparently failed, without a build log: https://launchpad.net/~pnorman/+archive/ubuntu/mapnik-testing/+build/630820907:24
pnormanHmm. I'd say it's time to abandon any thought of i386 on the PPAs. Which is probably fine, most users using the nightly trunk builds will have 8GB+ of RAM, and many will have 64GB+, so they're pretty obviously not i38607:25
wgrantI think your amd64 build might be driving them into swapdeath.07:27
pnormanAny way to diagnose? It'd surprise me, since clang++ built in <4GB https://github.com/mapnik/debian/issues/2#issuecomment-5383800807:28
wgrantAre you sure you're using the same version of clang?07:28
pnormanUbuntu clang version 3.4-1ubuntu3 on my server, and I'm depending on clang-3.4. Without a build log, I can't be *sure*, but I think I am07:30
pnormanah, there we go. someone rebuilt it and I see a buildlog now, which includes the same error as i386. I wonder if I should bisect this, see if something pushed up compile memory usage07:45
wgrantpnorman: Have you tried building it in a trusty chroot?07:47
wgrantIf this ever built before, there is a serious regression somewhere.07:47
pnormanI've built it not in a chroot just now07:48
wgrantOn trusty?07:48
pnormanya.07:49
geserbtw: your utopic build used g++ while only your trusty test build used clang07:54
pnormanhmm. while I'm not immediately concerned with utopic (precise and trusty are what's used most), I can't think of anything that would cause that, as there's no release-specific stuff going on07:56
geser"Build-Depends: g++-4.8" (from https://launchpadlibrarian.net/183497914/buildlog_ubuntu-utopic-amd64.mapnik_3.0.0%2Bdev20140829.git.8faa358-1~utopic1_FAILEDTOBUILD.txt.gz)07:58
pnormanrules passes CXX=/usr/bin/clang++ to ./configure08:03
pnormanOh, that's -1. That was still on g++. -2 is clang++08:03
mptLaunchpad Janitor claims to have confirmed bug 1308321, but didn’t09:21
ubot5bug 1308321 in unity (Ubuntu) "Can't open app from unity panel twice, only first time works" [Undecided,New] https://launchpad.net/bugs/130832109:21
mptI am confused09:22
=== Trevinho_ is now known as Trevinho
=== vidplace7_ is now known as vidplace7
=== Quintasan_ is now known as Quintasan
=== daker_ is now known as daker
geserchange conflict perhaps? according to the activity log you both changed something in the same second10:05
=== semiosis_ is now known as semiosis
=== elijah__ is now known as elijah
=== zoktar_ is now known as zoktar
=== popey_ is now known as popey
=== FourDollars_ is now known as FourDollars
=== cprov__ is now known as cprov
=== dch_ is now known as dch
=== ctracey_ is now known as ctracey
=== jjox` is now known as jjox
=== FloSoft_ is now known as FloSoft
=== heroux_ is now known as heroux
=== ral_ is now known as ral
=== BradCrittenden is now known as bac
=== beuno_ is now known as beuno
=== Pici` is now known as Pici
=== mthaddon` is now known as mthaddon
=== dobey_ is now known as dobey
=== TRB143__ is now known as TRB143
=== cjwatson_ is now known as cjwatson
sergio-br2i put one folder to bazaar ignore19:51
sergio-br2* i put the folder in the .bzrignore19:51
sergio-br2but if i delete some file from that folder, it does not ignores...19:51
sergio-br2what's the magic i need to do?19:52
sergio-br2i tried19:53
sergio-br2folder19:53
sergio-br2folder*19:53
sergio-br2folder/*19:53
=== RagingComput is now known as RagingComputer
=== jjox` is now known as jjox
=== NikitaKonovalov2 is now known as NikitaKonovalov
=== Quintasan_ is now known as Quintasan
methdoes launchpad have pull requests or is it just bug reports that act like both issues and pull requests?21:59
=== lifeless1 is now known as lifeless

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!