IRC logs for #buildstream for Monday, 2019-04-15

*** nimish2711 has joined #buildstream01:56
*** nimish2711 has quit IRC03:38
*** rdale has quit IRC04:58
*** tristan has quit IRC05:07
*** tristan has joined #buildstream05:21
*** alatiera has joined #buildstream06:25
*** abderrahim has quit IRC06:27
*** ChanServ sets mode: +o tristan07:38
*** nielsdg has quit IRC08:06
*** nielsdg has joined #buildstream08:07
*** toscalix has joined #buildstream08:20
*** rdale has joined #buildstream08:29
gitlab-br-botmarge-bot123 merged MR !1288 (tristan/platform-cache-quota-1.2->bst-1.2: Cache quote related backports) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/128808:45
*** tpollard has joined #buildstream08:49
*** alatiera has quit IRC08:59
*** alatiera has joined #buildstream09:00
gitlab-br-botmarge-bot123 merged MR !1261 (phil/expose-templated-tests->master: Expose templated source tests) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/126109:00
gitlab-br-bottristanvb opened MR !1289 (tristan/fix-non-strict-push-1.2->bst-1.2: Fix non strict push 1.2) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/128909:07
*** jonathanmaw has joined #buildstream09:08
*** raoul has joined #buildstream09:10
*** toscalix has quit IRC09:15
*** toscalix has joined #buildstream09:16
tristanphildawson, Want to take a look at #995 please ?09:31
gitlab-br-botIssue #995: Cannot choose what tests to run https://gitlab.com/BuildStream/buildstream/issues/99509:31
* tristan not sure but suspects this regression is from the plugin testing activities09:31
gitlab-br-bottristanvb opened issue #995 (Cannot choose what tests to run) on buildstream https://gitlab.com/BuildStream/buildstream/issues/99509:31
* phildawson takes a look09:35
*** lachlan has joined #buildstream09:37
phildawsontristan, you're correct, that is a regression is from my plugin testing work.09:39
tristanphildawson, I also cannot help thinking... do we really like the name 'plugintestutils' ?09:39
tristanseems like a pretty huge mouthful09:40
tristanmaybe something like 'testing' would be good, similar to how click exports their click.testing module09:40
phildawsonI personally thing it's fairly descriptive. I'm not overly attached to it though09:40
phildawsonthink09:40
phildawsonI'd also be happy with something like 'testing' if people prefer that.09:41
tristanLike, it's not like anything other than plugins ever uses the BuildStream API09:41
phildawsonTure09:41
phildawsonTrue09:41
tristan:)09:41
* phildawson can't type this morning09:41
* phildawson wonders what other people think09:41
tristanI mean, anyway it's not a huge deal but names will stick, I personally think we should change it before it stick09:42
tristans09:42
tristanIf people really *do* prefer that name I wouldnt complain09:42
gitlab-br-bottristanvb opened MR !1290 (tristan/fix-non-strict-push->master: Fix non strict push) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/129009:44
tristanjonathanmaw, already pinged you on #990, do you have an opinion on !1290 ?09:45
gitlab-br-botIssue #990: BUG in push with non-strict mode https://gitlab.com/BuildStream/buildstream/issues/99009:45
* jonathanmaw has a look09:46
tristanjonathanmaw, I found it interesting actually, I think just understanding this problem should be helpful for your refactoring work09:46
WSalmontristan, i am not really fussed what it is called but i am already using the cli tool from the pluging utils public API, i totally get that this is not stable and so i am not going to object to a name change but i would be sad if it change too often09:48
tristanWSalmon, yeah I understand, I just found this name to be unfortunate and probable worth the sedjobs earlier rather than later09:49
phildawsonIt doensn't look like bst-experimental is using plugintestutils yet, which also makes life slightly easier for the rename :)09:49
WSalmonThe plugin i am working on has a nice test sweat and should be made public at some time in the not to distant future09:50
raoulI prefer testing to plugintestutils fwiw, agree it's a bit of a mouthful09:51
* phildawson will get on that quickly then09:51
jonathanmawtristan: aha, the problem is that in `bst pull --non-strict`, Element._pull_pending assumes there's always going to be a pull. Thanks for pointing out that there's a time when this isn't true09:55
gitlab-br-botjonathanmaw approved MR !1290 (tristan/fix-non-strict-push->master: Fix non strict push) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/129009:55
tristanjonathanmaw, `bst push --no-strict` yeah09:57
jonathanmawah, yeah09:58
tristanjonathanmaw, note the FIXME comment I added, I'm not fussed if we change the whole paradigm of _schedule_foo()/_foo_done() for something different09:58
tristanBut it would be good if whether there is going to be a 'pull' is one of those foos and treated the same way as fetch/assemble/etc09:58
*** lachlan has quit IRC09:59
*** lachlan has joined #buildstream10:15
*** lachlan has quit IRC10:19
gitlab-br-botphildawson opened MR !1291 (phil/rename-plugintestutils->master: Rename 'plugintestutils' package to 'testing') on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/129110:23
tpollardtristan: looks like there's a test issue on 129010:24
*** gokcennurlu has joined #buildstream10:31
gitlab-br-botBenjaminSchubert opened issue #996 (Cache quota shouldn't be computed until we know we need to write to the cache) on buildstream https://gitlab.com/BuildStream/buildstream/issues/99610:44
tristantpollard, Eeek11:01
tristanThey are unrelated... do we have that many spurious errors in master now ?11:02
tpollardat least 3 of them had failed on the same test when I looked11:02
tpollardI've not seen that specific one11:02
tpollardgot a hit on a bazel issue via google though11:03
tristanohhh no it seems to be related11:04
tristanthis is strange now11:04
tristanbst artifact push --pullbuildtrees11:04
tristanthat complicates things11:04
tristanOk so... we have a case where bst artifact push, also pulls build trees11:05
tristanin that case, I suppose we need to not lie to the elements and tell them they've already been pulled11:05
*** nimish2711 has joined #buildstream11:10
tpollardthere's a couple of other instances of no pull commands that can spawns pulls via that option too11:10
tpollard*none pull11:10
tpollardor maybe just the build shell actually, the other one I was thinking about was workspace buildtrees but that's not landed11:11
tristanAhh, I wonder if bst shell suffers the same issue described in #990 !11:12
gitlab-br-botIssue #990: BUG in push with non-strict mode https://gitlab.com/BuildStream/buildstream/issues/99011:12
tristanI think not, trying it now11:15
*** nimish2711 has quit IRC11:18
tristanNot a problem for shell11:18
tristanI did `bst --no-strict shell core.bst`, and I'm seeing the weak (dark) cache keys related to elements getting staged11:19
tristanSo, we've resolved their keys without asking for a pull11:19
gitlab-br-botmarge-bot123 merged MR !1289 (tristan/fix-non-strict-push-1.2->bst-1.2: Fix non strict push 1.2) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/128911:21
*** lachlan has joined #buildstream11:36
*** lachlan has quit IRC11:41
gitlab-br-botcs-shadow opened issue #998 (Stack elements output empty "bst" directory) on buildstream https://gitlab.com/BuildStream/buildstream/issues/99811:47
*** lachlan has joined #buildstream11:49
*** lachlan has quit IRC11:53
*** lachlan has joined #buildstream11:59
gitlab-br-botmarge-bot123 closed issue #990 (BUG in push with non-strict mode) on buildstream https://gitlab.com/BuildStream/buildstream/issues/99012:00
gitlab-br-botmarge-bot123 merged MR !1290 (tristan/fix-non-strict-push->master: Fix non strict push) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/129012:00
*** lachlan has quit IRC12:03
*** lachlan has joined #buildstream12:07
*** lachlan has quit IRC12:17
gitlab-br-botraoul.hidalgocharman opened MR !1292 (raoul/974-Artifact-Rework->master: Artifact as a Proto: rework) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/129212:18
tpollard\o/12:18
*** tristan has quit IRC12:19
*** tristan has joined #buildstream12:28
*** lachlan has joined #buildstream13:19
*** lachlan has quit IRC13:24
*** lachlan has joined #buildstream13:31
*** lachlan has quit IRC13:34
*** lachlan has joined #buildstream13:35
*** lachlan has quit IRC13:44
*** tpollard has quit IRC13:58
*** raoul_ has joined #buildstream14:00
*** raoul has quit IRC14:02
laurenceis there an monthly irc meeting team tomorrow?14:04
laurenceI am quite sure there was one in the calendar - and I even emailed about it - but I can't see it in the calendar now14:05
toscalixlaurence: the serie finished on April 1514:06
toscalixperfect time for you to create the next serie14:07
toscalixso you become the organiser14:07
toscalixI would recommend you create it as an event of the public buildstream calendar14:07
laurencetoscalix, ok, thanks for that - i will figure out how to create it in the public calendar14:08
toscalixso anyone can join the invitation in case you need to change the schedule. Also the notifications will provide the contact info14:08
toscalixlaurence: first add the buildstream calendar to your calendars....14:09
*** nimish2711 has joined #buildstream14:09
toscalixcalendar ID: codethink.co.uk_mpgah0uj538hnbsf4l7b4rchts@group.calendar.google.com14:09
toscalixPublic URL to the calendar: https://calendar.google.com/calendar/embed?src=codethink.co.uk_mpgah0uj538hnbsf4l7b4rchts%40group.calendar.google.com&ctz=Europe%2FMadrid14:09
toscalixfor those using iCal format: https://calendar.google.com/calendar/ical/codethink.co.uk_mpgah0uj538hnbsf4l7b4rchts%40group.calendar.google.com/public/basic.ics14:09
toscalixI see your are already in the calendar as manager so you can already add events14:10
laurenceyeah i've always had it in my calendar14:15
laurencelet's see how to make a new event...14:16
*** lachlan has joined #buildstream14:17
laurenceah, it's a drop down when you create a new event. easy :)14:18
*** lachlan has quit IRC14:25
laurenceright that's done14:25
laurencei hope that anyone who is subscribed to the public calendar has now got an invite?14:26
*** nimish2711 has quit IRC14:27
laurencejuergbi, are you subscribed to the public calendar? did you get a note?14:27
*** nimish2711 has joined #buildstream14:27
juergbilaurence: I see it in my calendar but didn't get an invite mail14:28
laurenceok great, thank you14:29
laurencethat's good enough for me :)14:29
laurencethanks for your help, toscalix14:29
*** lachlan has joined #buildstream14:40
jennisraoul_, do you remember the failing test that was writing files like foo.bst-0?14:42
*** raoul_ has quit IRC14:43
*** tpollard has joined #buildstream14:44
*** raoul_ has joined #buildstream14:44
*** raoul_ is now known as raoul14:45
raouljennis, yeah think I raised an issue for it14:45
raoulyou find out what was causing it?14:46
*** nimish2711 has quit IRC14:50
*** nimish2711 has joined #buildstream14:50
tpollardjuergbi: with https://gitlab.com/BuildStream/buildstream/merge_requests/1292/ it introduces direct referencing/logic about buildtrees to _artfiactcache, are you ok with this? I know previously we've aimed to avoid specific content referencing re the buildtree there but removing the subdir/excluded_subdir parameters is a lot nicer imo15:06
juergbitpollard: I'll have to take a closer look but with the (proto) abstraction this should be much less of an issue15:10
tpollardcool15:10
*** nimish2711 has quit IRC15:10
*** nimish2711 has joined #buildstream15:11
*** lachlan has quit IRC15:15
*** lachlan has joined #buildstream15:16
jennisraoul, no but I'm seeing it elsewhere now15:25
*** nimish2711 has quit IRC15:26
raouloh, that's worrying15:26
raoulwhere?15:26
*** nimish2711 has joined #buildstream15:26
*** nielsdg has quit IRC15:28
raoulhmm it looks like on master, if you specify a test it will always run the plugintestutils tests, is this your doing phildawson?15:36
*** nimish2711 has quit IRC15:41
*** nimish2711 has joined #buildstream15:41
*** lachlan has quit IRC15:44
*** lachlan has joined #buildstream15:48
*** lachlan has quit IRC15:53
phildawsonraoul, it is.15:54
*** ChanServ sets mode: +o tristan15:56
* tristan points raoul at #99515:57
phildawsontristan, raoul, I'm working on it. In the mean time, if it helps, you can disable those tests by commenting out this line https://gitlab.com/BuildStream/buildstream/blob/master/tests/conftest.py#L18215:58
*** lachlan has joined #buildstream15:58
raoulah that'll be nice for now, ta15:59
* phildawson puts that on the issue15:59
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/129315:59
cs-shadowjuergbi: hi, if you find some time, might be worth having a look at ^16:00
juergbiwill do16:00
cs-shadowthanks!16:01
*** nimish2711 has quit IRC16:01
*** nimish2711 has joined #buildstream16:02
tristancs-shadow, I don't know if your branch will also intend to make sure we have a warning (or error) when we have out of sync projects16:03
tristanjuergbi, cs-shadow; if we can at least agree that that is problematic, I can take care of filing an issue16:03
*** lachlan has quit IRC16:04
juergbiyes, I agree as per our discussion16:04
tristanfrom what I recall in the thread, the diamond shape dependency graph (of projects) is worrisome, if a highlevel project is going to "decide" which edge to derive the common junction properties from, I think it is an error to blindly force those properties on the adjacent edge16:04
cs-shadowtristan: this branch doesn't at the moment as that's slightly orthogonal. The new method shouldn't allow for any new conflicts, but whatever conflicts were possible already will still be possible.16:04
cs-shadowI do agree that we should raise warnings16:04
tristancs-shadow, yes I understand it's orthogonal :)16:04
tristanok so as long as we agree, I'll file an issue first thing tomorrow16:05
cs-shadow+116:05
* tristan thinks it was a good discussion and a good observation, so doesnt want to leave it to get forgotten :)16:05
juergbithere should always be a way to override a specific warning/error, though16:06
tristanAlso agree16:06
*** nimish2711 has quit IRC16:07
tristanAt a high level, my thinking is that when I junction a project I probably use a tag of that project, and I want to have some guarantee that what I'm building is actually what that project advertizes via that tag16:07
tristananyway, I think we're all on the same page :)16:07
*** nimish2711 has joined #buildstream16:07
juergbiyes, I think we are :)16:09
*** toscalix has quit IRC16:12
*** nimish2711 has quit IRC16:17
*** nimish2711 has joined #buildstream16:17
*** nimish2711 has quit IRC16:22
*** nimish2711 has joined #buildstream16:23
*** benschubert has joined #buildstream16:40
*** lachlan has joined #buildstream16:44
*** nimish2711 has quit IRC16:48
*** nimish2711 has joined #buildstream16:48
*** nimish2711 has quit IRC16:58
*** nimish2711 has joined #buildstream16:58
*** nimish2711 has quit IRC17:23
*** nimish2711 has joined #buildstream17:24
*** lachlan has quit IRC17:26
*** raoul has quit IRC17:26
*** nimish2711 has quit IRC17:29
*** nimish2711 has joined #buildstream17:29
*** lachlan has joined #buildstream17:31
*** alatiera has quit IRC17:38
*** nimish2711 has quit IRC17:39
*** nimish2711 has joined #buildstream17:39
*** lachlan has quit IRC17:41
*** jonathanmaw has quit IRC17:42
*** nimish2711 has quit IRC17:44
*** nimish2711 has joined #buildstream17:45
*** lachlan has joined #buildstream17:50
*** nimish2711 has quit IRC17:55
*** nimish2711 has joined #buildstream17:55
*** lachlan has quit IRC17:56
*** lachlan has joined #buildstream18:00
*** nimish2711 has quit IRC18:05
*** nimish2711 has joined #buildstream18:05
*** jonathanmaw has joined #buildstream18:07
*** nimish2711 has quit IRC18:20
*** nimish2711 has joined #buildstream18:21
*** nimish2711 has quit IRC18:31
*** nimish2711 has joined #buildstream18:31
*** nimish2711 has quit IRC18:36
*** nimish2711 has joined #buildstream18:37
*** nimish2711 has quit IRC18:46
*** nimish2711 has joined #buildstream18:47
*** nimish2711 has quit IRC18:57
*** nimish2711 has joined #buildstream18:57
*** nimish2711 has quit IRC19:05
*** lachlan has quit IRC19:48
*** jibade has joined #buildstream19:56
*** jibade has quit IRC20:05
*** jonathanmaw has quit IRC20:08
laurencetristan, do you have the list moderator password for the list that you could pls email me?  I keep getting requests to approve mails but I'm pretty sure I was never given a moderator password (in fact I'm pretty sure I was just added as one and told about it after).20:48
laurenceNot that I mind being one20:48
laurenceOr you could remove me from being a mod?20:48
laurenceagain, don't mind either way20:48
*** alatiera has joined #buildstream22:27
*** alatiera_ has joined #buildstream22:59
*** alatiera has quit IRC22:59
*** alatiera_ is now known as alatiera23:00

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