| *** jsgrant has joined #buildstream | 04:35 | |
| *** toscalix has joined #buildstream | 07:23 | |
| toscalix | finn: around? | 07:54 |
|---|---|---|
| finn | hi | 08:01 |
| finn | toscalix | 08:01 |
| *** bethw has joined #buildstream | 08:33 | |
| toscalix | hi finn I was checking the tickets today in prep. for a meeting and I see you have 3 tickets with status "doing" and I was wondering if that reflects reality or if any of those should be in ToDo becuse you are waiting for something or not paying attention to them at the moment | 08:33 |
| toscalix | sorry finn it is not you, apologies | 08:34 |
| finn | np | 08:34 |
| toscalix | it would help if people add add an avatar to gitlab | 08:35 |
| toscalix | checking the boards would be easier | 08:35 |
| toscalix | I will send a mail about it | 08:35 |
| *** bochecha_ has joined #buildstream | 08:50 | |
| *** tiago has joined #buildstream | 08:54 | |
| *** jonathanmaw has joined #buildstream | 08:56 | |
| *** jennis has joined #buildstream | 08:58 | |
| *** bochecha_ has quit IRC | 09:01 | |
| *** bochecha_ has joined #buildstream | 09:03 | |
| *** awacheux has joined #buildstream | 09:22 | |
| finn | 10 points to whoever knows where my avatar is from ;) | 09:35 |
| *** tiago has quit IRC | 09:40 | |
| *** tiago has joined #buildstream | 09:42 | |
| toscalix | finn: no idea | 09:56 |
| tlater | Boo, can't set my usual profile image because it's 64kb too large :| | 09:58 |
| tlater | buildstream should really be able to do relative builds | 10:09 |
| tlater | It's a PITA to have to navigate to the root directory of my project every time I want to run a bst command | 10:10 |
| *** toscalix has quit IRC | 10:37 | |
| *** toscalix has joined #buildstream | 10:38 | |
| *** toscalix has quit IRC | 10:38 | |
| jennis | tlater, are you proposing from anywhere within the project or just anywhere? | 11:05 |
| jennis | E.g. with ostree commands you can specify --repo=<PATH | 11:05 |
| jennis | > | 11:05 |
| tlater | jennis: Just within the project | 11:05 |
| tlater | I dislike the --repo thing from ostree | 11:05 |
| tlater | A *lot* | 11:05 |
| tlater | Because it requires you actually type that everytime | 11:06 |
| tlater | Or set a custom alias for every shell you work in | 11:06 |
| jennis | ^ unless you're in the repo, right? | 11:06 |
| tlater | Having it closer to how git works would be nice | 11:06 |
| * jennis agrees ^ | 11:06 | |
| tlater | jennis: Not sure, I thought you still had to specify --repo? | 11:06 |
| jennis | Not from the top level of an ostree repo | 11:06 |
| tlater | Ah, well, then it's just like git, git has a -C flag iirc | 11:07 |
| jennis | Yeah I think so, anyway, we should probably write an issue for this, seems like a nice change to improve UX | 11:08 |
| tlater | There are a handful of similar issues | 11:08 |
| tlater | Not sure if this exact one is covered, they all seem to want something to fix this UX | 11:08 |
| * tlater will sit down and write up a proper issue for this in a bit | 11:09 | |
| jennis | Ok nice | 11:09 |
| jennis | It seems Gitlab is being slow... | 11:09 |
| *** bethw has quit IRC | 11:33 | |
| jonathanmaw | valentind: can you check https://gitlab.com/BuildStream/buildstream/merge_requests/404 when you have time? I'd like to know whether I've made any big costly errors before I duplicate them in implementing tracking. | 12:16 |
| juergbi | valentind: have you managed to get the CAS-based artifact cache fully operational? | 12:24 |
| *** bethw has joined #buildstream | 12:30 | |
| valentind | juergbi, I have setup one locally for testing. But adds68 is working on setting up one for freedesktop-sdk. I think it is running, but not yet used. | 12:52 |
| valentind | jonathanmaw, OK | 12:52 |
| jonathanmaw | thanks, valentind | 12:52 |
| juergbi | thanks for the info | 13:09 |
| jennis | Is anyone opposed to moving the plugins documentation (https://buildstream.gitlab.io/buildstream/authoring.html#plugins) up one level in the ToC? I find myself getting irritated navigating deeply to this every time I need it | 13:11 |
| jennis | ^^ This would mean it would no longer reside under "Authoring projects", instead, under "Reference Documentation" | 13:12 |
| *** xjuan has joined #buildstream | 14:38 | |
| jjardon | jennis: I think that makes sense | 14:48 |
| *** tristan has joined #buildstream | 14:57 | |
| tlater | Welcome back tristan! | 14:57 |
| * tristan fails to sneak by unnoticed ;-) | 15:04 | |
| tlater | ;p | 15:05 |
| gitlab-br-bot | buildstream: issue #417 ("Create a CAS-backed virtual directory implementation") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/417 | 15:15 |
| gitlab-br-bot | buildstream: merge request (jmac/cas_virtual_directory->master: WIP: CAS-backed virtual directory implementation) #481 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/481 | 15:21 |
| gitlab-br-bot | buildstream: merge request (jmac/cas_virtual_directory->master: WIP: CAS-backed virtual directory implementation) #481 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/481 | 15:22 |
| gitlab-br-bot | buildstream: merge request (jmac/cas_virtual_directory->master: WIP: CAS-backed virtual directory implementation) #481 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/481 | 15:25 |
| noisecell | Hi, when looking to the cache artifact.yaml file, I assume that the dependencies are build dependencies, are there a file where to see which elements installs any libraries/binaries in an element? | 15:27 |
| noisecell | or are there any command which lists this? | 15:28 |
| * noisecell is looking in ~/.cache/buildstream/artifacts/extract/baserock/foo/blah/meta/artifact.yaml | 15:30 | |
| tristan | noisecell, the format has changed since `artifact.yaml` I believe, but essentially it's the dependencies in `Scope.BUILD`, which is inclusive of recursive runtime dependencies of build dependencies | 15:30 |
| tristan | in a newer version of buildstream, the cache key would be changed for that artifact, and those keys would be in `dependencies.yaml` | 15:30 |
| tristan | (artifact metadata is not public/stable API) | 15:31 |
| noisecell | tristan, Im using 1.1.3 | 15:31 |
| tristan | hmmm, and there is an artifact.yaml ? | 15:31 |
| * tristan double checks, maybe there is still something in there | 15:31 | |
| noisecell | tristan, gimme a sec, I'be been working in 1.0.1 and 1.1.3 and I have both outputs | 15:32 |
| noisecell | tristan, I've found the one :) -- I will check it there. thanks | 15:33 |
| tristan | noisecell, was just double checking, anyway it sounds like interesting information to have `bst show` or such tell you, but only possible to implement with built artifacts present | 15:35 |
| tristan | So, no we dont have a feature ready to tell "what artifact a given staged file would belong to given a depending element" | 15:36 |
| noisecell | yeah, I was looking for example to the systems-minimal-system-image-x86_64 and I was wondering what ends up in the image in the end and what does end up in its build sandbox | 15:38 |
| noisecell | and if I can get that informations easily | 15:38 |
| gitlab-br-bot | buildstream: merge request (jennis/alternative_remote_expiry->master: Expire artifacts in the remote artifact cache) #477 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/477 | 15:39 |
| tristan | noisecell, at the moment we only have warnings when a given file is overlapped by another element in staging order | 15:40 |
| tristan | noisecell, interestingly it's not in any log files either, however it tends to be a pretty heavy duty list | 15:41 |
| noisecell | tristan, yeah, I saw the overlapping warnings. I didn't check whether they end up in logs, though. | 15:43 |
| tristan | the full lists of overlaps are saved in the individual build task logs - those are indicated as logdir relative log files when bst runs (usually ~/.cache/buildstream/logs) | 15:44 |
| tristan | but doesnt tell you the thing you specifically want, though :) | 15:45 |
| noisecell | yeah, that will give me, hopefully, a small set of what Im looking for. | 15:45 |
| noisecell | :) | 15:45 |
| noisecell | I will have to work out what does and what doesnt get in manually, though. | 15:46 |
| tristan | also, it seems one would want to get that info without necessarily having the log on hand, or needing to have such a list stored anywhere | 15:46 |
| tristan | then again, it could very easily go into a log, too | 15:47 |
| tristan | one could even create a sort of "summary" element who's sole purpose is to log stuff about dependencies | 15:47 |
| noisecell | tristan, but in the log, it will tells you if it goes to the element which that depends on, but not the final element, though | 15:48 |
| tristan | if one depends on some final element, then there should be enough context for a logger to capture what needs to be summarized | 15:49 |
| noisecell | I am looking for probably a summary of runtime dependencies for my final element and probably the build dependency tree expanded too (although that can be easily seen in the definition) | 15:49 |
| tristan | (although you lose context after a 'compose' element or such) | 15:49 |
| tristan | noisecell, to get a summary of runtime dependencies for a given element, you can run `bst show --deps run <element.bst>` | 15:51 |
| noisecell | tristan, as far as I know you can specify if it is build dependecy or runtime, and only runtime will go and get into the final element (I can be wrong here). I still need to find (Im pretty new on BuildStream) if this is the default flag | 15:51 |
| tristan | to get the file lists in their artifacts though, is not currently supported | 15:51 |
| noisecell | tristan, ok, I will check with bst show. Thanks! | 15:53 |
| tristan | noisecell, for dependency types, basically yes; more specifically though: a runtime dep is needed for running (is transient) | 15:53 |
| tristan | a buildtime dep is needed for building (not transient) | 15:54 |
| tristan | noisecell, the default is *both* | 15:54 |
| tristan | if not specified | 15:54 |
| *** bethw has quit IRC | 15:58 | |
| gitlab-br-bot | buildstream: merge request (jmac/cas_virtual_directory->master: WIP: CAS-backed virtual directory implementation) #481 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/481 | 16:02 |
| *** bethw has joined #buildstream | 16:03 | |
| noisecell | tristan, thanks for the information :) | 16:06 |
| awacheux | Is it ok to merge https://gitlab.com/BuildStream/buildstream/merge_requests/469 or do I have to do some more work on it? | 16:12 |
| gitlab-br-bot | buildstream: merge request (awacheux/artifact-type-error->master: _artifactcache/ostreecache.py: Fix artifact initialization result tuple) #469 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/469 | 16:29 |
| gitlab-br-bot | buildstream: merge request (328-support-for-downloading-sources-from-mirrors->master: WIP: Resolve "Support for downloading sources from mirrors") #404 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/404 | 17:01 |
| gitlab-br-bot | buildstream: merge request (jennis/alternative_remote_expiry->master: Expire artifacts in the remote artifact cache) #477 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/477 | 17:01 |
| *** bethw has quit IRC | 17:09 | |
| *** finn has quit IRC | 17:26 | |
| gitlab-br-bot | buildstream: merge request (richardmaw/cache-fail->master: WIP: Store failed builds in the cache) #475 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/475 | 17:28 |
| *** jonathanmaw has quit IRC | 17:31 | |
| gitlab-br-bot | buildstream: merge request (valentindavid/331_include->master: WIP: Add support for include in project.conf) #471 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/471 | 17:40 |
| *** toscalix has joined #buildstream | 18:12 | |
| *** finn has joined #buildstream | 18:15 | |
| gitlab-br-bot | buildstream: merge request (caching_build_trees->master: WIP: Caching buildtrees) #474 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/474 | 18:22 |
| gitlab-br-bot | buildstream: merge request (caching_build_trees->master: WIP: Caching buildtrees) #474 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/474 | 18:25 |
| finn | Can I just check something here. I'm making a python library with an Apache 2.0 license. In the same repo, I'm making a small app which will exercise that library. Will I need to be careful about any licenses in the library that the app uses? | 18:25 |
| finn | s/about any library/about any third party libraries | 18:26 |
| finn | Sorry, that s/ didn't make sense | 18:27 |
| finn | Can I just check something here. I'm making a python library with an Apache 2.0 license. In the same repo, I'm making a small app which will exercise that library. Will I need to be careful about any licenses in any third party libraries that the app uses? | 18:27 |
| *** toscalix has quit IRC | 18:27 | |
| gitlab-br-bot | buildstream: merge request (richardmaw/cache-fail->master: WIP: Store failed builds in the cache) #475 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/475 | 18:32 |
| *** jsgrant has quit IRC | 18:35 | |
| *** tristan has quit IRC | 19:01 | |
| *** tristan has joined #buildstream | 19:05 | |
| *** tristan has quit IRC | 19:56 | |
| *** xjuan has quit IRC | 20:16 | |
| *** jsgrant has joined #buildstream | 21:22 | |
| *** jsgrant_ has joined #buildstream | 21:31 | |
| *** jsgrant has quit IRC | 21:31 | |
| *** jsgrant_ is now known as jsgrant | 21:32 | |
| *** finn has quit IRC | 21:37 | |
| *** bochecha_ has quit IRC | 23:04 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!