IRC logs for #buildstream for Wednesday, 2019-01-09

*** tristan has joined #buildstream00:29
*** xjuan has quit IRC00:45
*** xjuan has joined #buildstream01:00
*** nimish has joined #buildstream01:00
*** xjuan has quit IRC01:09
*** nimish has quit IRC03:23
*** tristan has quit IRC06:20
*** alatiera has joined #buildstream07:20
*** toscalix has joined #buildstream08:52
*** jonathanmaw has joined #buildstream09:46
*** raoul has joined #buildstream09:58
valentindWhile building Freedesktop SDK with BuildStream and BuildGrid, I got: "Element plugin 'script' does not support virtual directories."10:03
valentindIs that an oversight?10:03
valentindjmac, probably you know about that ^10:06
jmacHmm! I've built freedesktop sdk with remote execution recently, so that's odd10:07
valentindUnless it was something merged recently.10:09
valentindI am using a branch.10:09
jmacScript needs a real directory to run, so it's not an oversight; it cannot support virtual directories locally.10:10
jmacWhat's the working branch for freedesktop-sdk? master does not seem to have moved since August.10:12
valentindjmac, I get also that: https://paste.gnome.org/po8vhxayd10:12
valentindjmac, it is 18.0810:12
jmacThe second error is completely unknown to me, sorry10:12
juergbijmac: why does script need a real directory?10:13
valentindjmac, I see, it is not an error, for the virtual directory but a warning.10:13
valentindBefore it says: "WARNING [script:remote-failure]: Artifact base/locales.bst is configured to use remote execution but element plugin does not support it."10:13
valentindjuergbi, I suppose it is more complicated because of the layout.10:14
juergbiI can't think of a reason why virtual directories couldn't be used with a custom layout10:15
jmacjuergbi: I don't see how else you could run commands10:16
juergbithe actual script commands still run in the sandbox10:17
jmacYes. Nothing that requires a sandbox can use virtual directories, can it?10:18
jmacOh, virtual vs CAS, I suppose10:18
juergbisandbox.run() is also used by build elements10:19
juergbiand can use a local or a remote sandbox10:19
juergbidon't see a significant difference between build elements and script elements in this regard10:19
juergbithe main special part of script elements is the layout functionality (+ support for read-write rootfs)10:19
jmacYes, they can use virtual directories then, they just have to be file-based ones10:19
valentindjmac, by the way, when compiling freedesktop-sdk, I had this issue with BuildGrid. Did not you? https://gitlab.com/BuildGrid/buildgrid/issues/15010:19
jmacvalentind: Nope, not seen that either10:20
juergbijmac: why file-based?10:20
jmacSorry, you're both now hitting me with too many questions, I'll have to come back to this later10:21
juergbiok, no problem10:22
valentindjmac, juergbi, I will create an issue for virtual directories in script. That will be more like a placeholder not to forget. Please feel free to edit it.10:24
gitlab-br-botvalentindavid opened issue #850 (script plugin should support virtual directories) on buildstream https://gitlab.com/BuildStream/buildstream/issues/85010:27
valentindYes. It is #85010:27
*** lachlan has joined #buildstream10:31
*** tintou has left #buildstream10:45
jmacRight, ten minutes between meetings10:48
jmacjuergbi: I don't see how you could run a sandbox locally with a CAS-based file system; you'd need to either export it all to a normal filesystem then repack it, or have the CAS FUSE running locally10:49
*** ahmed89 has joined #buildstream10:51
*** slaf has quit IRC10:52
*** slaf has joined #buildstream10:54
*** slaf has joined #buildstream10:54
*** slaf has joined #buildstream10:54
*** slaf has joined #buildstream10:54
*** slaf has joined #buildstream10:55
valentindjmac, there is something I need to understand here. Maybe the documentation of BST_VIRTUAL_DIRECTORY is incomplete. It says it should be false if Sandbox.get_directory is called. I do not see where in ScriptElement or script where Sandbox.get_directory is called. So in my opinion BST_VIRTUAL_DIRECTORY should be true.10:58
jmacSorry, been called into another meeting now :(10:59
*** phildawson_ has quit IRC11:00
*** phildawson_ has joined #buildstream11:01
*** raoul_ has joined #buildstream11:01
*** raoul has quit IRC11:02
*** raoul_ has quit IRC11:10
*** phildawson_ has quit IRC11:35
adds68hey jonathanmaw, everything has been resolved for the plugin here: https://gitlab.com/BuildStream/bst-external/merge_requests/60, when you get 5 minutes could you review please?11:36
*** phildawson_ has joined #buildstream11:39
*** raoul_ has joined #buildstream11:39
*** slaf has quit IRC12:19
*** slaf has joined #buildstream12:23
*** slaf has joined #buildstream12:24
*** cs-shadow has joined #buildstream12:42
jmacvalentind: I believe you're correct; we can set BST_VIRTUAL_DIRECTORY in script12:45
jmacI tried building freedesktop-sdk, and it's thrown this error: Pip package buildstream-external does not contain a plugin named 'git_tag'12:45
valentindjmac, OK, I will try to build freedesktop sdk with that.12:45
valentindjmac, you need to install or update bst-external.12:46
jmacbst-external is there and at current master12:48
jmacAh, it needs manually installing as well12:48
jmacGot it12:48
valentindjmac, I think you need the latest release.12:49
valentindYou can check with git hash in .gitlab-ci.yml12:49
jmacIt's building now, thanks12:50
valentindjmac, so the other issue I talked about before is with buildgrid. Apparently, it does not like when stdout or stderr of a job is too big.12:51
jmacRight, interesting12:52
valentindThe workaround is to disable stdout/stderr in the response from the bot. But then we do not get anything in the log.12:53
gitlab-br-botvalentindavid closed issue #780 (Remote execution: TLS support for execution service) on buildstream https://gitlab.com/BuildStream/buildstream/issues/78012:59
gitlab-br-botvalentindavid closed issue #631 (Remote-execution user configuration (technical debt)) on buildstream https://gitlab.com/BuildStream/buildstream/issues/63112:59
gitlab-br-botvalentindavid merged MR !1030 (valentindavid/remote_execution_configuration->master: Remote execution configuration: HTTPS and user configuration) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/103012:59
*** finn has joined #buildstream13:00
*** raoul_ has quit IRC13:08
valentindjmac, it looks like script runs fine remotely.13:29
valentindI will make a merge request.13:29
jmacCool, thanks.13:53
*** raoul_ has joined #buildstream13:54
gitlab-br-botvalentindavid opened MR !1047 (valentindavid/script_virtual_directory->master: buildstream/plugins/elements/script.py: Mark script as BST_VIRTUAL_DIRECTORY) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/104714:02
gitlab-br-botjmacarthur opened MR !1048 (jmac/rename_instance_name->master: Rename 'instance_name' option to 'instance-name') on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/104814:05
valentindjmac, found another bug. When an element produces an empty artifact, then we get a failure:14:05
valentind"FAILURE Directory '/buildstream-install' was not found inside the sandbox, unable to collect artifact contents"14:05
valentindIn freedesktop sdk it is split-locales.bst. Sure it should be a "stack" here instead of "manual". But there is no point failing on empty artifacts in my opinion. There would be probably cases were some elements are just empty for some architectures and not other for example.14:07
jmacI'll take a look at what creates that directory14:08
jmacI agree, empty artifacts shouldn't be a problem14:08
valentindI am creating an issue for that. You can follow up on it.14:08
gitlab-br-botvalentindavid opened issue #851 (Element with empty artifacts are disallowed by remote execution build) on buildstream https://gitlab.com/BuildStream/buildstream/issues/85114:12
valentindjmac, #85114:13
mablanchvalentind: For the BuildGrid log problem, you can try that: https://gitlab.com/BuildGrid/buildgrid/merge_requests/13814:13
valentindmablanch, yes, I am going to launch it now.14:13
mablanchvalentind: Great, thanks!14:13
*** finn has quit IRC14:18
valentindmablanch, It does not fail.14:26
valentindBut I am wondering why I do not see much in the logs in buildstream.14:27
jmacvalentind: The confusing thing is that by my reading, we've never allowed empty artifacts before. Is it possible that element isn't meant to have empty output?14:27
valentindI wonder if maybe in BuildStream for remote jobs, we do not log the commands and output.14:27
valentindjmac, Well, the artifact is not empty since it contains other stuffs than the files.14:28
valentindBut there is no file.14:28
valentindI can rephrase the issue.14:29
valentindjmac, I rephrased to make the issue a bit more precise.14:32
mablanchvalentind: Yes, I'm not sure either if BuildStream is actually making any use of the returned logs. Do you remember seeing any of it before you switch to that BuildGrid branch?14:33
*** finn has joined #buildstream14:35
gitlab-br-botjmacarthur approved MR !1047 (valentindavid/script_virtual_directory->master: buildstream/plugins/elements/script.py: Mark script as BST_VIRTUAL_DIRECTORY) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/104714:43
valentindThe command logs are missing in "bst artifact log". I will try with buildgrid master to see.14:43
gitlab-br-botvalentindavid closed issue #850 (script plugin should support virtual directories) on buildstream https://gitlab.com/BuildStream/buildstream/issues/85014:44
gitlab-br-botvalentindavid merged MR !1047 (valentindavid/script_virtual_directory->master: buildstream/plugins/elements/script.py: Mark script as BST_VIRTUAL_DIRECTORY) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/104714:44
jmacjuergbi: !1048 changes instance_name to instance-name in the config, as you spotted. If you can approve that I'll merge it.14:45
gitlab-br-botMR !1048: Rename 'instance_name' option to 'instance-name' https://gitlab.com/BuildStream/buildstream/merge_requests/104814:45
gitlab-br-botvalentindavid approved MR !1048 (jmac/rename_instance_name->master: Rename 'instance_name' option to 'instance-name') on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/104814:47
valentindmablanch, It is a BuildStream issue that the logs do not appear.14:48
valentindjmac, I see that the logs of commands in remote execution are not added to the logs in the artifact. Is there an issue tracking the work for that?14:51
jmacNot that I know of.14:53
valentindI am sure it is an important feature we need.14:53
valentindInterestingly, if a build fails, it also complains of the install-root directory not to be there. But only this. We do not get the output from the failing command.14:56
valentindOh, but I guess what happens is that we are supposed to get the logs through the artifact. But we cannot create the artifact because we are missing the output directory.14:57
*** nimish has joined #buildstream14:59
jmacI haven't paid much attention to build logs yet, to be honest. I do think they're important, but I'd like to get more basic functionality working with CI tests before adding more.14:59
jennisIs it possible to obtain an element's cache key in the test suite?15:04
*** nimish has quit IRC15:04
*** nimish has joined #buildstream15:05
valentindjennis, cli.get_element_key maybe.15:06
jennisahh, i missed that, that sounds like exactly what I need, thanks valentind15:08
laurencebenschubert, I can see a lachlan....is your query from Friday still relevant ?15:09
benschubertYep! thanks for pinging me laurence !15:09
benschubertlachlan: I have questions on benchmarking when you have time! I want to compare my branch against master, in terms of profile (pstat), memory usage, and speed (on three different benchmarks, to keep things separate). Ideally with a set of canonical repositories used for Benchmarking. Is there currently a way of doing (part) of this?15:10
*** mohan43u has quit IRC15:14
*** mohan43u has joined #buildstream15:18
lachlanbenschubert: Hi at the minute none of the tests a.s15:21
lachlanbenschubert: Hi at the minute none of the tests check for memory usage - but speed is determined by the time taken to execute tests15:22
benschubertlachlan: I am more interested in benchmarks than the tests, since the tests are not representative of real life scenarios (in terms of sizes)15:23
*** nimish has quit IRC15:25
*** nimish has joined #buildstream15:25
lachlanbenschubert: Sorry to clarify - the benchmarks we have represent a subset of the tests that are defined in the benchmarking repo. As to whether they act as representative real life scenarios, currently one benchmarking test (which represents a real life build) is currently broken due to an architecture nomenclature change.15:29
benschubertlachlan: oh that makes more sense I see. And for those, we only get the timing, not profile neither memory usage, correct?15:30
gitlab-br-botjmacarthur merged MR !1048 (jmac/rename_instance_name->master: Rename 'instance_name' option to 'instance-name') on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/104815:30
gitlab-br-botjonathanmaw opened issue #852 (Cover the use of WSL in CI) on buildstream https://gitlab.com/BuildStream/buildstream/issues/85215:31
lachlanAt the minute no memory usage - but I would have thought it would be possible to craft some script that could profile memory usage at the same time as running the underlying build activity15:31
lachlanIt is certainly something I would like to look at adding15:32
benschubertok! And lastly, I ahve looked at the repo, but I am not sure how I can run it, to compare two different branches at their latest commit15:32
lachlanAt the minute you would need to craft a benchmarking configuration for a specific branch/commit.15:33
benschubertcould you point me to an example? And I assume we then need to compare by hand or do we have utilities for this?15:36
lachlanThis can be done through the option to add extra versions to be tested in another file which can be appended to the test execution15:39
*** tristan has joined #buildstream15:39
lachlanIf you look in the repo under bst_benchmarks/template.benchmark you can see the general form15:39
benschubertperfect, I'll look into this soon, thanks!15:41
lachlanIf you create a file containing the versions you require and then add this to the end of the call as "-c <filename.benchmark>" it does these extra versions15:42
lachlanThe results will be output with the results for master15:42
benschubertlachlan: perfect thanks! For requests for improvements on the benchmarking side, I guess an issue on the repo is the best, or is there other discussions in other channels about it? (ML?)15:51
adds68jonathanmaw, thanks for the merge! :)15:55
adds68johnward, when will the next release be done?15:55
*** nimish has quit IRC16:05
lachlanbenschubert: At the moment raising an issue would be best.16:07
laurenceadds68, did you mean jonathanmaw there?16:07
adds68 laurence  correct sorry johnward  :)16:07
laurencebenschubert, yes, gitlab issue on that repo pls16:08
*** nimish has joined #buildstream16:08
jonathanmawadds68: I can do one now16:09
*** nimish has quit IRC16:13
*** nimish has joined #buildstream16:14
*** nimish has joined #buildstream16:14
adds68jonathanmaw, awesome :)16:14
jonathanmawadds68: done16:17
adds68\o/16:17
benschubertlachlan: I'll do thanks!16:18
*** nimish has quit IRC16:24
*** nimish has joined #buildstream16:25
*** nimish has quit IRC16:35
*** nimish has joined #buildstream16:35
*** nimish has quit IRC17:10
*** nimish has joined #buildstream17:11
*** nimish has quit IRC17:26
*** nimish has joined #buildstream17:26
*** nimish has quit IRC17:30
*** jonathanmaw has quit IRC18:26
*** toscalix has quit IRC18:37
*** raoul_ has quit IRC18:44
gitlab-br-botBenjaminSchubert opened issue #853 (BUG hit: "no module named 'grpc.framework') on buildstream https://gitlab.com/BuildStream/buildstream/issues/85319:02
benschubert^ If somebody wants to bang their head19:07
gitlab-br-bottristanvb opened MR !1051 (tristan/detox-tests->master: Allow using detox, and fix/refactor collection of coverage reports) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/105119:15
*** ChanServ sets mode: +o tristan19:16
tristanbenschubert, !1051 is going to fix #844 :)19:16
gitlab-br-botIssue #844: Coverage reports inacurate with multiple runs of `tox` https://gitlab.com/BuildStream/buildstream/issues/84419:16
benschubertOh great! Thanks19:17
tristandetox is nice with python 3.5, 3.6 and 3.719:17
*** phildawson_ has quit IRC19:32
*** tristan has quit IRC19:40
*** tristan has joined #buildstream19:45
*** alatiera has quit IRC19:49
*** lachlan has quit IRC20:05
gitlab-br-bottristanvb closed issue #844 (Coverage reports inacurate with multiple runs of `tox`) on buildstream https://gitlab.com/BuildStream/buildstream/issues/84420:36
gitlab-br-bottristanvb merged MR !1051 (tristan/detox-tests->master: Allow using detox, and fix/refactor collection of coverage reports) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/105120:36
*** mohan43u has quit IRC20:45
gitlab-br-bottristanvb opened MR !1052 (tristan/refine-coverage->master: .coveragerc: Omit some things which are irrelevant to cover.) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/105220:47
gitlab-br-bottristanvb merged MR !1052 (tristan/refine-coverage->master: .coveragerc: Omit some things which are irrelevant to cover.) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/105221:12
*** mohan43u has joined #buildstream21:36
*** tristan has quit IRC21:47
*** tristan has joined #buildstream22:08
*** ChanServ sets mode: +o tristan22:44
tristanInterestingly, this test https://gitlab.com/BuildStream/buildstream/blob/tristan/element-processing-order/tests/frontend/buildorder.py shows that the order of builds are not stable22:44
tristanFor me, the second test passes on py36 and py37, but finds a different order on py35... and it does it consistently22:44
*** tristan has quit IRC23:19
*** tristan has joined #buildstream23:19
*** ChanServ sets mode: +o tristan23:19
tristanscratch that, not consistent; different runs yield different results23:25
tristanlooks like a dictionary randomization is playing a part possibly23:26
tristanor maybe set()23:26
*** tristan has quit IRC23:35
gitlab-br-botjjardon closed issue #351 (Allow deploying directly to ostree) on buildstream https://gitlab.com/BuildStream/buildstream/issues/35123:43

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