IRC logs for #buildstream for Thursday, 2018-12-13

*** mohan43u has quit IRC00:28
*** mohan43u has joined #buildstream00:32
*** xjuan has quit IRC01:02
*** alatiera has joined #buildstream01:12
*** alatiera has quit IRC01:17
*** kapil___ has joined #buildstream02:01
*** juergbi has quit IRC03:16
*** juergbi has joined #buildstream03:25
*** nimish has joined #buildstream04:11
*** kapil___ has quit IRC04:50
*** nimish has quit IRC05:32
*** toscalix has joined #buildstream06:44
*** nimish has joined #buildstream07:06
*** tristan has joined #buildstream07:07
*** juergbi has quit IRC07:08
*** lagarcia_ has joined #buildstream07:09
*** juergbi has joined #buildstream07:10
*** tristan has quit IRC08:07
*** tristan has joined #buildstream08:33
*** nimish has quit IRC08:36
*** nimish has joined #buildstream08:37
*** nimish has quit IRC08:47
*** nimish has joined #buildstream08:47
*** nimish has quit IRC09:02
*** nimish has joined #buildstream09:02
*** toscalix has quit IRC09:08
*** toscalix has joined #buildstream09:10
*** toscalix has quit IRC09:12
*** kapil___ has joined #buildstream09:18
*** ChanServ sets mode: +o tristan09:38
tristanjuergbi, is there any reason why manual plugin does not set BST_VIRTUAL_DIRECTORY = True ?09:38
* tristan thinks he will make sure all build elements do this09:39
tristanlooks like there are a bunch that dont, makemaker does not, and make does; very strange09:40
Kinnisontristan: It's possibly worth waiting to see if jmac can weigh in on this, I think BST_VIRTUAL_DIRECTORY was from his introduction of the CASCache stuff ready for remote execution09:42
tristanKinnison, it was python and perl related plugins that were left behind, makemaker, modulebuild, pip and distutils09:45
tristanOh, and manual09:45
tristanThey are all simple BuildElement implementations, and don't behave any differently except for having different default commands09:46
gitlab-br-bottristanvb opened MR !1009 (tristan/dont-batch-prepare-assemble-by-default->master: Dont batch prepare assemble by default) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/100909:54
*** jonathanmaw has joined #buildstream09:56
*** tiagogomes has joined #buildstream09:59
*** raoul has joined #buildstream10:01
*** nimish has quit IRC10:02
*** nimish has joined #buildstream10:03
benschubertHey tristan , if you have time, it would be nice if you could give a final check to !702 before I go merge since it uses mocking in tests :)10:09
gitlab-br-botMR !702: Mock storage space checks for tests. https://gitlab.com/BuildStream/buildstream/merge_requests/70210:09
Nexusjuergbi: re: https://gitlab.com/BuildStream/buildstream/merge_requests/925#note_124450122   Do we actually support having a workspace which is also an project directory? This seems very odd to me10:15
Kinnisoncan we open a workspace on a junction, to edit the junction?10:16
KinnisonIf so, then yes10:16
Nexusapparently we can10:19
tristanbenschubert, oh still this one !10:22
benschuberttristan: Yes, sorry about that, it's the last test that prevents the testsuite from working on my personnal laptop :)10:22
tristanbenschubert, lets merge it... needs a rebase10:23
* tristan hits button10:24
tristanbenschubert, lucky you, you dont have dozens of failing linter checks ?10:24
benschubertMmh not last time I checked, but I haven't tested it for a while, been busy with fixing wsl failures :)10:29
*** lachlan has joined #buildstream10:30
tristanbenschubert, there is an issue of the linter updates and the linter's dependency updates inadvertently changing the behavior of the linter, such that things work in CI, but fail depending on what you happen to have on your laptop10:31
tristanwhich is... really annoying10:31
tristanI mean, the linter finding new problems is always good, but random testing behavior is not10:32
benschuberttristan: One thing I used to ud to avoid that is have two files: "dev-requirements.in", containing my base requirements with version range, and then a "dev-requirements.txt" which freeze the exact version of all dependencies. It allows to prevent such random behavior, having developers always install the .txt version, and the other one being used only when upgrading all deps10:33
benschubertWhich was propsoed actually by cs-shadow  in https://mail.gnome.org/archives/buildstream-list/2018-December/msg00054.html , I guess all those problem will go away once we do this :)10:34
tristanbenschubert, I tried a variety of version pinnings but couldnt find exactly the relevant things; of course at least separating the deps for developers and those for runtime is good, but then the point of having multiple CI runs on multiple distros is sort of to ensure that we do still pass our tests on a variety of likely existing dependency versions10:37
*** nimish has quit IRC10:38
benschuberttristan: sorry, I meant the .txt being used in the CI and by developers and the .in verison only used when someone wants to explicitely update the versions :)10:39
tristanjmac, I put 5 commits on this branch which extends support for virtual directories to the build elements where I think it was simply missed: https://gitlab.com/BuildStream/buildstream/merge_requests/1009/commits10:39
benschubertAh no sorry misread you10:39
tristanbenschubert, it's a bit of a pickle yeah10:39
tristanI think for now the first thing is to just fix all the linting problems with the latest versions of things10:40
tristanand anyway the CI remains stable because it always has exact versions of things in the docker images10:40
benschubertWe can also use the .in/.txt separation for dev-requirements anyways, since this if for developers and not for users10:40
benschubertThis would reduce the problems already10:41
tristanonly problem is *sometimes* we need to fix new linting errors on peoples laptops when they upgrade to new versions we havent seen yet10:41
*** nimish_ has joined #buildstream10:41
tristanbenschubert, it's kind of desirable to have developers work with a variety of environments too though right ? I mean we should catch more problems that way10:41
Nexustristan: did you have a chance to look at https://gitlab.com/BuildStream/buildstream/merge_requests/925#note_124513015 ?10:43
*** nimish_ has quit IRC10:43
benschuberttristan: Yes and no, I would expect every developer on a python project to use a virtual environment specific for this package, and having the test dependencies then would not be too disturbing I would say. I do agree on the normal requirements though, since those are the ones that might change for users10:43
*** nimish_ has joined #buildstream10:43
tristanbenschubert, yeah I agree as far as dev-only requirements go, since we *can* control those10:45
tristanbenschubert, but then there is always inadvertent overlap :)10:45
tristanNexus, lemme check10:45
benschubertobviously, but we cannot handle everything sadly :)10:46
benschubertOn the other hand, having tox would allow us to test multiple versions of the normal dependencies too actually, we could have something like "base minimum versions", "version proven to work (best versions to use)", and "latest versions, allowed to fail", what would you say about that?10:46
*** nimish_ has quit IRC10:48
gitlab-br-bottristanvb closed issue #530 (Cache quota size definition tests depend on the host system) on buildstream https://gitlab.com/BuildStream/buildstream/issues/53010:58
gitlab-br-bottristanvb merged MR !702 (BenjaminSchubert/fix-quota-tests->master: Mock storage space checks for tests.) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/70210:58
benschubertThanks a lot :D10:59
juergbitristan: no, I can't think of a reason why these other plugins wouldn't be compatible with virtual directories. for the manual one there is already a patch in a (not directly related) pending MR11:06
juergbias I mentioned I prefer something like SimpleBuildElement to avoid the duplication, but your MR looks good to me11:07
*** alatiera has joined #buildstream11:09
tristanjuergbi, I think we can do that orthogonally, I tend to agree but don't feel entirely certain11:10
juergbisure, the MR fixes the issue, we can add it later11:10
tristanjuergbi, I feel like the greater concern might be to have a way to disable the batching once you have it enabled11:11
tristanRight now it's a now way out situation, which might happen again11:11
tristanbut I suppose there is always a way to add more API for disabling it if needed11:11
juergbiI don't currently see a need for disabling11:12
juergbiunless we were to enable it by default again, but that could break some things11:12
tristanjuergbi, well, he had one in #800, where you derive from an abstract class which enables it, reuse a lot of it's functionality but only need to disable that11:12
gitlab-br-botIssue #800: There is no clear way to disable batching of prepare+assemble in BuildElement https://gitlab.com/BuildStream/buildstream/issues/80011:12
tristanI mean, another class could start to exist, in somebody's project not even in BuildStream, which other people derive from11:13
tristanRight now we've solved it for BuildElement, though, and in a way that doesnt break anything that might exist11:13
tristanagain, it's not a problem we really need to think about until it is raised I guess11:14
juergbiok, sure11:14
*** nimish_ has joined #buildstream11:18
*** nimish_ has quit IRC11:28
*** nimish_ has joined #buildstream11:29
*** lachlan has quit IRC11:31
*** nimish_ has quit IRC11:33
*** nimish_ has joined #buildstream11:40
*** lachlan has joined #buildstream11:47
*** nimish_ has quit IRC11:49
*** nimish_ has joined #buildstream11:50
*** alatiera has quit IRC11:51
*** abderrahim has quit IRC11:52
*** abderrahim has joined #buildstream11:53
*** alatiera has joined #buildstream11:54
*** nimish_ has quit IRC11:55
*** nimish_ has joined #buildstream11:59
*** nimish_ has quit IRC12:04
*** nimish_ has joined #buildstream12:08
*** nimish_ has quit IRC12:10
*** nimish has joined #buildstream12:11
*** nimish has quit IRC12:21
*** lachlan has quit IRC12:26
*** nimish has joined #buildstream12:26
*** lachlan has joined #buildstream12:28
*** nimish has quit IRC12:33
gitlab-br-botBenjaminSchubert merged MR !1006 (bschubert/fix-unbound-variable-exception->master: element.py: fix unbounded variable in nested python exception) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/100612:34
*** V0lTure has joined #buildstream13:10
*** jferrero has joined #buildstream13:54
*** phildawson has quit IRC14:00
*** phildawson has joined #buildstream14:00
*** raoul_ has joined #buildstream14:00
*** raoul has quit IRC14:01
*** raoul__ has joined #buildstream14:02
*** raoul_ has quit IRC14:03
gitlab-br-botknownexus closed MR !926 (issue_640-Build-All->master: Added default element build all functionality to `bst build`) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/92614:18
*** raoul__ has quit IRC14:24
*** raoul__ has joined #buildstream14:31
*** nimish has joined #buildstream14:38
*** raoul__ has quit IRC14:43
gitlab-br-botjmacarthur approved MR !985 (gokcennurlu/remote_url_override_push_error->master: Set ArtifactCache for push/pull correctly when `--remote` is used) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/98514:52
*** nimish has quit IRC14:53
*** nimish has joined #buildstream14:54
gitlab-br-bottristanvb closed issue #800 (There is no clear way to disable batching of prepare+assemble in BuildElement) on buildstream https://gitlab.com/BuildStream/buildstream/issues/80014:58
gitlab-br-bottristanvb merged MR !1009 (tristan/dont-batch-prepare-assemble-by-default->master: Dont batch prepare assemble by default) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/100914:58
*** nimish has quit IRC15:09
*** nimish has joined #buildstream15:09
*** raoul__ has joined #buildstream15:10
*** nimish has quit IRC15:21
gitlab-br-botwillsalmon approved MR !973 (aevri/contributing_e2e_tests->master: contributing: more clarity on testing) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/97315:30
benschubertCould someone add me as a developer on the BuildStream organization? It will be simpler than asking for every repo :)15:32
juergbisure15:37
juergbibenschubert: done15:38
benschubertThanks!15:41
*** lachlan has quit IRC16:04
*** CEnnis91 has joined #buildstream16:17
*** lachlan has joined #buildstream16:20
*** toscalix has joined #buildstream17:02
gitlab-br-botjmacarthur opened (was WIP) MR !952 (raoul/627-RE-instance-config->master: Remote-execution instance configuration support) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/95217:19
*** lachlan has quit IRC17:21
*** lsfranco has joined #buildstream17:24
*** lachlan has joined #buildstream17:28
*** lsfranco has quit IRC17:29
*** lsfranco has joined #buildstream17:30
*** lachlan has quit IRC17:35
*** lachlan has joined #buildstream17:39
*** jonathanmaw has quit IRC17:44
*** tpollard has quit IRC17:56
*** raoul__ has quit IRC17:57
gitlab-br-botaevri merged MR !973 (aevri/contributing_e2e_tests->master: contributing: more clarity on testing) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/97318:01
*** lachlan has quit IRC18:11
*** xjuan has joined #buildstream18:42
*** lsfranco has quit IRC18:45
*** lsfranco has joined #buildstream18:45
*** nimish has joined #buildstream18:50
*** nimish has quit IRC18:59
*** kapil___ has quit IRC19:31
*** xjuan has quit IRC20:00
*** toscalix has quit IRC20:01
*** xjuan has joined #buildstream20:44
*** jhed9 has joined #buildstream22:22
*** alatiera has quit IRC23:25
*** tristan has quit IRC23:31
*** manfromafar has joined #buildstream23:55

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