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

*** xjuan has quit IRC02:14
*** catonano has joined #buildstream02:57
*** catonano has quit IRC03:29
*** catonano has joined #buildstream05:28
*** alatiera_ has joined #buildstream05:57
*** ahmed89 has quit IRC06:07
*** ahmed89 has joined #buildstream06:08
gitlab-br-botbuildstream: merge request (juerg/dummy-sandbox->master: _platform/linux.py: Accept all configs for dummy sandbox) #843 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/84306:27
gitlab-br-botbuildstream: merge request (juerg/cas-batch-1.2->bst-1.2: CAS: Implement BatchUpdateBlobs support) #844 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/84406:31
gitlab-br-botbuildstream: merge request (juerg/sandbox->master: sandbox/_sandboxremote.py: Use helpers to set up cwd and env) #841 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/84106:34
*** ahmed89 has quit IRC07:02
*** ahmed89 has joined #buildstream07:02
*** catonano has quit IRC07:02
*** catonano has joined #buildstream07:07
gitlab-br-botbuildstream: merge request (juerg/sandbox->master: sandbox/_sandboxremote.py: Use helpers to set up cwd and env) #841 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/84107:08
*** toscalix has joined #buildstream07:40
valentindThe gnome wiki page for the buildstream events is locked.08:36
valentindHow can I edit it?08:36
*** jonathanmaw has joined #buildstream08:47
juergbivalentind: I guess you're not in https://wiki.gnome.org/TrustedEditorGroup yet. what's your wiki username?08:49
valentindjuergbi, ValentinDavid08:50
juergbivalentind: added, should work now08:50
valentindjuergbi, thank you08:50
tiagogomesWhy GitLab devs thought it would be better to show next to "Changes" the number of files changed, instead of the number of lines changed09:06
*** abderrahim has quit IRC09:07
*** abderrahim has joined #buildstream09:08
KinnisonIIRC it's the number of diff hunks09:08
Kinnisonno?09:08
tiagogomesThe "7 changed files" here https://gitlab.com/BuildStream/buildstream/merge_requests/836/diffs leads me to believe it is not09:16
Kinnisonboo :(09:16
KinnisonYou are quite correct09:16
*** tristan has joined #buildstream09:16
gitlab-br-botbuildstream: merge request (tpollard/494->master: WIP: Don't pull artifact buildtrees by default) #786 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/78609:20
*** lachlan has joined #buildstream09:28
*** bochecha has joined #buildstream09:30
tpollardis anyone able to run 'test_invalid_cache_quota' from artifactcache/expiry.py locally without it failing?09:44
tiagogomestpollard master?09:45
tpollardI'm running the tests with --addopts --integration, yet afaict the test isn't run in the CI at all09:45
tpollardyep09:45
tiagogomesit works for me09:47
tpollardsorry it is triggered in CI09:47
tpollardmine is claiming that 50% is not a valid cache quota09:47
tpollard'Error instantiating artifact cache: Your system does not have enough available space to support the cache quota specified' with 210G available....09:48
tiagogomestpollard yeah, you will have to free some space on your test machine ¬_¬09:48
tiagogomeshttps://gitlab.com/BuildStream/buildstream/issues/53009:49
tpollardphew, not just me then09:49
*** ChanServ sets mode: +o tristan09:50
tristantpollard, you need an env var09:50
tristantpollard, if I recall, I only get that error when I run a bst invocation which ran in a test to test it out myself09:51
tristanand running ./setup.py test will automatically set the BST_TEST_SUITE env var09:52
tristanOr, maybe I'm thinking of a different check09:52
tristanright09:53
tpollardI can ignore it locally, just wanted to confirm I wasn't needing to go down a rabbit hole (especially as my changes are not in its scope)09:54
tristanCommented on the issue just now09:59
tristantpollard, If I recall correctly, we use some big numbers for the cache expiry tests, however they are just numbers really - no reason why the same tests shouldnt work if we just run them with a very small cache quota10:01
tpollard50 & 200% currently10:02
*** solid_black has joined #buildstream10:03
tristanAhhhh, it's testing 50% and 200%10:03
tpollardand pony :D10:03
tristanI see, that is tricky, all of this to ensure that we parse the % properly ?10:03
tiagogomesSo can also create a loopbacked filesystem and point the cache location to there :) But that might be considered over-engineering10:07
Kinnisontristan, juergbi: I was looking at what it'd take to get the Linux platform's sandbox code to cleanly report if bwrap is too old (i.e. not at least 0.1.2) and I am confused by _local_sandbox_available()10:15
Kinnisonit seems redundant to call os.path.exists() around a utils.get_host_tool() and also would it not be of more use to call _site.check_bwrap_version(0, 1, 2) instead?10:15
juergbiKinnison: yes, that should be used there10:16
tristanKinnison, I think the main check is done at installation time10:16
Kinnisontristan: Yeah, but that's a problem for Linux systems which will only be used for remote execution10:16
Kinnisontristan: I have a use-case where a Linux system doesn't have bwrap or FUSE, but can contact a RE service10:17
* Kinnison was hoping to prepare an MR which removed the install-time check for bwrap, but only if there's a good runtime check which gives the user useful feedback10:17
tristanRight, so all of that will become optional10:17
juergbiyes, we most likely need to improve the user feedback on the runtime check10:17
juergbiproviding details why the local sandbox is not available10:18
juergbiotherwise it will get confusing for the common case of local builds10:18
KinnisonPerhaps SandboxDummy should be constructed with a reason why it was selected10:18
KinnisonThen if it tries to .run() it'd have a good message for the exception10:19
juergbicould be an option10:19
tristantiagogomes, I think a fuse mount would be good for those tests really; it's hard to test without a controlled, sized volume10:19
tristantiagogomes, And really, monkey patching system calls to work around that and "fake it" is error prone anyway10:19
* tiagogomes nods10:20
tristanI would steer away from a loopback cause I wouldnt want to require root for running those tests (and we require fuse anyway)10:20
tiagogomesmount on fedora has the setuid bit, but I guess that's not the same for other distros10:21
juergbitiagogomes: that's common but that doesn't allow loop mount, afaik10:22
gitlab-br-botbuildstream: merge request (willsalmon/outOfSourecBuild->master: Out of source builds) #776 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/77610:22
juergbi(setuid mount doesn't allow arbitrary mounts)10:22
Kinnisonsetuid mount is for entries in fstab which have the 'user' option listed10:22
Kinnisonfusermount exists explicitly to circumvent this for fuse filesystems10:23
tiagogomesaah "mount: only root can use "--options" option"10:24
tristanAnd this is why we use `mkfs -d` when generating system images :)10:24
gitlab-br-botbuildstream: merge request (jonathan/pickle-yaml->master: WIP: Add a cache of parsed and provenanced yaml) #787 changed state ("closed"): https://gitlab.com/BuildStream/buildstream/merge_requests/78710:33
*** WSalmon_ has joined #buildstream10:38
*** WSalmon has quit IRC10:39
tristanjuergbi, So mr !844 does the client side of batch blobs correct ?10:47
juergbitristan: that's both client and server side, but for uploads / artifact push10:48
juergbionly recently implemented in master10:48
tristanjuergbi, I'm curious why it modifies _artifactcache/casserver.py... oh you beat me to it10:48
tristanI see10:48
tristanjuergbi, Did we merge the client side for pull ?10:48
juergbibatch download support is already in both master and 1.210:48
juergbi1.2.1/1.2.2 has the server side but not the client side yet10:49
tristanOk, that's what I wanted to know :)10:49
tristanNice10:49
juergbiabderrahim did some testing and was seeing large speedups10:49
juergbifdo cache server already is on 1.2.1, iirc10:49
tristangreat, I will try it :)10:50
tpollardI've not taken metrics but my scenario seems faster too10:50
juergbi<abderrahim> 5 min vs 50+min10:51
juergbi<abderrahim> (for bst build with everything in the cache)10:51
juergbi<abderrahim> the above is for the flatpak runtimes, for the full gnome I get 13min vs 1h50m10:51
tristanSweet10:51
coldtomvalentind: upstreaming the fdo strip commands fails CI because the tests expect the debug symbols to be included, but the new commands remove them entirely10:52
valentindWhy does it remove them?10:52
valentindAre you sure it is just not a different path?10:52
gitlab-br-botbuildstream: merge request (tpollard/494->master: WIP: Don't pull artifact buildtrees by default) #786 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/78610:53
coldtomvalentind: looks like it should be the right directory :/11:06
valentindcoldtom, I am running it locally to understand what is happening.11:07
jjardonHi, now that buildstream is in https://pypi.org/project/BuildStream/, do you plan to upload bst-external there as well?11:08
jjardonjuergbi: fdo is updated, correct11:09
lachlantristan: I have updated !836 with my thoughts - will rework asap11:11
*** lachlan has quit IRC11:14
tristanjjardon, I hadn't considered it really, but I don't see an issue with that; unlike distro packaging, the expectations for API stability are different on PyPI11:15
tristanOne can always install the exact version they want from PyPI, too11:16
jjardontristan: BTW, there were some discussion about this; what is your vision about bst-external? place for plugins that have to mature to be included in buildstream repo or actually they will always be there? People seems to think is the former11:25
tiagogomesI would prefer the latter even if complicates a bit using buildstream11:26
tiagogomesI don't like the package name though11:26
jjardonOK, wherever is It would be good It's documented somewhere11:26
tristanjjardon, The former (almost), maybe not well named for communicating that, I might have preferred bst-experimental11:34
tristanjjardon, However, when I say (almost), what I mean is that it is a place for plugins to mature, not necessarily to land in BuildStream11:34
tristanjjardon, I.e. I would expect that more fringe plugins will mature and graduate to a more stable repo11:35
tristanSome of those plugins will probably land in core BuildStream, some of them might land elsewhere in more use-case specific repos11:36
tristanShould probably be documented in the bst-external repo's README11:36
juergbistaging might be a suitable name11:37
tristanjjardon, I should note too that it is also a place for us to get our plugin story straight and improve on that :D11:38
valentindcoldtom, "sh: read: line 34: illegal option -d"11:45
valentindcoldtom, I suppose alpine uses busybox11:45
tristanvalentind, Yes, that is true11:47
tristansounds familiar11:47
valentindread command is not documented in busybox.11:51
tristanvalentind, frankly, we might end up removing the default strip commands from BuildStream proper some day11:55
*** ahmed89 has quit IRC11:56
tristanIt would be a breaking change, but it's very OS/Platform specific, as such doesnt really belong in the defaults11:56
valentindtristan, I agree.11:56
valentindThough we should keep some recipes somewhere.11:56
valentindIt is difficult to make it correct.11:56
tristanyes11:56
coldtomit could be kept as an include somewhere11:56
tristanmaybe it can be a non-breaking change if we had some kind of platform specific defaults, not sure11:57
valentindtristan, for example in freedesktop sdk we use debugedit to extract necessary source files.11:57
valentindAnd also change the path.11:57
valentindAlso some people might want to use build id for the path of debug.11:57
*** catonano has quit IRC11:59
gitlab-br-botbuildstream: merge request (willsalmon/outOfSourecBuild->master: Out of source builds) #776 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/77612:06
*** catonano has joined #buildstream12:07
gitlab-br-botbuildstream: merge request (tristan/fix-status-messages->master: fix status messages) #845 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/84512:15
gitlab-br-botbuildstream: merge request (tristan/fix-status-messages-1.2->bst-1.2: fix status messages (1.2)) #846 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/84612:16
* tristan found the source of the obnoxious status messages which came back to haunt us12:19
tristangit cat-file etc12:19
*** mohan43u has quit IRC12:20
tristanjuergbi, llvm6 = 10 min 44 seconds12:38
tristanAs opposed to 1.5 hours :D12:38
juergbi:)12:39
Kinnisonjuergbi, tristan: Following on from our chat this morning, I have a WIP branch at https://gitlab.com/BuildStream/buildstream/tree/danielsilverstone-ct/bwrap-check-runtime-only (not filed as an MR yet, tests underway)12:42
juergbitristan: do you remember how long this took with OSTree?12:42
gitlab-br-botbuildstream: merge request (willsalmon/outOfSourecBuild->master: Out of source builds) #776 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/77612:42
tristanjuergbi, I don't, but I suspect we are now faster12:43
tristanjuergbi, I also recall there was an issue with freedesktop-sdk with many concurrent pulls, something to do with too many open connections12:43
tristanThat is probably much improved with these changes12:44
tristanWe only really optimized push, because ostree-push was severely non performant12:44
juergbiyes, we don't actually do any parallel requests for single pull job, so it should be light on connections12:44
Kinnisonjuergbi, tristan: If either of you peek at that branch and have ideas for good ways to test the changes, I'd appreciate some hints, I'm a bit lost in the test suite currently12:45
juergbiKinnison: branch makes sense at first glance. I guess testing is somewhat tricky as this checks host requirements12:46
Kinnisonjuergbi: yeah, I've been testing locally by temporarily renaming the bwrap binary, or replacing it with a shell script claiming different versions12:47
juergbiyes, manual testing like that might be sufficient for this, imo12:48
juergbiKinnison: one initial comment, I would still keep _local_sandbox_available() around (could also be a variables instead of a function) to avoid code duplication12:49
tristanKinnison, juergbi, One approach is to have a separate image for testing a bwrap-less environment12:49
juergbiKinnison: with https://gitlab.com/BuildStream/buildstream/merge_requests/843 we'd otherwise have three times fuse+bwrap check12:49
Kinnisonjuergbi: I was thinking at some point that the logic might want to be opened up a little bit (e.g. for fuse/no-bwrap -> SandboxUnix)12:50
tristanThen we mark tests to skip if bwrap exists12:50
Kinnisontristan: Interesting idea, so that'd be another docker container and branch on the .gitlab-ci.yml ?12:51
tristanKinnison, exactly12:51
Kinnisonjuergbi: Hmm I see, yes that might be a problem12:51
Kinnisontristan: that'd be well beyond me at the moment to set up I fear :(12:51
tristanWell, it's the way things are intended to work - test things which are testable in the environment12:52
tristanAnd skip tests which would not pass in the test environment12:52
tristanWe have tests/testutils/site.py where we declare HAVE_FOO for a bunch of things12:52
juergbiit should actually not be too bad with regards to CI time given that we'd skip all integration tests12:52
KinnisonI meant the docker stuff, I could probably manage a test of some kind :-)12:52
tristanThat is in buildstream-docker-images, which Chandan maintains12:53
tristanSo yeah, we would need to spin up a new image for that first12:53
juergbiideally, we'd even test on WSL but that's probably not straight forward to set up12:53
KinnisonDon't we have an image for testing the SandboxUnix stuff?12:53
KinnisonOr does that still have bwrap on, just with the backend forced?12:54
tristanI don't know, honestly I'm not extremely picky about this case, but setting up that image seems like it will be worthwhile for more tests than just this one12:54
juergbiKinnison: it uses the same fedora 27 image with bwrap12:54
Kinnisonoh :/12:54
tristanKinnison, No, we unfortunately use the same image and force the unix backend :(12:54
juergbibut if we create a bwrap-less image, we could use that for unix as well12:55
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/80612:55
Kinnisonjuergbi: aye, though it'd still need forcing because otherwise it'll pick the linux platform12:55
Kinnisonand the linux platform doesn't do unix sandbox12:55
tristanYeah, I'd like it if we were testing the unix backend on, say... a bsd machine12:55
juergbiyes, that would be great12:55
tristanIt's supposed to be "fallback", we don't really know that it works on non-linux or not12:55
persiaI remember someone trying to get it working on BSD: did that effort succeed?12:56
tristanpersia, No follow up really, someone provided a first iteration patch12:56
tristanIt should be very doable too12:56
gitlab-br-botbuildstream: merge request (willsalmon/outOfSourecBuild->master: Out of source builds) #776 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/77613:00
*** catonano has quit IRC13:04
*** catonano has joined #buildstream13:05
tpollardtristan: would it be possible for you to give a once over on this? There's some comments left dangling https://gitlab.com/BuildStream/buildstream/merge_requests/786/13:05
*** lachlan has joined #buildstream13:11
tristantpollard, w00t ! I will - but I don't think I can do a review today of that13:11
tpollardtristan: no worries, there's just a couple of comments opens on some specific points13:12
tpollardmainly the type of configuration it should be set at13:12
tpollard(not at project.conf :))13:13
tristanyeah I recall that :)13:13
tristanCommented on that :)13:18
gitlab-br-botbuildstream: merge request (tpollard/494->master: WIP: Don't pull artifact buildtrees by default) #786 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/78613:18
gitlab-br-botbuildstream: merge request (tristan/fix-status-messages-1.2->bst-1.2: fix status messages (1.2)) #846 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/84613:19
tpollardtristan: cheers!13:19
*** lachlan has quit IRC13:19
*** lachlan has joined #buildstream13:20
gitlab-br-botbuildstream: merge request (tristan/fix-status-messages->master: fix status messages) #845 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/84513:20
tristanSomeone care to take a look at https://gitlab.com/BuildStream/buildstream/merge_requests/845 ?13:21
tristanIt adds a very *weird* loop construct, but solves the issue of irrelevant status messages getting printed in the UI, as a result of consuming generator items from Source.get_source_fetchers()13:22
tristanAnother thought, is instead of the weird loop, maybe I could subclass `iter` with an object that overrides the __next__ implementation13:27
finnHey - anyone seen this error before?:       File "/home/buildgrid/buildstream/buildstream/_ostree.py", line 66, in ensure13:27
finn        repo.reload_config()13:27
finn    AttributeError: 'Repo' object has no attribute 'reload_config'13:27
*** tristan has quit IRC13:33
finnI'm getting this when running the flatpak-autotools example13:37
finnon master13:39
gitlab-br-botbuildstream: issue #690 ("flatpak-autotools example broken") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/69013:42
gitlab-br-botbuildstream: issue #690 ("flatpak-autotools example broken") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/69013:57
*** tristan has joined #buildstream13:58
*** lachlan has quit IRC14:12
*** lachlan has joined #buildstream14:17
gitlab-br-botbuildstream: merge request (danielsilverstone-ct/bwrap-check-runtime-only->master: WIP: Make bwrap check runtime only) #847 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/84714:27
gitlab-br-botbuildstream: merge request (danielsilverstone-ct/bwrap-check-runtime-only->master: WIP: Make bwrap check runtime only) #847 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/84714:28
tiagogomesSomething that is missing from the documentation: BuildStream for previous Yocto users14:30
tiagogomesWith some pointers for porting14:36
tpollardone of the first questions will be, where is my poky equivalent14:50
tiagogomeshmm, there isn't one, but we can point to freedestop-sdk, gnome-meta and minimal distro projects14:53
jonathanmawtristan: good news, I've managed to replicate your error case in the wild. Now I need to figure out how it's differing from my test cases.14:56
gitlab-br-botbuildstream: merge request (docs_Search_not_working->master: Fixing: Search functionality in the Documentation has stopped working) #848 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/84815:05
gitlab-br-botbuildstream: merge request (docs_Search_not_working->master: Fixing: Search functionality in the Documentation has stopped working) #848 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/84815:08
valentindadds68, Do you know when you will be testing !830 on Freedeesktop SDK infra?15:13
adds68valentind, i'm currently just rebasing the branch now, i will then run the release and open an MR15:13
adds68Probably ~1 hour15:13
valentindOK, great.15:14
gitlab-br-botbuildstream: merge request (tpollard/494->master: WIP: Don't pull artifact buildtrees by default) #786 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/78615:14
adds68valentind, lots of changes since switching to CAS15:14
*** lachlan has quit IRC15:15
gitlab-br-botbuildstream: merge request (tpollard/494->master: WIP: Don't pull artifact buildtrees by default) #786 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/78615:18
*** bochecha has quit IRC15:36
*** lachlan has joined #buildstream15:52
tiagogomeshmm, bitbake has download progress bars15:59
Nexusjuergbi around?15:59
gitlab-br-botbuildstream: merge request (docs_Search_not_working->master: Fixing: Search functionality in the Documentation has stopped working) #848 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/84816:00
gitlab-br-botbuildstream: merge request (lachlan/pickle-yaml-test-list-composite->master: Add yaml cache testing to yaml tests) #836 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/83616:00
*** lachlan has quit IRC16:15
*** bochecha has joined #buildstream16:15
juergbiNexus: yes16:20
Nexusjuergbi: could you have a look at https://gitlab.com/BuildStream/buildstream/merge_requests/848 for me pls?16:21
*** lachlan has joined #buildstream16:23
tpollardwill be good to have search working again :)16:23
Nexus+116:25
Nexushow do i set up a project with a remote artifact cache in pull only mode?16:28
tpollardif you don't add push:true it won't attempt to push16:29
gitlab-br-botbuildstream: merge request (docs_Search_not_working->master: Fixing: Search functionality in the Documentation has stopped working) #848 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/84816:29
tpollardor are you asking about running the artifact server itself?16:29
Nexusyup, that one :)16:29
tpollardhttps://buildstream.gitlab.io/buildstream/install_artifacts.html ?16:31
tpollardjust don't include --enable-push16:31
juergbiNexus: one comment, otherwise looks fine16:31
juergbiNexus: oh, and let's get used to the filename prefix in the commit summaries. i.e., .gitlab-ci.yml:16:32
jonathanmawOf course those tests failed! I go down an entirely different code path for the git source! (╯°□°)╯︵ ┻━┻16:35
tiagogomesI don't use filename prefix, but rather subsystem prefix16:35
Nexusno need to get angry jonathanmaw! ┬──┬︵ſ(°□°ſ)16:35
tiagogomescore, scheduler, artifactcache, ci, docs16:35
*** lachlan has quit IRC16:35
tiagogomesReason being, sometimes a commit spreads across more than one file if you want it to be in a working state16:37
jonathanmawI spent ages on this because I failed to notice an obvious fact! (╯°Д°)╯︵/(.□ . \)16:37
jonathanmaw(ranting over, just wanted an excuse to use that emoticon)16:37
Nexuslol16:38
tiagogomesAlso the recommended line length for the title in the commit message is too short to write "buildstream/_artifactcache/cascache:" for example16:38
Nexusノ┬─┬ノ ︵ ( \o°o)\16:38
jonathanmawlol16: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:39
gitlab-br-botbuildstream: merge request (docs_Search_not_working->master: Fixing: Search functionality in the Documentation has stopped working) #848 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/84816:40
*** toscalix has quit IRC16:42
*** lachlan has joined #buildstream16:42
*** phildawson has quit IRC16:42
gitlab-br-botbuildstream: issue #691 ("BuildStream does not automatically fetch a junction within a junction / displays an inaccurate helper") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/69116:45
*** solid_black has quit IRC16:50
*** bochecha has quit IRC16:50
*** bochecha has joined #buildstream16:51
*** bochecha has quit IRC16:55
*** bochecha has joined #buildstream16:55
Nexusjuergbi: Now using 1.7.9, have confirmed it works16:55
Nexussetting it to merge once pipeline succeeds16:55
juergbiok, ta16:56
Nexussearch will work again \o/16:56
*** jonathanmaw has quit IRC17:04
* laurence is seeing a different coloured fox favicon in buildstream gitlab tabs17:10
* tiagogomes takes credit on that one17:10
tiagogomesBut it is a beaver, not a fox17:11
tiagogomesAh wait, I didn't do anything on the buildstream gitlab, just the website17:12
laurencetiagogomes, nice17:12
laurenceit's odd because i'm only seeing it on certain tabs...17:12
gitlab-br-botbuildstream: issue #681 ("Search functionality in the Documentation has stopped working") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/68117:14
gitlab-br-botbuildstream: merge request (docs_Search_not_working->master: Fixing: Search functionality in the Documentation has stopped working) #848 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/84817:14
*** benbrown_ has quit IRC17:22
*** Nexus has quit IRC17:22
*** aiden has quit IRC17:23
*** jmac has quit IRC17:23
*** paulsher1ood has quit IRC17:23
*** milloni has quit IRC17:23
*** coldtom has quit IRC17:23
*** adds68 has quit IRC17:23
*** catonano has quit IRC17:23
*** johnward has quit IRC17:24
*** jennis has quit IRC17:24
*** mablanch has quit IRC17:24
*** valentind has quit IRC17:24
*** johanneshilling has quit IRC17:24
*** bethw has quit IRC17:24
*** laurence has quit IRC17:24
*** Nexus has joined #buildstream17:24
*** jennis has joined #buildstream17:24
*** laurence has joined #buildstream17:24
*** benbrown has joined #buildstream17:24
*** mablanch has joined #buildstream17:24
*** johanneshilling has joined #buildstream17:24
*** coldtom has joined #buildstream17:24
*** adds68 has joined #buildstream17:24
*** bethw has joined #buildstream17:24
*** johnward has joined #buildstream17:25
*** paulsherwood has joined #buildstream17:25
*** valentind has joined #buildstream17:25
*** jmac has joined #buildstream17:25
*** aiden has joined #buildstream17:28
*** milloni has joined #buildstream17:28
gitlab-br-botbuildstream: issue #692 ("SSL Root cettificate error when configuration a cache") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/69217:39
*** lachlan has quit IRC17:42
*** solid_black has joined #buildstream17:45
*** raoul has quit IRC17:49
*** johanneshilling has quit IRC17:58
*** jennis has quit IRC17:58
*** adds68 has quit IRC17:58
*** coldtom has quit IRC17:58
*** mablanch has quit IRC18:15
*** milloni has quit IRC18:15
*** bethw has quit IRC18:15
*** johnward has quit IRC18:15
*** laurence has quit IRC18:15
*** valentind has quit IRC18:15
*** aiden has quit IRC18:15
*** aiden has joined #buildstream18:18
*** laurence has joined #buildstream18:19
*** valentind has joined #buildstream18:20
*** bethw has joined #buildstream18:21
*** johnward has joined #buildstream18:21
*** milloni has joined #buildstream18:22
*** mablanch has joined #buildstream18:23
*** benbrown has quit IRC18:24
*** Nexus has quit IRC18:24
*** jmac has quit IRC18:24
*** paulsherwood has quit IRC18:24
*** benbrown has joined #buildstream18:29
*** coldtom has joined #buildstream18:34
*** toscalix has joined #buildstream18:38
*** toscalix has quit IRC18:39
*** toscalix has joined #buildstream18:54
*** toscalix has quit IRC18:54
*** catonano has joined #buildstream19:03
*** tristan has quit IRC19:41
*** adds68 has joined #buildstream20:05
gitlab-br-botbuildstream: merge request (valentindavid/rmtree_oserror->master: Catch correct exception from shutil.rmtree) #849 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/84921:25
*** xjuan has joined #buildstream21:41

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