**** BEGIN LOGGING AT Wed Dec 19 03:00:02 2018 Dec 19 12:36:33 JaMa: ok, I have now 4 hours of train to kill, and a not-so-great internet connection; I'll try the latest unstable build :) Dec 19 12:54:07 Tofe: cool, try unstable-rocko Dec 19 12:54:33 sumo and thud might have some other issues as well, it will be better to fix them one-by-one Dec 19 12:54:42 already downloading it, between 30Ko/s and 1.8Mo/s :) Dec 19 12:54:44 I'm still working on vboxtouch Dec 19 12:59:17 I'll merge 5.11.3 qt upgrade later today Dec 19 13:05:11 ok, good Dec 19 13:05:18 I'm flashing tissot now Dec 19 13:17:04 bootloop on tissot, no recovery: same status as elvispre; I'll compare the boot images Dec 19 13:27:25 small fix in gtest caused another qtwebengine rebuild for me, damn I need to buy faster builder Dec 19 13:30:34 JaMa: so far I don't see any obvious fatal change in initrd or boot image Dec 19 13:34:25 "SystemCallArchitectures=native" has been added to udev service, it's the only change Dec 19 13:35:50 but even that wouldn't explain recovery not booting Dec 19 13:36:09 so it must could be the kernel, but how?... Dec 19 13:37:41 IIRC in pyro we're still using gcc-5, but rocko has gcc-7 Dec 19 13:38:15 hmm 6.4 in pyro, but probably still 7 in rocko Dec 19 13:38:52 there were few patches to fix building with gcc-7, but there might be some runtime issues left Dec 19 13:39:06 I can trigger new rocko build with older kernel to test this Dec 19 13:41:24 JaMa: I can try repacking the boot image with a pyro kernel Dec 19 13:41:49 please do Dec 19 13:49:11 success ! rocko is booting Dec 19 13:49:37 sound & graphics work, touch too, etc Dec 19 13:50:07 So it is the kernel built with gcc-7 that is the issue. Dec 19 13:50:27 seems so yes Dec 19 13:50:43 that'll be a wonderful thing to debug... Dec 19 13:53:27 :) Dec 19 14:00:35 Can you see this? The power of Yocto - https://photos.app.goo.gl/SfLH7iqZCtXFfCvh8 (A webOS OSE build, from the other day, I think.) Dec 19 14:02:24 JaMa: do we have this? https://github.com/nathanchance/angler/commit/1d351648bb246e2826ff10399ec0f3c4f855cf2f Dec 19 14:03:40 elvispre: nice! Dec 19 14:04:31 Tofe: You need a lot of RAM once the qt builds all start trying to run at once. Dec 19 14:05:12 yes, that build of yours would overload my little 16Gb quickly :) Dec 19 14:06:12 Anyway with 4 yocto threads and make -j 4, I'm always with CPU at 100%, so I guess I can't do much more Dec 19 14:10:56 JaMa: I don't see this option on the tissot Makefile, that could be worth a try. Though it'll be a while until I can decently build a kernel here... Dec 19 14:11:56 Tofe: looks good Dec 19 14:12:14 I won't build it much faster here Load average: 19.84 19.90 21.81 Dec 19 14:12:30 qtwebengine+qtwebkit+qttools at the same time :/ Dec 19 14:13:21 ouch, I see :) Dec 19 14:13:42 Tofe: can you push the change to kernel repo? I'll trigger it on jenkins Dec 19 14:14:08 JaMa: yes, we can try that way Dec 19 14:15:23 * JaMa reconfiguring unstable to do rocko again Dec 19 14:17:56 ready from my end Dec 19 14:17:59 https://github.com/Tofee/tissot/commit/a8412322dc34a81517cfdb9f4ef1c75bcf263ad0 Dec 19 14:18:34 I'll update ./meta-xiaomi/recipes-kernel/linux/linux-xiaomi-tissot_git.bb Dec 19 14:18:41 perfect Dec 19 14:21:24 http://jenkins.nas-admin.org/view/luneos-unstable/job/luneos-unstable_tissot/19/console Dec 19 15:52:54 For the others we'd need to push the change upstream to Halium Dec 19 16:02:33 it's still building qtwebengine :/ Dec 19 17:12:04 Tofe: almost done if you're still bored in train :) Dec 19 17:13:07 damn 3 hour build Dec 19 17:13:20 "still building qtwebengine" story of my life Dec 19 17:14:04 that's why we need qtwebengine-less luneui-example-image for debugging issues like this Dec 19 17:14:13 or even smaller in this case Dec 19 17:14:20 or in my case a new Thinkpad Dec 19 17:15:20 building qtwebengine on any Thinkpad doesn't looks like fun Dec 19 17:15:53 there's a new one with a six-core Xeon Dec 19 17:16:06 I'll find out Dec 19 17:16:39 that's still 1/10 power of nice build server Dec 19 17:17:11 yes, but a lot better than the 6th-gen dual-core i5 I build it on currently :-) Dec 19 17:17:42 Sho_: lol. that was my entire life about 5 years ago when it took about 9 hours to build a webos system Dec 19 17:17:50 I have 1st gen bulldozer 8core @home so I agree Dec 19 17:18:06 I work on KDE Plasma myself, similar stack Dec 19 17:18:30 but a lot better isn't enough for me, I want more :) Dec 19 17:19:30 new 5K $ rig would be much faster, but still annoyingly slow for really big builds Dec 19 17:19:46 $5k is about that Thinkpad, too, all decked out Dec 19 17:20:20 if I push my changes to CI I can max-out 20+ servers for whole day :) Dec 19 17:21:14 BTW, I'm trying to understand the relationship between webos-ports and LGE better - are you guys in contact with them, is code flowing both ways, ...? Dec 19 17:31:07 fwiw, i'm presently employed by LG, but not in this capacity. i try to help. :-) Dec 19 17:31:23 * Sho_ waves Dec 19 17:31:31 i have absolutely no contact with the people who are employed in that capacity unfortunately Dec 19 17:31:42 I have a meeting with webOS leadership in Gangnam on Friday, that's why I'm scoping out the community a bit more Dec 19 17:37:50 Sho_: It's complicated LOL ;) Dec 19 17:38:08 always is Dec 19 17:39:47 There was HP who open sourced webOS 1st time and there was collaboration. Then LG worked on it internally and not on public GitHub anymore Dec 19 17:39:58 Last year out of the blue they came with OSE Dec 19 17:40:05 aye Dec 19 17:40:16 Which is basically HP's Open webOS + 4-5 years of development inside LG for various products Dec 19 17:40:22 Ehm this year March I mean Dec 19 17:40:38 so did you rebase your stuff on LG OSE or are you still on the HP branch these days? Dec 19 17:40:59 We're on HP branch, but currently working to move to OSE branches Dec 19 17:41:07 Just LG did a big code dump without history Dec 19 17:41:12 So it's not that straightforward Dec 19 17:41:21 And there are 30 or so repos that need migrating Dec 19 17:41:30 Some with just copyright changes, some with a lot more Dec 19 17:41:36 And we did changes ourselves too ;) Dec 19 17:41:44 So need to see what needs to be put there, upstreamed et Dec 19 17:41:46 +c Dec 19 17:41:53 has LGE officially reached out to webos-ports in any capacity? Dec 19 17:42:07 Yes Dec 19 17:42:09 We met with them in Paris in June Dec 19 17:42:35 And agreed on Xiaomi A1 as common device to work on for LuneOS and OSE Dec 19 17:42:57 And other collaboration and community/open source has been discussed Dec 19 17:43:09 the LGE webOS teams I've met so far are actually doing various R&D things on Raspberry Pis Dec 19 17:43:35 (but I think that's as much as I can say) Dec 19 17:44:22 Sho_: Yeah that's their target, robots as well, we've seen car demo's etc Dec 19 17:44:26 JaMa: The new rocko tissot image works for me (boots at second attempt). It is running First Use as I type. Dec 19 17:44:33 This is all on YouTube so public info Dec 19 17:45:10 We focus on phone & tablets, they focus on everything else with webOS ;) Dec 19 17:46:52 Indeedie Dec 19 17:47:14 But underlying infrastructure is the same or at least should be for a large extend Dec 19 17:47:40 Biggest difference currently is we're on Qt 5.11 and QtWebEngine, they used Chromium and older Qt for their bits Dec 19 17:47:49 But ideally we'd converge there at some point Dec 19 17:48:51 I had a talk with their GStreamer/multimedia folks about the browser engine situation recently Dec 19 17:50:50 elvispre: cool, will add the same to sumo build to see if it is enough there as well Dec 19 18:13:58 Sho_: if i may ask, can you give any details about what you're doing? Dec 19 18:15:13 EricBlade1: Not quite yet, also because nothing may come of it anyways, but I'm wearing my KDE foundation VP hat Dec 19 18:53:24 luneos-dev-emulator-qemux86 with dev-pkgs and dbg-pkgs without DEBUG_BUILD is still 2.3G (464MB without them, 3.4G with DEBUG_BUILD) still too big Dec 19 20:38:06 Sho_: We're looking at where there are synergies and de-duplicating code and upstreaming things where they make sense Dec 19 20:38:18 So eventually there will be a single codebase, at least that's our aim Dec 19 20:38:37 Same like we do with other projects like libhybris/mer/halium etc Dec 19 20:39:10 JaMa: why do you include dev-pkg? Dec 19 20:39:32 Sho_: o/ Dec 19 20:40:51 Tofe: just for easier debug of vboxtouch plugin Dec 19 20:41:05 Tofe: yo Dec 19 20:42:20 Sho_: for the multimedia stack that's one domain where a big convergence might happen; it would mean abandon qtwebengine&libcompat and switch to their chromium plus a gstreamer infra Dec 19 20:43:22 I didn't look at what effort it would mean for us yet though Dec 19 20:43:23 Tofe: I'd recommend you wait until spring to make that call (but can't tell you why :) Dec 19 20:43:53 Sho_: that shouldn't be a problem :) Dec 19 20:45:48 Sho_: are you also involved in plasma mobile with bshah? Dec 19 20:47:24 Tofe: Sorta, I haven't really done much specifically on PlaMo or its support bits, but I'm a core hacker on Plasma in general Dec 19 20:47:35 ok **** ENDING LOGGING AT Thu Dec 20 03:00:01 2018