IRC logs for #buildstream for Tuesday, 2019-04-16

*** rdale has quit IRC00:21
*** nimish2711 has joined #buildstream02:26
*** tristan has quit IRC04:27
*** tristan has joined #buildstream04:30
*** ChanServ sets mode: +o tristan04:34
tristanlaurence, for when you get in: I don't know why you receive any moderator emails for buildstream-list@gnome.org, the admin UI tells me that jjardon and myself are the only moderators04:36
tristanlaurence, Also, I am having a hard time tracking down the email automatically sent to me which informs me of the admin password, it appears that I can only use the UI because the password is cached04:36
* tristan thinks he had jjardon send him the password at some time04:36
*** nimish2711 has quit IRC04:42
*** alatiera has quit IRC04:50
*** alatiera has joined #buildstream04:53
*** nimish2711 has joined #buildstream05:02
gitlab-br-bottristanvb opened issue #999 (Warnings and errors whenever overriding subproject junction configurations) on buildstream https://gitlab.com/BuildStream/buildstream/issues/99905:28
tristanOhhh nice number !05:29
tristanappropriate, it is a very nice issue !05:29
tristancs-shadow, juergbi fwiw, elaborately summarized and detailed ^^^^05:29
*** tristan has quit IRC05:45
*** tristan has joined #buildstream06:22
laurencetristan, i think you both are the oweners, and i'm just a mod? anyway, yeah i have that issue with passwords too06:32
laurenceshould really use a password manager06:32
* laurence adds to todo list06:32
laurenceanyway i'll ask jjardon to send the password my way once he's awake (think he's west coast usa atm) - thanks !06:33
*** lchlan has quit IRC06:35
laurencei wonder who will open issue #1000...06:37
*** rdale has joined #buildstream06:44
*** lchlan has joined #buildstream06:59
*** nielsdg has joined #buildstream07:10
*** nimish2711 has quit IRC07:31
*** swick has left #buildstream07:43
*** toscalix has joined #buildstream07:57
*** admin has joined #buildstream08:18
*** alatiera has quit IRC08:40
*** alatiera has joined #buildstream08:41
*** jonathanmaw has joined #buildstream08:43
*** tristan has quit IRC08:59
*** phildawson_ has joined #buildstream09:03
*** phildawson has quit IRC09:04
*** tristan has joined #buildstream09:17
*** alatiera_ has joined #buildstream09:32
*** alatiera has quit IRC09:32
*** alatiera_ is now known as alatiera09:33
jennislchlan, tlater, I'm finding that with your benchmarking tool, the default behaviour is failing due to: https://gitlab.com/BuildStream/buildstream/issues/98809:36
jennisAre you also seeing this?09:36
*** lachlan has joined #buildstream09:37
*** alatiera_ has joined #buildstream09:39
*** alatiera has quit IRC09:39
*** alatiera_ is now known as alatiera09:40
*** phildawson_ is now known as phildawson10:04
phildawsonCould I get a quick review for !1295 please. It fixes a bug where the external plugin testing will fail if no plugins are provided because a .coverage file is not generated.10:04
gitlab-br-botMR !1295: ix empty external tests https://gitlab.com/BuildStream/buildstream/merge_requests/129510:04
*** ChanServ sets mode: +o tristan10:17
tristanphildawson, Done10:17
*** nimish2711 has joined #buildstream10:18
phildawsoncheers tristan. FYI keys specified in environments which inherit form [testenv] etc overriden, not extended.10:19
*** lachlan has quit IRC10:19
phildawsonYou can verify this by doing tox --show-config to inspect the configuration for each environment after tox has interpreted tox.ini10:19
*** lachlan has joined #buildstream10:33
tristanphildawson, they are only overridden if specified in other environments though, right ?10:35
tristanphildawson, That means that whenever you work on another environment, you *must* declare something if you want to ensure you are not inheriting something from [testenv]10:35
tristanphildawson, I setup tox.ini specifically so that this would not be the case10:36
tristanand that nothing is inherited by accident10:36
tristanphildawson, it would be nice if say, we could declare all the juicy test bits inside a [testenv:py{35,36,37}] block, and thus have clearer looking conditionals in there10:37
tristanbut I don't think that's possible10:37
*** lachlan has quit IRC10:42
phildawsontristan, you're correct on both counts there.  I see where you're coming from with how you initially wrote it but it was starting to make it hard to read (for me at least). I'll admit though I'm struggling to think of an environment where you wouldn't specify anny commands?10:42
phildawson"<tristan> but I don't think that's possible" not that I'm aware of, but I may be missing something10:42
*** alatiera has quit IRC10:46
*** alatiera has joined #buildstream10:49
phildawsonI spent some time trying to work out a way to do that when writing the external testing stuff.10:51
tristanYeah the conclusion I keep coming to is that we need the conditionals to be done at the assignments of keys10:56
tristantox has multiple ways10:56
*** lachlan has joined #buildstream10:56
tristanbut that seems to be the only one that works for all the cases we use conditionals for10:56
tristanphildawson, also I was hoping to say... be able to *explicitly* include declarations from [testenv] in a separate env, but it seems there is a hard coded list of variables/keys and you cannot declare things in [testenv] and then refer to them in other sections :-/10:57
tristanphildawson, for commands it is not very relevant, but for deps, setenv, passenv, etc... everything else I think it is important to not allow adjacent environments to inherit anything10:58
phildawsontristan, would you be happy if I reinstate the conditionals for the keys which aren't command? I personally like using the deps as a default, but I don't feel strongly enough to worry either way.11:01
tristanphildawson, If you want to change the approach entirely, then it might be better - in which case I would want all environments to explicitly override everything, consistently; even in cases where no override is needed and only the setting inherited from [testenv] is unneeded11:03
tristani.e. then we have each env very explicit and *clear* about it being *required* to set everything11:03
tristanAnd it would be good to have comments to that effect near the top of the file explaining why11:04
tristanI.e. I don't think it's fair to say "You have to know all about tox" or read upstream docs just to fiddle with the tox.ini file, I prefer that it is self documenting11:04
tristanphildawson, The main reason I had set it up that way was to ensure that others who happen to fiddle with the tox.ini in other sections, dont find themselves wondering why settings they didnt declare are curiously set11:05
tristanSo if we can make it 100% explicit across the board and reduce the conditionals in [testenv], I think that also solves the problem11:05
tristanIt is however a complete switch in the way we use tox11:06
tristanphildawson, I would however prefer consistency; I.e. not having a dual standard is better11:06
*** nimish2711 has quit IRC11:31
*** alatiera has quit IRC11:35
*** lachlan has quit IRC11:37
cs-shadowquestion about import plugin - it does not do anything with its build dependencies, right?11:43
tristancs-shadow, iirc juergbi has a branch that disallows build dependencies of imports, or was planning one11:45
tristancs-shadow, only blocker is that a lot of test cases need tedious updates11:45
cs-shadowtristan: ah I see. Thanks for confirming my suspicions11:46
*** lachlan has joined #buildstream11:47
*** alatiera has joined #buildstream11:54
*** lachlan has quit IRC11:58
juergbics-shadow: yes, see juerg/import-no-build-deps branch. not planning to work on this right now, though12:00
cs-shadowthanks. I'll see if I have time to push it over the finish line12:01
tristanProbably take an hour or two to s/depends/runtime-depends/ in all the tests which use import elements12:01
phildawsontristan, I agree a proper rework would be nice, but I don't really have time to do that right now. I just attempted to throw up a quick patch tidying things up a little while I was already in tox.ini for something else.  I know it's not the perfect final solution,  but I've attempted to leave things slightly better than I found them. If you'd prefer, I can drop those commits and open an issue about refactoring tox.ini.12:02
tristanphildawson, Ok so then please omit the tidying until later12:03
tristanphildawson, I know it's verbose, but right now the strategy is to have [testenv] not export things which get inherited, so it should be pretty consistent in this regard, switching it to the other way around and making everything explicit in the adjacent envs would be equally consistent, but let's not have a situation where "some keys work this way, and some keys work the other way"12:05
tristaninteresting... tox not working "right now" for me12:06
tristanpip is timing out12:06
juergbitristan, cs-shadow: just switching everything to runtime-depends may not lead to identical tests. the issue is that (I think) we're using import elements also to test scheduler behavior with regards to build dependencies12:13
tristanI see12:13
juergbii.e., while import elements don't actually use build dependencies, the scheduler / element logic might still behave differently12:13
tristanhttps://gitlab.com/BuildStream/buildstream/-/jobs/197506163 looks like a spurious error caused by pytest-xdist12:14
juergbiI've not seen this INTERNALERROR before, but seems likely12:16
tristancomplains that we're using signals in a thread and not in the main process12:16
tristanseems fragile that it pytest-xdist is using threads :-/12:16
tristanwell, not an issue if it hardly ever causes a problem12:17
phildawsontristan, I've dropped those commits, are you happy for me to assign to marge?12:19
tristanphildawson, marge it !12:20
phildawsonCheers :)12:20
juergbitristan: xdist is using multiple python processes, not threads, afaik, for the parallel jobs. however, there must be a strange issue somewhere with regards to asyncio12:23
tristanI see12:23
tristanyeah the INTERNALERROR is about using _signal in a thread12:24
tristanwe dont do any threads ourselves so, maybe the error is just misplaced12:24
tristanor maybe we have another bad actor library going a head and *spawning threads* without being asked to !!!12:24
juergbihttps://bitbucket.org/pytest-dev/pytest-timeout/issues/8/pytest-xdist-interop-signal-only-works-in12:25
juergbihttps://github.com/pytest-dev/pytest-xdist/issues/20412:25
* tristan still recalls a mailing list thread from 15 years ago when we decided to make glib initialize the threading subsystem unconditionally12:25
juergbihaha12:26
*** lachlan has joined #buildstream13:33
*** lachlan has quit IRC13:39
*** lachlan has joined #buildstream13:46
laurencenb all - monthly irc team meeting starting in 13 mins13:47
laurenceover on #buildstream-meetings13:47
*** lachlan has quit IRC13:59
*** alatiera_ has joined #buildstream14:01
*** alatiera has quit IRC14:01
*** lachlan has joined #buildstream14:01
*** alatiera_ is now known as alatiera14:01
*** lachlan has quit IRC14:23
gitlab-br-bottristanvb opened MR !1294 (tristan/rename-errno-fix-1.2->bst-1.2: plugins/sources/git.py: Cope with rename returning error EEXIST) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/129414:37
*** alatiera has quit IRC14:38
gitlab-br-botjonathanmaw approved MR !1291 (phil/rename-plugintestutils->master: Rename 'plugintestutils' package to 'testing') on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/129114:39
tristanHuh ?14:39
tristanDid I ?14:39
gitlab-br-botmarge-bot123 merged MR !1294 (tristan/rename-errno-fix-1.2->bst-1.2: plugins/sources/git.py: Cope with rename returning error EEXIST) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/129414:40
tristangitlag-br-bot, are you labbing ?14:40
gitlab-br-botphildawson opened MR !1295 (phil/fix-empty-external-tests->master: ix empty external tests) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/129514:40
phildawsonErm, the bot appears to be rather confused14:43
gitlab-br-botcs-shadow opened issue #1001 (Provide better error messages when launching a shell is not possible) on buildstream https://gitlab.com/BuildStream/buildstream/issues/100114:45
gitlab-br-botmarge-bot123 merged MR !1295 (phil/fix-empty-external-tests->master: Fix empty external tests) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/129514:48
tpollardmarge is broken on the inside again14:49
gitlab-br-botphildawson closed issue #944 (Expose templated tests for source plugins) on buildstream https://gitlab.com/BuildStream/buildstream/issues/94414:51
*** lachlan has joined #buildstream14:51
*** tristan has quit IRC14:53
KinnisonPoor marge14:54
*** tristan has joined #buildstream15:10
tpollardjuergbi: I've replied to your comments on !1271, hopefully we can resolve them :)15:12
gitlab-br-botMR !1271: Follow-up from "Artifact 'abstraction' class" https://gitlab.com/BuildStream/buildstream/merge_requests/127115:12
juergbiok, ta15:12
*** lachlan has quit IRC15:20
*** lachlan has joined #buildstream15:56
*** lachlan has quit IRC16:01
*** toscalix has quit IRC16:08
*** lachlan has joined #buildstream16:12
*** lachlan has quit IRC16:16
*** tpollard has quit IRC16:59
*** jonathanmaw has quit IRC17:03
*** lachlan has joined #buildstream17:05
*** lachlan has quit IRC17:30
*** nimish2711 has joined #buildstream18:02
*** nimish2711 has quit IRC19:45
*** tristan has quit IRC21:34

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