*** Mia7584 has joined #buildstream | 00:57 | |
*** Mia7584 has quit IRC | 00:59 | |
*** Clara1293 has joined #buildstream | 01:30 | |
*** Clara1293 has quit IRC | 01:31 | |
*** rdale_ct has quit IRC | 02:31 | |
*** mohan43u has quit IRC | 05:35 | |
*** mohan43u has joined #buildstream | 05:39 | |
*** mohan43u has quit IRC | 05:45 | |
*** mohan43u has joined #buildstream | 05:49 | |
*** tristan has quit IRC | 05:50 | |
*** tristan has joined #buildstream | 06:03 | |
*** ChanServ sets mode: +o tristan | 06:03 | |
gitlab-br-bot | tristanvb approved MR !1888 (juerg/sandbox->master: Switch preferred sandbox from bwrap to buildbox-run) on buildstream https://gitlab.com/BuildStream/buildstream/-/merge_requests/1888 | 06:10 |
---|---|---|
gitlab-br-bot | marge-bot123 closed issue #719 (Support BuildBox for local builds) on buildstream https://gitlab.com/BuildStream/buildstream/-/issues/719 | 07:02 |
gitlab-br-bot | marge-bot123 merged MR !1888 (juerg/sandbox->master: Switch preferred sandbox from bwrap to buildbox-run) on buildstream https://gitlab.com/BuildStream/buildstream/-/merge_requests/1888 | 07:02 |
tristan | gah, something happened in bst-plugins-experimental which ended up using the removed BST_FORMAT_VERSION :-S | 07:06 |
tristan | ah, ok no worries... I thought for a second I would have to play "redirect the reference to the other repository" for two repos now | 07:09 |
tristan | Do we have a lot less runners in bst-plugins-experimental ? or is there an issue: https://gitlab.com/BuildStream/bst-plugins-experimental/pipelines/ ? | 07:18 |
traveltissues | looks like it might be stuck | 07:21 |
*** mohan43u has quit IRC | 07:22 | |
WSalmon | tristan, AFAIK the runners are shared accross the group so if a lot of ci is happening in one project it can effect another availability of runners in another | 07:23 |
tristan | Right now we have one running in buildstream and one running in bst-plugins-experimental | 07:24 |
tristan | So I think we're a little short handed, or something is stuck | 07:24 |
*** jude has joined #buildstream | 07:25 | |
*** mohan43u has joined #buildstream | 07:25 | |
tristan | Hmmm, my other pipeline had no trouble starting in buildstream, bst-plugins-experimental still on standby | 07:27 |
juergbi | tristan: the permanent runners have been disabled because of the docker cleanup issue. however, I think it's better to re-enable them, as we can temporarily run the cleanup manually | 07:27 |
juergbi | done | 07:27 |
tristan | And tada ! the pipeline runs :) | 07:28 |
tristan | Ok so lets try to merge this BST_MIN_VERSION plugin origins overhaul once this thing finishes | 07:28 |
tristan | juergbi, we have tagging to do on bst-plugins-experimental then, are we waiting for anything else for that ? | 07:29 |
*** benschubert has joined #buildstream | 07:29 | |
tristan | and as I understand, there is also another metadata you mentioned ? | 07:29 |
tristan | setup() in setup.py needs a version bump | 07:30 |
tristan | anything else ? | 07:30 |
juergbi | I'm not aware of any pending MRs that are crucial before a snapshot | 07:30 |
juergbi | tristan: setup.py and doc/source/conf.py | 07:30 |
tristan | For BuildStream snapshots, I would like to squeeze in something else | 07:30 |
juergbi | do we also need a new snapshot on the BuildStream side? | 07:31 |
tristan | I have a branch in the works which addresses #1291, as that is PluginOrigin related (and also enhances errors/warnings to include provenance which has been missing thus far) | 07:31 |
tristan | juergbi, actually, I'm not calling for one honestly | 07:32 |
tristan | I thought you were this week, but maybe that already happened ;-) | 07:32 |
juergbi | 1.93.2 already happened :) | 07:32 |
tristan | ok ok :) | 07:32 |
juergbi | or do the min-format changes in bst-plugins-experimental break with 1.93.2? in that case, we might need another one | 07:34 |
*** gitlab-br-bot has quit IRC | 07:34 | |
tristan | Oh interesting game of whackamole, rebasing the bst-plugins-experimental branch causes the commit sha to be GC'ed and fails on buildstream side | 07:35 |
juergbi | yes, that can happen | 07:36 |
juergbi | the only breakage I see is due to tests/sources/git_tag/lfs/project.conf | 07:36 |
juergbi | dropping the plugin format version from project.conf will break on 1.93.2 I suppose | 07:36 |
tristan | Right it will | 07:37 |
tristan | indeed | 07:37 |
tristan | Oh damn | 07:39 |
tristan | I expect it's pipeline will fail | 07:39 |
tristan | if only we landed this before that new project.conf snuck in :-S | 07:39 |
juergbi | tristan: I actually see other project.conf files in tests with the same issue | 07:39 |
juergbi | but your branch doesn't change them | 07:40 |
juergbi | wondering what's up with those | 07:40 |
tristan | indeed yeah | 07:40 |
tristan | maybe those tests arent being run in CI ? | 07:40 |
juergbi | maybe, I don't know | 07:41 |
* tristan will first update those project.conf's in the branch regardless | 07:41 | |
juergbi | theoretically, we could generate project.conf programmatically and be smart about what version we're running against | 07:41 |
juergbi | but probably not worth it | 07:41 |
tristan | And I guess we have a situation where only brute force will work | 07:41 |
tristan | Well yeah, brute force or bending over backwards | 07:42 |
tristan | Ok I've updated the branch (_and_ the tox.ini reference in the BuildStream side branch) | 07:47 |
*** seanborg_ has joined #buildstream | 07:48 | |
tristan | I take it that passing tests for https://gitlab.com/BuildStream/buildstream/-/merge_requests/1885 are an indication that the bst-plugins-experimental branch works | 07:48 |
*** benschubert has quit IRC | 07:48 | |
*** dbuch[m] has quit IRC | 07:48 | |
*** walterve[m][m] has quit IRC | 07:48 | |
*** jward has quit IRC | 07:48 | |
*** benschubert has joined #buildstream | 07:48 | |
*** jward has joined #buildstream | 07:49 | |
tristan | Wait a sec, where does bst-plugins-experimental get it's BuildStream from ? | 07:49 |
tristan | Aha, there is "master" and a tag in bst-plugins-experimental | 07:50 |
tristan | in tox.init | 07:50 |
tristan | ini | 07:50 |
WSalmon | tristan, https://gitlab.com/BuildStream/bst-plugins-experimental/-/blob/master/tox.ini#L20 | 07:51 |
tristan | So I suppose it would run the tag in regular CI and against master nightly or such | 07:51 |
WSalmon | https://gitlab.com/BuildStream/bst-plugins-experimental/-/blob/master/tox.ini#L46 | 07:51 |
WSalmon | https://gitlab.com/BuildStream/bst-plugins-experimental/-/blob/master/tox.ini#L5 | 07:52 |
*** walterve[m][m] has joined #buildstream | 07:52 | |
WSalmon | if you just run `tox --intergration` | 07:52 |
WSalmon | then it will run master and fixed for every version of python you have installed | 07:53 |
juergbi | tristan: it runs both in regular MR pipelines but master is allowed to fail | 07:53 |
WSalmon | the CI has stages that run a verity of fixed, master and versions of python | 07:53 |
tristan | Ah allowed to fail also makes sense | 07:53 |
tristan | Alright so, once this pipeline passes again on master, I'll brute force bst-plugins-experimental and then roll a tag on bst-plugins-experimental (with updated metadata) | 07:55 |
tristan | Then we'll probably want another snapshot, because we'll want to update bst-plugins-experimental CI to reference a new tag of BuildStream for all to be fine across the rainbow | 07:55 |
*** phildawson has joined #buildstream | 08:07 | |
*** dbuch[m] has joined #buildstream | 08:15 | |
tristan | Alright, bst-plugins-experimental is tagged and metadata adjusted to 1.93.2 | 08:19 |
tristan | And !1885 is adjusted to refer to the branch and given to marge | 08:20 |
*** tpollard has joined #buildstream | 08:20 | |
tristan | After the land, we'll need to adjust bst-plugins-experimental tox.ini to get the new buildstream | 08:20 |
*** rdale has joined #buildstream | 08:22 | |
*** santi has joined #buildstream | 08:36 | |
*** seanborg_ has quit IRC | 08:50 | |
*** seanborg_ has joined #buildstream | 08:50 | |
traveltissues | bst-plugins-experimental@master is intended to be broken atm then? | 08:52 |
tristan | juergbi, when you do a buildstream snapshot, do you just push a tag and thats it ? | 08:52 |
tristan | traveltissues, for another 20min or so yes | 08:52 |
traveltissues | ok | 08:52 |
juergbi | tristan: first add a new heading to NEWS but then yes | 08:53 |
tristan | Ok | 08:53 |
juergbi | we haven't done any official announcements of those snapshots, afair | 08:53 |
tristan | Gah, that means the NEWS has to go through CI | 08:54 |
juergbi | oh, that reminds me, I forgot to mention the sandbox change in NEWS | 08:54 |
juergbi | tristan: there is this: https://docs.gitlab.com/ee/user/project/push_options.html#push-options-for-gitlab-cicd | 08:55 |
tristan | Did we figure out how to merge a patch with [no-ci] ? | 08:55 |
juergbi | I haven't tried it out yet, though, forgot it last time | 08:55 |
tristan | I tried it and was able to have a branch not run CI, but I was not able to merge it | 08:55 |
tristan | The CI correctly "doesn't run" and that was it | 08:55 |
tristan | maybe something specific with that branch though | 08:55 |
juergbi | it makes sense that gitlab doesn't simply allow skipping the CI requirement with that flag | 08:56 |
juergbi | however, with sufficient privilege it would make sense that it could be overridden in the MR | 08:56 |
juergbi | theoretically, the setting could be changed temporarily but that feels wrong | 08:56 |
tristan | yeah right now we're in lock down, even force push from command line is refused | 08:57 |
tristan | traveltissues, this conversation mostly means: bst-plugins-experimental will remain broken for say... another 40min hehe | 08:58 |
tristan | time it takes to run yet-another-ci-for-NEWS-update | 08:58 |
traveltissues | np | 09:00 |
tristan | juergbi, I missed my news entry too... so what shall I say about sandboxes... "buildbox is now the default sandbox implementation" ? | 09:08 |
juergbi | tristan: maybe "buildbox-run is now the default sandbox backend on all platforms" | 09:09 |
tristan | https://gitlab.com/BuildStream/buildstream/-/merge_requests/1891 | 09:12 |
juergbi | ta | 09:13 |
*** tpollard has quit IRC | 09:19 | |
*** tpollard has joined #buildstream | 09:19 | |
*** lachlan has joined #buildstream | 09:20 | |
*** phildawson_ has joined #buildstream | 09:42 | |
*** phildawson has quit IRC | 09:42 | |
*** phoenix has joined #buildstream | 09:48 | |
*** lachlan has quit IRC | 09:55 | |
*** phoenix has quit IRC | 09:58 | |
*** CTtpollard has joined #buildstream | 10:10 | |
*** tpollard has quit IRC | 10:10 | |
*** coldtom has quit IRC | 10:14 | |
tristan | traveltissues, it should be fixed now | 10:17 |
tristan | is there anything I need to change in bst-plugins-experimental other than the tox.ini to refer to which tag of BuildStream to use ? | 10:17 |
*** coldtom has joined #buildstream | 10:21 | |
traveltissues | i think that's all tristan | 10:35 |
traveltissues | thanks | 10:35 |
*** CTtpollard is now known as tpollard | 10:35 | |
traveltissues | https://gitlab.com/BuildStream/bst-plugins-experimental/-/commit/d54e71daefc8434fe4967fe2687071f5d6cef123 | 10:36 |
tristan | Hmmm, what's up with source consistency, we threw it out in favor if is_cached() ? | 10:46 |
* tristan kind of liked that API | 10:47 | |
tristan | is there some ML discussion I can read up about that ? | 10:47 |
tristan | Also what replaces it ? How do we determine the difference between "It's locally cached" and "We wouldnt even know what to download until you ran bst track" ? | 10:48 |
*** lachlan has joined #buildstream | 10:57 | |
tristan | Also where are the message APIs on Context() ? | 10:58 |
tristan | messenger, got that | 10:58 |
tristan | never got as far as getting some convenience global message APIs though :-S | 10:59 |
*** lachlan has quit IRC | 11:02 | |
juergbi | tristan: !1739 | 11:31 |
juergbi | sometimes we only need to know whether the source is reolved, not whether it's locally cached. and determining the latter can take a bit of tim | 11:32 |
juergbi | *time | 11:32 |
tristan | So is_resolved() is added too... | 11:33 |
tristan | juergbi, makes sense, I did like having a single method for this but, I guess there is a real gain to changing this :) | 11:34 |
* tristan posts !1892 ... and wonders where our gitlab bot has gone | 11:35 | |
* tristan thinks the policing of loaded plugins could be more improved | 11:36 | |
tristan | I was adding a plugin to test deprecation warnings, and it's unclear how long it would take me to figure out what methods I'm really required to implement | 11:37 |
tristan | maybe it would be good to do some checks at plugin loading time instead of just raising ImplError "whenever the vfunc gets used" | 11:37 |
WSalmon | tristan, can i use the latest tag of bst and bst-plugins-experimental together now? | 11:38 |
tristan | WSalmon, yes, but if you use the latest tag of bst-plugins-experimental, the tox in bst-plugins-experimental will break | 11:40 |
tristan | i.e. running tox in bst-plugins-experimental would break, but everything else (latest both tags) works together | 11:40 |
WSalmon | ok, im not worried about testing but using them on projects | 11:41 |
WSalmon | thanks tristan | 11:41 |
tristan | WSalmon, yeah then you don't need to care | 11:42 |
WSalmon | :) | 11:44 |
tristan | hmmmm, broken pipeline in bst-plugins-experimental... | 11:53 |
tristan | The FUSE stager child process unexpectedly died with exit code 1 | 11:53 |
tristan | looks unrelated :-S | 11:54 |
tristan | juergbi, these new bst-plugins-experimental failures seem related to your buildbox-run switcheroo | 11:55 |
tristan | maybe we need to update .gitlab-ci or tox.ini to install buildbox correctly ? | 11:55 |
* tristan switches locations | 11:55 | |
traveltissues | yes, i'm hitting that now | 11:58 |
*** tristan has quit IRC | 11:58 | |
traveltissues | Error executing command: std::runtime_error exception thrown at [buildboxcommon_client.cpp:723] | 11:58 |
*** lachlan has joined #buildstream | 11:58 | |
*** lachlan has quit IRC | 12:02 | |
juergbi | ah, yes, I had to fix an issue with the debian image | 12:04 |
juergbi | need to bump the docker image in bst-plugins-experimental to the same as in buildstream master | 12:04 |
traveltissues | thanks | 12:05 |
traveltissues | can i get a review/merge please: https://gitlab.com/BuildStream/bst-plugins-experimental/-/merge_requests/102 | 12:15 |
traveltissues | WSalmon: i don't have permissions for the merge button | 12:27 |
WSalmon | me nether | 12:27 |
traveltissues | juergbi? | 12:27 |
* juergbi clicks | 12:28 | |
traveltissues | thanks | 12:28 |
juergbi | should probably fix those permissions | 12:28 |
WSalmon | juergbi, could you add traveltissues and myself to bst-external and bst-plugins-experimental, we have had things merged to both and are conservitave merges | 12:28 |
juergbi | yes, I see that currently only maintainers have the permission to merge. I think in buildstream we have an explicit list | 12:29 |
WSalmon | i belive that is the case | 12:29 |
WSalmon | any one can be a dev and then people are explicitly added after they have had work merged was how it used to work | 12:30 |
WSalmon | i presume we can extend that to the plugin repos? | 12:30 |
WSalmon | unless you want to do something more sweaping, that might want a ML? | 12:30 |
juergbi | yes, I think the policy should be the same. I've added you two to the list | 12:31 |
WSalmon | ta | 12:32 |
WSalmon | for both? | 12:32 |
juergbi | ah, no, only experimental. let me check bst-external | 12:33 |
WSalmon | has coldtom had stuff merged to bst-plugins-experimental? | 12:33 |
WSalmon | he can already merge to bst-external i belive | 12:34 |
traveltissues | ty | 12:35 |
WSalmon | oh no he cant, can juergbi add coldtom too | 12:35 |
WSalmon | he has done lots of maintenance there | 12:35 |
juergbi | yes, makes sense | 12:35 |
WSalmon | thanks juergbi | 12:35 |
*** lachlan has joined #buildstream | 13:02 | |
*** Nevaeh2639 has joined #buildstream | 13:09 | |
*** Nevaeh2639 has quit IRC | 13:11 | |
traveltissues | seems that bst-plugins-experimental is falling over sometimes because the cache fills up | 13:17 |
traveltissues | does the cache get cleared immediately following a job? | 13:20 |
WSalmon | i dont think so, we could key it off the cache key version maybe | 13:22 |
traveltissues | i think it's the same issue for the failure on your branch WSalmon | 13:22 |
traveltissues | and @master | 13:23 |
traveltissues | https://gitlab.com/BuildStream/bst-plugins-experimental/-/issues/27 | 13:23 |
WSalmon | i yes i accently pused that after it had been merged, need to work out how to get rid of it | 13:24 |
*** phildawson_ has quit IRC | 13:36 | |
*** phildawson has joined #buildstream | 13:45 | |
*** phildawson has quit IRC | 13:48 | |
traveltissues | WSalmon: i'm not sure what you mean by "we could key it off the cache key version maybe" | 13:49 |
traveltissues | do you mean the job id? | 13:49 |
juergbi | traveltissues: there is a cleanup issue which is why the runners were disabled | 13:51 |
juergbi | manual cleanup seems to work, though | 13:51 |
juergbi | maybe I should simply set up a cron job until this is solved properly | 13:51 |
*** narispo has quit IRC | 13:53 | |
WSalmon | traveltissues, you can add a key to the gitlab-cache, usually people use the branch or something like that as the key, but for us there is no point keeping cache after a cache key change so i wondered if we could find a way to do it off that but i think it would need to be manual | 13:53 |
*** narispo has joined #buildstream | 13:53 | |
traveltissues | WSalmon: sure, that makes sense | 13:53 |
traveltissues | juergbi: i think the issue is sharing this between jobs | 13:54 |
juergbi | I don't think it's an issue with the gitlab runner cache, although I'm not completely sure | 13:54 |
juergbi | docker containers and volumes from old jobs seem to stay around, filling up the disk | 13:54 |
juergbi | right now it should be fine again but it's filling up quickly | 13:54 |
WSalmon | oh sorry | 13:55 |
WSalmon | i got the wrong end of that stick | 13:55 |
traveltissues | juergbi: odd, is that only affecting bst-plugins-experimental? is the disk not shared over the organization? | 13:56 |
WSalmon | im supprised that we get though that many docker images, i know we have 10 or so but we dont rotate them that often | 13:56 |
WSalmon | traveltissues, i think this is effecting all the ci, is that right juergbi | 13:57 |
juergbi | traveltissues: the disk is shared across projects | 13:57 |
juergbi | WSalmon: afaict, it's about the overlays on top of the prebuilt images. mainly the .tox directory created as part of the job | 13:57 |
juergbi | bst-plugins-extra might be causing bigger .tox directories, so it affects that more | 13:58 |
juergbi | I don't know whether it only happens for failed jobs or for all jobs. haven't looked into it that closely | 13:58 |
traveltissues | i've only seen this on failed jobs | 13:59 |
*** lachlan has quit IRC | 14:01 | |
*** seanborg__ has joined #buildstream | 14:05 | |
*** seanborg_ has quit IRC | 14:05 | |
juergbi | traveltissues: what I meant was, I don't know whether the docker volumes stay around also for jobs that completed successfully or whether only failed jobs contribute to this issue | 14:10 |
traveltissues | i see | 14:11 |
*** lachlan has joined #buildstream | 14:18 | |
*** tristan has joined #buildstream | 14:27 | |
*** ChanServ sets mode: +o tristan | 14:29 | |
*** phildawson has joined #buildstream | 14:29 | |
tristan | traveltissues, Does https://gitlab.com/BuildStream/bst-plugins-experimental/-/merge_requests/94 fix the crazy buildbox related CI breakage we've been seeing ? | 14:32 |
* tristan didn't expect that other factors would break after landing the BST_MIN_VERSION patch in bst-plugins-experimental | 14:33 | |
tristan | didn't see that coming :-/ | 14:33 |
traveltissues | not that i'm aware, if you mean the issue related to "<traveltissues> Error executing command: std::runtime_error exception thrown at [buildboxcommon_client.cpp:723]" that was resolved in !102 | 14:33 |
tristan | traveltissues, is it rebased on latest master of bst-plugins-experimental today ? | 14:35 |
tristan | if so, then it accidentally fixes things | 14:35 |
* tristan thinks so because he sees a bunch of CI which happened post breakage | 14:35 | |
traveltissues | it's rebased | 14:36 |
traveltissues | as of 2h ago at least | 14:36 |
tristan | yeah, so without looking deep enough (it's late here, and I just went to have dinner)... I believe the recent breakage on master is related to having an outdated version of BuildBox in the bst-plugins-experimenal CI | 14:36 |
tristan | I'm expecting that a recent change of default sandbox to use buildbox by default is what caused this breakage in bst-plugins-experimental CI | 14:37 |
tristan | because I pointed tox.ini to recent master, naively thinking that _only_ my patch would have broken things | 14:37 |
traveltissues | `824 [00:00:00] FAILURE project-a.bst: Cache too full` | 14:38 |
traveltissues | on master | 14:38 |
traveltissues | so it might just be cache related | 14:38 |
traveltissues | `error: Writing content object: min-free-space-percent '3%' would be exceeded, at least 4.1 kB requested` | 14:39 |
tristan | yeah what I'm seeing is: The FUSE stager child process unexpectedly died with exit code 1 | 14:39 |
traveltissues | on master? | 14:39 |
tristan | for a lot of tests | 14:39 |
tristan | master bst-plugins-experimental | 14:39 |
tristan | But your branch is passing | 14:40 |
tristan | so if you are rebased against master and pointing to latest BuildStream, then I believe you've inadvertently also fixed this issue | 14:40 |
tristan | possibly by updating a docker image or such | 14:40 |
traveltissues | i'm not seeing that on master: https://storage.googleapis.com/gitlab-gprd-artifacts/62/15/6215215f70b8b4f59a12d61af2e4629469304c721c3bebaafd34ea33393a3e3c/2020_04_29/531656522/578045880/job.log?response-content-type=text%2Fplain%3B%20charset%3Dutf-8&response-content-disposition=inline&GoogleAccessId=gitlab-object-storage-prd@gitlab-production.iam.gserviceaccount.com&Signature=d0iZYBXYdtIp9aQs%2FWHz3wmMUbYriXsB6tR7%2FsptGOqzMmtnrSP7lLiRj9Eu% | 14:40 |
traveltissues | 0AKbrgG87ZJjSD0WOX9PjyTKvs0OVwGZMzf%2FdLMoYSckWgnRdj7kp7VSoLFu%2Bi%0AaFqAQOF7D%2BbKYGsiF%2BUXCRNMUpPXbQEhzw9WtZ%2FpsVxDZZ2iUhzrOLUu9Waf%0A2zGD6DxpgNVmh6HrKFPlvMBY8ox6x6%2BbOEasokksxOmDFCw8M3lQclknZJaG%0AXKAWHyFR%2FosCAj3qAkuc9IDxYQUKBIkNH8LygYsENKA%2B%2BxnE7mEteVobbFoq%0AL8rKt2WvZLF6EkduedGG4SlTeY%2Bu1klGLlCTHw0XVA%3D%3D&Expires=1588171819 | 14:40 |
traveltissues | oops, sorry | 14:40 |
traveltissues | yes, that (docker image update) was a change in !102 | 14:41 |
tristan | Ah | 14:42 |
tristan | Ok that makes sense, thanks for !102 :) | 14:42 |
traveltissues | np | 14:42 |
*** tpollard has quit IRC | 15:01 | |
*** tpollard has joined #buildstream | 15:01 | |
*** lachlan has quit IRC | 15:28 | |
*** lachlan has joined #buildstream | 15:54 | |
*** seanborg__ has quit IRC | 15:54 | |
*** lachlan has quit IRC | 16:05 | |
*** seanborg__ has joined #buildstream | 16:06 | |
*** seanborg_ has joined #buildstream | 16:16 | |
*** seanborg__ has quit IRC | 16:16 | |
*** lachlan has joined #buildstream | 16:19 | |
*** lachlan has quit IRC | 16:21 | |
*** lachlan has joined #buildstream | 16:22 | |
*** lachlan has quit IRC | 16:30 | |
*** lachlan has joined #buildstream | 16:33 | |
*** jude has quit IRC | 16:34 | |
*** lachlan has quit IRC | 16:40 | |
*** lachlan has joined #buildstream | 16:42 | |
*** seanborg_ has quit IRC | 16:49 | |
*** lachlan has quit IRC | 16:50 | |
*** lachlan has joined #buildstream | 16:52 | |
*** lachlan has quit IRC | 16:59 | |
*** tpollard has quit IRC | 17:11 | |
*** santi has quit IRC | 17:16 | |
*** lachlan has joined #buildstream | 17:51 | |
*** lachlan has quit IRC | 18:03 | |
*** benschubert has quit IRC | 19:18 | |
*** phoenix has joined #buildstream | 19:25 | |
*** phildawson has quit IRC | 19:26 | |
*** phoenix has quit IRC | 22:54 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!