IRC logs for #buildstream for Tuesday, 2018-10-30

*** Prince781 has quit IRC00:27
*** Prince781 has joined #buildstream00:47
*** bochecha has quit IRC01:14
*** xjuan has quit IRC01:16
*** Prince781 has quit IRC04:09
*** Prince781 has joined #buildstream04:11
*** Prince781 has quit IRC04:12
*** Prince781 has joined #buildstream04:29
*** catonano has joined #buildstream05:09
*** catonano has quit IRC06:08
*** Prince781 has quit IRC06:11
*** catonano has joined #buildstream06:28
*** catonano has quit IRC06:32
*** catonano has joined #buildstream06:32
*** catonano has quit IRC06:36
*** catonano has joined #buildstream06:36
*** catonano has quit IRC06:47
*** catonano has joined #buildstream06:48
*** Prince781 has joined #buildstream07:09
*** catonano has quit IRC07:17
*** catonano has joined #buildstream07:17
*** catonano has quit IRC07:21
*** catonano has joined #buildstream07:21
*** catonano has quit IRC07:27
*** catonano has joined #buildstream07:31
*** Prince781 has quit IRC07:39
*** tristan has joined #buildstream07:52
*** lankanmon has joined #buildstream08:18
*** catonano has quit IRC08:30
*** catonano has joined #buildstream08:30
*** solid_black has quit IRC08:31
*** solid_black has joined #buildstream08:31
*** solid_black has joined #buildstream08:32
*** catonano has quit IRC08:34
*** catonano has joined #buildstream08:34
*** catonano has quit IRC08:56
*** catonano has joined #buildstream08:56
*** catonano has quit IRC09:00
*** catonano has joined #buildstream09:00
*** catonano has quit IRC09:04
*** catonano has joined #buildstream09:04
*** catonano has quit IRC09:10
*** catonano has joined #buildstream09:10
*** catonano has quit IRC09:14
*** catonano has joined #buildstream09:14
*** bochecha has joined #buildstream09:15
*** toscalix has joined #buildstream09:16
*** toscalix has quit IRC09:18
*** toscalix has joined #buildstream09:21
*** benschubert has joined #buildstream09:43
*** catonano has quit IRC09:44
*** tristan has quit IRC09:46
*** tristan has joined #buildstream09:47
*** catonano has joined #buildstream09:51
*** raoul has joined #buildstream09:56
*** tristan has quit IRC10:03
*** jonathanmaw has joined #buildstream10:17
*** autoprime has joined #buildstream10:29
*** lachlan has joined #buildstream10:31
laurencetpollard, re this comment - https://gitlab.com/BuildStream/buildstream/merge_requests/786#note_11309609310:31
laurencencie work - if we can get into the habit of doing this for all tickets it'd be an ideal workflow, so thanks for starting us off10:32
tpollardI didn't know to do it for the mr or the issue, so decided on mr10:32
laurencecouold i ask that the associated gitlab issue gets moved inot 'Verify' instead of 'Doing' ?10:32
tpollardOk10:33
laurencethere are no boards for MRs on gitlab, which would be a better method.10:33
tpollardalthough I thought verify was post merge?10:33
KinnisonYes, verify is once the MR is merged10:34
* tpollard will hold off on that then10:43
laurenceah, good point, so it is...10:45
* laurence gets more coffee 10:45
laurenceand considers adding to the policy adjustments MR10:45
toscalixtpollard: we are not pushing any policy related with labels on MR at this point10:46
toscalixthe main goal for pushing several scales of labels is to have a clear WIP view that help to us understand what is being done or what we should pay attentio to10:46
toscalixsince there are no boards for MR, the need for pushing labels is reduced10:47
toscalixso we haven't. It is better to improve the current state of issues so at least we have a clear WIP view there than have issues and MR in a nonoptimal state10:47
toscalixthe win on using labels is when everybody use them10:48
toscalixthe more labels... the bigger chance to have them used only partially10:49
adds68The meaning of labels is not documented anywhere, so nobody will ever use them10:50
adds68Unless the label itself is clear, like "Documentation" for EG10:51
laurencemost of them are documented, there is a small note next to them to explain, when you see the list of all labels (which the policy points you too)10:55
laurenceto*10:55
adds68laurence, to get to that list though, you have to scroll down to the bottom of the issue template > "view contribution guidelines" > "visit policies guide" > then visit "Global milestones on Gitlab: https://gitlab.com/groups/BuildStream/-/milestones"11:05
adds68sorry * Check the global scale labels: https://gitlab.com/groups/BuildStream/-/labels11:06
jmachttps://gitlab.com/BuildStream/buildstream/labels lists them both (group and project labels)11:12
toscalixadds68: they are https://gitlab.com/BuildStream/nosoftware/alignment/blob/master/proposal_to_apply_Gitlab_features_to_BuildStream.md11:16
toscalixit is complete , but they are11:17
toscalixthat was the original proposal, and the policy is here: https://gitlab.com/cip-project/cip-testing/imported-kernel-tests11:18
toscalixunfinished, but is there11:19
*** jonathanmaw has quit IRC11:20
adds68toscalix, could you please review: https://gitlab.com/BuildStream/nosoftware/alignment/merge_requests/811:24
adds68jmac thanks for that link, that seems the best place to go :)11:24
*** jonathanmaw has joined #buildstream11:25
*** mohan43u has quit IRC11:26
jmacI think that's where most people will find the label descriptions - I agree with Sander that the nosoftware repo is a bit obscure at the moment11:27
*** mohan43u has joined #buildstream11:27
*** tristan has joined #buildstream11:29
*** mohan43u has quit IRC11:38
*** mohan43u has joined #buildstream11:39
toscalixadds68: thanks for the commit, I appreciate it11:40
adds68toscalix, no problem, just trying to help where i can :)11:41
*** lachlan has quit IRC11:44
toscalixadds68: I added before the wrong link, sorry. This is the policy: https://gitlab.com/BuildStream/nosoftware/alignment/blob/master/BuildStream_policies.md11:45
*** mohan43u has quit IRC11:46
*** mohan43u has joined #buildstream11:46
*** lachlan has joined #buildstream11:47
*** ctolentino has joined #buildstream11:48
*** tristan has quit IRC12:21
*** tristan has joined #buildstream12:25
*** bochecha has quit IRC12:35
*** ctolentino has quit IRC12:56
jonathanmawtristan: I've finished making changes in response to your review of https://gitlab.com/BuildStream/buildstream/merge_requests/86912:58
*** tiagogomes has quit IRC13:03
*** tiagogomes has joined #buildstream13:04
*** alatiera_ has joined #buildstream13:07
alatieraregarding this mail, https://mail.gnome.org/archives/buildstream-list/2018-October/msg00058.html13:09
alatiera>  3.) Additional dependencies for testing an element should not be required while building it.13:09
alatieraWould the above mean that I won't be able to declare a dep on asan.bst module while building my tests?13:09
*** ChanServ sets mode: +o tristan13:10
tristanAhh, looks like I duplicated that in my added (6) :)13:10
*** chill has joined #buildstream13:10
* alatiera looks13:10
tristanalatiera, I'm not sure what asan.bst is, but I think the point is that you would indeed13:11
tristanalatiera, I.e. let's say that asan.bst provides something that you only need for testing your module, something like xvfb is a decent example (a fake X server required for running tests for a lot of GUI apps)13:11
alatieraI brought it up as an example, its an adress sanitizer13:11
tristanalatiera, the point is that you don't implicitly bring it in to the module's dependencies that you are building, just because you need it to test; because you test in a separate element13:12
alatieratristan: but will I be able to include it for the tests with the proposal above or would the tests use the build deps?13:13
tristanjonathanmaw, Interesting... so what I was not sure about in my comment is why cli.py remains unchanged - looking at your test case it looks like this implicitly changes the behavior of `bst shell --build`13:13
tristanalatiera, it's easier to consider the whole thing without the "conditions" feature13:14
tristanalatiera, Just imagine you have a separate element which depends on the build, and it's purpose is to test the build13:14
tristanalatiera, it can depend on other things as well13:14
alatieratristan: oh I think I understand it now, thanks!13:15
tristanalatiera, The "conditions" feature is mostly there to express a dependency graph which does this with less verbosity in your pipeline declaration :)13:15
alatierafwiw, I was experiementing with using bst as the CI environment for some GNOME libraries the other day13:16
alatierathe idea was to reuse the gnome-build-meta module set, but we did not want to have every element depend on valgrind for example just for the tests13:17
tristanjonathanmaw, I'll update the issue, sec...13:17
tristanalatiera, right, that is precisely the kind of thing this is about :)13:17
alatierahence my intrest in it13:18
alatieraoverall bst has been really nice for me so far, amazing work!13:18
tristanalatiera, it's still only one half of the recipe to make things very nice though13:18
tristanFor instance, right now every element needs to be declared in a separate bst file13:19
tristanAnd this means that we require a lot of files to express a more complicated pipeline, an enhancement to that would be to focus on ways to make it more convenient to express the testing element in the same bst file as the build element13:20
*** jonathanmaw_ has joined #buildstream13:20
*** jonathanmaw has quit IRC13:21
benschubertHey, could I get some feedback on https://gitlab.com/BuildStream/buildstream/issues/736 ? I'm slightly worried that we might be leaking too many things between our tests :/13:45
toscalixbenschubert: we have scheduled on thursday a meeting to go over the backlog of tickets opened the last 3 weeks, where many of us has been at events. We will go over this one13:52
*** jonathanmaw_ is now known as jonathanmaw13:57
jonathanmawtristan: also, I've picked up and fixed https://gitlab.com/BuildStream/buildstream/merge_requests/743 again, iirc there was some interest in this during the gathering13:58
tristanjonathanmaw, Ah right !13:59
benschuberttoscalix: thanks!14:24
adds68Can you print to the console from inside a plugin?14:36
adds68( for debugging purposes )14:36
skullmanself.status() etc.14:36
skullmanself.debug and run with --debug would be more appropriate for debugging14:36
adds68skullman so just calling that from inside the plugin class will allow me to print?14:38
skullmanyep, sends messages to the parent process to log to console if it's in a subprocess etc.14:39
adds68skullman oh nice thanks :)14:40
tiagogomeshmm, options of type string are not supported?14:43
tristantiagogomes, that is intentional, to strictly limit the possible outputs of a given project14:46
tristanThe same is true of integers14:46
tiagogomesRight14:56
*** Prince781 has joined #buildstream14:57
*** catonano has quit IRC14:59
jonathanmawadds68: last time I tried it, though, I found that it doesn't work from within Plugin.configure. Dunno if it's changed since, that was a *long* while ago.14:59
*** catonano has joined #buildstream15:01
*** Prince781 has quit IRC15:06
*** tristan has quit IRC15:06
tiagogomesI am using the include directive to include a file from a junctioned project. I am always getting a 'var' undefined to matter the places where I define that 'var' in the subproject15:18
*** lachlan has quit IRC15:19
*** lachlan has joined #buildstream15:21
*** bochecha has joined #buildstream15:46
adds68jonathanmaw, yes it doesn't seem to work for me either =/15:52
*** brool has joined #buildstream15:56
lachlanHi, I'm trying to use a runner for the benchmarking page and I'm getting "ERROR: Preparation failed: Error response from daemon: Get https://registry-1.docker.io/v2/buildstream/buildstream-fedora/manifests/latest: received unexpected HTTP status: 503 Service Unavailable"15:57
lachlanIs anybody else experiencing a similar problem?15:57
*** chiaratolentino has joined #buildstream15:58
*** ctolentino has joined #buildstream16:03
*** ctolentino has quit IRC16:04
*** ctolentino has joined #buildstream16:08
tiagogomesShould be working now16:08
*** ctolentino has quit IRC16:10
adds68skullman seems self.debug and self.status do not print anything when building16:14
adds68skullman, is there a specific place i should put them? I am extending the Element class16:14
skullmanyou'd know as much as me there, try jonathanmaw16:15
adds68skullman, thanks jonathanmaw ^ :D16:15
*** tristan has joined #buildstream16:17
jonathanmawadds68: odd, not sure what causes that16:17
WSalmonlachlan, did you fix it? i had a ci funny earlier, i clicked try again and all was fine the second go...16:17
jonathanmawadds68: it seems status messages are dropped if buildstream is not being run in verbose mode16:18
cs-shadowlachlan: WSalmon: Docker Hub (and the CDNs in front of it) have been known to cause such failures from time to time. Not sure if there is an easy fix16:18
adds68jonathanmaw ah ok, so i need to pass --verbose as well as --debug ?16:18
*** solid_black has quit IRC16:18
*** ctolentino has joined #buildstream16:19
jonathanmawadds68: I think it should be verbose for status16:19
jonathanmawnot sure of the exact behaviour for debug16:19
*** chiaratolentino has quit IRC16:21
jonathanmawyep, looks like you should just need --debug to get debug messages.16:22
WSalmonjonathanmaw, do you need it before the command tho? bst [bst options] command [comand options] ? eg, bst --debug workspace open?16:23
adds68WSalmon yea that is how i am running it atm16:24
jonathanmawyeah, bst --verbose --debug workspace open, I think16:24
adds68jonathanmaw, this is where i have put self.debug("test message")16:24
adds68https://gitlab.com/freedesktop-sdk/freedesktop-sdk/blob/valentindavid/experimental-manifest/bootstrap/plugins/collect-manifest.py#L3216:24
jonathanmawthey don't work in configure, afaict, even with special command-line stuff16:25
jonathanmawWhen I was fiddling around trying to get stuff to work, I ended up using 'print'16:25
jonathanmawthough I never tried it, maybe self._get_context().message("test message") would work, but I haven't tried it.16:26
WSalmoni have had issues with even prints not getting out, the only sure fire way i have found to get stuff to stdout is to raise a exception however that is o"bviously suboptimal"16:26
WSalmon*  "obviously suboptimal"16:27
WSalmonlol16:27
adds68jonathanmaw i shall try that16:28
adds68WSalmon, yes print statements don't work for me either =/16:28
adds68I'm not sure how people are expected to debug =/16:29
*** tristan has quit IRC16:30
*** tristan has joined #buildstream16:30
*** zack12 has joined #buildstream16:31
coldtomwhen i was trying to get stuff to print i wrote to a logfile :P16:31
ctolentinoHello! Could I have developer permissions for the BuildStream project please (username: chiaratolentino)? Thanks!16:35
ctolentinoBtw, the links to the IRC logs doesn't seem to be working16:35
adds68coldtom, eugh serious, that was like the one thing i didn't want to do :P16:39
adds68I get debug messages from every single element, but for some reason nothing from the plugin 0_016:40
jonathanmawhrm, I'm looking at buildstream/_frontend/cli.py and wondering whether I could generalise out ensure_project_dir (since I would like to be able to search for files other than project.conf in the same way)16:50
juergbihi ctolentino, done16:51
ctolentinoThanks!16:51
jonathanmawAUIU that's there for bash completions, so I don't know whether importing functions from utils would be permitted16:51
jonathanmawor whether importing specific functions from utils would make that better (but is proscribed by CONTRIBUTING.bst)16:53
*** Prince781 has joined #buildstream17:02
*** catonano has quit IRC17:03
*** catonano has joined #buildstream17:08
adds68toscalix, https://gitlab.com/BuildStream/buildstream/merge_requests/913 This is a second MR for the issue template change, could you please review17:11
*** MindlessDrone has joined #buildstream17:14
*** rdale has quit IRC17:15
toscalixadds68: added comments17:15
*** rdale has joined #buildstream17:17
*** abderrahim has joined #buildstream17:22
*** t_acko has joined #buildstream17:22
adds68toscalix, done17:23
*** abderrahim4 has quit IRC17:24
*** xjuan has joined #buildstream17:28
*** Prince781 has quit IRC17:28
*** brlogger has joined #buildstream17:30
*** Prince781 has joined #buildstream17:30
*** tiagogomes has quit IRC17:47
*** toscalix has quit IRC17:53
*** slaf has quit IRC18:03
*** jonathanmaw has quit IRC18:08
*** raoul has quit IRC18:09
*** slaf has joined #buildstream18:19
*** Prince781 has quit IRC18:25
*** lachlan has quit IRC18:34
*** catonano has quit IRC18:39
*** catonano has joined #buildstream18:42
*** Prince781 has joined #buildstream19:34
*** catonano has quit IRC20:02
*** Prince781 has quit IRC21:04
*** Prince781 has joined #buildstream21:06
*** sircmpwn has joined #buildstream21:35
*** SirPNut has joined #buildstream22:19
*** tristan has quit IRC22:31
*** catonano has joined #buildstream22:46
*** Prince781 has quit IRC22:55
*** alatiera_ has quit IRC22:58
*** Prince781 has joined #buildstream23:01
*** slaf has quit IRC23:31

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