IRC logs for #buildstream for Monday, 2020-01-20

*** traveltissues has quit IRC07:11
*** traveltissues has joined #buildstream08:40
*** bochecha has joined #buildstream08:57
gitlab-br-botcoldtom opened issue #1258 (Plugin tests accessing private API) on buildstream https://gitlab.com/BuildStream/buildstream/issues/125809:38
gitlab-br-botcoldtom opened MR !1806 (coldtom/testing-api->master: Stop plugin tests using private API) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/180609:41
*** tiagogomes has joined #buildstream09:48
*** tme5 has joined #buildstream09:50
*** tpollard has joined #buildstream09:56
coldtomack mypy isn't happy about that because i'm doing imports from a cython file09:57
benschubertdoa  #type: ignore on the line fo rthis09:58
benschubertWe should provide typings for those files, especially since we are opening them up now09:58
benschubertbut it's quite complex to write correctly :/09:59
coldtomty benschubert10:00
*** phildawson has joined #buildstream10:11
*** jonathanmaw has joined #buildstream10:21
tme5does anyone have any ideas on how to test what a git source actually downloads?10:55
tme5since the repo gets deleted when it's staged i can't look at that10:56
benschubert> since the repo gets deleted when it's staged i can't look at that10:57
benschubertAll sources keep a local copy of the source. So in that case, you keep the .git.10:57
benschubertOpening a workspace would also ensure you get the .git folder.10:57
benschubertBut ultimately, what is it exactly that you are interested in? Ensuring that a particular file/directory exists? you can 'source checkout' and assert on that for example10:57
tme5i'm writing a test for the feature of fetching with depth=1 when an exact tag is given11:00
tme5so i think i need some way of testing the repo created by the fetch11:00
tme5a workspace is a good idea11:01
benschubertjjardon: around the tar removal, which breaks many tests. I was wondering if we should go for an approach where we tag tests requiring external plugins (@pytest.mark.plugins) and then run them at the same time as the source test plugins? That would allow us to have more complete and easy tests setup (especially if tar/git move away, that's a lot of tests that rely on them)11:11
coldtombenschubert: would this approach also allow at least some test of an external element in the bst test suite too? that seems to be something missing at the moment11:13
benschubertcoldtom: depends where the test lives: if it's in buildstream/tests, yes. if it's in the plugin repo no (but that can be fixed by triggering other pipelines through our tests, which is a separate thread I want to start)11:14
coldtomof the two approaches, i definitely prefer bst triggering pipelines on bst-plugins-*11:15
benschubertYep, I however think we might still need the first one too (e.g: the example tests)11:16
benschubertso I think we might require both11:16
coldtomah, yeah, it seems difficult to make useful examples without needing plugins that will soon be external11:17
coldtomcould someone take a look at https://gitlab.com/BuildStream/bst-plugins-experimental/merge_requests/61 and https://gitlab.com/BuildStream/bst-plugins-experimental/merge_requests/72 if they have time please?11:36
coldtomi've also opened https://gitlab.com/BuildStream/bst-plugins-experimental/merge_requests/73, which i'd appreciate opinions on11:51
benschubertI like that :D11:53
*** santi has joined #buildstream11:55
*** santi has quit IRC11:56
*** santi has joined #buildstream11:57
benschubertcoldtom: actually we should also probably remove the pylint parts around code formatting just in case :)12:02
coldtombenschubert: good point, i just removed pycodestyle due to conflicts , i can only assume pylint formatting will be a similar issue12:04
benschubertyep. I believe we had a commit that did that in BuildStream itself12:04
*** santi has quit IRC12:51
*** santi has joined #buildstream12:53
*** pointswaves has joined #buildstream12:53
*** phildawson has quit IRC12:59
*** phildawson has joined #buildstream12:59
*** pointswaves has quit IRC13:02
*** narispo has quit IRC13:31
*** narispo has joined #buildstream13:31
*** traveltissues has quit IRC13:40
*** phildawson has quit IRC13:47
*** phildawson has joined #buildstream13:48
*** phildawson has quit IRC14:01
*** lachlan has joined #buildstream14:03
*** lachlan has quit IRC14:12
*** narispo has quit IRC14:23
*** narispo has joined #buildstream14:23
*** lachlan has joined #buildstream14:24
*** lachlan has quit IRC14:33
*** lachlan has joined #buildstream14:35
*** lachlan has quit IRC14:39
*** lachlan has joined #buildstream14:48
*** lachlan has quit IRC14:51
*** lachlan has joined #buildstream14:57
*** phildawson has joined #buildstream15:06
coldtomjust ooi, is there any idea of when bst 2 will be released as stable at all?15:07
*** lachlan has quit IRC15:09
*** pointswaves has joined #buildstream15:23
juergbicoldtom: there is no timeline yet. however, Chandan posted a tentative list of 2.0 blockers to the ML a few months back15:25
bochechawas it decided what the plugin story will be like for 2.0? (there were plans of splitting everything out, making bst capable to install the plugins required by a project, eventually one venv per plugin…)15:32
coldtombochecha: i _think_ it's going to be a few domain-related repositories, although what exactly this means is TBD15:33
coldtomi.e. presumably something like bst-plugins-container, bst-plugins-scm, bst-plugins-buildsystems or the like15:34
bochechaok, so it's still not entirely decided15:41
juergbiright, deciding and implementing this is a blocker for 2.015:42
*** lachlan has joined #buildstream15:46
*** lachlan has quit IRC15:52
*** lachlan has joined #buildstream16:00
*** santi has quit IRC16:03
*** phildawson has quit IRC16:10
*** lachlan has quit IRC16:10
*** phildawson has joined #buildstream16:10
*** lachlan has joined #buildstream16:14
*** pointswaves has quit IRC16:17
*** lachlan has quit IRC16:30
*** phildawson has quit IRC16:36
*** phildawson has joined #buildstream16:41
tme5should i denote cache key breaks in the NEWS file?16:48
*** bochecha has quit IRC16:48
tpollardI don't think it's needed, have we done it before?16:51
coldtomon a per-plugin basis i don't think so, but personally i'd like NEWS entries for general cache key breaks16:52
* coldtom would like to know if he has to build everything again before updating bst16:52
*** lachlan has joined #buildstream17:07
*** phildawson has quit IRC17:07
*** santi has joined #buildstream17:10
*** lachlan has quit IRC17:22
*** santi has quit IRC17:25
*** santi has joined #buildstream17:30
*** lachlan has joined #buildstream17:30
*** xjuan has joined #buildstream17:32
*** xjuan has joined #buildstream17:33
*** lachlan has quit IRC17:34
*** lachlan has joined #buildstream17:37
*** lachlan has quit IRC17:45
*** tme5 has quit IRC17:46
*** lachlan has joined #buildstream17:46
*** lachlan has quit IRC17:49
*** xjuan has quit IRC17:56
*** xjuan has joined #buildstream17:57
*** lachlan has joined #buildstream18:01
*** lachlan has quit IRC18:04
*** lachlan has joined #buildstream18:11
*** lachlan has quit IRC18:26
*** pointswaves has joined #buildstream18:33
*** santi has quit IRC18:34
*** xjuan has quit IRC18:34
*** santi has joined #buildstream18:35
*** pointswaves has quit IRC18:37
*** pointswaves has joined #buildstream18:37
*** lachlan has joined #buildstream18:39
*** jonathanmaw has quit IRC18:40
*** pointswaves has quit IRC18:40
*** lachlan has quit IRC18:44
*** lachlan has joined #buildstream18:47
*** lachlan has quit IRC18:50
*** pointswaves has joined #buildstream19:30
*** santi has quit IRC19:59
*** santi has joined #buildstream19:59
*** delli3_ has joined #buildstream20:01
*** delli3 has quit IRC20:03
*** dellie__ has joined #buildstream20:10
*** delli3_ has quit IRC20:13
*** santi has quit IRC20:32
*** pointswaves has quit IRC21:40
*** pointswaves has joined #buildstream22:40
*** pointswaves has quit IRC23:17
*** tristan has quit IRC23:43
*** tristan has joined #buildstream23:43

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