IRC logs for #buildstream for Monday, 2018-09-24

*** iker has joined #buildstream07:03
*** tiagogomes has joined #buildstream07:10
*** toscalix has joined #buildstream07:52
*** finn has joined #buildstream07:56
finnvalentind, do you have an example of the flatpak plugin?07:57
*** phildawson has joined #buildstream08:10
valentindfinn, in freedesktop-sdk, there are several elements in elements/flatpak-images08:42
finnthanks, I'll have another look tonight08:54
*** tpollard has joined #buildstream09:05
*** jonathanmaw has joined #buildstream09:06
gitlab-br-botbuildstream: merge request (juerg/cas-batch->master: _artifactcache/cascache.py: Use BatchReadBlobs) #813 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/81309:11
*** lachlan has joined #buildstream09:29
*** dtf has quit IRC09:45
*** lachlan has quit IRC09:46
*** lachlan has joined #buildstream09:50
*** finn_ has joined #buildstream09:56
*** lachlan has quit IRC09:56
*** finn has quit IRC09:57
*** lachlan has joined #buildstream10:08
*** cs-shadow has joined #buildstream10:10
gitlab-br-botbuildstream: merge request (mac_fixes->master: WIP: Implement compatibility fixes for MacOSX and WSL Blocks #411 and #412") #726 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/72610:10
gitlab-br-botbuildstream: merge request (willsalmon/outOfSourecBuild->master: Out of source builds) #776 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/77610:20
gitlab-br-botbuildstream: merge request (mac_fixes->master: WIP: Implement compatibility fixes for MacOSX and WSL Blocks #411 and #412") #726 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/72610:23
toscalixjmac: ticket #664 is it in your radar for the short term?10:27
jmactoscalix: Yes, I'm working on it now. I have a fix, it just needs lots of testing10:29
jmacBuilding freedesktop-sdk takes many hours10:29
toscalixthanks10:30
toscalixthis ticket and the cache being filled are our pain points this week10:31
*** dtf has joined #buildstream10:41
gitlab-br-botbuildstream: merge request (juerg/cas-batch->master: _artifactcache/cascache.py: Use BatchReadBlobs) #813 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/81310:46
gitlab-br-botbuildstream: merge request (mablanch/630-remote-execution-reconn->master: Handle connection losses during remote build execution) #806 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/80610:49
*** tiagogomes_ has joined #buildstream10:52
*** tiagogomes has quit IRC10:53
*** tiagogomes has joined #buildstream10:54
*** tiagogomes_ has quit IRC10:55
*** tiagogomes_ has joined #buildstream10:57
*** tiagogomes has quit IRC10:58
gitlab-br-botbuildstream: merge request (mac_fixes->master: WIP: Implement compatibility fixes for MacOSX and WSL Blocks #411 and #412") #726 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/72611:06
toscalixReminder: please add the topics you want to discuss during the gathering in this page https://wiki.gnome.org/Projects/BuildStream/Events#Proposed_topics11:12
toscalixplease add yourself to the participants list if you are attending11:12
toscalixI just added the Gathering to the calendar event11:13
gitlab-br-botbuildstream: merge request (juerg/cas-batch->master: _artifactcache/cascache.py: Use BatchReadBlobs) #813 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/81311:18
valentindjuergbi, I tried fill up a cache server. I found something that I do not think is right.11:55
valentindjuergbi, while uploading objects, we check for disk space and prune if needed. Before we set a ref. So that means that what is being uploaded which is probably unreachable yet will be removed.11:55
valentindTypically, when the cache is full, I do a push, I get no error. But when I pull it back, then it complains about missing files.11:56
juergbivalentind: yes, that sounds like an issue12:01
juergbito handle concurrent uploads, we need a more robust solution12:02
*** lachlan has quit IRC12:02
valentindjuergbi, I see 2 ways to fix it. Either we make an LRU on objects instead of refs. And remove automatically refs that use them when they are removed.12:03
valentindOr... actually I am not sure how to solve it otherwise.12:04
juergbithe latter part sounds expensive12:04
valentindWe would need to change the protocol.12:04
juergbiin what way?12:05
valentindWe need a way to have transactions.12:05
juergbithat would be a huge REAPI change/addition12:05
valentindjuergbi, we need it fixed on 1.2 branch.12:06
valentindDo you see any other way to fix that?12:06
juergbiI was thinking that we keep LRU of refs but refrain from removing objects that have a recent mtime12:06
valentindIt is urgent. Gnome and Freedesktop sdk depend on it.12:06
valentindhow recent?12:06
juergbiand let FindMissingBlobs update the mtime12:06
juergbimaybe something like an hour?12:07
juergbinot ideal that we need a fixed time for this but not sure how to handle this otherwise12:07
valentindI am afraid some push might take more than an hour.12:07
juergbimaybe even a few hours to be on the safe side12:07
*** jonathanmaw_ has joined #buildstream12:07
juergbiyes, was just thinking12:08
*** jonathanmaw has quit IRC12:08
juergbimaybe 6 hours or so? that should be sufficient time for large uploads and yet small enough to not be an issue for minimal cache size12:08
juergbicould also extend it to 24 hours. would probably still be fine12:09
valentindjuergbi, I can try that.12:09
juergbigreat, ta, the FindMissingBlobs part is clear to you?12:10
valentindjuergbi, yes, I just touch all digests.12:10
juergbiyes12:10
valentindAnd then in cas.prune I ignore recent digests.12:10
valentindjuergbi, I think you still need to find a better solution for 1.4.12:11
juergbivalentind: what issues do you expect?12:13
*** lachlan has joined #buildstream12:14
valentindjuergbi, not being able to upload much for a while after a lot was uploaded at once.12:14
valentindjuergbi, we can still keep the mtime thing. But if the client could send a request saying that all it uploaded is safe after sending all the refs, that would help unlocking objects.12:15
juergbivalentind: i.e., you expect the disk quota to be smaller than the working set of a 6h window?12:15
valentindI do not want to have expectations from what the users do.12:16
juergbiwill think about it some more12:20
gitlab-br-botbuildstream: merge request (mac_fixes->master: WIP: Implement compatibility fixes for MacOSX and WSL Blocks #411 and #412") #726 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/72612:20
juergbivalentind: btw: while the pruning before the ref is an issue, is this really the cause for #609? i.e., wouldn't it delete too much instead of too little?12:21
gitlab-br-botbuildstream: merge request (mac_fixes->master: WIP: Implement compatibility fixes for MacOSX and WSL Blocks #411 and #412") #726 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/72612:22
*** lachlan has quit IRC12:22
valentindjuergbi, I am not sure. I suppose the cache gets stuck full for a while. Nobody sees the error.12:22
valentindBut then suddenly there is concurrent push.12:22
valentind2 request for beginning of upload of big objects. They both call _clean_up_cache. And both think there is enough space.12:23
gitlab-br-botbuildstream: merge request (mac_fixes->master: WIP: Implement compatibility fixes for MacOSX and WSL Blocks #411 and #412") #726 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/72612:24
valentindAnd then they both upload. But the sum of the two object is bigger than the space remaining.12:24
valentindI suppose we need to _clean_up_cache at each request.12:25
valentindOr fallocate the file.12:25
valentindLike fallocate first, and then _clean_up_cache.12:26
valentindTo avoid race condition.12:26
juergbiwe already _clean_up_cache on every request12:28
valentindIt seems it does it only when "resource_name" is None.12:29
valentindjuergbi, you can confirm there is no way that _ByteStreamServicer.Write cannot be called concurrently?12:30
valentindBecause we do many "out.write" on the temporary file.12:30
valentindjuergbi, does not the iterator of request_iterator yield?12:33
juergbivalentind: it can be called concurrently12:34
juergbithe server is actually multi-threaded12:34
juergbihowever, we also have a 2 GB buffer12:34
juergbiwe could probably keep track of reserved space, though, or indeed use fallocate12:35
juergbiI don't think it's very likely that this is the cause for the issue, though, given the 2 GB buffer and we probably don't have too many concurrent uploaders12:36
juergbi(a single upload job writes files one by one)12:36
*** bochecha has joined #buildstream12:37
NexusI cam across the issue where if there is a `project.conf` anywhere above the test suite when running `tests/format/project.py::test_missing_project_conf ` the test will fail.    From what i can see there are 2 options to fix this, 1: do a check for project.conf out of bounds before the test, and if it is found, skip the test. 2: Add an optional argument to the `_ensure_project_dir()` function to allow12:38
Nexusyou to limit the number of times it cycles through directories, for the sake of testing12:38
Nexusanyone got any thoughts of additional options?12:39
gitlab-br-botbuildstream: merge request (bochecha/blessings->bst-1.2: _frontend/status.py: Remove leftover blessings import) #821 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/82112:42
skullmanNexus: rather than a limit to the number of times it'll go up, you could set a directory it won't attempt to traverse up out of, which at least could see some use if it defaults to $HOME12:45
valentindjuergbi, CI has many uploaders at once.12:45
valentindUsually 4 per branch because 4 architectures.12:45
valentindThen it is not uncommon to have more than 5 branches building in the same time.12:45
valentindSo 20 uploaders is not impossible.12:46
juergbiok but that would still require an average blob (not artifact) size of 100 MiB and all starting upload at almost the same time12:48
juergbinot impossible but it doesn't sound very likely. well, unless we're creating image files or similar. maybe fdo sdk does create such large files12:50
valentindllvm is 43M12:50
valentindAnd we do have vm images.12:50
juergbisingle file?12:50
juergbivm images could certainly trigger such issues12:51
valentindI am not sure about gnome though.12:51
juergbiin any case, fallocate does sound sensible, if it's easily doable from Python12:53
valentindjuergbi, there is a weird behavior I do not understand. With "df" I look at the space available.12:53
valentindAnd at each upload it goes double size.12:53
valentindAnd then comes back down.12:53
valentindSo, it seems the temporary file is copied rather than linked.12:54
juergbithat's actually indeed the case12:55
valentindShould not we cound double size when calling _clean_up_cache?12:55
juergbiwe use add_object() which normally does this to ensure regular user files (which may be concurrently modified) are not linked into the CAS, avoiding corruption12:57
juergbihowever, in the case where the CAS server is creating and writing the file, we shouldn't need this precaution and could thus avoid the double write12:57
juergbiwe still need to verify the digest but we could do this during the upload12:58
gitlab-br-botbuildstream: merge request (mac_fixes->master: WIP: Implement compatibility fixes for MacOSX and WSL Blocks #411 and #412") #726 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/72612:59
*** lachlan has joined #buildstream13:04
gitlab-br-botbuildstream: merge request (bochecha/blessings->bst-1.2: _frontend/status.py: Remove leftover blessings import) #821 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/82113:06
gitlab-br-botbuildstream: merge request (mablanch/630-remote-execution-reconn->master: Handle connection losses during remote build execution) #806 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/80613:06
bochechajuergbi: with my MR merged, do you think there should be a new release quickly?13:17
bochechaas it is, `pip install` 1.2.1 is broken :-/13:17
juergbiah, because it's not in setup.py :/13:17
juergbifor people updating it presumably works because the dependency will still be installed, but new installations will likely fail13:21
bochechaexactly13:22
juergbimight indeed warrant a new release. not ideal that tristan is away13:22
bochecha(it even fails on upgrades in some systems, like rpm-ostree which removes unnecessary deps, and thus removes blessings when bst is updated)13:23
*** toscalix_ has joined #buildstream13:26
*** toscalix_ has quit IRC13:27
*** lachlan has quit IRC13:29
gitlab-br-botbuildstream: merge request (juerg/rebuild->master: element.py: Fix cache check in non-strict mode) #822 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/82214:01
*** lachlan has joined #buildstream14:02
jjardonHi, if I do `bst shell base/opus.bst` I get a shell, but if I do `bst shell --build base/opus.bst` I get the following error: https://paste.gnome.org/p5o7xazo6 ; is this the expected behavior?14:05
juergbiskullman: I'd appreciate a review of !822. fixes a regression introduced by the failed build caching support14:06
skullmanjuergbi: looking now14:06
juergbijjardon: if those are indeed not cached, yes14:06
juergbibst shell without --build doesn't stage build-only dependencies14:06
jjardonjuergbi: ah! ok. So how I can force it to be cached?14:07
jjardonI would expect `bst shell --build base/opus.bst` to automatically cache build deps?14:07
juergbibst build --all base/opus.bst should work, however, it's a bit overkill14:08
gitlab-br-botbuildstream: merge request (mac_fixes->master: WIP: Implement compatibility fixes for MacOSX and WSL Blocks #411 and #412") #726 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/72614:08
juergbias it will also ensure all indirect build dependencies are available14:08
juergbijjardon: iirc, there was a recent discussion that we're missing a command to only build what's needed for a build shell14:08
jjardonmmm, that ring a bell; bochecha was that you?14:09
jjardonjuergbi: thanks for the  build --all base/opus.bst ; I will try that for now14:09
bochechajjardon: yes14:09
bochechathat was me14:09
bochechatristan asked me to send a proposal to the mailing-list, and I completely forgot :)14:09
jjardonbochecha: did you open an issue by any chance?14:10
bochechathe idea was to remove --all and to instead have a --deps which does like the one for bst pull14:10
bochechaand maybe then add a suboption to --deps, in addition to none/all14:10
bochechajjardon: I didn't, because tristan said this is the kind of proposal which should go through a discussion on the mailing-list14:11
jjardonI would like `bst shell --build base/opus.bst` to do all this automatically14:11
gitlab-br-botbuildstream: merge request (mac_fixes->master: WIP: Implement compatibility fixes for MacOSX and WSL Blocks #411 and #412") #726 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/72614:11
jjardonI'm actually saying to bst I want a sysroot to build this element; so I'd expect everything the element needs to be included14:11
jjardonin what situations `bst shell --build base/opus.bst` would be useful if not?14:12
gitlab-br-botbuildstream: merge request (mac_fixes->master: WIP: Implement compatibility fixes for MacOSX and WSL Blocks #411 and #412") #726 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/72614:15
juergbijjardon: we currently don't implicitly start a build session on 'bst shell' and 'bst checkout'. if you think we should change that, we probably should discuss this on the list14:17
gitlab-br-botbuildstream: merge request (mac_fixes->master: WIP: Implement compatibility fixes for MacOSX and WSL Blocks #411 and #412") #726 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/72614:17
gitlab-br-botbuildstream: merge request (juerg/rebuild->master: element.py: Fix cache check in non-strict mode) #822 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/82214:18
skullmanjuergbi: reviewed14:18
bochechajjardon: agreed that automatically doing this would be **very** nice, but in general bst doesn't do anything automatically… so the next best thing is to be able to build just the needed deps :)14:18
jjardonjuergbi: sure; if I understand this correctly that is expected when running `bst shell base/opus.bst`, but if I explicity add the `--build` option, I think is clear that what I want is to have everything there so I can build?14:19
*** raoul has joined #buildstream14:19
jjardonI'm trying to imagine a case when you do `bst shell --build base/opus.bst`  but you dont actually want the needed things to build in the shell14:20
juergbijjardon: well, you could say the same for bst shell without --build, i.e., it's clear you want everything so that you can run it14:20
juergbior bst checkout14:21
bochechajjardon: to be fair, I can't imagine a case where I'd do `bst shell base/opus.bst` and not want everything to be built either :)14:21
bochechajuergbi: how about adding a --auto-build option to shell and checkout?14:21
juergbii.e., I don't see a reason to distinguish between these cases. either we always build implicitly or never14:21
juergbicould be an option (or could also be the other way round, auto build by default)14:21
jjardonthe docs says: "Use the –build option to create a temporary sysroot for building the element instead." but then when I run that I can not build? It's a bit confusing :)14:21
juergbitrue, it doesn't fit in any sensible workflow14:22
*** lachlan has quit IRC14:22
*** laowei has joined #buildstream14:27
*** ikerperez has joined #buildstream14:29
*** iker has quit IRC14:30
gitlab-br-botbuildstream: merge request (jonathan/source-mirror-project-refs->master: tests: Add regression test for mirroring with project.refs) #823 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/82314:31
*** abderrahim has quit IRC14:47
*** abderrahim has joined #buildstream14:48
*** lachlan has joined #buildstream15:01
*** lachlan has quit IRC15:08
*** lachlan has joined #buildstream15:11
*** lachlan has quit IRC15:19
*** tiagogomes has joined #buildstream15:26
*** tiagogomes_ has quit IRC15:27
*** finn_ has quit IRC15:33
*** lachlan has joined #buildstream15:37
*** finn has joined #buildstream15:38
*** tiagogomes_ has joined #buildstream15:47
*** tiagogomes has quit IRC15:48
*** tiagogomes_whostolemyidentity has joined #buildstream15:55
juergbibochecha: 1.2.2 release is out, hopefully I didn't miss anything15:56
*** tiagogomes_ has quit IRC15:56
juergbijjardon: can you please update the topic?15:56
*** ikerperez has quit IRC15:58
*** jjardon changes topic to "BuildStream 1.2.2 is out ! | https://gitlab.com/BuildStream/buildstream | Docs: https://buildstream.gitlab.io/buildstream | IRC logs: https://irclogs.baserock.org/buildstream | Mailing List: https://mail.gnome.org/mailman/listinfo/buildstream-list | Roadmap: https://wiki.gnome.org/Projects/BuildStream/Road"15:59
*** toscalix has quit IRC16:02
gitlab-br-botbuildstream: issue #607 ("Non strict build causes "Missing artifact"") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/60716:02
gitlab-br-botbuildstream: merge request (juerg/rebuild->master: element.py: Fix cache check in non-strict mode) #822 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/82216:02
*** tiagogomes_whostolemyidentity has quit IRC16:05
*** tiagogomes has joined #buildstream16:07
juergbics-shadow: would it be possible for you to upload 1.2.2 to PyPI?16:10
cs-shadowjuergbi: sure, i'll do it in just a few minutes16:12
juergbithanks16:12
bochechaha! I wanted to update the Fedora package, but can't… because it downloads from PyPI :P16:13
*** lachlan has quit IRC16:13
bochechacs-shadow: can you ping me when you've managed to find the time, so I proceed with the package? :)16:13
*** finn has quit IRC16:17
cs-shadowbochecha: sure, i'll ping you in a bit16:18
*** finn has joined #buildstream16:18
bochechathanks16:18
gitlab-br-botbuildstream: merge request (mac_fixes->master: WIP: Implement compatibility fixes for MacOSX and WSL Blocks #411 and #412") #726 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/72616:22
gitlab-br-botbuildstream: merge request (richardmaw/push-failed-build-regression->master: tests: Add regression test for pushing failed builds) #824 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/82416:22
*** tiagogomes has quit IRC16:33
*** tiagogomes has joined #buildstream16:34
gitlab-br-botbuildstream: issue #595 ("BUG: Missing Artifact when checking out with --no-strict") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/59516:36
cs-shadowbochecha: juergbi: https://pypi.org/project/BuildStream/ is now updated16:38
*** lachlan has joined #buildstream16:38
*** tiagogomes has quit IRC16:38
gitlab-br-botbuildstream: merge request (jonathan/source-mirror-project-refs->master: tests: Add regression test for mirroring with project.refs) #823 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/82316:40
bochechajuergbi: I wonder though, how did the CI actually pass on Tristan's cherry-pick, since it couldn't work?16:41
bochechaI guess nothing tests frontend/_app.py?16:42
juergbibochecha: it is tested, the issue is that the CI image used includes blessings16:44
juergbior at least that's what I suspect16:45
cs-shadowjuergbi: that's correct. It's kind of a chicken-and-egg problem with dependencies. We wanted to them to be pre-installed in the image so that we don't waste time on installing them during tests. But this method is bound to cause problems anytime we wish to change the dependencies16:48
bochechajuergbi: ah, right16:49
juergbiyes, tricky to handle16:49
bochechain a previous project, what we did is that the deps were pre-installed in the image16:51
bochechabut when building the image, we'd clone the repo to find the deps to install16:51
bochechathis way, as long as the image was regularly updated, it had a relatively up-to-date list of dependencies16:52
*** lachlan has quit IRC16:52
cs-shadowbochecha: that's exactly what we do but the issue is that if you clone the repo, you will never get the changes that are in-flight, which is why our CI didn't catch this because the images got rid of blessings only after they were merged in this repo16:52
bochechacs-shadow: doh, obviously /o\16:53
* bochecha needs a bit more sleep16:53
cs-shadowthe exact same problem also happens if we want to add a new dep :)16:53
* cs-shadow isn't aware of a "clean" solution for this16:54
juergbisave deps list in CI image. in CI job check whether deps match. if they don't, clear out dependencies from base image and install them from the new list?16:57
juergbidoesn't sound very nice, though16:57
gitlab-br-botbuildstream: merge request (jmac/stop-caching-vdirs->master: WIP: Stop caching virtual directories if get_directory is used.) #818 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/81817:00
gitlab-br-botbuildstream: merge request (jmac/stop-caching-vdirs->master: Stop caching virtual directories if get_directory is used.) #818 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/81817:01
cs-shadowjuergbi: yeah, something like that could work but still is hairy. For example, if we just have one teststuite image, then it will either break on master or on the PR updating the deps. Maybe we can enforce that each dependency update has to come with an accompanying PR to docker-images? Would that be acceptable?17:01
gitlab-br-botbuildstream: merge request (jmac/stop-caching-vdirs->master: Stop caching virtual directories if get_directory is used.) #818 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/81817:02
gitlab-br-botbuildstream: issue #674 ("utils.safe_copy() fails to copy *to* a location where leading directories do not exist") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/67417:03
gitlab-br-botbuildstream: merge request (jonathan/source-mirror-project-refs->master: tests: Add regression test for mirroring with project.refs) #823 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/82317:10
gitlab-br-botbuildstream: merge request (jmac/stop-caching-vdirs->master: Stop caching virtual directories if get_directory is used.) #818 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/81817:11
juergbics-shadow: as that's not very frequent, it might be acceptable17:12
jmac#674 is interesting. I'm trying to write down all the rules for file import at the moment.17:12
cs-shadowjuergbi: okay, i'll try to see if we can implement something like this easily17:14
*** alatiera_ has joined #buildstream17:31
*** raoul has quit IRC17:32
*** lachlan has joined #buildstream18:11
*** toscalix has joined #buildstream18:15
*** lachlan has quit IRC18:22
*** lachlan has joined #buildstream18:54
gitlab-br-botbuildstream: issue #632 ("CAS server: Implement BatchReadBlobs") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/63219:28
*** bochecha has quit IRC19:42
*** lachlan has quit IRC20:00
*** jonathanmaw_ has quit IRC20:09
*** toscalix has quit IRC20:22

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