IRC logs for #automotive for Friday, 2016-06-10

*** FelixH has quit IRC00:17
*** FelixH has joined #automotive00:17
*** albanc has quit IRC00:17
*** albanc has joined #automotive00:20
*** Tarnyko has quit IRC00:27
*** IOBN has quit IRC01:29
*** IOBN has joined #automotive01:31
*** AlisonChaiken has joined #automotive03:34
*** jobol has joined #automotive06:59
*** leon-anavi has joined #automotive07:03
leon-anavimorning07:03
*** fredcadete has joined #automotive07:05
*** CTtpollard has quit IRC07:10
*** rajm has joined #automotive07:10
*** CTtpollard has joined #automotive07:13
*** shout-user18 has joined #automotive07:31
*** shout-user18 has left #automotive07:31
*** Tarnyko has joined #automotive07:38
*** kooltux_ has joined #automotive07:50
CTtpollardmorning all07:52
fredcadetegood morning08:09
*** kooltux_ has quit IRC08:15
*** toscalix has joined #automotive08:16
*** rajm has quit IRC08:20
*** rajm has joined #automotive08:21
Tarnykomorning08:32
*** jonathanmaw has joined #automotive08:34
toscalixmorning08:49
*** sanjeev has quit IRC08:56
jbocklage2german, but mabye you get the point: http://www.heise.de/developer/meldung/Qt-will-mit-einer-eigenen-Suite-ins-Auto-3233599.html?wt_mc=rss.developer.beitrag.atom09:09
jbocklage2it mentions AGL: http://www.heise.de/developer/meldung/Qt-will-mit-einer-eigenen-Suite-ins-Auto-3233599.html?view=zoom;zoom=109:11
toscalixby twiter I asked yesterday the Qt company if they see AGL and GENIVI only as middleware09:31
toscalixthey did not answer. I will ask formally09:31
toscalixbut the block diagram is misleading, in my opinion09:31
toscalixspecially in the case of AGL09:32
toscalixwell, in both cases09:32
Tarnykotoscalix: interesting diagram, thanks09:38
Tarnykotoscalix: I suppose their automotive parts are the red ones ; it consists mostly in an Application Framework and its backends (plugins ?) apparently09:39
rjekAll block diagrams have to be simplified in order to fit onto one page/slide, and that simplification causes them to become outright lies.09:40
rjekIf things were actually that simple we'd all be much happier, though09:40
Figuretoscalix: if you look it from the ui perspective only then yes GENIVI and AGL are mostly visible as middleware09:50
Figuremaybe middleware is not the right wording09:50
Figurebut in a sense app developers would be using Qt API's that transfer/translate information to GENIVI middleware09:51
Figuretoscalix: in our vision Application Manager replaces weston completely and removes the need for over complex buffer transfer in current layer management09:53
Figurethat's my 2 cents09:53
CTtpollardFigure: what vision is that out of interest?09:55
toscalixFigure: is that similar to the approach with QNX?09:55
FigureCTtpollard: Application Manager would implement QtCompositor API and be responsible of controlling the wayland layers.09:57
Figuretoscalix: QNX is a bit difference since we can't use directly the QtCompositor API. In QNX we need to play around with the QNX screen that should be able to do same things as wayland09:58
toscalixFigure: got it09:59
FigureCTtpollard: the compositor codes are available @ http://code.qt.io/cgit/qt-apps/neptune-ui.git/10:01
CTtpollardFigure: cool, will take a look10:03
Figurealso all the other parts are open as well10:03
Figurehttp://code.qt.io/cgit/10:04
toscalixFigure: good stuff10:13
toscalixWill be a talk about it at QtCon ?10:13
Figuretoscalix: not sure I haven't followed who from our side goes to QtCon10:20
FigureI've been busy optimizing boot time :)10:20
Figurecurrent number is 1.266ms cold boot to our cluster demo10:20
Figureinitial was 1.560 http://blog.qt.io/blog/2016/04/20/fast-booting-qt-devices-part-1-automotive-instrument-cluster/10:21
fredcadeteFigure: could you detail how an compositor that doubles as application manager would simplify buffer *transfer* ?10:25
fredcadeteI understand how it would simplify management of buffer display10:26
fredcadetebut qtwayland still uses the wayland API, wayland_egl and stuff between the applications and the compositor10:26
fredcadeteor not, please correct me if I am wrong10:27
*** mdurnev has joined #automotive10:34
Figurefredcadete: your are correct. It simplifies tha managet of buffer displays not the transfer it self10:37
Figurefredcadete: also it allows that if end user want's they can also implement first class application that would run inside the application manager10:37
Figurefredcadete: those would have direct access to the gpu so no wayland over head at all10:37
Figureof course this comes with the cost that you really need to trust those applications. since if they crash then crashes the compositor also10:38
fredcadeteok thanks10:39
Figurefredcadete: also with the qtcompositor api you can easly run shader programs over wayland surfaces so for example blurring application behind when popup comes would be really easy10:39
fredcadeteyes, that's the kind of things that are much much easier to do directly in the compositor10:40
Figuresame of course applies to animations etc since in the end it's just a qml engine also running so I would imagine that having custom transformation for wayland buffers would be nice way to animate opening and closing of the application10:40
fredcadeteI don't mean to nitpick much more (sorry...), but wayland applications outside the compositor do have direct access to the GPU, just not to the display10:41
fredcadeteanimations and resize are very tricky with an external layer manager, I have white hairs that prove it10:41
Figurefredcadete: well it's good to correct if some one else is reading this also. Anyhow that's completely true.10:42
fredcadetegreat :)10:42
fredcadeteI can also say from my experience that having rich UI effects in the compositor with a framework familiar to HMI developers probably makes it easier to transition from a monolithic application to separate components10:43
*** gunnarx has joined #automotive10:44
gunnarxHi10:44
fredcadeteresizing/overlay animations are always what HMI developers ask for when you propose composited components10:44
gunnarxHMI developers...10:46
FigureHi10:46
gunnarxI better not finish that thought :-)10:46
gunnarxfredcadete, On recent Volvo systems the ask is more like:  Zoom this out by 12%, blur it and keep it in the background, split this item in two and let it fly in from z axis, and display everything on top of each other at 60fps. :-P10:48
Figuregunnarx: exactly where QtCompositor api comes handy :P10:49
gunnarxYes, I am not disputing that.10:49
Figuregunnarx: that was something we were discussing before you joined10:50
gunnarxGot it10:50
gunnarxAt least what can be seen in production now got some of it.  It's acceptable but we can do even better soon.  Obviously can't go into any more details.10:50
gunnarxCTtpollard, where are we with Go stuff.  Did we have some more things to sort out or any news since yesterday?10:51
gunnarxand pedroalvarez if you're there...10:51
pedroalvarezthings seems to be working so far10:52
CTtpollardgunnarx: just sent a simple PR to g-d-p.git to test those 4 pipelines, one has failed due to a non related issue but it is reporting10:52
CTtpollardhttps://github.com/GENIVI/genivi-dev-platform/pull/1710:52
*** rosch has quit IRC10:53
gunnarxGood.  I'm thinking about some minor tweaks.  Grouping of pipelines.  GDP_Maintenance - how about calling it something with Pull_Request_Testing (so it's more obvious why these may be failing once in a while)10:53
pedroalvarez+110:53
gunnarxMind if I restructure a bit (I usually just do it :-)10:53
*** rosch has joined #automotive10:54
pedroalvarezI don't mind, please go ahead10:54
gunnarxdon't want to step on the revered GDP maintenance team's delicate toes.10:54
* CTtpollard puts on steel-toecap boots 10:54
gunnarxawesome10:56
CTtpollardsure go ahead10:56
CTtpollardleon-anavi: have you ever had meta-rust fail to fetch a snapshot in rustc-1.7.0?10:57
leon-anaviCTtpollard, hm, no but I haven't recently tried it out.10:59
leon-anaviDo you have such a problem?10:59
CTtpollard'curl: (77) error setting certificate verify locations'10:59
CTtpollardone moment11:00
CTtpollardleon-anavi: http://paste.baserock.org/kowiticofu11:00
CTtpollardon of our pipelines failed with that11:00
leon-anavihm...11:04
leon-anaviis any of the other pipelines having the same issue?11:04
CTtpollardthe other target pipelines building the same PR have not failed yet, although qemu is the only one so far too finish11:05
CTtpollardwill keep an eye out11:05
leon-anaviok11:05
leon-anaviping me when you have results11:05
gunnarxAnyone familiar with "my-genivigo-testagent" that has popped up?11:07
CTtpollardnope11:08
jbocklage2(just for completeness: https://blog.qt.io/blog/2016/06/08/announcing-the-qt-automotive-suite/ )11:14
gunnarxI feel like it is "announced" over and over again. ;-)11:49
*** IOBN has quit IRC11:55
Figuregunnarx: now the source code is actually available :)12:00
gunnarxAh yes, I could see it was (new) implementation that was the news here12:02
gunnarxAlthough v1.0 planned to be tagged end of the month it seems12:02
*** praneeth has quit IRC12:06
*** praneeth has joined #automotive12:07
gunnarxpedroalvarez, CTtpollard you might want to study the pipeline group: Administration_for_codethink-genivigo-agent1-x86 and the wipe-temp-dir job .  For the others I have set it to run on a timer once a week.  I didn't want to force it onto your agent unless you think it's a good idea.13:19
pedroalvarezI think it's a good idea, will look into it13:20
CTtpollardnot sure if I have access to be able to view that13:20
gunnarxThe Parameters tab on the pipeline is important.13:21
gunnarxCTtpollard, do you see the pipeline group?  the pipeline?13:23
CTtpollardI can see the pipelines, but I get a different view of the xml compared to pedroalvarez13:23
gunnarxCTtpollard, can you access any templates at all?13:23
CTtpollardand I have no options to modify anything on the agent tab13:23
CTtpollardyes I can access the templates, but not in xml form13:24
gunnarxwell that's by design ;)13:24
gunnarxNo only pedroalvarez is l33t enough.13:24
pedroalvarezmuahah13:24
gunnarxYou want to edit XML CTtpollard?  I can make it happen.  But it's a masochistic behavior.13:25
gunnarxOnly admin can use the backdoor of hacking the XML directly, I guess it makes some sense - it is quite easy to wipe out the whole configuration in one go.13:27
pedroalvarezgunnarx: btw, I've seen some sort of backup in github of the XML13:34
CTtpollardgunnarx: I'm ok to not have this responsibility for now13:35
gunnarxpedroalvarez, that is correct.  It is backed up once an hour IIRC13:36
pedroalvarezcool13:36
gunnarxjust a feature I added when I first installed Go13:37
gunnarxpretty useful.13:37
pedroalvarezgunnarx: regarding "wipe_dir_pattern" template, it has hardcoded some /var/lib/.. paths13:37
gunnarxoh13:37
pedroalvarezbut anyway it can run in our  server anyway13:37
gunnarxah yes I guess it has hard coded the standard installation path of go-agent, yes13:37
gunnarxGo internally puts the config in git so it was just a matter of adding an ssh key to a github account and a cron job that does git push.13:38
gunnarxThe git history is a useful audit log if required so it makes it more secure also.13:39
pedroalvarezgunnarx: I was actually pondering cleaning all of /var/lib/go-agent/pipelines/13:49
gunnarxSure if you wish.  Generally I think downloads should remain.13:50
gunnarxWe should align on whether to reuse DL_DIR or use PREMIRRORS13:50
gunnarxSome part of me felt it safer to copy to a fresh DL_DIR but from a local mirror.  I'm not sure it matters but that's what I thought13:50
gunnarxAt least it's a local file copy rather than using bandwidth13:50
gunnarxI think this is repetition, but I've settled on /var/cache/yocto/downloads as my preferred path13:51
pedroalvarezthat would be for DL_DIR, right?13:52
gunnarxdamn there is a "gunnarx2" in github.13:53
pedroalvarezhaha13:53
* gunnarx 'gonna have to go Highlander on him13:55
gunnarxpedroalvarez, yes either DL_DIR or local mirror.  It can be both I suppose.14:01
pedroalvarezI'm ok for enabling /var/cache/yocto/download instead of /srv/go/dl in our pipelines14:05
pedroalvarez"ct_test" resource has to die :)14:06
gunnarx+114:18
CTtpollardI think building each target for every commit to g-d-p also has to die, in terms of that being the trigger14:18
gunnarxunless we can very heavily optimize the build?14:19
gunnarxI'd like to see reliable incremental builds on those quick checks14:19
gunnarxwith reused sstate etc.14:19
*** mdurnev has quit IRC14:20
CTtpollardI'd want to switch to time based polling in those pipelines, at least until we have more agent bandwith14:20
gunnarxsure, we can do that14:21
gunnarxit's a good idea14:21
CTtpollardbut they do still server a purpose, just because a PR pipeline built fine doesn't mean it will once it is merged14:22
*** AlisonChaiken has quit IRC14:22
CTtpollarde.g other PR's could be merged during that time window, which just so happen to break the PR that at the time built ok14:22
gunnarxyes14:23
CTtpollardbut still, building per 24h would catch such small chances14:23
gunnarxsounds good to me.  With the timer setup in cron format it can be spaced over time14:35
gunnarxSo which one should be triggered first is the question :)14:36
CTtpollardqemu14:39
*** oscaletta has joined #automotive14:42
CTtpollardif that daily is broke, then we're doomed14:43
fredcadeteI have been reusing sstate for my development builds and it has been going well14:43
fredcadeteI did have issues with some things like for example Renesas kernel modules, so I hesitate to use it on CI14:44
fredcadetereusing sstate on CI should work as long as the build does not involve rebuilding the kernel modules14:45
CTtpollardI've had problems with unpacking navit from sstate before across different builds14:45
fredcadetethat will have worse effects than the kernel module, because I imagine navit is nearer the tips of the dependency tree and is rebuilt more often14:46
fredcadeteanyway, it should be a matter of analyzing the offending recipes and go Yocto IRC help on them14:47
fredcadetemaybe manually correcting the sstate directories for those packages : http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#shared-state14:48
fredcadetesuch a simple and fun thing to do that I have spent about 2 months thinking of it and never started it14:49
CTtpollardfredcadete: friday afternoon sounds the perfect time to start then!14:49
fredcadeteit's also a great prank for a newbie in the team14:50
fredcadete"easy starter task, just make this sstate thing work. report back this afternoon"14:51
fredcadetethe last rookie here was unfortunately too good to try this, he would have caught on to it14:52
gunnarxaaaah, great rookie task :)14:55
gunnarxsstate looks like some black art magic for sure...14:56
gunnarxnot that I have looked into it.14:56
*** CTtpollard has quit IRC14:57
gunnarxWhen I've been really upset with Yocto, I have however considered a loop that builds one package, commits the entire build state to git, build one more package, commit to git, and so on...!14:57
gunnarxBut that would probably make the whole build totally predictable and turn Yocto into Baserock... so that can't be right ;-)15:00
*** CTtpollard has joined #automotive15:01
*** rajm has quit IRC15:01
*** oscaletta has quit IRC15:05
*** Tarnyko has quit IRC15:06
*** rajm has joined #automotive15:13
*** AlisonChaiken has joined #automotive15:15
*** mvick has quit IRC15:17
*** mvick has joined #automotive15:19
toscalixgunnarx: all CTs are in a meeting...otherwise they would have jumped like popcorn15:33
gunnarx:)15:33
*** CTtpollard has quit IRC15:36
*** rajm has quit IRC15:37
*** rajm has joined #automotive15:37
*** jonathanmaw has quit IRC15:49
*** gunnarx has quit IRC15:52
*** toscalix has quit IRC16:11
*** jonathanmaw has joined #automotive16:12
pedroalvarezhahah16:14
pedroalvarezbelieve me, baserock is not about pushing binaries to git to get reproducible builds :)16:15
*** rajm has quit IRC16:15
*** fredcadete has quit IRC16:16
*** nisha has quit IRC16:21
*** nisha has joined #automotive16:26
*** leon-anavi has quit IRC16:28
*** jlrmagnus has quit IRC16:46
*** jobol has quit IRC16:52
*** jonathanmaw has quit IRC16:54
*** Tarnyko has joined #automotive17:39
*** jlrmagnus has joined #automotive17:50
*** chbae has joined #automotive18:33
*** chbae has quit IRC19:06
*** jlrmagnus has quit IRC19:07
*** clopez_ is now known as clopez20:06
*** AlisonChaiken has quit IRC21:46
*** AlisonChaiken has joined #automotive21:49
*** mvick has quit IRC23:11
*** e8johan has quit IRC23:48
*** AlisonChaiken has quit IRC23:57

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