IRC logs for #buildstream for Monday, 2019-04-29

*** nimish2711 has joined #buildstream00:31
*** connorshea[m] has quit IRC01:51
*** nimish2711 has quit IRC03:15
*** alatiera has quit IRC03:17
*** tristan has quit IRC05:14
*** nimish2711 has joined #buildstream05:26
*** tristan has joined #buildstream05:27
*** mohan43u has joined #buildstream05:52
*** nimish2711 has quit IRC06:03
gitlab-br-bottristanvb opened issue #1013 (Better error message when staging a file into a not-directory) on buildstream https://gitlab.com/BuildStream/buildstream/issues/101307:29
*** bochecha has joined #buildstream07:50
*** alatiera has joined #buildstream07:57
*** tpollard has joined #buildstream08:41
*** raoul has joined #buildstream08:52
*** jonathanmaw has joined #buildstream09:34
*** lachlan has joined #buildstream09:38
*** lachlan has quit IRC09:42
gitlab-br-botmarge-bot123 merged MR !1313 (fixed-bug-for-pip-test->master: tests/testutil/python_repo.py: fixed executable path when running pip) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/131309:44
*** lachlan has joined #buildstream10:02
*** ChanServ sets mode: +o tristan10:17
tristanIt is damn difficult to make a test for #1012 :-/10:17
tristanMaybe I should just fix it without a test10:17
tristanIt would require a clean state for every `cli` invocation, which I guess by itself is doable10:18
tristanI need to cleanup the plugins table and re-initialize the counter, but by doing that I've already fixed the issue10:19
tristanjuergbi, Any opinion on that ? Maybe I should just fix the bug in this case without regression test ?10:20
tristanThe regression test also requires that (A) We have a source that is configured with an alias, but not a mirror, so that we hit the `track` scenario with a cloned Source, and we also require that that track implementation triggers a frontend message10:22
tristanSomehow I'm having trouble reproducing in there10:22
tristanactually it appears that cloned sources in the `cli` fixtures dont produce any messages at all, instead of crashing :-S10:23
juergbitristan: it might not be worth the effort to have a test for this, imo10:24
juergbiwe should make sure to add a proper comment for the itertools count change, though10:24
tristanyeah I have a patch which does exactly that (notes why the counter must start at 1)10:25
tristanon the other hand, if I do find time, getting to the bottom of it would have benefits... maybe10:25
juergbimaybe we could add a check for ID 0 in the plugin ID error message10:25
juergbii.e., in case it were to happen again, we would get clearer error message10:25
tristanRight10:25
tristanI found another bug in the process of trying to wrangle up a test, so I aught to file/fix that too10:26
tristanit appears that validation of mirror configuration is not being done properly (if you use a string instead of a list of URL mirrors, you hit an assert instead of a LoadError() :-S)10:27
*** lachlan has quit IRC10:39
*** lachlan has joined #buildstream10:43
gitlab-br-bottristanvb opened MR !1315 (tristan/fix-cloned-plugin-ids-1.2->bst-1.2: Tristan/fix cloned plugin ids 1.2) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/131510:43
gitlab-br-bottristanvb opened MR !1316 (tristan/fix-cloned-plugin-ids->master: Fix cloned plugin ids) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/131610:48
tristanjuergbi, Also added that assertion, in both branches (master and bst-1.2 MRs)10:48
* tristan should roll out a 1.2.6 with this fix soon10:49
tristanI think it effects any invocation of `bst track foo.bst` (single source tracking) in any project which has mirrors declared where the source does not implement source fetchers10:49
tristan(or even git, fetchers are orthogonal to tracking)10:50
benschuberttristan: the addition of the assert in 'lookup' might have a significant cost given how many times we call it :/10:50
tristanbenschubert, I'm rather ambivalent about that assert myself10:50
tristanI mean, it would be better to remain an assert, and introduce a Bug() exception that doesnt inherit from BstError10:51
tristan(i.e. make it safe to disable asserts)10:51
benschuberttristan: and for the change, what about setting clone._unique_id = self._unique_id, we would skip some indices but that should not be a problem, and this would be faster for the "norma" use case?10:51
tristanbenschubert, Well, that's what I had initially, and I thought it was a horribly brute force hack of an eye sore ;-)10:52
tristanI do see your concern though10:52
benschuberttrue, but if it's more performant :)10:52
tristanavoid a single if for every instantiation10:53
benschubertThis part is called a lot and has a significant performance impact10:53
tristanyeah10:53
benschubertactually might not be that bad, plugin.__init__ takes 3s out of a 250s run for bst show10:54
benschubertso it's not _that_ bad10:54
tristanHeh10:56
tristanThat depends I think10:57
tristanI.e. a 250s run of bst show may very well perform differently depending on what sources are employed (interrogation of source consistency is probably the most expensive)10:57
tristanbenschubert, I'm going to step out and meed friends for dinner, I'll want to close this tomorrow though10:59
tristanbenschubert, I would be more happy keeping the assert in the knowledge that the longer term plan is to replace important asserts with `raise Bug()`10:59
tristanAnd I am happy to change the __init__ approach if you deem it to be important11:00
benschuberttristan: sure, fine by me. We can always revert if that's a problem later :)11:00
gitlab-br-botBenjaminSchubert approved MR !1316 (tristan/fix-cloned-plugin-ids->master: Fix cloned plugin ids) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/131611:00
tristanOk thanks :)11:00
*** tristan has quit IRC11:05
*** lachlan has quit IRC11:06
laurencewould anyone object to making me a 'maintainer' at the group level ? https://gitlab.com/BuildStream11:14
laurencei would like to tidy up some of the benchmarks repo organisation, and i think i need higher permissions in order to create a new subgroup11:14
laurencei promise to not abuse my power11:14
*** lachlan has joined #buildstream11:26
*** tristan has joined #buildstream11:31
*** lachlan has quit IRC11:37
valentindtlater[m], let's talk about the cache server in tomorrow's meeting. I think we could just use the freedesktop sdk cache. But I want to know the opinions of others.11:50
tlater[m]valentind I'm not sure I can make tomorrow's meeting, unfortunately11:51
tlater[m]University has started again, and this particular week is the final week for a number of projects.11:52
valentindtlater[m], OK. But I will talk about that tomorrow before I start setting it up.11:52
valentindI will update you tomorrow on that.11:52
tlater[m]Thanks - I'll try to glance over irc as much as possible11:53
*** lachlan has joined #buildstream12:08
*** lachlan has quit IRC12:12
*** raoul_ has joined #buildstream13:00
*** lachlan has joined #buildstream13:01
*** raoul has quit IRC13:02
*** CTtpollard has joined #buildstream13:02
*** tpollard has quit IRC13:03
gitlab-br-botphildawson opened MR !1317 (phil/separate-local-tests->master: testing._sourcetests: Don't special case 'local' in parameter list) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/131713:07
*** lachlan has quit IRC13:13
jennisjuergbi, regarding your review comment: https://gitlab.com/BuildStream/buildstream/merge_requests/1299#note_163509529, are you eluding to having such logic within the CacheKey base class or still within Element?13:31
adds6814:41 <@alexlarsson>  ramcq: https://github.com/flatpak/flatpak/pull/2867 GET YA SOME DOCKER!13:47
adds68Add flatpak in docker seccomp profile by alexlarsson · Pull Request #2867 · flatpak/flatpak13:47
adds68This is a docker seccomp profile that allows you to run flatpak inside a docker container, given some special requirements: The host kernel must support unprivileged user namespaces (Supported by ...13:47
adds6814:42 <ramcq>  d to the o the c to the k!13:47
adds6814:42 <ramcq>  nice13:47
adds6814:44 <bochecha>  can something similar help run buildstream (i.e bubblewrap) inside unpriviledged Docker?13:47
adds6814:44 <@alexlarsson>  bochecha: yes13:47
adds6814:45 <ramcq>  bochecha: surely yes13:47
adds6814:45 <bochecha>  this is going to be very nice for a lot of CIs :)13:47
adds6814:45 <bochecha>  (gnome, fdo sdk, …)13:47
adds68benschubert ^13:47
adds68good catch bochecha :D13:48
bochechaadds68: well, this is the kind of something we (flatpak, buildstream, …) have all been wondering for a while now13:48
bochechaAlex just went and did it ^^13:48
bochechas/the kind of // (wth did I try to type?)13:48
adds68bochecha haha, praise to Alex :)13:49
*** nimish2711 has joined #buildstream13:52
juergbijennis: I expect Element class to be a better fit (see also tristan's comment)13:58
juergbiwith the weak_cached simplification, these methods might actually be completely cache key independent13:58
*** lachlan has joined #buildstream14:00
*** raoul_ has quit IRC14:03
*** raoul_ has joined #buildstream14:04
*** lachlan has quit IRC14:06
*** nimish2711_ has joined #buildstream14:11
*** nimish2711 has quit IRC14:11
*** nimish2711_ is now known as nimish271114:12
*** nimish2711_ has joined #buildstream14:23
*** nimish2711 has quit IRC14:23
*** nimish2711_ is now known as nimish271114:23
*** lachlan has joined #buildstream14:46
*** lachlan has quit IRC14:49
*** CTtpollard is now known as tpollard14:55
*** bochecha has quit IRC15:26
gitlab-br-botmarge-bot123 merged MR !1312 (jonathan/reduce-update-state-calls->master: Reduce the amount of times we call Element._update_state()) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/131215:35
tpollardI'm trying to update artifactcache/push.py test to support artifact as a proto15:51
tpollardthe element being pushed is a stack element, and internally requires a method associated to to it's __artifact member in element.py to be called.15:52
tpollardmy issue is that it seems to not be initialising an artifact member for it (this use to be done in the constructor for element, but now it's done in _update_state)15:53
tpollardI've tried to force a _preflight() and update_state() on it (to match pipelines resolve_elements) but it still lacks an __artifact15:54
tpollardthe integration tests are working fine, so I'm pretty sure this is to do with poking around internally on the specific test15:56
tpollardso I'm wondering if a stack element purposely doesn't get initialised with keys or not15:58
juergbitpollard: I don't think so, stack elements don't have special treatment in that regard16:07
juergbiat what point in the test do you get an error and what's the backtrace?16:09
*** lachlan has joined #buildstream16:12
tpollardjuergbi: if you take https://gitlab.com/BuildStream/buildstream/commits/tpollard/prototemp and run tests/artifactcache/push.py16:13
tpollard_push_artifact in _artifact_cache it attempts to call the simple accessor to the artifact method for _get_proto16:14
tpollardwhich worked fine before moving __artifact creation to update_state16:14
tpollardI have the MR working without going through artifact, but we'd prefer to just have one entry point16:15
*** lachlan has quit IRC16:15
tpollardjuergbi: it has me pretty stumped, but that's not too unusual especially on a Monday...16:34
laurenceHi all, I am on holiday next time there's a Buildstream monthly irc team meeting16:35
laurenceTuesday 14 May16:35
laurenceCan someone volunteer to run it?16:35
laurenceincluding a call for agenda the week before it16:35
laurencethe 'shake the tree' email, as i like to call it16:35
*** phil has joined #buildstream16:37
juergbitpollard: the issue could be that the elements are not marked as required when fiddling with the internals16:37
juergbialthough, update_state should create Artifact in any case, afaict16:38
*** phildawson_ has quit IRC16:38
tpollardindeed :S16:41
juergbitpollard: have you also tried calling update_state on the dependencies?16:44
tpollardif it can be sussed then _artifact_cache.py having its own implementation of getting the proto can be removed16:44
juergbitpollard: https://pastebin.com/i6PSU1KY16:48
gitlab-br-botBenjaminSchubert opened MR !1318 (bschubert/remove-duplicated-code->master: _yaml.py: remove duplicated check) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/131816:52
tpollardjuergbi: that might do the trick, I'll check in the morning :)16:54
laurencei'll ask tomorrow morning, if i remember17:00
*** jonathanmaw has quit IRC17:02
*** lachlan has joined #buildstream17:18
*** lachlan has quit IRC17:22
*** raoul_ has quit IRC17:23
*** lachlan has joined #buildstream17:25
*** lachlan has quit IRC17:29
*** lachlan has joined #buildstream17:39
*** lachlan has quit IRC17:44
*** phil has quit IRC17:52
*** phil has joined #buildstream17:52
*** nimish2711 has quit IRC18:42
*** lachlan has joined #buildstream19:17
*** lachlan has quit IRC19:29
*** lachlan has joined #buildstream19:40
*** lachlan has quit IRC19:49
*** gokcennurlu has quit IRC20:04

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