[01:25] <wgrant> lamont: Ah, fair point. Sorry.
[03:45] <lamont> wgrant: no worries
[03:45] <lamont> I'm planning to re-abuse 63 for next rollout of lp-buildd, assuming you don't say "NO"
[08:44] <getxsick> anyone from the Launchpad staff is online?
[08:45] <lifeless> for some value of staff, and some value of online.
[08:45] <lifeless> whats up
[08:50] <getxsick> our project needs more RAM for building
[08:50] <getxsick> is it any possibility to increase an amount for RAM for our builds?
[08:50] <getxsick> it's the PyPy project
[08:51] <lifeless> I don't know if that is configurable; we run in VM's and the ram is set by the machine it is building on.
[08:51] <lifeless> you should have GB's already ;)
[08:51] <lifeless> anyhow, please goto https://answers.launchpad.net/launchpad
[08:51] <lifeless> 'ask a question' there, and that will get the attention of folk that can answer this better.
[08:52] <lifeless> spm: unless you're still here and know? ^
[08:53] <getxsick> GB's of RAM? 2MB is let say our minimum now ;)
[08:53] <lifeless> I think you mean 2GB ?
[08:53] <getxsick> and swap is not the option :(
[08:53] <getxsick> sure, typo
[08:53] <spm> lifeless: yes, but in call atm
[08:54] <lifeless> spm: (guessing) : 'hi Tom'
[08:54] <spm> tom lols back
[08:54] <mthaddon> :)
[08:54] <lifeless> :)
[08:54] <getxsick> :D
[09:08] <getxsick> spm: long chat ;)
[09:10] <spm> getxsick: weekly call with the boss. you do the math. :-)
[09:11] <spm> getxsick: and no, I don't know the answer unf. the soyuz guys who would should be starting "nowish" so one of them should be able to help in some way shape or form.
[09:11] <bigjools> spm: whut!
[09:11] <spm> punctuation, optional. :-)
[09:12] <spm> [17:50:19] <getxsick> our project needs more RAM for building
[09:12] <spm> [17:50:40] <getxsick> is it any possibility to increase an amount for RAM for our builds?
[09:12] <spm> [17:50:45] <getxsick> it's the PyPy project
[09:12] <spm> bigjools: ^^
[09:12] <bigjools> RAM?
[09:12] <getxsick> yes
[09:12]  * bigjools punts back to spm
[09:13] <spm> ?? is this a tweak in the UI?
[09:13] <bigjools> AFAIK the builders have quite a lot of RAM already
[09:13] <getxsick> yes
[09:13] <bigjools> spm: RAM not space
[09:13] <bigjools> disk space that is
[09:13] <bigjools> I presume?
[09:13] <noodles775> getxsick: See the discussion at https://answers.edge.launchpad.net/soyuz/+question/105818
[09:13] <getxsick> what i do sometimes is just 'retry to build'
[09:13] <getxsick> and one of 3 builds usually is completed
[09:14] <getxsick> but i don't think is the correct solution :)
[09:14] <getxsick> bigjools: we need a physicall RAM
[09:14] <bigjools> lamont is the best person for this, he'll be on in a few hours
[09:14] <getxsick> ok
[09:14] <bigjools> it's not something I have any control over
[09:15] <bigjools> getxsick: your best bet, to be frank, is to fix your package to not need as much RAM
[09:16] <bigjools> there's a low chance of getting more RAM installed on builders just for you :)
[09:16] <getxsick> bigjools: haha good joke :)
[09:19] <getxsick> noodles775: exactly
[09:19] <getxsick> LaMont Jones said on 2010-04-02:
[09:19] <getxsick> Most of the buildd machines have at least 1.5GB, though I suspect that at least one has .75GB of RAM. More than 2GB of RAM would be rare, and over 3.5GB would surprise me.
[09:20] <getxsick> it's not promising :(
[09:22] <getxsick> noodles775: unfortunately, there is no solution provided
[09:23] <noodles775> getxsick: no, but as bigjools said, while Lamont is the person to talk to, it's very unlikely that a machine with extra ram can be put aside for one person :/
[09:23] <getxsick> sure
[09:23] <getxsick> but maybe we can just use only machines with +1.5GB
[09:23] <bigjools> that's not going to happen
[09:23] <getxsick> for this project
[09:23] <getxsick> why not?
[09:24] <bigjools> your best chance is to fix your package
[09:24] <bigjools> seriously
[09:24] <getxsick> actually it's technically impossible
[09:24] <bigjools> because nobody else has a problem
[09:24] <bigjools> I very much doubt that
[09:27] <lifeless> getxsick: its like this:
[09:27] <lifeless>  - we don't have the software features to reserve machines in the way you are asking
[09:27] <lifeless>  - if we did, it would probably be a commercial service anyway - remember that the daily builds are a free service to the community, running on what spare capacity Ubuntu has available.
[09:28] <lifeless>  - but we don't, so its really an irrelevant consideration: We simply don't have a software feature to do what you are asking.
[09:29] <getxsick> can we build it locally and push binaries?
[09:36] <bigjools> unfortunately we don't allow people to upload binaries because one of the guarantees that we make is that the source you see is the source that was used to build the binary you're installing.
[09:38] <getxsick> yeah
[09:38] <getxsick> i will ping lamont later maybe he can help somehow
[09:39] <bigjools> I understand it's probably quite frustrating for you, but this is a free service we're providing and we support it on a best-effort basis
[09:39] <bigjools> right, lamont may be able to offer some advice
[09:39] <mwhudson> how is it failing currently?
[09:40] <getxsick> i know, i just take your resources like i click 'retry to build' and after next 30hours again to get the correct virtual machine
[09:40] <getxsick> hi michael!
[09:40] <getxsick> mwhudson: swapping, signal 15
[09:40] <bigjools> the process monitor kills it because there's no log output for a long time
[09:40] <getxsick> exactly
[09:40] <bigjools> I would write more stuff to the log ...
[09:41] <getxsick> i can't imagine how lot the pypy translation would take even if put 'more stuff' to the log just to keep it alive, weeks? :)
[09:41] <getxsick> s/lot/long
[09:43] <mwhudson> ah
[09:43] <mwhudson> how much ram do the buildds have on average?
[09:44] <getxsick> mwhudson: don't know the avarage, but the minimum is ~1.5GB
[09:44] <lifeless> mwhudson: backlog
[09:44] <lifeless> mwhudson: ew're told most are 1.5G, some are 0.75, some are more
[09:45] <mwhudson> ah
[09:45] <mwhudson> lifeless: i guessed that much :-)
[09:45] <lifeless> by lamont
[09:45] <lifeless> :>
[09:45] <mwhudson> anyway, i need to reboot, so i'll now miss some more of this conversation!
[12:40] <edakiri> I discovered a mozilla add on which may be useful to you: Leak Monitor .
[15:45] <jenkins> dpm are you David Planella (translations coordinator) ? If so when you have a moment would you like to join #ubuntu-manual and we can talk about what you would like the Ubuntu Translations Quickstart booklet to look like.
[15:58] <dpm> jenkins, sure, I am, thanks for coming back to me. I'll join #ubuntu-manual now, but I need to be on a call in a few minutes and might not be available until in ~1h or so
[15:59] <jenkins> dpm no problem
[16:06] <bdesk> "It's not just you! http://launchpad.net  looks down from here. "
[16:07] <mwhudson> canonical data centre issues apparently
[16:07]  * mwhudson updates http://identi.ca/launchpadstatus
[16:08] <jml> mwhudson, thank you.
[16:12] <mwhudson> it got fixed before i got around to it
[16:42] <getxsick> lamont: ping
[16:43] <lamont> si?
[16:44] <getxsick> lamont: i have a problem with building our packages. we need ~1.4G RAM at least, however most of machines don't have enough
[16:45] <getxsick> lamont: any idea? can we pick onl machines which have enough RAM?
[16:45] <getxsick> s/onl/only
[17:23] <lamont> getxsick: bigjools writes the code, I just abuse^Wadmin the machines..  There isn't any way to select a particular machine or machines to build on.  I suppose you could have the build look at /proc/meminfo and /proc/swaps and decide if it wants to just die early, or give it a shot
[17:25] <getxsick> lamont: yeah, that's what i figured out and trying to test now (just waiting in queue). just to be sure, is there a way to send signal of failing the build? and can i do some automatic to start rebuild if so?
[17:30] <mkanat> How do I control my mailing list options for a list that I've signed up with via launchpad?
[17:31] <mkanat> I want it to send me duplicates, and apparently it's configured to not send duplicates.
[17:40] <matsubara> sinzui, is it possible to do what mkanat is asking ^?
[17:41] <mkanat> The problem is that I'm sorting by List-Id headers, and because of the "don't send duplicates", I have to manually file some messages.
[17:42] <mkanat> I've added a filter on my side to also check the To/CC list, but that's not foolproof if somebody copies two lists. Then I lose threading in one of the lists.
[17:46] <matsubara> mkanat, this looks like it: https://bugs.edge.launchpad.net/launchpad-registry/+bug/424195
[17:46] <mkanat> matsubara: Ah, thanks. :-)
[17:50] <matsubara> np
[18:02] <mtaylor> thumper: up yet?
[19:25] <mkanat> Where is RT?
[19:25] <james_w> mkanat: it's internal to Canonical, sorry
[19:26] <mkanat> Ah, okay.
[19:31] <Kangarooo> where was launchpad RSS feeds? cna find in google
[19:33] <Kangarooo> also im having oops on refresh.. OOPS-1643K1495 and OOPS-1643O1384
[19:45] <Kangarooo> maybe rss feed blog post can be made easyr to find? in blog easyr or in irc changel topic?
[19:51] <matsubara> Kangarooo, what RSS feed are you looking for?
[19:51] <Kangarooo> ive seen some where in lp blog rss feed where all bugs are listed
[20:00] <matsubara> Kangarooo, I'm not sure I understand. You can find the RSS feed for the launchpad blog here: http://blog.launchpad.net/feed or the latests bugs for the launchpad project here:  http://feeds.edge.launchpad.net/launchpad-project/latest-bugs.atom
[20:02] <Kangarooo> matsubara: yes somewhere ive seen theese rss and there was also rss for all bugs
[20:02] <matsubara> Kangarooo, about the oopses you got while filing a bug, I think we have a bug filed for that one, I'm looking for it, just a min
[20:03] <matsubara> Kangarooo, all bugs on which project? I don't think there's a rss for all bugs for all projects registered in LP
[20:06] <matsubara> Kangarooo, I think the OOPSes you got are this bug: https://bugs.edge.launchpad.net/malone/+bug/426946
[20:13] <Kangarooo> ah yes. now i found https://help.launchpad.net/Bugs/Subscriptions and yes now ive fount out all cant be seen. but thats ok since actually im insterested in only ubuntu bugs.. can to that page added some tag RSS couse that would be easyr to remember when looking again for that page?
[20:41] <Agafonov> Hi! How can I free my email which was assigned as lp team contact email after the team removal?
[20:44] <matsubara> Kangarooo, usually the browser shows you an icon besides the address bar with the RSS icon when there's a feed available in the page
[20:45] <Agafonov> wow, my email is set as https://launchpad.net/~registry team email
[20:46] <sinzui> Agafonov, I think there was a merge accident
[20:46] <matsubara> Agafonov, let me check that for you
[20:46]  * sinzui just removed the email
[20:46] <matsubara> thanks SiNiESTrO
[20:46] <matsubara> thanks sinzui
[20:47] <sinzui> I saw this happen a few weeks ago. Agafonov, did you have a team that was deleted recently?
[20:48] <Agafonov> yes, I created a team and deleted but clicked activate email then
[20:48] <Agafonov> by mistake
[20:49] <sinzui> Agafonov, I think there is a fault during delete/merge. The emails of the team should be deleted, not transferred.
[20:50] <Agafonov> that team was added as a sub-team meanwhile :)
[20:50] <Agafonov> and de-activated
[20:52] <Agafonov> https://launchpad.net/~ubutnu-ru-admins-merged (~ubutnu-ru-admins originally) trigged such a error
[20:53] <Agafonov> I just forgot I can rename team and deleted misspelled one...
[20:54] <Agafonov> sinzui: that was completely my fault so thank you for help
[22:50] <Kangarooo> im still getting OOPS-1643H1500
[23:31] <getxsick> hmm interesting, i received an email that one build failed, however it's still in a queue