**** BEGIN LOGGING AT Mon Mar 04 02:59:57 2019
Mar 04 08:17:15 <Herrie|Laptop> Morning!
Mar 04 08:17:33 <Herrie|Laptop> For Athene not sure what happened there. Probably something in TheMuppets that got updated and broke stuff
Mar 04 08:22:22 <JaMa> the diff between old and new workspace is huge 1.4G, but the file exists only in one of them
Mar 04 08:22:39 <JaMa> running the device setup in both to see why it wasnt fetched in the new one
Mar 04 08:23:08 <JaMa> jenkins@bonaire:~$ find  workspace/halium-luneos-7.1-build/halium-luneos-7.1/ halium-old/halium-luneos-7.1/ -name com.motorola.frameworks.core.addon.xml
Mar 04 08:23:11 <JaMa> halium-old/halium-luneos-7.1/vendor/motorola/athene/proprietary/etc/permissions/com.motorola.frameworks.core.addon.xml
Mar 04 08:23:57 <JaMa> jenkins@bonaire:~$ grep vendor workspace/halium-luneos-7.1-build/halium-luneos-7.1/anthene.setup.log halium-old/halium-luneos-7.1/anthene.setup.log
Mar 04 08:24:00 <JaMa> workspace/halium-luneos-7.1-build/halium-luneos-7.1/anthene.setup.log:I: Refreshing device vendor repository: device/motorola/athene
Mar 04 08:24:03 <JaMa> halium-old/halium-luneos-7.1/anthene.setup.log:I: Refreshing device vendor repository: device/motorola/athene
Mar 04 08:26:01 <JaMa> jenkins@bonaire:~/halium-old/halium-luneos-7.1$ grep vendor/motorola .repo/local_manifests/device.xml <project path="vendor/motorola/athene" name="vendor_motorola_athene" remote="lyud" />
Mar 04 08:27:43 <JaMa> different repo is being used for some reason:
Mar 04 08:27:45 <JaMa> -       url = https://github.com/TeamRedStar/android_vendor_motorola_athene
Mar 04 08:27:45 <JaMa> -       projectname = android_vendor_motorola_athene
Mar 04 08:27:45 <JaMa> +       url = https://github.com/Lyudmila17/vendor_motorola_athene
Mar 04 08:27:45 <JaMa> +       projectname = vendor_motorola_athene
Mar 04 08:28:36 <JaMa> jenkins@bonaire:~/workspace/halium-luneos-7.1-build/halium-luneos-7.1$ grep vendor/motorola .repo/local_manifests/device.xml <project path="vendor/motorola/athene" name="android_vendor_motorola_athene" remote="lyud" />
Mar 04 08:29:55 <JaMa> in device.xml it looks the same except (android_)vendor_motorola_athene with the prefix used only in the new workspace
Mar 04 08:32:08 <JaMa> device.xml diff: https://paste.ubuntu.com/p/wXK6rkdB55/
Mar 04 08:33:18 <JaMa> so it's halium/devices$ cat manifests/motorola_athene.xml
Mar 04 08:33:24 <JaMa> difference
Mar 04 08:35:03 <JaMa> changed in this commit https://github.com/Halium/halium-devices/commit/404c784cebd76722df0b8f8882612b2908c677da
Mar 04 08:40:58 <JaMa> the missing xml files was removed from proprietary-files.xml a while ago, but in different branch: https://github.com/TeamRedStar/android_device_motorola_athene/commit/efb60ac8440e10d30ef5e3002616d764ee5c3a87
Mar 04 08:43:37 <JaMa> oh, it was only moved
Mar 04 08:45:01 <JaMa> removed in https://github.com/TeamRedStar/android_device_motorola_athene/commit/755cb44ed9aeea90d9eabbef9434c65c1d4a08e7#diff-e18a190ec9e1d301d38ff968dea34a59
Mar 04 08:53:26 <Tofe> That's the issue when relying on repos that don't have Halium in mind
Mar 04 08:55:47 <Herrie|Laptop> Tofe: Well Lyudmila17 is part of TeamRedStar and did the Halium port
Mar 04 08:55:51 <Herrie|Laptop> So it's a bit weird ;)
Mar 04 08:56:40 <Tofe> ah, ok... weird indeed...
Mar 04 08:59:01 <Tofe> JaMa's commit doesn't seem to be present in the "halium-7.1" branch
Mar 04 08:59:05 <JaMa> there are also some uncommited changes applied on top of vendor/motorola/athene looks from LineageOS
Mar 04 08:59:24 <JaMa> Tofe: the 1st one (which moved it) is, the 2nd isn't
Mar 04 09:01:30 <JaMa> I can revert the jenkin-job.sh change to restore the halium-devices override, but I have no idea what else we might be missing from this newer athene port or other halium-devices changes
Mar 04 09:05:01 <JaMa> or we can PR removal of this file like previous Herrie cleanup :) https://github.com/TeamRedStar/android_device_motorola_athene/commit/ef6f5bfb2b5ce44b3d1609b4755402abb49706ea but I have no idea what this xml file does :)
Mar 04 09:05:12 <Herrie|Phone> We could simply drop Athene. Anyway we never got a working image
Mar 04 09:05:31 <JaMa> that works for me as well :)
Mar 04 09:05:59 <Herrie|Phone> If people want to be bothered can always put it back again
Mar 04 09:08:59 <Herrie|Phone> We can quickly try that
Mar 04 09:09:31 <Herrie|Phone> I mean to change the proprietary-files.txt
Mar 04 09:09:45 <Herrie|Phone> XML not likely very needed
Mar 04 09:10:00 <Herrie|Phone> It's moto stuff we don't really use anyway
Mar 04 09:10:31 <JaMa> ok, remove
Mar 04 09:10:33 <JaMa> d
Mar 04 09:10:48 <JaMa> https://github.com/webOS-ports/jenkins-jobs/commit/44126922cc5dbb52a91db459ecd0c585df61ae2f
Mar 04 09:11:33 <JaMa> I'll trigger new build now, to confirm that new workspace works, before deleting the old backup
Mar 04 12:09:11 <Herrie|Laptop> JaMa/Tofe: The reason for not picking up the upstream 7.1 changes might be that we're missing running: https://github.com/webOS-ports/android/blob/luneos-halium-7.1/update-halium-subtree.sh ?
Mar 04 12:55:32 <Tofe> Ah, that could be, it would be a good idea to update it yes
Mar 04 12:56:22 <Tofe> The good way to use that is to checkout our repo, then run the script, and commit the result
Mar 04 12:56:57 <Tofe> though we could simply do a test run with calling the script on the fly
Mar 04 13:46:45 <Herrie|Laptop> JaMa: I noticed there's a timestamp missing here: http://build.webos-ports.org/luneos-unstable-thud/images/hammerhead/
Mar 04 13:46:49 <Herrie|Laptop> In the filename
Mar 04 15:58:04 <Herrie|Laptop> On Thud for Hammerhead I get: https://bpaste.net/show/571e4d447585
Mar 04 15:58:57 <Herrie|Laptop> Output is a bit garbled, because it bootloops, so I couldn't pull a clean /proc/last_kmsg. Seems it doesn't like something in init/partition: "[    .5833] inItrd: PANIC for Peason: Couldn't find data pArtition"
Mar 04 16:03:05 <Herrie|Laptop> This is a "clean" Hammerhead on which I never used LuneOS. Maybe I should check a working image first :P
Mar 04 16:29:40 <Herrie|Laptop> OK stable release works, so device seems fine :P
Mar 04 16:57:29 <Herrie|Laptop> If I flash boot.img from Doppio release to try to boot Thud image I get: https://bpaste.net/show/cc0d169c9473
Mar 04 17:01:09 <JaMa> there is another kernel fix needed even with gcc7, let me check
Mar 04 17:01:45 <JaMa> https://github.com/shr-distribution/meta-smartphone/commit/1199e2735917dda5e263a992f7657e1a5d4a20ae
Mar 04 17:01:49 <JaMa> this one from tissot
Mar 04 17:03:23 <JaMa> but that shouldn't cause [    6.507468] systemd[1]: Failed to determine whether /sys is a mount point: Bad file descriptor
Mar 04 17:13:10 <Tofe> It looks like the sideload didn't go well, somehow
Mar 04 17:13:24 <Tofe> I'll also check on my N5
Mar 04 17:13:42 <Tofe> It's been off a long time, since last stable
Mar 04 17:31:57 <Tofe> mmmh "initrd: PANIC for reason: Couldn't find data partition."
Mar 04 17:33:14 <Tofe> that newer gcc isn't going to be my friend...
Mar 04 17:38:54 <Tofe> JaMa: do you know if there has been some pulseaudio-related changes between rocko and sumo ?
Mar 04 17:39:22 <Tofe> I'm wondering why I don't get any sound with sumo, while PA seems to work
Mar 04 18:02:02 <JaMa> Tofe: there is newer version in sumo, our local patches weren't too different after rebase: https://github.com/webOS-ports/meta-webos-ports/commit/c29c9cdc30a64a2b66ee9f52892a978bd335e98d
Mar 04 18:02:09 <JaMa> gtg for a bit
Mar 04 18:08:47 <Tofe> JaMa: thanks; I'll also check on the pa-modules-droid side, just in case
Mar 04 18:09:41 <Tofe> https://github.com/webOS-ports/meta-webos-ports/blob/thud/meta-luneos/recipes-multimedia/pulseaudio/pulseaudio-modules-droid_git.bb#L33 mmmh "10.0" ... could it be simply the wrong directory ?
Mar 04 18:11:33 <Tofe> yup, PA went from 10.0 to 11.1 from rocko to sumo, and this pulseaudio-modules-droid seems to put its files in the wrong directory.
Mar 04 18:12:03 <Tofe> Maybe we could devise a way to put them always in the right folder, but I'm not sure how
Mar 04 18:12:18 <Tofe> I'll PR the fix anyhow
Mar 04 18:18:54 <Tofe> JaMa: https://github.com/webOS-ports/meta-webos-ports/pull/314 <-- I've also included my last commits from pyro, that should also fix virtual keyboard
Mar 04 18:19:05 <Tofe> meaning, a-priori, we're good to go on sumo
Mar 04 18:22:22 <Tofe> At some point it could also be a good idea to bump pulseaudio-modules-droid's srcrev
Mar 04 19:37:47 <Herrie|Laptop> Tofe: Why not now :P ?
Mar 04 19:38:00 <Tofe> Just checking the build :)
Mar 04 19:38:20 <Herrie|Laptop> Tofe: How's your Hammerhead behaving?
Mar 04 19:38:30 <Tofe> Herrie|Laptop: exactly the same as yours
Mar 04 19:38:49 <Herrie|Laptop> Tofe: OK
Mar 04 19:38:57 <Herrie|Laptop> Could be the 3.4 kernel with systemd again?
Mar 04 19:39:08 <Herrie|Laptop> Or we're at older systemd with sumo still
Mar 04 19:39:17 <Tofe> for the userdata issue, that's gcc probably
Mar 04 19:39:44 <Tofe> I didn't test sumo on hammerhead
Mar 04 19:40:31 <Tofe> Also it seems that gcc makes Qt (the rendering part) crash on tissot
Mar 04 19:40:57 <Herrie|Laptop> Tofe: Ah sorry I meant Thud
Mar 04 19:41:15 <Tofe> not sure what version thud uses for systemd
Mar 04 19:41:22 <Herrie|Laptop> 2.39
Mar 04 19:41:37 <Herrie|Laptop> 239
Mar 04 19:41:45 <Herrie|Laptop> 237 on Sumo it seems
Mar 04 19:41:56 <Herrie|Laptop> Both probably problematic with 3.4 kernels
Mar 04 19:42:01 <Tofe> ok; so that's a possibility yes
Mar 04 19:43:22 <Tofe> bump PR'ed
Mar 04 19:43:54 <Herrie|Laptop> We're on 232 in pyro
Mar 04 19:44:14 <Tofe> If sumo works well on hammerhead and tissot I think we can switch testing to this level
Mar 04 19:44:56 <Tofe> though I'm not sure what will happen with qemu target if we do that
Mar 04 19:44:59 <Herrie|Laptop> Tofe: Yes, I guess testing tenderloin wouldn't hurt
Mar 04 19:45:09 <Herrie|Laptop> qemu is broken in pyro currently too
Mar 04 19:45:14 <Herrie|Laptop> So not much we lose ;)
Mar 04 19:45:21 <Tofe> well, yes :)
Mar 04 19:46:13 <Tofe> tenderloin too, yes; I was mainly thinking in terms of kernel versions and architectures
Mar 04 19:49:11 <Herrie|Laptop> Tofe: Couldn't we introduce another variable in the recipe called PAV or something where we set the pulseaudio version and then have PV consist of PAV etc. Something like: https://bpaste.net/show/21b08ed90ac7
Mar 04 19:49:21 <Herrie|Laptop> I haven't tested this ,just quickly drafted on bpaste :P
Mar 04 19:54:55 <Tofe> That's a good idea; I was trying to extract PA's version somehow, but maybe it's just hopeless :)
Mar 04 19:56:25 <Tofe> let me reorganize a bit my PR commits
Mar 04 19:59:18 <Tofe> https://github.com/webOS-ports/meta-webos-ports/pull/314/commits/ca6248dc456418139d3f0c5f9d24964611b891a6 ?
Mar 04 19:59:44 <Tofe> Not build-checked, though
Mar 04 20:04:21 <Tofe> ^ seems alright !
Mar 04 20:04:58 <Tofe> JaMa: do you see a problem with https://github.com/webOS-ports/meta-webos-ports/pull/314  ?
Mar 04 20:05:17 <JaMa> will check after another reboot, something is wrong with this fs
Mar 04 20:42:10 <Herrie|Laptop> Tofe: I suspect we'll probably need some more namespaces goodness to be patched into 3.4 but I could be wrong of course. Found some references: https://github.com/pascua28/Elite-Boeffla-Kernel/commit/af0f87fb2b36a75fc44b92b3d3792959d889c9b5 and https://github.com/aosp-mirror/kernel_common/commits/457adc35f6e50337b8246063c9df37bfc08b6d4e and https://github.com/Samsung-KYLEPROXX/android_kernel_samsung_kyleproxx/commits/1c8f40
Mar 04 20:42:12 <Herrie|Laptop> https://github.com/LineageOS/android_kernel_oppo_msm8974/commits/lineage-16.0
Mar 04 20:42:32 <Herrie|Laptop> And https://lore.kernel.org/patchwork/patch/217023/
Mar 04 20:42:38 <Herrie|Laptop> Just so we have some references logged for now
Mar 04 20:50:27 <Herrie|Laptop> And some more: https://lists.linuxfoundation.org/pipermail/containers/2012-November/031023.html
Mar 04 21:01:05 <Tofe> we'll see... Let's keep hope that it might be solved in an easy way :)
Mar 04 21:15:29 <Herrie|Laptop> Tofe: Well it's good to have some reference 3.4 kernels that are more up to date with some patches
Mar 04 21:34:58 <Herrie|Laptop> Tofe: In general the https://github.com/LineageOS/android_kernel_oppo_msm8974/commits/lineage-16.0 seems interesting for quite some 3.4 backports
**** ENDING LOGGING AT Tue Mar 05 02:59:57 2019