IRC logs for #buildstream for Tuesday, 2018-03-06

*** toscalix has quit IRC00:16
*** Prince781 has joined #buildstream01:03
*** mcatanzaro has quit IRC03:35
*** tristan has joined #buildstream06:22
*** Prince781 has quit IRC08:44
*** valentind has joined #buildstream09:10
*** dominic has joined #buildstream09:22
*** dominic has left #buildstream09:22
gitlab-br-botbuildstream: merge request (tristan/shell-enhancements->master: WIP: Support env var expansion in shell configuration) #306 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/30609:28
gitlab-br-botbuildstream: merge request (tristan/shell-enhancements->master: WIP: Support env var expansion in shell configuration) #306 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/30609:28
jmacssssam[m]: Aha! Thanks for the advice.09:35
*** adds68 has joined #buildstream09:36
*** adds68 has quit IRC09:37
*** aday has joined #buildstream09:38
*** jonathanmaw has joined #buildstream09:44
*** adds68 has joined #buildstream10:02
jonathanmawHi tristan, I've been told there's a request for buildstream to be able to handle multiple repo aliases, but I can't find any open issue that discusses it10:08
jonathanmawthe closest I could find was https://gitlab.com/BuildStream/buildstream/issues/179 and that's only tangentially related10:09
tristanthat doesnt seem related10:12
tristanthat is artifact cache related, source aliases are different10:12
tristanthere was a request I think to do it in `git.py` plugin specifically, a weird request10:13
tristansomething about having a single source declaration have fallback uris to try the next one and then the next one10:13
tristanjonathanmaw, that issue I rejected in favor of proper source mirroring support, because the original request is really not desirable10:13
tristanmaybe this is not the same request you are talking about, but it seems to me that multiple repo aliases falls into the category of "Think about doing source mirroring properly"10:14
jonathanmawokay, so I should put together my own gitlab issue for this.10:15
tristanOr, maybe you should A.) find out the reason *why* this is being requested, and B.) figure out if that would *also* be solved by having support for source mirroring10:15
tristanand then C.) Write up a proposal to the list for how you might think source mirroring should work10:16
juergbijonathanmaw, tristan: https://gitlab.com/BuildStream/buildstream/issues/24410:17
tristanAh right, there it is :)10:18
*** valentind has quit IRC10:28
gitlab-br-botbuildstream: merge request (tristan/shell-enhancements->master: WIP: Support env var expansion in shell configuration) #306 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/30610:34
*** aday has quit IRC10:46
gitlab-br-botbuildstream: merge request (change_the_location_of_generate-base.sh->master: Changed the location of generate-base.sh) #307 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/30711:09
*** aday has joined #buildstream11:24
gitlab-br-botbuildstream: merge request (tristan/shell-enhancements->master: WIP: Support env var expansion in shell configuration) #306 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/30611:24
gitlab-br-botbuildstream: merge request (change_the_location_of_generate-base.sh->master: Changed the location of generate-base.sh) #307 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/30711:26
gitlab-br-botbuildstream: merge request (tristan/shell-enhancements->master: Support env var expansion in shell configuration) #306 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/30611:27
tristanjuergbi, so fyi... I've added an `environment` section to the `shell` project configuration, along side the existing `environment-inherit`, in the above MR 30611:29
tristanI wondered if maybe we should nuke `environment-inherit`, since one can achieve the same with the `environment` dictionary, with more verbosity11:29
tristanbut think lets just leave it in as it's a bit more convenient in the typical cases ?11:30
tristanjuergbi, any other API concerns before landing this ?11:30
juergbitristan: if `environment-inherit` didn't exist yet, I probably wouldn't add it but I don't have strong feelings on removing it11:34
juergbino concerns come to mind right now11:35
juergbi(as it's only needed in project.conf, i.e., once per project, convenience is not the biggest concern for me)11:36
tristanRight, I think we *could* potentially remove before a 1.2 if we want to11:36
tristanIf we do remove it, the main advantage I can see is more concise documentation11:36
juergbiyes, the configuration structure would be slightly simpler / stream-lined11:36
juergbihowever, it doesn't matter much, imo11:37
tristanWell, maybe I should do it now11:37
juergbiif we remove it, we should probably do it as soon as possible11:37
juergbito avoid other people having to migrate project.conf11:37
tristanit's not much work, I'll see what the project.conf for gnome-build-meta looks like11:37
tristanand with versioning it's nice that nothing breaks really11:37
tristanyeah, I'm gonna kill it11:39
tristanjuergbi, I can see that project.conf is *also* more readable without a mixture of both11:39
tristanthat sells me, work required is almost none11:40
tristanI think with this, I'm ready to roll out 1.1.111:40
tlaterOooh, another new buildstream release :)11:42
jjardon[m]\o/11:49
jonathanmaw\o/11:50
jonathanmawoh, one thing, I think11:51
tristanyeah this one mostly marks the addition of shell features making testing with `bst shell` more useful11:51
jonathanmawtristan: should we slip in https://gitlab.com/BuildStream/buildstream/merge_requests/304 first?11:51
tristanjonathanmaw, I'm not picky about that right now to be honest11:59
jonathanmawokie doke11:59
tristanjonathanmaw, mostly because, people usually read the docs on the web page, I dont think anyone is building it themselves11:59
tristanjonathanmaw, wait a sec... I *AM* certainly picky about that, just dont think it merits holding the release for :D12:00
jonathanmawheh12:00
tlatertristan: This is entirely unrelated, but should we perhaps start having a look at opening the testutils api? jennis_ has had to copy that module to bst-external, it would be nice to nip that duplication in the bud.12:01
tristantlater, I've mentioned before that I'm interested in sharing this API yes, the only question is who will work on doing it :)12:01
tristanand when :)12:02
tlaterDo we have an open issue yet?12:02
* tlater can't remember off the top of his head12:02
tristantlater, you will also see that I've done a minor refactor in the integration Cli fixture12:02
tristanafter I merge my branch...12:02
* tlater opens an issue for opening the testutils api - probably more likely we'll get someone to do it that way ;) 12:04
gitlab-br-botbuildstream: merge request (tristan/shell-enhancements->master: Support env var expansion in shell configuration) #306 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/30612:05
tlatertristan: Ah, I see, yeah, that's prettier :)12:07
tlaterBetter than trying to force the same project.conf on everything12:07
tristantlater, yeah this is a hybrid of both; we keep a template around where the source aliases are defined in one place; and composite test case specific stuff on top of the loaded project.conf12:09
tristanapi is better, and stuff defined in less places12:09
gitlab-br-botbuildstream: issue #281 ("Make the testutils API public") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/28112:20
gitlab-br-botbuildstream: merge request (tristan/shell-enhancements->master: Support env var expansion in shell configuration) #306 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/30612:20
gitlab-br-botbuildstream: merge request (jmac/build-uid->master: WIP: Specify custom UID for build sandbox in elements) #301 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/30112:24
ltuanyone have anything to discuss for the meeting at 14:00 UTC?12:27
tristanI was going to ask the same :)12:30
tristanagenda looks thin, and at the same time things are pretty fast moving12:31
gitlab-br-botbuildstream: merge request (239-use-pylint-for-linting->master: Resolve "Use pylint for linting") #283 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/28312:33
*** mcatanzaro has joined #buildstream12:35
gitlab-br-botbuildstream: merge request (tristan/shell-enhancements->master: Support env var expansion in shell configuration) #306 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/30612:37
*** aday has quit IRC12:46
*** ChanServ sets mode: +o tristan12:53
*** tristan changes topic to "/BuildStream 1.1.1 is out ! | https://gitlab.com/BuildStream/buildstream | Docs: https://buildstream.gitlab.io/buildstream | IRC logs: https://irclogs.baserock.org/buildstream | Roadmap: https://wiki.gnome.org/Projects/BuildStream/Roadmap"12:53
gitlab-br-botbuildstream: merge request (239-use-pylint-for-linting->master: Resolve "Use pylint for linting") #283 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/28312:55
gitlab-br-botbuildstream: merge request (239-use-pylint-for-linting->master: Resolve "Use pylint for linting") #283 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/28312:57
jennis_juergbi ^^ rebased the linting branch so it's aligned with master12:59
juergbita13:00
*** jmac has quit IRC13:02
*** jmac has joined #buildstream13:02
gitlab-br-botbuildstream: issue #223 ("Make it possible to run functional GNOME apps from bst shell") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/22313:07
juergbi\o/13:08
tristananother one bites the dust :)13:12
* tlater is a bit disappointed at how much code he has to duplicate from OSTree.diff_dirs :|13:12
tlaterLooks like about 200 loc in total13:13
*** aday has joined #buildstream13:14
tristanjuergbi, jonathanmaw... just pushed this for docs now, fyi: https://gitlab.com/BuildStream/buildstream/commit/5a0f56af779c18eee27d1ae2d617faa4b01f168713:14
tristanthat is a pattern now, anything added in the format should indicate the since version13:14
juergbimakes sense, ta13:15
* tristan also notes ...13:20
tristanIt's very pleasant how tab completion is much more responsive now :)13:20
tristannoticeably13:20
juergbiyes, i noticed this as well13:21
tlater\o/13:21
tristanltu, I'd like to add to the agenda: "Feature prioritizations"13:31
*** sstriker has joined #buildstream13:33
tristanltu, I have a couple of items, and think it might be good to have some chat by interested parties regarding prioritization13:33
* sstriker peeks up13:33
gitlab-br-botbuildstream: issue #282 ("Status bar regression after enhancing log configurability") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/28213:41
ltutristan, sure, added13:47
*** tristan has quit IRC13:48
*** tristan has joined #buildstream13:55
tristannb all: Monthly (or rather 4-weekly) team meeting starting in a few minutes in #buildstream-meetings13:57
*** sstriker has quit IRC13:58
*** jennis_ is now known as jennis13:58
*** sstriker has joined #buildstream13:59
ltuwe're just starting the meeting now, over in #buildstream-meetings14:03
*** aday has quit IRC14:56
persiaMeeting log at http://meetbot.gnome.org/buildstream-meetings/2018/buildstream-meetings.2018-03-06-14.04.log.html for anyone who didn't make it.15:08
*** aday has joined #buildstream15:12
jennisThe file tests/integration/base/generate-base.sh doesn't seem to be "called" anywhere and when manually run it creates an alpine-base.tar.gz file which looks to contain the sysroot of the alpine docker image15:33
jennisTo update the integration tests in bst-external I need to have quilt installed in the alpine docker image, tlater has suggested modifying said script to include quilt and then point the import element to the generated tar file15:34
jennisHowever, when pointing to this tar file before I make any changes to the .sh script, the majority of integration tests fail15:36
jennisIs this because the use of this tar file is redundant?15:36
tristanThe tarball is not to be revisioned in the BuildStream git repo.15:36
tristanIntegration tests require an external runtime to be downloaded; it's up to us to host it somewhere if we want to run the integration tests15:37
nexusthis whole tar docker img thing is confusing15:37
tristanThe script is important if we ever want to be able to update the tarball15:37
tristanProbably the first thing you want to do, is add buildstream/tests/integration/README15:38
jennisI think tlater wads going to add something to HACKING...?15:39
tlaterjennis: Yep, not related to this image though; I was only made aware of it by you15:39
tristanHACKING is a good place for this to be documented too yes15:40
tlaterCould also document the update process though, I'm pretty sure I know how it works at this point15:40
tlaterAs for your issue, jennis, I'm pretty sure you are just misconfiguring your base-alpine.bst15:40
tlaterWould you mind sharing it so we can have a look?15:40
jennistristan, the tar file created by this script != https://gnome7.codethink.co.uk/tarballs/integration-tests-base.v1.x86_64.tar.xz15:40
tlaterA paste of the test failures would be neat too.15:40
jennisHow do you update the latter...?15:40
tristanjennis, first of all; I dont think you update the latter15:41
tristanjennis, if this is something for bst-external, then bst-external uses a different tarball, that is slightly more heavy by virtue of including quilt15:41
tristannext, you figure out hmmm, where should we host this15:42
jennisit does or it should?15:42
tristanbst-external != buildstream15:42
tristanTo the maintainers of bst-external: We do not make any promises that our own integration testing sysroot provides things your integration tests depend on.15:43
tlaterRight, wouldn't make sense to slow buildstream's tests down for this...15:44
jmacI'm not sure who the maintainers of bst-external are now ssssam's wondered off.15:44
tristanRight, that is a separate topic, I'm just clarifying separation :)15:45
tlaterjmac: I think jonathanmaw is practically the maintainer at this point15:45
tristanAlso, you might coordinate with https://gitlab.com/BuildStream/buildstream-docker-images15:45
tristanif you want centralization of a common generator script which generates both15:45
tristanand you may want to push for that repo to add automation of hosting of tarballs for both projects in some way15:46
tlatertristan: Would we want to host those tarballs on gnome7?15:46
tlaterdockerhub can't host tarballs unfortunately15:46
tristanthat might be a reasonable proposal, that someone might want to write up, if they wanted such separation, because of something they are working on.15:47
jennistlater, there's my base-alpine.bst15:47
jennistristan, you mentioned that bst-external uses a different tarball15:47
tristantlater, that does not really mean that https://gitlab.com/BuildStream/buildstream-docker-images doesnt have a .gitlab-ci.yml for automation of "things"15:47
jennisThe old style tests do not seem to point to any tarball15:48
tristanjennis, I am not aware of the details of what bst-external uses; I made a statement that buildstream will not guarantee anything to external consumers, when it comes to *our* internal testing sysroot tarball.15:48
tlaterjennis: As for what bst-external *currently* uses, it uses a slightly odd version of gnome's flatpak sdk15:49
tristantlater, I dont know if gnome7 is going to continue being that place we use for that honestly; we may decide to move the sysroot tarball somewhere else, too15:49
tristantlater, in light of new infra which has arisen for ostree sysroots and artifact caches15:50
tlaterAh, I hadn't heard of that yet15:50
tlaterBut anyway I think it's important to streamline this process a bit; having someone manually scp a file to gnome7 isn't very newcomer friendly15:50
tristanwell, we had some issues with infra stability; and require more production support for artifact caches, than what could immediately be provided for those aarch64 sleds15:51
tristanSo gnome7 might go away and become a flathub arm machine, or an aarch64 SDK builder, possibly by way of running a gitlab worker15:51
tristantlater, exactly, that's the right thinking; probably someone should think it over, come up with a plan and propose it in some way15:53
tlaterAssuming we can figure out where to host this I can probably have a look. Wouldn't want poor jennis' branch to be left in the void for too long ;)15:54
tristanOne can always come up with a prototype and move to a more permanent hosting later15:55
tristanThis is why buildstream has a `sysroot` alias for integration tests, and the gnome7 URL is only specified in exactly one place15:56
tristan(for the alpine sysroot)15:56
tlaterYeah, that seems fine. Man this alias feature is a lot cooler than I originally thought :)15:57
gitlab-br-botbuildstream: merge request (issue-243_dpkg_import_source_plugin->master: WIP: Created DPKG Source plugin for Issue #10) #305 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/30516:29
adds68Hi, i have a dependency in a file, that i only want to build on specific platforms, is there anyway to specify this?16:40
juergbiadds68: if you have a project option for this you can use a (?) conditional around the dependency16:45
adds68Hi juergbi, do these options have to be defined in the project.conf?16:48
juergbiyes16:48
juergbihttps://buildstream.gitlab.io/buildstream/projectconf.html#options16:48
adds68cheers, i shall take a look, i think we do have some options defined16:49
*** noisecell has quit IRC16:53
ltuMilestone created to capture immediate priorities - https://gitlab.com/BuildStream/buildstream/milestones/117:05
ltuNo dates assigned, for now.17:05
tlaterOh, that means we'll get pretty work-efficiency graphs in the nearish future :)17:09
juergbionly if we added a due date17:12
juergbiand as we use this only to track the immediate priorities, it wouldn't be that useful17:12
*** xjuan has joined #buildstream17:17
*** jonathanmaw has quit IRC17:19
*** valentind has joined #buildstream18:20
*** Prince781 has joined #buildstream19:47
*** xjuan has quit IRC19:56
*** Prince781 has quit IRC20:16
*** aday has quit IRC20:58
*** valentind has quit IRC21:53
*** tristan has quit IRC22:25
*** xjuan has joined #buildstream22:48
*** xjuan has quit IRC23:00

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