IRC logs for #baserock for Monday, 2016-04-04

*** cosm has quit IRC00:25
*** cosm has joined #baserock00:31
*** cosm has quit IRC01:36
*** cosm has joined #baserock01:50
*** cosm has quit IRC02:45
*** cosm has joined #baserock02:46
*** toscalix has joined #baserock03:44
*** cosm has quit IRC03:50
*** toscalix has quit IRC06:29
*** CTtpollard has joined #baserock06:59
*** faybrocklebank has quit IRC07:37
*** faybrocklebank has joined #baserock07:38
*** bashrc_ has joined #baserock08:00
*** rdale has joined #baserock08:13
*** ctbruce has joined #baserock08:21
*** anahuelamo has joined #baserock08:22
*** franred has joined #baserock08:30
*** tiagogomes has joined #baserock08:41
*** jonathanmaw has joined #baserock08:51
*** tiagogomes has quit IRC09:03
*** tiagogomes has joined #baserock09:05
*** ssam2 has joined #baserock09:11
*** ChanServ sets mode: +v ssam209:11
*** locallycompact has joined #baserock09:18
*** bwh has quit IRC10:01
*** benbrown_ has quit IRC10:01
*** locallycompact has quit IRC10:01
*** SotK has quit IRC10:01
*** paulsherwood has quit IRC10:02
*** paulsherwood has joined #baserock10:02
*** SotK has joined #baserock10:03
*** franred has quit IRC10:04
*** bwh has joined #baserock10:08
*** benbrown_ has joined #baserock10:08
*** locallycompact has joined #baserock10:11
*** franred has joined #baserock10:19
pedroalvarezjjardon: sorry, I didn't spot this error when reviewing: https://gerrit.baserock.org/#/c/2049/11:07
pedroalvarezred mason is red :)11:07
franredpedroalvarez, you can go ahead and merge it11:08
jjardonpedroalvarez: mmm, sorry; I think ybd builds that without complaining11:09
pedroalvarezno worries :) it's fixed now11:09
*** cosm has joined #baserock11:27
*** cosm has quit IRC11:29
pedroalvarezgreat! find the submit button here: https://gerrit.baserock.org/#/c/2048/212:00
pedroalvarezit has changed with latest release :)12:00
franredpedroalvarez, you can press it ;-)12:01
pedroalvarezthe thing is that I can't, and that's what I mean. The button now says that you won't be able to when you hover over it12:03
pedroalvarezthis is cool :)12:04
pedroalvarezfranred: thanks for reviewing12:04
*** edcragg has joined #baserock12:09
*** franred has quit IRC12:17
*** tiagogomes has quit IRC12:20
*** franred has joined #baserock12:29
*** tiagogomes has joined #baserock12:53
*** franred has quit IRC13:23
*** franred has joined #baserock13:23
*** franred has quit IRC13:53
*** franred has joined #baserock14:03
edcraggi'm getting 'ERROR: Ref 48416261f38c2d1e4ee7a4482238565299c4a605 was not found in repo git://git.baserock.org/baserock/baserock/definitions.' when i try to run morph, i usually have changes in my local definitions that aren't on g.b.o, can't understand why this is happening14:47
ssam2are you using --local-changes=ignore setting?14:58
ssam2if so, all the commits need to be pushed, it actually ignores your local repo other than to find out what commit you want to build14:59
ssam2the error could definitely be improved there (or the behaviour made less confusing)14:59
ssam2i'm not sure there's any value in that behaviour beyond making it easy to know you're not accidentally building uncommitted stuff.. but there are other ways to check that15:00
ssam2so morph should just read the files off disk where it can15:00
*** ssam2 has quit IRC15:06
edcraggi agree15:08
edcraggi'm not using --local-changes=ignore, though15:09
*** ssam2 has joined #baserock15:22
*** ChanServ sets mode: +v ssam215:22
edcraggthanks ssam2... seems to be avoided by changing the remote origin to my usual repo15:24
edcraggfor the moment15:24
*** cosm has joined #baserock15:25
*** cosm has quit IRC15:38
*** CTtpollard has quit IRC15:39
*** CTtpollard has joined #baserock15:40
*** ssam2 has quit IRC16:01
*** ssam2 has joined #baserock16:13
*** ChanServ sets mode: +v ssam216:14
jjardonpedroalvarez: nice series!16:19
pedroalvarezjjardon: it's not complete, they are a lot...16:20
pedroalvarezsent them as separate commits to avoid merge conflicts when possible16:20
pedroalvarezworked on them this weekend, and I don't know when I'll have time to continue, that's why I sent it as it is16:23
*** gtristan has joined #baserock16:34
edcraggit appears ybd doesn't keep cache keys in its metadata format... anyone know otherwise?16:51
paulsherwoodedcragg: what do you mean?16:53
paulsherwoodiirc the meta file does not contain the cache-key, if that's your question16:54
edcraggpaulsherwood: morph keeps record of the cache key in .meta files, i can't see any evidence of this in ybd (at least in built system images)16:54
edcraggyes, i think that's what i mean16:54
paulsherwoodi think you're correct16:54
paulsherwoodis there a benefit to including it?16:55
*** ctbruce has quit IRC16:55
rdaleas the meta file is in the artifact's cached entry, you can't find it unless you know the cache key16:56
richard_mawor you could be scanning through the contents of /baserock16:56
ssam2I like that Morph stores every factor that went into the cache key in the metadata16:57
ssam2it means that there's a way to reconstruct the cache key from the contents of the file16:57
ssam2which gives a way to validate it16:58
ssam2i've never actually used it for that, but i like that it's there16:58
richard_mawalso that for some systems you can get to something resembling the system you have by walking the metadata to get your build graph and run the commands yourself16:58
edcraggpaulsherwood: it was previously used by the genivi manifest generation script, and included in the manifest output16:59
edcraggthe more information the better, i think, for reproducibility16:59
paulsherwoodhttps://github.com/devcurmudgeon/ybd/issues/20217:00
ssam2it does lead to long metadata files, because you have to list all deps17:00
paulsherwoodpatches welcome, or i'll get to it when i return from holiday :)17:00
ssam2but not too long in practice -- morph's are not crazily long17:00
*** bashrc_ has quit IRC17:01
*** jonathanmaw has quit IRC17:01
edcraggthe longest thing in most seems to be the list of files afaict17:02
ssam2oh yeah, that's long too17:03
edcraggor at least, can be17:03
ssam2but it's essential for providing 'what chunk contains this file' info17:03
rdaleybd meta files have the list of files for a chunk, or the list of components for a stratum and the git sha1s - i would expect that to be enough for ybd to construct the cache keys, but i might be wrong17:03
ssam2oh, nice17:03
*** toscalix has joined #baserock17:05
* edcragg assumed cache keys must depend on build commands too, but may very well be wrong17:05
rdaleah, yes - it isn't just the git sha1s on the chunks, it is a reference the the sha1 of the definition perhaps that you need as well17:07
*** ssam2 has quit IRC17:07
*** tiagogomes has quit IRC17:25
*** anahuelamo has quit IRC17:26
*** locallycompact has quit IRC17:34
*** toscalix has quit IRC17:43
*** edcragg has quit IRC17:51
*** rdale has quit IRC17:53
*** locallycompact has joined #baserock18:59
*** locallycompact has quit IRC19:39
*** locallycompact has joined #baserock20:11
*** gtristan has quit IRC21:48
*** cosm has joined #baserock21:56
*** edcragg has joined #baserock22:14
*** edcragg has quit IRC22:44
*** locallycompact has quit IRC23:01

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