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

*** nimish has joined #buildstream01:31
*** nimish has quit IRC01:45
*** nimish has joined #buildstream01:48
*** ajibade_ has joined #buildstream01:52
*** ajibade__ has joined #buildstream01:56
*** ajibade_ has quit IRC02:18
*** ajibade__ has quit IRC02:18
*** nimish has quit IRC03:08
*** bochecha has joined #buildstream03:41
*** bochecha has quit IRC03:59
*** bochecha has joined #buildstream04:04
*** mohan43u has joined #buildstream04:51
*** kapil___ has joined #buildstream06:25
juergbidoras[m]: the root-read-only flag is a feature of the script element that works for actual (automated) builds, but bst shell --build doesn't know about this flag06:55
juergbiwould probably be good if bst shell handles it the same way but that's not trivial to fix06:56
doras[m]Well, that explains it. A bit counterintuitive, I have to say. I had always imagined "bst shell --build" to be the exact action that happens when a real build runs (minus the shell part), so as to be able to debug build issues and behavior in a reproducible way.07:00
juergbidoras[m]: yes, it typically is very close. the issue is that the plugin API supports the root read-only flag only for Sandbox.run() which is used to actually execute a build command. That method is not used for bst shell as build commands are not executed07:05
*** ZOZO has joined #buildstream07:44
*** ZOZO has quit IRC08:57
*** kapil___ has quit IRC09:04
*** WSalmon_ has joined #buildstream09:28
*** jonathanmaw has joined #buildstream09:36
*** raoul has joined #buildstream10:11
*** jonathanmaw_ has joined #buildstream10:36
*** jonathanmaw has quit IRC10:37
*** bochecha has quit IRC10:45
*** cs-shadow has joined #buildstream11:42
*** bochecha has joined #buildstream12:21
*** nimish has joined #buildstream13:07
*** nimish has quit IRC13:11
*** nimish has joined #buildstream13:12
gitlab-br-botraoul.hidalgocharman approved MR !1117 (jennis/warn_for_nonexistent_domains->master: Fail when we explictly try to include/exclude non-existent domains in a filter element) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/111713:35
jennisthanks for the review rafaelff[m]13:59
jennisraoul *13:59
*** kapil___ has joined #buildstream14:04
gitlab-br-botjennis merged MR !1117 (jennis/warn_for_nonexistent_domains->master: Fail when we explictly try to include/exclude non-existent domains in a filter element) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/111714:47
gitlab-br-botLaurenceUrhegyi closed issue #466 (Optimize `bst build` initialization time) on buildstream https://gitlab.com/BuildStream/buildstream/issues/46615:07
*** toscalix has joined #buildstream15:56
*** nimish has quit IRC16:10
*** kapil___ has quit IRC16:24
*** bochecha has quit IRC16:45
*** toscalix has quit IRC17:06
*** ipatch has joined #buildstream17:35
cs-shadowI am trying to backport all/most of our tox improvements to bst 1.2 so that it can be tested more reliably. Would be good if someone can have a look at !1111 (I love that number!)17:56
cs-shadowMore details in the MR17:56
gitlab-br-botMR !1111: Run tests using tox https://gitlab.com/BuildStream/buildstream/merge_requests/111117:56
*** jonathanmaw_ has quit IRC18:05
*** dtf has joined #buildstream18:15
*** dtf has joined #buildstream18:17
*** raoul has quit IRC18:19
gitlab-br-botjjardon opened issue #894 (Document roadmap / plans for cache server for buildstream 2.0) on buildstream https://gitlab.com/BuildStream/buildstream/issues/89418:19
juergbics-shadow: 1.2 will still use pytest-runner. that shouldn't be an issue, right?18:23
juergbiI'm not sure about some remaining differences in requirements/ between your branch and master18:24
juergbie.g., your branch has pytest=4.1.1 in dev-requirements.txt while master has ==4.0.2. intentional?18:24
juergbialso pytest, pluggy, pytest-forked, wrapt, pytest-xdist have higher req in your 1.2 branch than in master. is this just somewhat random, would it make sense to align?18:26
cs-shadowjuergbi: That's right, `pytest-runner` shouldn't be an issue as it is only involved during "setup.py test" and not "pytest" directly. And all the tox stuff uses `pytest`18:27
cs-shadowthe versions are more interesting. We could, in theory, keep them the same as master iff we had exactly the same requirements, which we don't18:27
cs-shadowso, what I ended up doing was updating them to their current latest versions (which is what `setup.py test` would have given us anyway)18:28
juergbisome versions are also older, though, e.g., protobuf, pylint18:29
juergbiso it seems a bit odd looking at the numbers, but it's probably not a real issue18:29
cs-shadowthe ones that are older, are usually because the 1.2 branch had them pinned. For example, we have `pylint == 2.1.1` in the requirements.in (which was copied from existing setup.py)18:30
juergbithat makes sense18:30
juergbias long as these version differences don't cause any pain in CI, I don't mind, of course18:31
juergbijust wanted to check that this is not an issue18:31
cs-shadowI definitely agree with your motivation. Not having pain the CI is more than half the reason why I'm doing it :)18:32
juergbiI haven't been following the details of the toxification on master, so no expert in this area. but the MR looks good to me18:33
juergbianyway no risk on the code side as no actual code was touched18:33
cs-shadowjuergbi: thanks very much!18:34
gitlab-br-botcs-shadow merged MR !1111 (chandan/toxify-1.2->bst-1.2: Run tests using tox) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/111119:54
*** cs-shadow has quit IRC22:07
*** phildawson has quit IRC22:31

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