IRC logs for #buildstream for Wednesday, 2018-10-24

*** bochecha has quit IRC00:01
*** xjuan has quit IRC00:41
*** Prince781 has quit IRC01:47
*** Prince781 has joined #buildstream02:27
*** raoul has joined #buildstream03:59
*** coldtom has joined #buildstream04:56
*** Prince781 has quit IRC05:17
*** mohan43u has quit IRC07:05
*** mohan43u has joined #buildstream07:05
*** adds68 has joined #buildstream07:51
*** finn has joined #buildstream07:57
*** Nexus has joined #buildstream08:13
*** jennis has joined #buildstream08:24
*** paulsherwood has joined #buildstream08:31
gitlab-br-botphildawson closed MR !887 (aevri/prompt-config->master: Add 'prompt.*' config options to buildstream.conf) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/88708:40
gitlab-br-botphildawson reopened MR !887 (aevri/prompt-config->master: Add 'prompt.*' config options to buildstream.conf) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/88708:40
*** ikerperez has joined #buildstream08:52
*** jmac has joined #buildstream09:00
*** alatiera_ has joined #buildstream09:02
*** jonathanmaw has joined #buildstream09:14
gitlab-br-botjmacarthur approved MR !889 (valentindavid/ruamel_warnings->master: Fix some ruamel warnings during tests) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/88909:19
*** Nexus_ has joined #buildstream09:28
*** Nexus_ has joined #buildstream09:28
*** lachlan has joined #buildstream09:29
jennisWhere does our file that keeps track of the cache size get stored?09:30
jennisI'm guessing it's in ~/.cache/buildstream?09:30
gitlab-br-botaevri opened MR !893 (aevri/unknown-uri-452->master: _downloadablefilesource: handle ValueError-s) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/89309:31
jennisAhh, ~/.cache/buildstream/artifacts09:31
*** Nexus__ has joined #buildstream09:33
*** Nexus has quit IRC09:36
*** Nexus_ has quit IRC09:36
*** Nexus has joined #buildstream09:36
*** lachlan has quit IRC09:41
*** lachlan has joined #buildstream09:45
*** lachlan has quit IRC10:01
raoulWhen terminating jobs I always get something along the lines of "Unknown child process pid 20093, will report returncode 255" which seems to be coming from the async library, this isn't supposed to be happening right?10:10
raoulThought it was a change I made but it's happening on master10:11
*** lachlan has joined #buildstream10:17
*** coldtom has quit IRC10:18
*** adds68 has quit IRC10:18
*** jennis has quit IRC10:18
*** ikerperez has quit IRC10:18
*** coldtom has joined #buildstream10:19
*** ikerperez has joined #buildstream10:21
*** jennis has joined #buildstream10:22
*** adds68 has joined #buildstream10:22
*** lachlan has quit IRC10:25
*** Prince781 has joined #buildstream10:29
*** Prince781 has quit IRC10:31
tlater[m]raoul: This has been happening since my scheduler refactor, I believe. tristan thought he'd fixed it in the past... In any case, it's definitely not supposed to happen, and probably happens because BuildStream tries to kill a child process twice.10:35
tlater[m]Hm, I should really just make that the next issue I look at.10:35
raoulYeah I saw some closed off issues, not sure if it's causing any issues but probably not good nonetheless10:37
*** lachlan has joined #buildstream10:42
KinnisonHi all, I've got a fairly large MR in terms of commit count (!892) which is almost entirely lint cleanups.  tlater[m] has already been over it, and I'd appreciate at least one more pair of eyes before I do as Tristan asked and rebase it into a smaller number of commits ready for merge.10:59
KinnisonVery few if any of the changes should be controversial10:59
tlater[m]Kinnison: As an aside, I think I would prefer a commit for every 'type', but that can be really annoying to orchestrate. file-granularity makes little sense, since the individual changes happen across files. Maybe one big commit is the way to go, except for certain kinds of errors that you think should be considered separate?11:01
Kinnisontlater[m]: Hopefully whoever can spare the time to go over the MR will also weigh in, I'm fine with any combination of rebase from "none" to "one giant commit of doom" but I'd be most comfortable with something along the lines of per-file, with the potential bug-fix split out11:02
KinnisonThough there would be something quite satisfying about merging a 43 commit sequence11:02
KinnisonOnce this is merged, we can look to update pylint on our CI docker images11:03
Kinnisonwhich will be nice11:03
Kinnisonsince the newer pylint definitely spotted a bug when I was doing this work11:03
tlater[m]Kinnison: Hah, well, I wouldn't be too opposed to the full 43 commit sequence.11:05
* tlater[m] is really looking forward to this, his linter has been threatening him11:06
*** Prince781 has joined #buildstream11:17
juergbiI'd definitely keep at least the actual bug fixes separate commits11:30
juergbiI like grouping by type as well, e.g., 'Remove unused imports' across the tree. however, I'd also be fine with other groupings or even no grouping, as long as the bug fixes are kept separate11:38
Kinnisonjuergbi: noted.12:04
*** bochecha has joined #buildstream12:07
KinnisonOh for pity's sake12:13
* Kinnison grumps at pylint 12:14
tlater[m]Haha12:25
tlater[m]#disable-line-too-long makes the line too long12:25
tlater[m]Adorable12:25
*** tlaxkit has joined #buildstream12:58
* Kinnison wonders if juergbi or phildawson has had a chance to actually look through the changes13:11
* Kinnison trusts tlater[m] but would feel more comfortable with at least one other pair of eyes13:11
KinnisonThen I'll make a decision on the commit sequence and whether I cba. to squish things13:11
Kinnisontlater[m]: Are you familiar with how gitlab.io instances are managed?13:12
phildawsonKinnison, not yet. I've got quarter of an hour before the next meeting so will have a quick look now :)13:13
tlater[m]Kinnison: Not particularly. jjardon set up the magic, I believe13:29
*** lachlan has quit IRC13:33
*** lachlan has joined #buildstream13:34
*** catonano has joined #buildstream13:39
*** anahuelamo has quit IRC13:40
Kinnisonokies13:40
Kinnisonlachlan: You may want to prod jjardon13:40
*** anahuelamo has joined #buildstream13:41
lachlanKinnison: He has very kindly already provided some information to follow-up on.13:46
Kinnisoncool13:47
tlater[m]Would someone mind taking a look at https://gitlab.com/BuildStream/buildstream/merge_requests/670 ?13:49
tlater[m]It's been reviewed a few times by tristan at this point, but I'd like to get someone to say it looks good before I prod him again ;)13:49
Kinnisontlater[m]: I can look, but I won't feel confident okaying it13:50
tlater[m]That's alright, I just want a "yup, this doesn't look horrifying"13:50
* Kinnison skims13:51
Kinnisontlater[m]: I don't see anything awful, and the general refactor looks nice.  But I can't say if it's good or not14:00
tlater[m]Yes, that's fair14:01
tlater[m]There's also one little behavior detail that I want to discuss with tristan anyway14:01
tlater[m]Thanks for looking at it though :)14:01
tlater[m]Ah, tristan is tristan_ atm14:03
tlater[m]tristan:14:04
tlater[m]Hm, maybe neither14:04
tlater[m]Eh, I'll find him some other day.14:04
KinnisonI think he's at ELCE so probably not responding much14:04
tlater[m]Oh, right, I keep forgetting about ELCE14:05
*** catonano has quit IRC14:27
cs-shadowjuergbi: hey! Would you consider taking a look at https://gitlab.com/BuildStream/buildstream/merge_requests/820 (bst source-checkout) when you get a chance14:31
juergbisure14:32
cs-shadowthanks :)14:32
Kinnisonjuergbi: I've responded to your comments on my linting MR too when you have a moment :-D14:35
*** catonano has joined #buildstream14:38
*** benschubert has joined #buildstream14:48
*** benschubert has joined #buildstream14:49
benschubertHey, I'd like to add a test to make sure that ensure we are not caching failures that are due to host tools. Where would be the best place to put the test?14:50
KinnisonIf you actually need to run a proper sandbox then you'll need to put the test somewhere in tests/integration IIRC14:51
benschubertintegration/cachedfail?14:52
Kinnisonthat sounds like a reasonable starting point at least14:52
tpollard+114:53
benschubertthanks I'll go for this!14:53
*** WSalmon has joined #buildstream14:58
*** WSalmon_ has quit IRC14:58
*** lachlan has quit IRC15:05
gitlab-br-botjuergbi opened issue #724 (Follow-up from "Fix lint issues": Avoid the need to disable `assignment-from-no-return` for abstract methods) on buildstream https://gitlab.com/BuildStream/buildstream/issues/72415:10
juergbiKinnison: commented15:13
*** Prince781 has quit IRC15:23
*** catonano has quit IRC15:26
*** lachlan has joined #buildstream15:26
*** lachlan has quit IRC15:35
*** lachlan has joined #buildstream15:36
gitlab-br-botraoul.hidalgocharman opened issue #725 (Job cancellation on remote builds) on buildstream https://gitlab.com/BuildStream/buildstream/issues/72515:41
Kinnisontlater[m]: Do you happen to know what triggers the new linting?  pylint is locked at 2.1.1 which is what I have, and yet I get the lints where the current CI doesn't15:46
raouljuergbi, could I get dev access so I can assign an issue to myself?15:48
tlater[m]Kinnison: that's interesting. How do you run pylint? Through setup.py or manually?15:49
Kinnisonsetup.py15:49
Kinnisonand I'm talking about what's in my .eggs/15:49
tlater[m]It's possible setup.py doesn't actually run what's in there, but knowing you that's probably the only pylint on your system.15:50
tlater[m]My only suspicion is that you use he -m flag and that that picks up different modules than the default configuration.15:51
tlater[m]Have you tried updating the pylint version the CI uses, just in case?15:51
KinnisonI've not touched the CI15:51
KinnisonI was getting these lint warnings regardless of using "-m pylint"15:52
tlater[m]Hm, maybe we tagged the wrong version, but assert() was definitely part of the very first pylint version we used. I did find that odd.15:52
tlater[m]Let me have a look at the config...15:53
* Kinnison thinks that when jonathanmaw tried to regenerate the CI worker images he encountered the lint issues15:55
Kinnisonjonathanmaw: ^^ is that true?15:55
jonathanmawKinnison: yep15:55
KinnisonSo perhaps I don't need to touch dev-requirements.txt ?15:56
Kinnisonjonathanmaw: related discussion: https://gitlab.com/BuildStream/buildstream/merge_requests/892#note_11150950415:56
jonathanmawKinnison: linting runs at https://gitlab.com/BuildStream/buildstream/-/jobs/11117341715:56
KinnisonThat definitely looks like the pile'o'lints my MR fixes15:56
juergbiraoul: done15:57
raoulcheers juergbi15:57
Kinnisonjuergbi: Given ^^^ do you think I need to adjust dev-requirements.txt still?15:57
jonathanmawKinnison: there's a dev-requirements in the root of buildstream, which is used if you install by setup.py, and the CI workers have a dev-requirements which is used to populate the CI workers15:57
KinnisonOh right15:57
KinnisonSo juergbi might have meant the other dev-requirements.txt ?15:58
* Kinnison is very confused15:58
juergbiI meant both. aren't they kept in sync?15:59
* Kinnison has literally no idea :(15:59
jonathanmawjuergbi: they seem to have the same contents, but in a slightly different order16:00
juergbiKinnison: my main point was that CI was apparently not catching these issues before. and whatever needs to be done to change this, should be in the branch (or in corresponding docker image branch)16:00
Kinnisonjuergbi: afaict what needs to be done is that the CI images need regenerating16:00
Kinnisonjuergbi: i.e. that if we regenerate them, these lints will hit us16:00
tlater[m]That can't be done in-branch16:00
tlater[m]Yes, that's annoying.16:01
juergbiwell, you can generate new CI images and then change gitlab-ci in the main MR16:01
juergbito use the new images16:01
tlater[m]Side effect of hosting the code separately from the testing environment.16:01
tlater[m]juergbi: The issue is that the image CI fails because it now suddenly picks up new errors16:01
* Kinnison would definitely need help with that16:01
tlater[m]So they can't update the images16:02
KinnisonUrgh16:02
juergbiah, that was added, hm16:02
tlater[m]Iirc we'll first need to land the changes in master and then update the images.16:02
juergbisure, not too much of an issue. let's just not forget it16:03
juergbii.e., do it immediately16:03
KinnisonWould someone who knows what to do be prepared to merge the lint fixes MR and then immediately hit the image update?16:03
tlater[m]Sure - it seems jonathanmaw is already on it?16:04
Kinnisonjonathanmaw: ^^ ?16:04
tlater[m]Otherwise I'm happy to16:04
jonathanmawtlater[m]: I'm not currently working on that16:04
jonathanmawI updated the image as part of adding pexpect (though it looks like I won't be using pexpect after all)16:05
tlater[m]Then I'll prepare the images :)16:05
gitlab-br-botvalentindavid opened MR !894 (valentindavid/sysroot_dependencies->master: Add support for importing build dependencies in sysroots.) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/89416:08
tlater[m]jonathanmaw: Ah, so you just updated the image ref, we already have a CI image that recognizes the new errors.16:10
jonathanmawtlater[m]: yep, I needed a new image ref that included pexpect, and that's when I stumbled over a huge pile of linting errors16:11
tlater[m]Cool, well, that should be fixed with this branch. I'll just bump the version.16:12
*** abderrahim3 has joined #buildstream16:14
*** abderrahim2 has quit IRC16:16
*** lachlan has quit IRC16:17
tlater[m]Err, it looks like my push is not appearing in gitlab?16:17
*** tlaxkit has quit IRC16:21
*** lachlan has joined #buildstream16:23
tlater[m]Hm, no, just held back because CI takes a while.16:25
laurencejonathanclaw, jennis, I cannot remember, pls remind me - did we ever improve the filter documentation ? if so, can we close https://gitlab.com/BuildStream/buildstream/issues/278 ?16:27
laurencejonathanmaw, ^^16:27
jennisI think phildawson ended up writing that16:29
jonathanmawlaurence: A MR was merged for it which improved the docstring16:30
jonathanmawI think I paraphrased heavily what tristan outlined in the issue, so I wasn't confident to close the MR16:31
jonathanmawI think it's been a while since people have been perplexed by filter elements at us, so maybe it's fine to close it now16:33
*** lachlan has quit IRC16:33
phildawsonlaurence, I started writing a filter example a while back but couldn't get it working at the time (people had their hands full at the time so I was struggling to get help to work it out). I think I've still got it sat on a branch somewhere.16:34
laurencejonathanmaw, thanks16:39
laurencephildawson, ah ok, i think that falls under examples in general rather than this specific issue16:39
laurencejonathanmaw, I suggest we close it for now and link to the MR tht was merged16:39
jonathanmawlaurence: it's already linked to the MR that was merged16:41
jonathanmawah, it was reopened as being related to https://gitlab.com/BuildStream/buildstream/issues/437 by the looks of it16:43
laurencedear me, right in that case sorry for the noise all16:43
*** lachlan has joined #buildstream16:46
Kinnisontlater[m]: Why is my MR stuck on pipeline pending again?16:57
Kinnisontlater[m]: oh no matter, I see your commit \o/16:58
* Kinnison decides to have some dinner16:58
tlater[m]I had to add a commit for the image update.16:58
tlater[m]Now we need to wait for others' CI to finish...16:58
Kinnison:-D16:58
tlater[m]:)16:59
KinnisonDefinitely dinner'o'clock then16:59
* Kinnison waves16:59
KinnisonI'll try and check in later16:59
tlater[m]o/16:59
gitlab-br-botaevri opened issue #726 ('Are you sure?' prompts don't suite all users) on buildstream https://gitlab.com/BuildStream/buildstream/issues/72617:00
*** lachlan has quit IRC17:05
*** lachlan has joined #buildstream17:10
laurenceWSalmon, is there a gitlab ticket raised for Workspaces - defaults?17:17
*** lachlan has quit IRC17:25
*** raoul has quit IRC17:42
gitlab-br-botBenjaminSchubert opened MR !895 (bschubert/dont-cache-errors-from-host-tools->master: WIP: Don't cache host tools failures) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/89517:47
*** lachlan has joined #buildstream17:48
*** catonano has joined #buildstream17:50
gitlab-br-botBenjaminSchubert opened issue #727 (Don't cache host tools failures) on buildstream https://gitlab.com/BuildStream/buildstream/issues/72717:50
benschubertCould I get your feedback on https://gitlab.com/BuildStream/buildstream/issues/727 ? Thanks!17:51
benschubertlet me know if you want me to pass this to the ML17:51
*** jonathanmaw has quit IRC17:59
*** finn has quit IRC18:04
*** finn has joined #buildstream18:06
*** finn has quit IRC18:09
*** xjuan has joined #buildstream18:26
*** lachlan has quit IRC18:34
*** xjuan has quit IRC19:00
*** alatiera_ has quit IRC19:04
*** mohan43u has quit IRC19:10
*** mohan43u has joined #buildstream19:13
*** catonano has quit IRC20:27
*** Prince781 has joined #buildstream20:42
*** catonano has joined #buildstream21:06
*** xjuan has joined #buildstream21:35
*** mohan43u has quit IRC21:40
*** mohan43u has joined #buildstream21:43
*** catonano has quit IRC21:58
*** Prince781 has quit IRC22:04
*** ssssam[m] has quit IRC22:44
gitlab-br-botcs-shadow opened MR !896 (chandan/source-doc-directory->master: plugins: Don't redundantly document common configurations) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/89622:49
*** alatiera has quit IRC22:59
*** dineshdb[m] has quit IRC22:59
*** inigomartinez has quit IRC22:59
gitlab-br-botcs-shadow approved MR !893 (aevri/unknown-uri-452->master: _downloadablefilesource: handle ValueError-s) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/89323:07
*** ssssam[m] has joined #buildstream23:18
*** Prince781 has joined #buildstream23:25
*** bochecha has quit IRC23:38
*** alatiera has joined #buildstream23:41
*** dineshdb[m] has joined #buildstream23:52

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