IRC logs for #buildstream for Thursday, 2017-11-30

*** jude has quit IRC09:25
*** jude has joined #buildstream09:25
*** nexus_ has joined #buildstream09:37
*** laurenceurhegyi has quit IRC09:38
*** nexus has quit IRC09:38
*** paulsherwood has quit IRC09:38
*** bochecha has quit IRC09:38
*** cs_shadow has quit IRC09:38
*** hergertme has quit IRC09:38
*** pro[m] has quit IRC09:38
*** tlater has quit IRC09:38
*** cgmcintyre[m] has quit IRC09:38
*** mattiasb has quit IRC09:38
*** inigomartinez has quit IRC09:38
*** kailueke[m] has quit IRC09:38
*** jjardon[m] has quit IRC09:38
*** mrmcq2u[m] has quit IRC09:38
*** waltervargas[m] has quit IRC09:38
*** jude has quit IRC09:38
*** tpollard has quit IRC09:38
*** adds68_ has quit IRC09:38
*** WSalmon has quit IRC09:38
*** tristan has quit IRC09:38
*** gitlab-br-bot has quit IRC09:38
*** saxa has quit IRC09:38
*** juergbi has quit IRC09:38
*** paulsherwood has joined #buildstream09:39
*** bochecha has joined #buildstream09:39
*** jude has joined #buildstream09:39
*** tpollard has joined #buildstream09:39
*** adds68_ has joined #buildstream09:39
*** WSalmon has joined #buildstream09:39
*** tristan has joined #buildstream09:39
*** gitlab-br-bot has joined #buildstream09:39
*** cs_shadow has joined #buildstream09:39
*** saxa has joined #buildstream09:39
*** juergbi has joined #buildstream09:39
*** hergertme has joined #buildstream09:39
*** laurenceurhegyi has joined #buildstream09:40
*** tlater has joined #buildstream09:42
*** bethw has joined #buildstream09:45
*** jonathanmaw has joined #buildstream09:52
*** tpollard has quit IRC10:03
*** tristan has quit IRC10:05
*** tpollard has joined #buildstream10:05
*** bethw has quit IRC10:05
*** bethw has joined #buildstream10:05
*** tristan has joined #buildstream10:12
*** ssam2 has joined #buildstream10:14
*** valentind has joined #buildstream10:18
tlaterHuh... The baserock 'busybox' elements have always had the wrong 'track' for me - always 1_2_3_1 instead of 1_23_1, resulting in failed git clones. It seems that `bst track` changes the 'track' parameter. Is that supposed to happen?10:45
*** kailueke[m] has joined #buildstream11:03
*** kailueke[m] has quit IRC11:08
*** WSalmon has quit IRC11:16
juergbitlater: it changed it from 1_2_3_1 to 1_23_1 on its own?11:27
tlaterAfter a `bst track`, seemingly on its onw11:27
juergbithat seems very odd11:28
juergbican you reproduce this?11:28
* tlater attempts11:28
tristansounds quite impossible11:28
*** valentind has quit IRC11:28
tristanthis is done through the get_ref() / set_ref() api paths, to pass just the ref from the child tracking process to the main process11:29
juergbissam2, tristan: i'm now using multiprocessing instead of subprocess for pushreceive. seems the best way to get proper coverage (total should now be at 83%)11:29
juergbihave to clean this change up, but i'll probably best postpone this until the multi cache branch is done11:30
tristanw00t !11:30
*** inigomartinez has joined #buildstream11:30
tlaterYup, I can reproduce it11:31
tristanyeah that sounds a bit easier than launching the thing under coverage explicitly11:31
tristanjuergbi, what do you think, do we bother with deprecating the earlier hack and reduce the code paths for artifact sharing ?11:31
juergbissam2: there is currently a behavior difference between local and ssh push urls (no failure on init of the remote in case of non-existing local repo) and the current pull tests seem to rely on that11:32
tlaterI simply copied the baserock project.conf and gnu-toolchain/busybox.bst into a separate repo, fixed the minor incompatibilites and that results in 1_23_1 -> 1_2_3_111:32
* tlater thinks this might be ruamel.yaml trying to escape something11:32
juergbitristan: what i did was use pushreceive for local paths as well, essentially dropping the old local path special casing11:32
* tlater tries to minimize the files and set up an issue11:33
tristanjuergbi, dropping the branchy special casing sounds good :)11:33
juergbiit's slightly slower but this was anyway done only for testing11:33
juergbissam2: one remaining difference between ssh/http and local (test) behavior is that with urls we can deduce whether we want push+pull (ssh) or just pull (http) from the uri scheme. with local paths we dont' have that distinction11:36
juergbiso we can't really test that aspect but it's just a small point11:37
*** tristan has quit IRC11:40
ssam2tlater, yeah, i think it's a ruamel corner case ... that library is not perfect at all11:46
ssam2i fixed a bunch of corner cases in it a few years ago11:46
ssam2which did get merged eventually, so it's worth sending patches11:46
ssam2juergbi, sounds fine to me11:47
tlaterI'll record it as an issue for now, and then perhaps move on to debugging it later - it's surprisingly hard to get this image to build ;-;11:47
ssam2really? it's worked in CI11:47
ssam2oh, buildstream has changed since then11:48
ssam2you should use an old version of buildstream for now11:48
ssam2i do have a branch to update things, but still WIP: https://gitlab.com/baserock/definitions/commits/sam/buildstream-artifact-cache-update11:48
ssam2if you look at the gitlab CI it logs what version of buildstream was used in the successful build11:48
ssam2juergbi, FWIW my sam/multiple-caches support is feature complete, just need to figure out why the tests hang11:49
ssam2and rebase11:49
tlaterHm, I think I might move from your WIP branch, since this will be documentation, so I don't really want to record outdated information11:49
ssam2tlater, the stuff that changed isn't really related to image building11:49
ssam2tlater, mostly the decision to always run autoreconf for autotools modules which broke a lot of things11:50
ssam2juergbi, is your test suite branch pushed ? i'll try and rebase on top of it if so11:50
ssam2(and if i get time between meetings :/)11:50
tlaterI've seen those issues, yeah, but there are a lot of boilerplate elements that a lot of people will probably just copy when they attempt this11:51
* tlater thinks it's probably best to keep these things up-to-date11:51
ssam2i'm confused what your goal is here ...11:53
ssam2surely not linking to the Baserock stuff directly ?11:54
tlaterI think that would result in the simplest tutorial?11:55
juergbissam2: not pushed yet. we get a cyclic rebase problem ;) i can push it but it still contains a hack that i wanted to solve after rebasing on top of your updated branch11:55
ssam2tlater, hmm perhaps. not sure external deps for the docs makes sense though12:00
ssam2who knows whether baserock will be kept up to date in future12:00
ssam2juergbi, ok, i guess i have to figure out the hang myself then :-)12:00
*** mrmcq2u[m] has joined #buildstream12:02
* tlater isn't sure about how he will document this yet, I'll see what I end up with - avoiding to link to external projects, of course :)12:04
*** pro[m] has joined #buildstream12:08
tlaterIs https://buildstream.gitlab.io/buildstream supposed to 404?12:09
*** tristan has joined #buildstream12:14
tlaterNvm, I guess gitlab just takes some time to deploy the pages12:16
gitlab-br-botbuildstream: issue #166 ("bst sometimes modifies source `track` parameters") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/16612:18
*** cgmcintyre[m] has joined #buildstream13:42
*** mcatanzaro has joined #buildstream13:46
*** tristan has quit IRC13:55
*** kailueke[m] has joined #buildstream14:35
*** waltervargas[m] has joined #buildstream14:40
*** jjardon[m] has joined #buildstream14:46
gitlab-br-botbuildstream: merge request (juerg/recursive-pipelines->master: WIP: Junctions and subprojects) #160 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/16014:56
juergbissam2: i've pushed it to juerg/recursive-pipelines in case it's useful for your debugging but i don't expect it to be related14:57
ssam2ok, t14:57
ssam2ta14:57
juergbionly the top two commits are relevant but they depend on earlier commits14:57
* juergbi starts merging simple preparatory refactoring patches from the start of my branch15:03
*** tristan has joined #buildstream15:05
*** mattiasb has joined #buildstream15:18
*** jude has quit IRC15:22
*** bethw has quit IRC15:45
*** jude has joined #buildstream15:54
* tlater finds it annoying that gitlab pulls our documentation off the net every time someone commits to master15:55
gitlab-br-botbuildstream: merge request (114-give-better-warnings-on-overlaps->master: WIP: Resolve "Give better warnings on overlaps") #165 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/16516:07
tristantlater, why ?16:11
tlaterWell, our documentation's uptime will be awful this way16:12
tlaterAnd it seems unnecessary to wait for the full build when the actual deployment is probably just a few seconds16:12
tristantlater, the current problem with that right now is https://gitlab.com/gitlab-org/gitlab-ce/issues/3514116:12
tristanwhat ?16:12
tristanwhy uptime awful, that part I dont understand16:13
tristantlater, the docs are always there, they are just "slightly" behind master, until they get updated16:13
tlatertristan: From what I've seen they go offline for a short while until the build finishes16:13
tristanI've never seen that16:13
tlater"short" being the time it takes to test and build16:13
tristanreally never16:14
tlaterI've only been running into it today, maybe it's a regression?16:14
tristanthat is something new... but; yesterday or the day before it may have happened16:14
tristanonce16:14
tlaterI've seen it three times today16:14
tristanbecause I changed the .gitlab-ci.yml once and screwed it up once16:14
tlaterMaybe I'm just very unlucky16:14
tristanif there is a bug, there is a bug16:15
tristanI havent seen it happen, but if it's happening, needs investigation I guess16:15
* tlater will be on the lookout and point it out if it happens again16:15
tristanreally though, gitlab wont delete the pages, it will just deploy the pages quite atomically once it gets there16:16
tristantlater, there is *another* gitlab bug though we might be running into16:16
tristanlemme see...16:16
tristanwe've managed to not run into this for a long time, it happened around 6 months ago and things got more stable16:17
tristanhere: https://gitlab.com/gitlab-org/gitlab-ce/issues/3489916:17
tristanwhat you're seeing *might* be related to that16:17
tristanstill, afaics you really *should* have the last version, the worst that can happen is a failed deploy and you have to retrigger a build to get the docs updated16:18
tlaterI get a gitlab 404 when it happens16:18
tristan(whereas not updating them results only in not having up-to-date docs, not *lack* of docs)16:18
tlaternexus_ confirmed it at some point today, because I was trying to point him to something in the docs16:18
nexus_+116:19
*** bethw has joined #buildstream16:20
*** semanticdesign has joined #buildstream16:46
ssam2this hang is one of those great ones that seems to be fixed by adding print() statements16:55
adds68_Hey16:55
nexus_hi16:56
adds68_When following install commands for debian stable, it points to an old version of ostree16:56
ssam2ah yes, nexus_ spotted the same thing :-(16:56
nexus_adds68_: yes, the current docs dont work :0 use docker instead for now16:56
nexus_OR16:56
adds68_I'm trying to install ostree from source, however my libostree version is out of date also16:56
nexus_use debian testing16:56
ssam2https://gitlab.com/BuildStream/buildstream/issues/15916:56
ssam2libostree is ostree16:57
adds68_ssam2, which is what is confusing me :P16:57
adds68_ssam2, when i run ostree it says my libostree version is not up to date16:57
nexus_i believe libostree got removed in one of the updates...16:57
nexus_im not certain i cant rememeber16:57
adds68_yet i've compiled from the latest source16:57
ssam2i'll come have a look16:57
adds68_ssam2, \o/16:57
nexus_if you sort it, let me know :()16:57
nexus_:)*16:57
*** jude has quit IRC16:58
adds68_nexus_, aye i did ask what your solution was as i saw your issue16:58
juergbiprobably need to use stretch-backports similar to how it's required for jessie16:58
adds68_nexus_, i was hoping it wasn't Docker haha16:58
nexus_adds68_: yeah i say that a minute ago, for now, i used docker16:58
nexus_sowwy16:58
nexus_i think at one point, jonathanmaw gave me some files?? and that fixed it16:59
juergbior rather, jessie won't work anymore even with backports. buildstream ostree requirements was increased this summer or so16:59
nexus_but i did a clean install for the sake of documenting16:59
jonathanmawnexus_: i.e. I had a working source tree for ostree, but have lost the provenance of it17:00
* tlater wonders how long it will be until we can give installation instructions that only involve apt and python17:00
nexus_tlater: as soon as current sid becomes stable17:00
juergbifor debian stable, buster release, i suppose17:00
juergbifor stretch i expect the official backports repo to work17:01
juergbiwe just need to verify and update the docu17:01
juergbihttps://backports.debian.org/Instructions/17:02
nexus_juergbi: i'll look into that17:03
* nexus_ never got 2 people helping17:04
* nexus_ cries favouritism17:04
nexus_... that worked?17:09
tlater(Y)17:10
tlaterErm no17:10
tlater\o/17:10
* tlater doesn't know where that (Y) came from17:10
nexus_kk backports it is17:12
nexus_ssam2 seems to be working on something different with adds68_, lets see how that works out17:12
* nexus_ would rather not have to say "add backports" in the install docks17:12
adds68_it seems the buildsteam setup.py checks for an ostree version17:16
adds68_which if you build from source doesnt get added to the ostree binary17:17
adds68_ssam2, is looking into why that could be17:17
ssam2this is weird as17:18
ssam2i just built v2017.13 and installed into a prefix, and YEAR_VERSION is right there17:19
ssam2you built commit ae61321046ad7f4148a5884c8c6c8b2594ff840e right ?17:19
juergbissam2: maybe need to set GI_TYPELIB_PATH ?17:19
juergbiif it's not in /usr17:19
ssam2i thought we did, but will double check17:19
ssam2missing 'export' :/17:25
adds68_ssam2, as we don't install in /usr i cant get pip to install it as global command can i?17:29
adds68_ssam2, will i have to add bst to my path to call it?17:30
ssam2yeah I recommend `pip3 install --user`17:30
ssam2so bst goes in ~/.local/bin17:30
ssam2which you can add to your path if it's not present17:30
ssam2even better, `pip3 install --user -e` so that it runs the actual code from your git clone of buildstream.git17:31
ssam2saves you from having to reinstall after pulling or making changes17:31
nexus_is it working now?17:31
adds68_ssam2, awesome, thanks17:32
*** tiago has joined #buildstream17:35
adds68_nexus_, yes this works17:35
nexus_\o/17:35
nexus_ssam2, adds68_ what did you do? I'd like to have a look at it and see if it solved my problem17:35
nexus_:)17:35
adds68_nexus_, installed ostree from source, but not in /usr land, used /opt as ssam2 suggeted17:36
adds68_nexus_, installed ostree from source, but not in /usr land, used /opt as ssam2 suggested17:36
ssam2set GI_TYPELIB_PATH correctly so the .typelib file in /opt/ostree/lib/girepository-1.0 was picked up17:36
adds68_nexus_, also add that ^^17:36
nexus_adds68_: which source did you use?17:37
adds68_tag 2017.13, but master should work also17:37
nexus_kk ty17:37
* nexus_ shall look into this17:37
nexus_that sounds like a nicer fix than backports17:37
adds68_nexus_, ping me if you get blocked17:38
adds68_nexus_, aye defo17:38
nexus_adds68_: shall do17:38
*** bethw has quit IRC17:39
gitlab-br-botbuildstream: merge request (142-potentially-printing-provenance-more-than-once-in-loaderrors->master: Issue #142: Ensure we don't append provenances twice) #170 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/17017:46
gitlab-br-botbuildstream: issue #158 ("Support for lzip is missing") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/15817:48
gitlab-br-botbuildstream: merge request (lzip->master: Add support for lzip in tar source) #162 changed state ("closed"): https://gitlab.com/BuildStream/buildstream/merge_requests/16217:48
gitlab-br-botbuildstream: merge request (142-potentially-printing-provenance-more-than-once-in-loaderrors->master: Issue #142: Ensure we don't append provenances twice) #170 changed state ("closed"): https://gitlab.com/BuildStream/buildstream/merge_requests/17017:53
gitlab-br-botbuildstream: issue #142 ("Potentially printing provenance more than once in LoadErrors") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/14217:54
gitlab-br-botbuildstream: merge request (132-loading-external-plugins-works-without-explicit-requirement-in-project-conf->master: Resolve "Loading external plugins works without explicit requirement in project.conf") #125 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/12517:54
tristanssam2, can you help me update the docker ?18:01
ssam2ok18:02
*** jonathanmaw has quit IRC18:10
*** ssam2 has quit IRC18:24
*** tristan has quit IRC18:31
gitlab-br-botbuildstream: issue #167 ("Workspaced element's cache keys are calculated 4 times during a build") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/16718:42
*** valentind has joined #buildstream21:14
gitlab-br-botbuildstream: merge request (jjardon/configuration_parameters->master: WIP: buildstream/plugins/elements: Add *-global and *-local configuration variables) #171 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/17121:31
*** bethw has joined #buildstream21:44
gitlab-br-botbuildstream: merge request (jjardon/configuration_parameters->master: WIP: buildstream/plugins/elements: Add *-global and *-local configuration variables) #171 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/17121:45
gitlab-br-botbuildstream: merge request (jjardon/configuration_parameters->master: WIP: buildstream/plugins/elements: Add *-global and *-local configuration variables) #171 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/17121:45
gitlab-br-botbuildstream: merge request (jjardon/configuration_parameters->master: WIP: buildstream/plugins/elements: Add *-global and *-local configuration variables) #171 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/17121:45
gitlab-br-botbuildstream: merge request (jjardon/configuration_parameters->master: buildstream/plugins/elements: Add *-global and *-local configuration variables) #171 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/17121:51
gitlab-br-botbuildstream: merge request (jjardon/configuration_parameters->master: WIP: buildstream/plugins/elements: Add *-global and *-local configuration variables) #171 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/17121:52
gitlab-br-botbuildstream: merge request (jjardon/configuration_parameters->master: WIP: buildstream/plugins/elements: Add *-global and *-local configuration variables) #171 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/17121:58
gitlab-br-botbuildstream: merge request (jjardon/configuration_parameters->master: buildstream/plugins/elements: Add *-global and *-local configuration variables) #171 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/17122:02
gitlab-br-botbuildstream: merge request (jjardon/configuration_parameters->master: buildstream/plugins/elements: Add *-global and *-local configuration variables) #171 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/17122:03
gitlab-br-botbuildstream: merge request (jjardon/configuration_parameters->master: buildstream/plugins/elements: Add *-global and *-local configuration variables) #171 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/17122:05
*** bethw has quit IRC22:36
*** cs_shadow has quit IRC22:53
*** tristan has joined #buildstream22:57
gitlab-br-botbuildstream: merge request (jjardon/configuration_parameters->master: buildstream/plugins/elements: Add *-global and *-local configuration variables) #171 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/17123:04
*** valentind has quit IRC23:32

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