IRC logs for #buildstream for Thursday, 2019-04-18

*** alatiera has joined #buildstream01:19
*** tristan has quit IRC02:48
*** tristan has joined #buildstream03:21
*** nimish2711 has joined #buildstream03:23
*** nimish2711 has quit IRC03:38
*** nimish2711 has joined #buildstream03:38
*** nimish2711 has quit IRC04:03
*** nimish2711 has joined #buildstream04:08
*** nimish2711 has quit IRC04:19
*** nimish2711 has joined #buildstream04:20
*** alatiera has quit IRC04:25
*** cgmcintyre[m] has joined #buildstream04:27
*** connorshea[m] has joined #buildstream04:27
*** asingh_[m] has joined #buildstream04:27
*** awacheux[m] has joined #buildstream04:27
*** abderrahim[m] has joined #buildstream04:27
*** albfan[m] has joined #buildstream04:27
*** Demos[m] has joined #buildstream04:27
*** doras[m] has joined #buildstream04:27
*** dbuch has joined #buildstream04:27
*** Trevinho[m] has joined #buildstream04:27
*** dineshdb[m] has joined #buildstream04:27
*** jjardon[m] has joined #buildstream04:27
*** kailueke[m] has joined #buildstream04:27
*** pro[m] has joined #buildstream04:28
*** inigomartinez has joined #buildstream04:28
*** m_22[m] has joined #buildstream04:28
*** rafaelff[m] has joined #buildstream04:28
*** theawless[m] has joined #buildstream04:28
*** ssssam[m] has joined #buildstream04:28
*** waltervargas[m] has joined #buildstream04:28
*** segfault3[m] has joined #buildstream04:28
*** mattiasb has joined #buildstream04:28
*** krichter[m] has joined #buildstream04:28
*** tlater[m] has joined #buildstream04:28
*** nielsdg has joined #buildstream04:28
*** skullone[m] has joined #buildstream04:28
*** mrmcq2u[m] has joined #buildstream04:28
*** tchaik[m] has joined #buildstream04:28
*** reuben640[m] has joined #buildstream04:28
*** nimish2711 has quit IRC04:35
*** nimish2711 has joined #buildstream04:35
*** nimish2711 has quit IRC04:40
*** nimish2711 has joined #buildstream04:40
*** nimish2711 has quit IRC04:45
*** nimish2711 has joined #buildstream04:46
*** alatiera has joined #buildstream04:55
*** nimish2711 has quit IRC06:01
*** nimish2711 has joined #buildstream06:01
*** nimish2711 has quit IRC06:16
*** nimish2711 has joined #buildstream06:27
*** nimish2711 has quit IRC06:37
*** nimish2711 has joined #buildstream06:37
*** nimish2711 has quit IRC06:57
*** nimish2711 has joined #buildstream06:57
*** nimish2711 has quit IRC07:02
*** nimish2711 has joined #buildstream07:03
*** nimish2711 has quit IRC07:18
*** nimish2711 has joined #buildstream07:18
*** nimish2711 has joined #buildstream07:19
*** ikerperez has joined #buildstream07:23
*** rdale has joined #buildstream07:26
*** nimish2711 has quit IRC07:29
*** nimish2711 has joined #buildstream07:29
*** nimish2711 has joined #buildstream07:29
*** nimish2711 has joined #buildstream07:30
*** nielsdg_ has joined #buildstream07:32
*** nimish2711 has quit IRC07:40
*** nimish2711 has joined #buildstream07:40
*** nimish2711 has quit IRC07:45
*** nimish2711 has joined #buildstream07:45
* Kinnison takes a small box of cats and sets them amongst you pigeons :D07:46
*** jennis has joined #buildstream07:54
*** nimish2711 has quit IRC07:55
*** nimish2711 has joined #buildstream07:56
*** nimish2711 has quit IRC08:01
*** nimish2711 has joined #buildstream08:01
*** toscalix has joined #buildstream08:05
*** toscalix has quit IRC08:07
*** toscalix has joined #buildstream08:07
*** nimish2711 has quit IRC08:21
*** nimish2711 has joined #buildstream08:22
*** nimish2711 has quit IRC08:37
*** nimish2711 has joined #buildstream08:37
*** nimish2711 has quit IRC08:52
*** nimish2711 has joined #buildstream08:52
*** jonathanmaw has joined #buildstream08:57
*** nimish2711 has quit IRC09:02
*** nimish2711 has joined #buildstream09:03
*** phil has joined #buildstream09:03
*** tpollard has joined #buildstream09:04
*** nimish2711 has quit IRC09:13
*** nimish2711 has joined #buildstream09:13
*** lachlan has joined #buildstream09:46
*** nimish2711 has quit IRC09:48
*** nimish2711 has joined #buildstream09:48
philIt looks like the CI in bst-experimental is still using a docker image with bst 1.2. I believe it needs to be updated to one which contains BuildStream master, but I'm not sure which image tag to use.  I'm stuck between nightly, and nightly-master-56618785. My gut feeling is the later, as it would make for a more predictable CI, but given the rate of change in buildstream at the moment there's potential that this won't be updated as often as it09:51
philshould be.09:51
*** nimish2711 has quit IRC09:53
Kinnisonexperimental should surely use nightly?09:53
Kinnisonit is, after all, experimental09:53
KinnisonAt least until bst2 drops09:53
*** nimish2711 has joined #buildstream09:54
jennisI agree, nightly should be the one to use09:55
*** lachlan has quit IRC10:04
*** nimish2711 has quit IRC10:04
*** nimish2711 has joined #buildstream10:04
philNightly it is then10:05
*** lachlan has joined #buildstream10:08
*** nimish2711 has quit IRC10:09
*** nimish2711 has joined #buildstream10:09
*** tristan has quit IRC10:12
*** tristan has joined #buildstream10:12
*** ChanServ sets mode: +o tristan10:12
tristanphil, jennis, Kinnison ... I kind of disagree10:12
tristanBefore you go ahead and change it, please just hear me out :)10:12
tristanI mean, obviously it should be using master10:12
tristanBut... We have carefully setup CI before to always use explicit refs10:12
tristanThis is because we want to be sure that the only thing that ever changes from on CI run to the next, is the commit which is under CI10:13
tristanSo, the idea is that explicitly updating the ref to an external counterpart, *also* explicitly triggers CI10:14
tristanI believe I had a conversation with juergbi at some point where we discussed the possibility of a nightly automated MR, which would *attempt* to update the ref in a .gitlab-ci.yml, and merge if that passes10:15
tristanjennis, phil Does that make sense ^^^ ?10:15
jennisSo you're proposing to have a testsuite-image container, and then clone + install BuildStream at the very latest master? Rather than whatever master was from last night?10:15
philtristan, I could see arguments for both, hence my asking :) That was also my initial leaning, though as I said, I do worry slightly that a fixed image won't be updated often enough.10:15
KinnisonAll I care is that at least one of the repos attempts to marry master-of-buildstream and master-of-bst-experimental10:15
KinnisonI don't mind how that happens10:16
tristanjennis, I am proposing that we *always* use an exact ref for any merge request10:16
tristanjennis, not a moving target, ever10:16
tristanjennis, and that *moving* that target equally needs to pass through CI10:17
tristanjust trying to explain to jennis why this is important, to always know whether it was a change in BuildStream, or a change in a merge request, which causes a test to break10:18
tristan(I think Kinnison and phil already understood :))10:18
jennisYeah, I still don't think I'm following10:18
*** nimish2711 has quit IRC10:19
tristanjennis, Ok so this is the same reason that (A) we used to have all dependencies in a docker image preinstalled for BuildStream CI ... and that (B) When we changed that, we started pinning *all* dependencies to exact versions in a requirements.txt file (to allow easier docker maintenance)10:19
*** lachlan has quit IRC10:20
*** nimish2711 has joined #buildstream10:20
tristanjennis, Basically when someone submits a merge request... we don't want to introduce any changing noise, we want to know that it is the *commit* that we are testing, and not some external debris10:20
jennisThanks tristan, also just had a quick chat with phil, I understand it now10:21
tristanjennis, Likewise, any update to the requirements.txt files also goes through CI, so when we update those, we know if an external dependency is what caused CI to break10:21
tristanSo it would be possible for example, on some host... to setup a node.js script which automatically submits a merge request to bst-experimental every night10:22
tristanThat would be the really awesome solution10:22
philI do really like the idea of the CI periodically auto updating the image it uses10:22
tristanjennis, i.e. imagine that every night there is an automatically submitted merge request which updates .gitlab-ci.yml with the latest ref of BuildStream master10:23
*** lachlan has joined #buildstream10:23
tristanit's actually not all that hard to do10:23
jennisYes I agree that something like that needs to happen otherwise we run the risk of our plugins becoming incompatible, right?10:23
tristanonce you've got some sample of a node.js script and a host to run it on a cron job :)10:23
tristanjennis, Indeed, or it needs to be done periodically10:24
tristanautomating it would be great though10:24
jennisI agree10:24
philI imagine it could probably be done via a periodic gitlab CI job, which could commit directly if CI passes, rather than needing human intervention on a MR every day.10:24
philAnd perhaps provide some sort of notification (e.g raise an issue) if the auto update fails.10:25
philAny way, we're getting a bit sidetracked. For now I just want to update the image currently being used.10:26
*** lachlan has quit IRC10:33
* phil goes for nightly-master-56618785 for now.10:34
philCrossing my fingers that CI passes10:34
tristanphil, I'm not sure that it is possible to do *on gitlab*, but it might even be !10:36
tristanphil, I suspect we'd still need to use a node.js script from inside the job in order to trigger the merge request10:36
tristanas there is no self-merge-request-generation kind of feature that I know of10:36
tristanBut automatically generating merge requests with the gitlab API is something I've done few years ago...10:36
tristanCould probably find that code, would have to search a bit10:37
* phil wonders if the gitlab API has a python client10:37
philhttps://python-gitlab.readthedocs.io/en/stable/10:37
philIt does :)10:37
philI guess it was too much to hope that updating the image would just work10:39
tristanOh that's cute, but in any case it's mostly just a simple restful API :)10:41
gitlab-br-botmarge-bot123 closed issue #995 (Cannot choose what tests to run) on buildstream https://gitlab.com/BuildStream/buildstream/issues/99510:43
gitlab-br-botmarge-bot123 merged MR !1297 (phil/fixup-templated-test-collection->master: Ensure templated source tests aren't collected unconditionally) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/129710:43
*** lachlan has joined #buildstream10:52
* phil smiles at pytest --sw10:56
gitlab-br-bottpollard opened issue #1003 (Simplify metadata within Artifact class) on buildstream https://gitlab.com/BuildStream/buildstream/issues/100311:09
*** nimish2711 has quit IRC11:10
*** nimish2711 has joined #buildstream11:10
*** tristan has quit IRC11:11
*** rdale has quit IRC11:12
*** nimish2711 has quit IRC11:20
*** nimish2711 has joined #buildstream11:20
*** nimish2711 has quit IRC11:30
*** nimish2711 has joined #buildstream11:31
laurenceah we reached issue #100011:33
*** tristan has joined #buildstream11:36
*** nielsdg_ has quit IRC11:38
*** nimish2711 has quit IRC11:40
*** nimish2711 has joined #buildstream11:42
*** nielsdg_ has joined #buildstream12:01
*** kapil___ has joined #buildstream12:02
tpollardnice summary email on the plugins tristan12:02
*** alatiera_ has joined #buildstream12:35
*** alatiera has quit IRC12:35
*** alatiera_ is now known as alatiera12:36
*** rdale has joined #buildstream12:50
gitlab-br-botcs-shadow opened (was WIP) MR !1293 (chandan/pseudo-junction->master: Add support for defining target for junction elements) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/129313:31
*** alatiera_ has joined #buildstream13:36
*** alatiera has quit IRC13:37
*** alatiera_ is now known as alatiera13:37
*** nimish2711 has quit IRC13:43
*** phildawson_ has joined #buildstream14:03
*** phil has quit IRC14:03
*** nimish2711 has joined #buildstream14:09
*** nimish2711 has quit IRC14:10
*** nimish2711 has joined #buildstream14:11
*** phildawson_ has quit IRC14:14
*** phildawson_ has joined #buildstream14:14
*** nimish2711 has quit IRC14:15
*** nimish2711 has joined #buildstream14:16
tpollardjuergbi: I'll get around to replying to comments on !1292 just getting it rebased against master first14:27
gitlab-br-botMR !1292: Artifact as a Proto: rework https://gitlab.com/BuildStream/buildstream/merge_requests/129214:27
juergbisure, makes sense14:28
coldtomany interest for a hg plugin in bst-external/bst-plugins-experimental? i've got one which *seems* to work here https://gitlab.com/coldtom/bst-in-bst/blob/master/plugins/sources/hg.py14:31
*** lachlan has quit IRC14:57
*** toscalix has quit IRC15:00
*** lachlan has joined #buildstream15:06
*** lachlan has quit IRC15:29
jonathanmawtristan: jennis and I have sorted out the changes after !1271, ready for you to have a look at15:42
gitlab-br-botMR !1271: Follow-up from "Artifact 'abstraction' class" https://gitlab.com/BuildStream/buildstream/merge_requests/127115:42
gitlab-br-botjennis approved MR !1293 (chandan/pseudo-junction->master: Add support for defining target for junction elements) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/129315:54
*** lachlan has joined #buildstream16:07
*** alatiera has quit IRC16:14
*** alatiera_ has joined #buildstream16:14
*** alatiera_ is now known as alatiera16:15
*** lachlan has quit IRC16:16
cs-shadowjuergbi: is !1293 good for you now? I was about to marge it but was wondering if you wanted to have a final look16:40
*** lachlan has joined #buildstream16:42
juergbics-shadow: it generally looks good to me. I'm wondering about 'Note that when targeting another junction, the names of the junction element must not be the same as the name of the target.'16:43
juergbiI understand why that's the case but we should probably lift this limitation16:43
juergbiand I'm wondering whether we should try to lift it now or defer this16:43
cs-shadowjuergbi: I was thinking the same thing. I think it will be useful to not have this limitation but that may require some rework around the loader. Would you be okay with creating an issue to fix this separately?16:45
cs-shadowI do think we should do that but I don't want to block this change because of that16:45
cs-shadow(I mean I can create the issue if that's okay with you)16:46
juergbics-shadow: ok, let's open an issue for this. we might end up tweaking the semantics a bit but I think the approach in the MR is simple enough for this to be low risk16:46
cs-shadowjuergbi: cool, thanks! I am bit keen to get this landed this soon as this will unblock a few things on our side16:47
*** tpollard has quit IRC16:51
gitlab-br-botcs-shadow opened issue #1005 (Allow junction elements to be named same as junction targets) on buildstream https://gitlab.com/BuildStream/buildstream/issues/100517:07
*** lachlan has quit IRC17:09
gitlab-br-botmarge-bot123 merged MR !1293 (chandan/pseudo-junction->master: Add support for defining target for junction elements) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/129317:15
*** jonathanmaw has quit IRC17:36
*** nielsdg_ has quit IRC18:33
*** nimish2711 has quit IRC19:33
*** kapil___ has quit IRC20:30
*** cs-shadow has quit IRC20:38
*** alatiera has quit IRC21:35

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