/srv/irclogs.ubuntu.com/2017/02/27/#launchpad.txt

=== hggdh_ is now known as hggdh
=== karstensrage_ is now known as karstensrage
=== maclin1 is now known as maclin
=== maclin1 is now known as maclin
=== maclin1 is now known as maclin
=== lan3y is now known as Laney
shadeslayerhey, can you tell me if Launchpad's arm64 builders are somehow specially configured for large memory allocations when building armhf packages?12:19
cjwatsonshadeslayer: probably depends on exactly what you mean, but they have a modified kernel built with CONFIG_ARM64_VA_BITS=48: https://git.launchpad.net/~wgrant/ubuntu/+source/linux/log/?h=arm64-va-3912:36
shadeslayercjwatson: well my cross build on a arm64 machine still fails when ld fails to allocate enough memory12:37
shadeslayer00:29:28.719 /usr/bin/ld.gold: fatal error: libQt5WebEngineCore.so.5.7.1: mmap: failed to allocate 2226595652 bytes for output file: Cannot allocate memory12:37
shadeslayerwhich is a bit odd since the machine has 128 GB's of memory12:37
cjwatsondon't know more, sorry12:37
shadeslayerok :)12:37
shadeslayerperhaps someone else in the channel will :)12:37
shadeslayersomeone suggested I bump nr_hugepages to 2012:38
shadeslayerwhich I've done now to see if it helps12:38
cjwatsonwe aren't doing anything like that AFAIK.  The only other specialised arm64ish thing I'm aware of is that we boot the VMs with compat_uts_machine=armv7l (modulo typos, I don't have the current config file to hand).12:39
wgrantshadeslayer: As Colin says, are kernels are stock xenial plus the patch to unbreak Qt (CONFIG_ARM64_VA_BITS=39, which also reduces the number of page table levels)12:42
wgrantWe've done nothing special to increase address space sizes -- in fact we've shrunk the 64-bit ones.12:42
shadeslayeraha12:42
shadeslayerI have CONFIG_ARM64_VA_BITS=4812:43
cjwatsonYeah, 39, sorry, I misread the git log.12:43
wgrantThat's the default, yeah. It breaks old Qts because they expect to tag their pointers up at like bit 42.12:43
shadeslayerI see12:43
wgrantIt usually manifests as Qt apps segfaulting, not what you're seeing.12:44
shadeslayerold qt?12:44
cjwatsonApparently fixes for that are trickling through to things we might get in updates, so hopefully we can ditch that patch eventually.12:44
wgranthttps://bugreports.qt.io/browse/QTBUG-5482212:44
shadeslayertyvm :D12:44
wgrantBut should be totally unrelated.12:44
shadeslayerright, that's at runtime, but good to know12:45
shadeslayerI'm more curious about the link failiure12:45
cjwatsonI mean in a 32-bit address space it doesn't necessarily matter how much physical memory you have.12:46
cjwatsonbut I'm not sure exactly what you mean by "cross build".12:46
cjwatsonLP doesn't do cross builds.12:46
shadeslayeroh this isn't on LP12:47
shadeslayercjwatson: but then how do you build qtwebengine?12:47
shadeslayerbecause afaict https://launchpadlibrarian.net/308759960/buildlog_ubuntu-zesty-armhf.qtwebengine-opensource-src_5.7.1+dfsg-6build1_BUILDING.txt.gz12:47
shadeslayerhttps://launchpadlibrarian.net/308759960/buildlog_ubuntu-zesty-armhf.qtwebengine-opensource-src_5.7.1+dfsg-6build1_BUILDING.txt.gz12:47
shadeslayerer12:47
shadeslayerKernel version: Linux bos01-arm64-005 4.4.0-64-generic #85+buildd1-Ubuntu SMP Wed Feb 22 12:26:21 UTC 2017 aarch6412:47
cjwatsonwe build in an armhf chroot rather than cross-building.12:48
cjwatsoncross-building usually refers to building with tools from one architecture but generating code to run on another.12:49
cjwatsonin this case we're using armhf throughout, but in a chroot running atop an arm64 base system (and kernel).12:49
shadeslayerah ok, that's what I'm doing too, armhf docker container ontop of a arm64 one12:50
shadeslayer*arm64 host12:50
shadeslayerit's a bit odd that it compiles just fine on Launchpad but not on my machine13:53
=== yofel_ is now known as yofel
shadeslayercjwatson: wgrant JFYI apparently Debian ships the patch to Qt for this14:34
shadeslayerso maybe you don't need that anymore?14:35
cjwatsonit's making progress, but it needs to be in all series etc.14:35
shadeslayer*that config option14:35
cjwatsonI think Mirv is looking after that on our side14:35
shadeslayerah ok :)14:36
Mchi16:54
Mcjust to signal that bots have started posting comments to bug reports that they did not open themselves (i don't recall that happening before in bugs.lp)16:55
Mchttps://launchpad.net/~pop6216:55
=== jik is now known as Guest949
Guest949Launchpad down?17:00
cjwatsonGuest949: it looks OK from here and our graphs seem fine17:01
Guest949Just came back.17:01
Guest949I got several "Something went wrong, check twitter or freenode IRC" errors in a row before it came back.17:02
Guest949i.e., the problem clearly wasn't on my end with my network, given that I got the launchpad error page in my browser.17:02
cjwatsonMc: doing some cleanup, thanks17:05
Mcthanks :)17:08
McI'm losing the battle on lp answers spam18:35
McI can find no regexes for my procmailrc to filter out that new spam that asks questions similar to real ones18:36
McIt's just too similar to real questions18:36

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