IRC logs for #buildstream for Wednesday, 2018-12-19

*** alatiera has joined #buildstream01:32
*** alatiera has quit IRC01:33
*** bochecha has quit IRC01:54
*** max has quit IRC01:56
*** xjuan has quit IRC01:57
*** nimish has joined #buildstream02:31
*** nimish has quit IRC03:23
*** werew has joined #buildstream04:23
*** kapil___ has joined #buildstream04:27
*** nssy has joined #buildstream04:34
*** ManiacTwister has joined #buildstream06:22
*** alatiera has joined #buildstream07:02
*** Kinnison has quit IRC07:32
*** Kinnison has joined #buildstream07:45
*** kapil___ has quit IRC08:17
*** slaf_ has joined #buildstream08:50
*** slaf has quit IRC08:52
*** slaf_ is now known as slaf08:52
gitlab-br-botcoldtom opened issue #825 (Stack Trace while trying to use autocompletions on `bst workspace open` with mistyped initial segment) on buildstream https://gitlab.com/BuildStream/buildstream/issues/82508:59
*** toscalix has joined #buildstream09:30
jennisadds68, there is not currently, although the information is there as we use this to update the file recording the cache size iirc09:47
jennisadds68, were you wondering whether you could check the size *before* you `bst pull`...? Or just know the size once you've `bst pull`ed?09:48
adds68jennis, ah ok, currently i can never tell if my network is super slow or bst has stopped pulling from the cache09:49
adds68It would be nice instead of time, to report xMb of YMb downloaded09:50
jennisOr potentially something we can work into the pull log09:55
jennisadds68, sounds like you want to know whther bst is pulling or not, regardless of the size...?09:56
adds68jennis, well it has the timer, but llvm reported 4 hours the other day, which is not correct, as it usually takes ~20 minutes09:57
adds68So i don't trust it09:58
benschubertjjardon: do we only have one aarch64 runner for buildstream-docker-images? https://gitlab.com/BuildStream/buildstream-docker-images/pipelines/40687623 seems to have only one job running10:10
*** bochecha has joined #buildstream10:58
toscalixvalentind: around?11:09
valentindyes11:09
toscalixI thi Sander's request to provide to the overall community background about the infra is a good one11:10
toscalixthink11:10
*** max has joined #buildstream11:10
toscalixIt would good to describe the servers we are using, what for and who is in charge11:11
jmacI'm not sure what you mean by infrastructure in that email. Haven't we always had one?11:11
toscalixand some background on who was providing them earlier11:11
toscalixjmac: yes, but I guess we haven been explicit about it11:12
jmacNo, that's true11:12
toscalixso telling everybody what we are using and who is in change is a good thing11:12
bochechajust listing the services would have done a lot of difference :)11:12
*** milloni has quit IRC11:13
toscalixwe should take this opportunity to find a second maintainer of the infra, since there are vacations, sick leaves etc.11:13
toscalixvalentind: is thi soemthing you can do?11:14
bochechaalso, the buildstream package is now in Fedora 30, as well as in the updates-testing repository for Fedora 29 and 28 :)11:14
toscalixsend a mail to the mailing list informing about this?11:14
valentindOK11:15
toscalixbochecha: are you suggesting to use this new subgroup to store those?11:15
valentindBut it is so minor, I wonder why we need to have a discussion about it.11:15
valentindI have a repository with the ansible configuration for the sleds.11:15
toscalixit is not about the info itself, it is about transparency11:16
valentindNext time I have to change something, I will make more ansible configuration.11:16
bochechatoscalix: to store what?11:16
toscalixsomebody is in chanrge of a key area for the project and people wants to know details about it. I see it as a normal thing11:16
toscalixbochecha: nevermind11:17
*** milloni has joined #buildstream11:17
jjardonbenschubert: you need to ask valentind11:17
valentindbenschubert, we have 8 builders.11:17
toscalixbochecha: it would be a good thing to announce the package availability on the mailing list and include the links in the web11:18
*** kapil___ has joined #buildstream11:18
benschubertjjardon: thanks :)11:18
benschubertvalentind oh... I only got one job at a time, is there a way of seeing their health / what they are doing somewhere?11:18
tpollardjuergbi: I'm asking in relation to 'buildstream_pb2.GetReferenceRequest()'11:18
bochechatoscalix: I was planning on doing that once they hit stable11:18
bochechatoscalix: as well as send a MR to change the install instructions11:18
tpollardjuergbi: in pull for instance, we assign the ref to it's key field11:19
juergbitpollard: this is a gRPC generated class based on the .proto11:19
toscalixbochecha: fair enough11:19
tpollardI'm looking to pass another field with it11:19
juergbithat would be a proto extension11:19
valentindbenschubert, you are right. They seem to be disabled.11:19
valentindbenschubert, they got disconnected from the network.11:26
benschubertvalentind: ouch. Would it be possible to have healthchecks somewhere? not saying now, but as a long term goal :)11:27
valentindbenschubert, like this? https://gitlab.com/groups/BuildStream/-/settings/ci_cd11:32
benschubertvalentind: ah, I get a 404, guess I don't have enough rights :/11:33
valentindProbably11:33
valentindsled22 is not working at all.11:33
valentindAh, it is booting.11:35
valentindI am redeploying. It might take 15-30 minutes.11:35
benschubertthanks a lot!11:35
tpollardjuergbi: basically I'm trying to let GetReference handle artifacts with missing buildtrees11:38
juergbitpollard: how do you want to extend the request for this?11:39
juergbithe ReferenceStorage service doesn't know anything about the artifact structure. and it shouldn't, imo11:39
tpollardinternally it calls _reachable_refs_dir which falls over in this case, so I'm looking to have an argument to allow it to skip it11:39
juergbiyou want to completely skip it or restrict it to certain subdirs?11:40
tpollardhandle it as with pull, i'e if dirnode.name in 'excluded_dirs' or whatever, then don't bother walking into it11:40
juergbiI'm wondering whether we should turn it around11:41
tpollardI've got it working clientside, but within casserver I have no way to reference back to the context of the element that is being requested11:41
juergbii.e., optionally specify which subdirs we're interested in and then potentially even return the tree digests for each subdir11:41
juergbiif you add a field to the request in the .proto file, and then regenerate the code, you should be able to access the field also on the server side11:42
juergbii.e., same way as key works right now11:43
tpollard'message GetReferenceRequest' in buildstream.proto ?11:45
juergbiyes11:46
juergbicheck CONTRIBUTING.rst for how to regenerate the code11:48
gitlab-br-botjjardon opened (was WIP) MR !1014 (jjardon/license_badge->master: README.rst: Add license badge) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/101411:51
jmacIs there a quick fix for the x86-64/x86_64 issue that's stopping freedesktop-sdk building?11:59
valentindjmac, you mean a work around?12:00
jmacYes, I just want to build it to test something else12:00
valentindYou can set -o bootstrap_build_arch x86_64 -o target_arch x86_6412:00
valentindbetwenn "bst" and "build" in the command line.12:00
jmacThat works, many thanks12:01
jmac(I altered ARCH_OPTS in Makefile with the same options)12:02
*** raoul has joined #buildstream12:10
jmacActually, when I tried that directly, it says "Unknown option 'bootstrap_build_arch' specified on the command line"12:24
jmacWait, I see, that's something specific to freedesktop-sdk12:26
*** nimish has joined #buildstream12:26
*** nimish has quit IRC12:36
bochechajmac: yeah, the -o options will usually be per project (defined in project.conf)12:37
*** nimish has joined #buildstream12:37
*** raoul has quit IRC12:46
*** nimish has quit IRC12:52
*** nimish has joined #buildstream12:52
gitlab-br-botaevri closed MR !957 (aevri/safe_noninteractive->master: BREAK: make destructive action scripts consistent) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/95712:55
*** lsfranco has quit IRC13:07
*** lsfranco has joined #buildstream13:08
*** max has quit IRC13:11
*** lsfranco has quit IRC13:18
*** lsfranco has joined #buildstream13:18
gitlab-br-botaevri opened issue #826 (Remove auto-init behaviour) on buildstream https://gitlab.com/BuildStream/buildstream/issues/82613:52
*** nimish has quit IRC14:07
*** nimish has joined #buildstream14:07
*** lachlan has joined #buildstream14:16
*** abderrahim has quit IRC14:19
*** abderrahim has joined #buildstream14:19
gitlab-br-botcs-shadow opened issue #828 (Sort NEWS before release) on buildstream https://gitlab.com/BuildStream/buildstream/issues/82814:29
*** nimish has quit IRC14:30
*** nimish has joined #buildstream14:33
gitlab-br-botwillsalmon closed issue #740 (`bst shell --build` should let the user choose whether to use cached build trees) on buildstream https://gitlab.com/BuildStream/buildstream/issues/74014:35
gitlab-br-botwillsalmon merged MR !986 (willsalmon/shellBuildTrees->master: Shell --build has optional buildtrees) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/98614:35
tpollardjuergbi: what would you expect the behaviour to be for the user if they specific --pull-buildtrees, but the remote artifact is missing the blob for it?14:45
tpollardWe already capture the missing blob exception, just debating what the best course of action is at a user level14:45
juergbitpollard: I don't think this should cause any fatal errors14:46
juergbia warning could make sense14:46
juergbior maybe even just an info message14:47
*** nimish has quit IRC14:47
*** nimish has joined #buildstream14:48
gitlab-br-botwillsalmon opened issue #829 (Download buildtrees on damand for bst shell --build) on buildstream https://gitlab.com/BuildStream/buildstream/issues/82914:50
tpollardI think if they've explicitly asked for the buildtree then we shouldn't pull the partial artifact. maybe this could come under configurable warnings I'm not sure14:50
tpollardbut I'm not 100% sure14:51
tpollardhmm14:51
valentindWhen building with buildgrid and buildbox, at some point I get error StatusCode.RESOURCE_EXHAUSTED from buildbox. And then it stops working.14:54
*** nimish has quit IRC15:03
*** nimish has joined #buildstream15:04
juergbitpollard: my point of view is from pull-buildtrees in userconfig15:04
juergbiif it's set globally, we shouldn't fail15:04
juergbias otherwise it's not usable as global option15:04
juergbiand different behavior between userconfig and CLI option would surprise me as a user15:05
juergbiif you run a command where you specify to actually use the buildtree, e.g., bst shell --use-buildtree=... would fail in any case if there is no buildtree, no matter whether the artifact is local-only or pulled from a remote15:06
*** nimish has quit IRC15:07
tpollardjuergbi: would you find it acceptable if _fetch_directory utilised _reachable_refs_dir for generating the blobs it needs to fetch, instead of having it's own loop?15:25
*** nimish has joined #buildstream15:30
gitlab-br-botLaurenceUrhegyi approved MR !1014 (jjardon/license_badge->master: README.rst: Add license badge) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/101415:35
*** nimish has quit IRC15:45
*** lsfranco has quit IRC15:48
*** lsfranco has joined #buildstream15:49
*** lachlan has quit IRC15:50
*** max has joined #buildstream16:05
*** bochecha has quit IRC16:09
gitlab-br-botjjardon merged MR !1014 (jjardon/license_badge->master: README.rst: Add license badge) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/101416:09
*** lsfranco has quit IRC16:19
*** lsfranco has joined #buildstream16:19
*** lsfranco has quit IRC16:34
*** lsfranco has joined #buildstream16:34
*** max has quit IRC16:58
gitlab-br-botwillsalmon opened (was WIP) MR !1017 (716-add-example-with-build-directory-outside-of-source-directory-2->willsalmon/outOfSourecBuilddocs: Add example with build directory outside of source directory) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/101717:04
gitlab-br-botwillsalmon opened MR !1018 (willsalmon/outOfSourecBuilddocs->master: Adding Out of Source Build Example) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/101817:09
gitlab-br-botwillsalmon closed MR !1017 (716-add-example-with-build-directory-outside-of-source-directory-2->willsalmon/outOfSourecBuilddocs: Add example with build directory outside of source directory) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/101717:09
gitlab-br-botaevri opened (was WIP) MR !1015 (aevri/rm-autoinit->master: BREAK: remove auto-init behaviour) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/101517:28
gitlab-br-botjmacarthur opened issue #830 (_relative_symlink_target depends on the host filing system) on buildstream https://gitlab.com/BuildStream/buildstream/issues/83017:31
jmacI've spent most of the day trying to figure out the symlinks issue. Hopefully #830 is a reasonable summary of it17:40
jjardonHi, Is this page meant to be there? https://buildstream.build/detail.html17:56
jjardontoscalix: ^17:56
jjardonIs there a page somewhere with reasons to use buildstream above other build systems?17:57
toscalixjjardon: no there is not. I think that would be a topic for a post, signed by somebody, instead of something on the web which "represents everybody"18:09
toscalixthat would be a corporate approach18:09
toscalixthis is my view on doing benchmarking or feature comparassions with other open source projects18:09
toscalixit is not elegant in general18:10
toscalixI do not see it as a competition18:10
jjardontoscalix: I do not understand what you mean by corporate, I'm only interested in the technical arguments18:10
jjardonI think https://docs.buildstream.build/main_about.html#why-should-i-use-buildstream is a good start18:10
toscalixeven technical arguments can be arguable18:10
*** drakythe has joined #buildstream18:10
toscalixagree18:11
toscalixtalking about your strengths is the right approach18:11
jjardonCan someone review https://gitlab.com/BuildStream/website/merge_requests/105 , please?18:13
toscalixcorporate = commercial product, for instance18:14
toscalixwhen you position your product "against" the segment leader18:14
jjardonI do not see why is that any different from competition with FOSS projects. Pretty common to have a page with differences/advantages over the others18:22
*** toscalix has quit IRC18:30
cs-shadowjumping late to this convo but I think such a page may also help users answer the question of what is the right tool for the job, and is buildstream the right tool for their use-case18:54
cs-shadowit's not always about pointing out deficiencies in other projects, but more about highlighting similarities and differences as I see it18:55
jjardonexactly18:57
*** alatiera has quit IRC19:23
gitlab-br-botcs-shadow opened MR !1019 (chandan/abstract-git-source->master: Expose base class for Git source plugins) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/101920:07
*** juergbi has quit IRC21:00
*** juergbi has joined #buildstream21:01
*** kapil___ has quit IRC21:17

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