IRC logs for #automotive for Thursday, 2016-06-09

*** jlrmagnus has quit IRC00:07
*** mdurnev has joined #automotive00:09
*** chbae has quit IRC00:20
*** AlisonChaiken has quit IRC00:41
*** tjamison has left #automotive00:58
*** jackjack has joined #automotive04:12
*** jackjack has left #automotive04:29
*** Tarnyko2 has quit IRC05:10
*** jobol has joined #automotive05:23
*** DSVenky has quit IRC05:23
*** mdp has quit IRC05:25
*** leon-anavi-cloud has quit IRC05:25
*** Tartarus has quit IRC05:25
*** albanc has quit IRC05:25
*** jjardon has quit IRC05:25
*** FelixH has quit IRC05:25
*** leon-anavi-cloud has joined #automotive05:26
*** FelixH has joined #automotive05:26
*** DSVenky has joined #automotive05:28
*** mdp has joined #automotive05:31
*** albanc has joined #automotive05:32
*** jjardon has joined #automotive05:33
*** Tartarus has joined #automotive05:34
*** leon-anavi has joined #automotive06:37
leon-anavimorning06:38
*** sanjeev has quit IRC06:42
*** rajm has joined #automotive07:15
CTtpollardmorning07:22
*** CTtpollard has quit IRC07:24
*** fredcadete has joined #automotive07:28
*** CTtpollard has joined #automotive07:28
*** toscalix has joined #automotive07:53
*** sanjeev has joined #automotive08:06
*** jani_ is now known as jani08:16
*** sanjeev has quit IRC08:18
janigood morning..08:18
janihey, is that qt ivi project announchement stufff you guys have been working on or do they have their own project ?08:20
*** sanjeev has joined #automotive08:26
JEEBsome people here develop their solutions with Qt, but I don't think we've seen too many Qt people around here08:29
janiyeah, i just saw agl mentioned and mistake or not, thought it was associated with most of you guys .. and the fact that demo ivi was qt ..08:31
*** Tarnyko has joined #automotive08:31
leon-anavijani, as far as I know for the moment Qt is involved in both GDP and AGL.08:32
janicheck.08:39
janidunno if i ever mentioned this but company i work for is doing similar stuff as qt for automotive field.08:40
leon-anavijani, which is this company?08:43
*** jonathanmaw has joined #automotive08:46
CTtpollarddoes anyone know how AGL (AGL Demo) CI handles testing patchsets/changes that requires changed to both agl-demo and meta-agl or the agl 'repo' at the same time?08:47
CTtpollardIt's a problem I want to tackle with meta-genivi-dev and genivi-dev-platform08:49
CTtpollardleon-anavi: when you added sota-client to AGL this would be one of the situations08:52
*** fredcadete has quit IRC09:29
*** fredcadete has joined #automotive09:37
leon-anavihi CTtpollard, when a patch is submitted to AGL through Gerrit, the AGL Jenkins in Gerrit users gives it Code-Review-1. If the build is successful AGL Jenkins gives Code-Review+109:40
leon-anaviso a jenkins build is started for each new patch09:40
leon-anaviyou can monitor the build statuses here: https://build.automotivelinux.org/09:41
CTtpollardleon-anavi: but how does it handle patch to two different repositories that need to be built together? so in your case the commit to add sota recipes, and then the commit to the 'repo' to add meta-rust?09:41
leon-anaviI am not sure if the problem that you are tacking is solved in AGL09:41
leon-anaviYou better ask Stephane or someone else from iot.bzh regarding this09:42
CTtpollardoki doke09:42
CTtpollard:)09:42
leon-anavibtw Tarnyko, can you share some details related to AGL jenkins setup?09:42
CTtpollardwe could not test PR's to meta-genivi-dev, and only test PR's to genivi-dev-platform. But if a problem was found at that stage it could mean having to revert the commits09:43
leon-anaviright09:48
leon-anavibtw the testing should have another step if the package is not included by default in a certain image.09:48
leon-anavithe build system should add it to local.conf as IMAGE_INSTALL_append09:49
CTtpollardindeed09:51
CTtpollardcurrently we don't carry an optional packages as such, but we did for sota/rvi core09:52
fredcadeteCTtpollard: from my Jenkins experience, the only way I imagine that to work is to setup a build that "follows" meta-genivi-dev and just happens to build it in the environment of genivi-dev-platform09:55
fredcadeteit's quite possible to make a SCM setup where meta-genivi-dev is taken as one Git SCM, and genivi-dev-platform is taken as another with the sparse-checkout option to *not* checkout meta-genivi-dev09:56
leon-anaviCTtpollard, btw one of the things that I really enjoy in AGL is that there are several different images: agl-image-minimal, agl-image-ivi, agl-demo-platform.09:56
leon-anaviI think they just inherit each other therefore the maintenance effort should not be that big.09:57
leon-anaviIt is very similar to what we have in Poky and in my opinion it is quite convenient for development09:57
CTtpollardfredcadete: We do that now, all PR's for meta-genivi-dev are taken as a separate checkout against master of genivi-dev-platform, for each target09:58
leon-anaviI mentioned this approach as a proposition for GDP during the open call several weeks ago but I understood that the majority of other people involved in the project don't like it much :)09:58
CTtpollardleon-anavi: we have the -ivi image included from meta-ivi, but no differential for a -minimum yet09:59
leon-anaviyes09:59
CTtpollardI agree it would be nice to have, but I don't think GDP is big enough yet to justify splitting10:00
leon-anaviok10:00
*** rajm has quit IRC10:00
CTtpollardbut, that's just my opinion10:00
CTtpollardfredcadete: I need to create a pipeline/system in which it can somehow link two github PR's across two repo's together, and build them in parallel10:01
CTtpollardand instance of this is the current PR's to adapt meta-ivi1010:02
fredcadeteCTtpollard: that would be tricky. why is that necessary?10:02
CTtpollardit requires changes to recipes in meta-genivi-dev to support ivi10/yocto2.0, and changes to genivi-dev-platform to update the submodules/layers to jethro branches. To be built together10:02
CTtpollardif either at tested separately, they fail due to the dependency on each other10:03
fredcadeteoh, I see, this one? https://github.com/GENIVI/genivi-dev-platform/pull/1410:05
CTtpollardso, we could just merge the meta-genivi-dev changes without testing, and then only test the PR which tells genivi-dev-platform to use this sha, as well as the other changes I listed before10:05
CTtpollardbut, it's not nice that way10:05
fredcadetethis is certainly not an automotive-specific problem10:06
fredcadetebut I don't know of a solution10:06
CTtpollardfredcadete: yep that PR10:06
CTtpollardanother instance of this situation can be seen here: https://github.com/GENIVI/genivi-dev-platform/pull/610:07
CTtpollardan update of meta-raspberrpi had to be built with an update of meta-genivi-dev at the sametime10:07
CTtpollardThe only real solution I've been able to see aiding this situation is merged both repo's together10:08
CTtpollardso meta-genivi-dev is not an external submodule10:08
CTtpollardthat would be my eventual proposal for the GDP10:11
fredcadetethat would solve the issue when the interdependency is meta-genivi-dev<->other, not between other<->other. But that's maybe enough for GDP10:13
CTtpollardif it's other-other, those are would be existing sha's that we can point to10:14
*** rajm has joined #automotive10:14
CTtpollardI think it's enough for what GDP can realistically aim for10:16
fredcadetethat would probably be much easier than trying to "link" PRs to different repos10:16
CTtpollard:)10:18
toscalixleon-anavi: size is one thing, the fact that we have Baseline is another one10:32
*** rajm has quit IRC10:33
*** rajm has joined #automotive10:33
*** clopez has quit IRC10:33
toscalixwe are concentrating first in moving fast towards shipping talest software and providing a major release with several targets10:34
toscalixwhen we achieve both goals, we can increase the offering10:34
leon-anaviok10:34
leon-anavisounds as a plan10:34
toscalixDid you read the document I sent to the project mailing list about GDP viewed as portfolio?10:34
leon-anavitoscalix, sorry, I haven't read it yet.10:35
toscalixthat is an attempt to describe target -> deliverable10:35
leon-anaviI busy with some other tasks but I will read it by the end of the week.10:35
toscalixok, please let me know what you think about it10:35
toscalixI thought about the idea of "flavors"10:35
toscalixbut based on my experience.... I think we need to prioritise some other things first10:36
toscalixhaving Baseline in place10:36
toscalixwhat I like about AGL is that all those flavours come from the same "trunk"10:37
toscalixthat is the most efficient way of dacing the challenge involved in supporting them10:37
*** clopez has joined #automotive10:37
toscalixs/dacing/facing10:37
toscalixmy talk at 14th AMM about GDP portfolio was in that direction10:38
leon-anaviyes10:38
leon-anaviI like this in AGL too10:39
CTtpollardtoscalix: the structure of AGL is virtually mirrored in GDP10:39
CTtpollardmeta-agl = meta-ivi, agl-demo = gdp10:39
toscalixas output, yes10:39
CTtpollardbuilding on top of poky releases, using OE10:39
toscalixwe deffer in how we deliver it10:39
toscalixdiffer10:40
Tarnykoleon-anavi: I do not really knox the Jenkins setup, sorry for that10:59
leon-anaviTarnyko, ok. CTtpollard was asking about it? Could you point him in the right direction to someone with experience in it?11:00
Tarnykothis was the initial setup notice : https://lists.linuxfoundation.org/pipermail/automotive-discussions/2015-September/000822.html . I guess Jan-Simon is the good person to ask about11:05
CTtpollardthanks all11:07
*** gunnarx has joined #automotive11:51
*** gunnarx has joined #automotive11:51
gunnarxCTtpollard, read your email now11:53
gunnarx^^ I have read11:53
gunnarxEnglish is an ambiguous language in writing :)11:54
gunnarxCTtpollard, can you explain more about "It also can't handle the parallel PR dependency, such as can be seen with the 'GDP10' situation"?11:54
*** praneeth has quit IRC12:06
*** praneeth has joined #automotive12:06
CTtpollardgunnarx: been discussing the in here today, but can quote an example12:14
CTtpollard'<CTtpollard> and instance of this is the current PR's to adapt meta-ivi1012:14
CTtpollard<fredcadete> CTtpollard: that would be tricky. why is that necessary?12:14
CTtpollard<CTtpollard> it requires changes to recipes in meta-genivi-dev to support ivi10/yocto2.0, and changes to genivi-dev-platform to update the submodules/layers to jethro branches. To be built together12:14
CTtpollard<CTtpollard> if either at tested separately, they fail due to the dependency on each other '12:14
CTtpollardthis situation has also occurred for example in the upgrade of the raspi kernel recently, and the addition of rvi sota client12:15
gunnarxsorry, I can go back read the logs.  been off IRC for a little while12:15
CTtpollardnp12:15
CTtpollardI believe agl and potentially other yocto system using submodules/google-repo will have this problem, but I've yet to find out how they handle it12:16
gunnarxah yes, now I understand.  Yes changes that need to be done in m-g-d and g-d-p simultaneously?12:16
CTtpollardyup12:17
CTtpollardso, you can seen on the genivi.go that the pipelines we've introduced to do m-g-d(PR) against master g-d-p fail, because they require the PR in g-d-p to bring in dependencies12:18
gunnarxafter thinking about it 30 seconds only... yeah maybe the PR can't be built automatically.12:18
gunnarxI mean in fact you can't create a g-d-p PR until you have a commit hash in m-g-p to refer to12:18
CTtpollardyes unless the github api/go.cd plugin has a smart way to link PR's across repos12:19
CTtpollardwhich I highly doubt12:19
gunnarxso there's some working around there anyhow.  at first you need your submodule change accepted, (alternatively provide a fork) then you can propose a submodule change to point to that and that can be built (automatically)12:20
gunnarxA special incoming branch on m-g-d that anyone can commit to.  Then you havea  commit hash and you can point g-d-p PR to that.  It will be built.  The PR can be merged on g-d-p, then m-g-d updated.  It will only work if the merge is a fast forward so the hash doesn't change....12:22
gunnarxm-g-d updated means merging the commit over to master which as I said cannot be an actual merge as such.  Fun times for maintainers :)12:23
gunnarxOK, so regarding PR integration.  https://github.com/GENIVI/meta-genivi-dev/pull/7 seems to be built here: https://go.genivi.org/go/tab/build/detail/GDP-Yocto-RPI2-meta-genivi-dev-GITHUB-PR/1/build/1/init_and_bitbake agreed?12:25
gunnarxI think reporting the result back to GitHub is the failing step.12:26
gunnarxCTtpollard, are you ignoring me or busy  trying to make sense of my rambling :)12:28
gunnarxI am not offended either way :)12:29
CTtpollardgunnarx: no ignoring, just currently on lunch :)12:29
gunnarxlunch is important12:30
CTtpollardvery cheap supermarket sushi, but it's not all that bad12:30
gunnarxIf I want the PR build to fail as fast as possible, do you have a suggestion of a file in meta-genivi-dev to screw up? :)12:36
gunnarxI'm not sure what is read first from the layer...12:37
CTtpollardgunnarx: I usually just add a dummy file to test pr's12:37
CTtpollardgoing back to parse your comments now12:38
gunnarxyes but I want the build to fail also.  I'll put something in layer.conf, I suppose that should work12:38
*** Saint_Isidore has quit IRC12:39
CTtpollardah ok then, just bork a file path in layer/bblayers12:39
*** Saint_Isidore has joined #automotive12:40
gunnarxhmm, was it meta-genivi-dev that was deleted before?12:41
CTtpollardgunnarx: the way works, but as you point out it requires the shas to match, meaning m-g-d has to stay stagnant during the PR process. This happens a lot, and I usually just amend, or ask the submitter to rebase the PR and amend12:43
CTtpollardagain, and example of that: https://github.com/GENIVI/genivi-dev-platform/pull/1312:43
gunnarxthe forks that were created in GitHub are no longer connected to GENIVI/m-g-d because of its deletion.  They are not part of the GENIVI network.  My fork suddenly derives from toscalix/m-g-d :-)12:45
CTtpollardonce the meta-genivi-dev side was merged, the sha in g-d-p PR did not match due to commits in the meantime to m-g-d12:45
toscalixwow, I am upstream :-)12:45
gunnarxYes I see, so it's a common thing then.   I guess the process kind of works then if wanted to set it up that way.12:45
gunnarxEveryone knows toscalix is the definitive version of GDP12:45
toscalix:-)12:46
gunnarxThe downside is I can't seem to create PRs back to the GENIVI copy.  GitHub doesn't know any connection to that repo apparently.12:47
CTtpollard.....12:47
CTtpollardNicr12:47
CTtpollard*e12:47
pedroalvarezso, problem found12:48
pedroalvarez(that's good)12:48
gunnarxQuestion or statement pedroalvarez ?12:48
pedroalvarezcelebration12:48
gunnarx:?12:48
pedroalvarezI mean, we know what the problem is, that's good12:48
gunnarxWe are 6 people in a private network on meta-genivi-dev12:48
gunnarxWhich problem?12:48
gunnarxYou think this affects the PR builds you mean?12:49
pedroalvarezoh, I thought you were thinking that12:49
CTtpollardgunnarx: all that I can deem, taking AGL for example (all be it that's using google-repo,jenkins,gerrit but same concept) is that changes to agl-demo don't get tested, it only gets tested at the point when 'submodule' sha is updated in the 'repo'(g-d-p in our instance) side12:49
gunnarxdon't know if there's a connection to that yet12:49
gunnarxCTtpollard, makes sense12:49
CTtpollardbut that can lead to having to revert changes in 'demo' if they don't work once the testing is carried out at the repo/gdp stage12:50
pedroalvarezgunnarx: sorry, totally misunderstood the conversation12:51
gunnarxpedroalvarez, FYI you are part of the "disconnected" network :)   Doesn't matter now but I will re-fork the repo from GENIVI later on.12:51
gunnarxnp pedroalvarez, we will get to the PR discussion also, I'm juggling a few different things12:51
CTtpollardSo if people are happy with that model of CI then I'm happy to trial it, although I still believe combining the repo's is the ultimate solution12:51
gunnarxHmm, I'm quite surprised I can't even by typing in the name force GitHub to consider a pull request from my copy...   Can PRs only be made within the known "network" of forks...?12:53
gunnarxmeta-genivi-dev has not changed the hash of its base commit or anything weird right?  It's still the same content?12:54
CTtpollardshould be12:57
janileon-anavi: rightware12:59
jonathanmawDoes anyone here have experience with booting the renesas Silk? I've got it loading the kernel and dtb, but nothing after "Starting kernel ...", which seems to be a problem with the kernel's tty interface.13:06
gunnarxFYI I temporarily replaced ct_test resource with yocto_build resource in the PR pipeline, so another agent can be used13:08
CTtpollardgunnarx: ok, we also added the renesas binaries to the codethink agent so it should be part of the pool for those pipelines13:12
gunnarxPending check!   https://github.com/GENIVI/meta-genivi-dev/pull/1013:13
CTtpollardwoop13:15
gunnarxplot thickens13:15
gunnarxbugs galore...13:15
gunnarxA paused pipeline is not paused for PRs.  PRs will trigger it anyhow?  wth.13:15
pedroalvarezso all of them have been triggered, but only the non-paused one has actually comunicated "check pending" to github13:18
gunnarxyes13:20
gunnarxmight be a coincidence though.  maybe first one wins on the reporting13:20
gunnarxMight be some weirdness going on.  It's a little hard with the pipelines that have multiple material - they will trigger on either repo changing.  These 4 seem to be PR triggered though AFAICT13:21
gunnarxAnyhow, I think we're back on track.  I just wanted to confirm first.  The gocd user seems to need write access to the repo to report on checks.  The pipelines are triggered with only read access, but no indication inside GitHub without write.13:22
gunnarxGo itself only has a OAUTH token though, so there are some limits on what it can actually do13:23
CTtpollardif it only needs write to report, then it should be granted? Unless it has capabilities to take successful PR's as triggers to auto-merge like some tools then no13:24
gunnarxno parse13:25
gunnarxThe username is a collaborator with Write access now (it was Read).13:26
gunnarxGo server logs in with username and token, so the scope of the token itself also limits13:27
CTtpollardIf it just needs write access to report on success/failure then fine, I'm just aware other 'gatekeeper' type workers also can take success==merge13:27
CTtpollardok then13:27
gunnarxOK I see what you mean.  We don't have any auto merge functionality, no.13:29
gunnarxHmm, this thing single PR triggering multiple pipelines might still need some work.13:31
*** gunnarx has quit IRC13:39
*** gunnarx has joined #automotive13:39
pedroalvarezcan we un=pause them now? or will you sort that out, gunnarx?13:47
gunnarxjust a sec13:48
gunnarxOK, yeah I guess it built, failed as expected, and reported the failure.  In other words successful PR check.13:49
gunnarxOK, I unpaused them again13:50
CTtpollardFailure==Success \o/13:50
gunnarxexactly13:50
gunnarxstill not sure where we stand with multiple pipelines triggered by the same PR13:50
gunnarxlooks like only one is being handled and reported.  I guess we keep testing some more13:51
CTtpollardyeh, ultimately we'd want it to report all targs13:51
pedroalvarezI was hoping that is what happens13:51
gunnarxNo wait, look https://github.com/GENIVI/meta-genivi-dev/pull/1013:51
gunnarx4 checks!13:52
CTtpollard:D13:52
pedroalvarezpurrrfect13:52
gunnarxI guess we have been accustomed to being too negative.  It works as intended apparently13:52
gunnarxthat's one win for today at least :)13:53
pedroalvarezthis is the closest thing we have ever had to a proper CI, so YAY!13:53
CTtpollard+113:54
gunnarx+113:54
radiofree_is SOTA/Software Manager being used in the CI pipeline?13:55
CTtpollardnot directly13:56
CTtpollardsota client is integrated into gdp, but there's no interaction taking place as of yet13:57
*** steve_l has joined #automotive14:01
CTtpollardgunnarx: will try and be more eloquent with explaining the 'parallel PR' situation next time, now there's some existing PR's that show it it's easier to describe/visualise though14:02
toscalixrajm: I added you to the group GDP maintainers14:03
gunnarxdisk full on ct agent :(14:03
gunnarxhttps://go.genivi.org/go/tab/build/detail/GDP-Yocto-MINNOWBOARD-GITHUB-PR/1/build/1/init_and_bitbake14:03
rajmthanks toscalix!14:04
gunnarxWe have a new GDP maintainer?14:04
gunnarxAh yes14:04
toscalixrajm: Robert Marshall14:04
gunnarxnever mind :)14:04
gunnarxGood to see you in action rajm14:05
* steve_l hears hdd is cheap but agents are harder to come by :(14:06
* steve_l although Spook agents are ten-a-penny seemingly14:07
*** mdurnev has quit IRC14:13
rajmThanks gunnarx looking forward to the work!14:13
*** fredcadete has quit IRC14:14
*** rajm has quit IRC14:21
*** rajm has joined #automotive14:35
*** fredcadete has joined #automotive14:41
*** fredcadete has quit IRC14:46
*** fredcadete has joined #automotive15:00
*** fredcadete has quit IRC15:00
*** fredcadete has joined #automotive15:01
*** rajm has quit IRC15:09
*** rajm has joined #automotive15:09
*** toscalix has quit IRC15:10
*** jlrmagnus has joined #automotive15:10
*** toscalix has joined #automotive15:11
gunnarxCTtpollard, pedroalvarez still there?15:14
pedroalvarezyup15:14
CTtpollardo/15:15
*** toscalix_ has joined #automotive15:15
gunnarxDo you guys have the graphics binaries, it looks like the recipes you set up for porter are doing copy_gfx_ etc.15:15
*** toscalix has quit IRC15:15
gunnarxDo you have them on your agent I mean15:15
CTtpollardthey should be pedroalvarez?15:15
CTtpollardls /var/go/sgx_bin/ shows them15:16
gunnarxPreviously I've set up the porter builds to only build on a machine that was allowed to have the binaries15:16
gunnarxAnd I used a different path15:16
gunnarxJust basically looking to see that we agree on paths15:16
CTtpollardI took the path from the existing renesas template iirc15:17
gunnarxOh.  Didn't know there was a defined path.  In the long run recipes should be buildable on multiple agents.  currently PR recipes are tied to CT agent.15:17
gunnarxAnd the template for the PR build, it seems like we could use the same template everywhere really.15:18
gunnarxI'm happy to adapt to yours, just saying we seem to be developing the same in parallel but different15:18
gunnarxso let's sync up.15:18
pedroalvarezthe goal of our pipeline is to try to save some diskspace.15:18
pedroalvarezour agent is full of pipelines that take up to 60G15:19
gunnarxgreat, why don't we discuss some strategies for that.15:19
gunnarxyes, you are using a shared DL_DIR, OK15:19
pedroalvarezmy current one is to have sstate and downloads in a common place for all of them15:19
pedroalvarezexactly15:20
gunnarxI've been requesting that we agree on paths for that15:20
gunnarxAlthough I was more leaning towards PREMIRRORS, but that's because d/l isn't that big after alll15:20
gunnarxit's a few gigs I think15:20
gunnarxMost of the 60G is stuff generated during the build right?15:20
pedroalvarezah, I also remove tmp/ when the build finishes15:21
gunnarxand before I noticed :)15:21
gunnarxsorry got interrupted. afk15:21
pedroalvarezoh, just before, not after15:22
CTtpollardinstead of removing /tmp it might be cleaner to inherit="rm_work"15:22
steve_l60G! rm_work really is your friend. http://git.projects.genivi.org/?p=genivi-demo-platform.git;a=blob;f=gdp-src-build/conf/local.conf;h=d3b433fb42007670fce222f2fe724448350c7892;hb=refs/heads/porter#l615:23
CTtpollardI'm not sure it that will actually save space constantly though15:23
CTtpollardsnap steve_l15:23
steve_lIndeed. Though note my comment below that line about navit.15:24
CTtpollardyeh I kept that when switching to the templates https://github.com/GENIVI/genivi-dev-platform/blob/master/gdp-src-build/conf/templates/porter.local.conf15:25
steve_lCTtpollard: Did Jonathan solve his silk kernel issue do you know? He's unresponsive on irc :)15:25
CTtpollardhowever, now that some form of FSA functionality has been merged to meta-genivi, I might send a PR to remove it15:25
CTtpollardsteve_l: I believe he's managed to boot into a shell now, if I stare across the room long enough he might notice15:26
CTtpollardjonathanmaw ^15:27
jonathanmawsteve_l: yep, the problem was that I was specifying ttySC6, not ttySC1015:27
jonathanmawI got it booting into a shell. from there I can figure out why I'm not getting anything out to the touchscreen.15:28
* steve_l he's <insert that hipster word for being in the zone>15:28
steve_l^ ahh good :)15:28
gunnarxOK I'm back but in another meeting and have to go soon15:32
* paulsherwood is amazed to see automotive folks actually using irc productively now... who'dathunk? :)15:37
* jbocklage2 not15:37
paulsherwoodnot amaze, not productive, or wouldn't have considered it possible? :)15:37
CTtpollardpaulsherwood: I can ask about my intermittent clutch slipping if you want15:38
jbocklage2hehe :) No. 315:38
paulsherwoodCTtpollard: i'm a software guy, that sounds like hardware to me15:38
CTtpollardgunnarx: I was referencing http://go.genivi.org/go/admin/templates/Yocto_GDP_Build_Renesas/stages/build/job/init_and_bitbake/tasks for the sgx path15:39
gunnarxRight CTtpollard.  And I wrote that :)15:40
steve_lCTtpollard: That's because your using an old generation single core clutch. If you were using a modern multi-core clutch you could integrate all the other h/w into just the clutch.15:40
gunnarxfacepalm15:40
*** tjamison has joined #automotive15:40
*** rajm has quit IRC15:40
CTtpollardgunnarx: I know, so it made sense to do the same :)15:41
CTtpollardsteve_l: have you been on that IPA you mentioned already today?15:41
* gunnarx logs off irc in shame15:41
gunnarxseriously I have to go.  let's sync up on aligning the templates later on.  if you want you can use resource yocto_build to open up for more agents running the builds15:42
gunnarxbye15:42
*** gunnarx has quit IRC15:42
CTtpollardo/15:42
steve_lCTtpollard: sadly no but in the current humidity it is a mightly attractive idea15:43
*** mpaolino has joined #automotive15:44
steve_lpedroalvarez: There is some detris in the folder tree as well but for illustration my GDP build with rm_work on Porter is 15GB. download directory outside of the tree15:45
*** ashwasimha_ has joined #automotive15:50
*** jlrmagnus has quit IRC15:51
*** clopez has quit IRC15:59
*** clopez_ has joined #automotive16:02
*** jlrmagnus has joined #automotive16:03
jonathanmawwell, that's the HDMI display problem fixed. The cable was loose >.<16:08
*** fredcadete has quit IRC16:08
*** chbae has joined #automotive16:15
chbaehello16:19
*** chbae has quit IRC16:26
*** jonathanmaw has quit IRC16:31
*** toscalix_ is now known as toscalix16:32
*** Tarnyko has quit IRC16:37
*** jlrmagnus has quit IRC16:42
*** |\n has joined #automotive16:47
|\nhello guys, i'm trying to find a replacement for bosch blower motor or at least maybe there is some catalog where i could see dimensions16:48
|\nthe point of interest is 013011104016:49
*** jobol has quit IRC17:05
toscalix|\n: check the topic of the channel, at the top part of your IRC client17:10
toscalixthis channel is for automotive....software discussions17:11
toscalixyou do not want software engineers to provide you support on mechanical problems....trust me17:11
|\noh, my fault, toscalix, is there anything similar to can bus triple project btw?17:12
|\nif regarding software17:12
leon-anavitoscalix, well said :)17:17
*** Tarnyko has joined #automotive17:18
toscalix:-)17:20
*** mpaolino has quit IRC17:20
*** leon-anavi has quit IRC17:38
*** steve_l has quit IRC17:41
*** toscalix has quit IRC17:42
*** kooltux_ has quit IRC17:58
*** kooltux__ has joined #automotive17:58
*** JEEB has quit IRC17:58
*** JEEB has joined #automotive17:59
*** jjardon has quit IRC18:12
*** jjardon has joined #automotive18:17
*** jjardon has quit IRC18:22
*** jjardon has joined #automotive18:22
*** IOBN has quit IRC18:30
*** IOBN has joined #automotive18:31
*** ashwasimha_ has quit IRC19:01
*** |\n has left #automotive19:12
*** jlrmagnus has joined #automotive20:20
*** Saint_Isidore has quit IRC21:21
*** kooltux_ has joined #automotive21:51
*** kooltux_ has quit IRC21:58
*** Saint_Isidore has joined #automotive22:04
*** tjamison has quit IRC23:58

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