IRC logs for #buildstream for Monday, 2018-11-12

*** w0rd has joined #buildstream00:26
*** bochecha has quit IRC00:41
*** toscalix has joined #buildstream06:40
*** mohan43u has quit IRC08:07
*** mohan43u has joined #buildstream08:11
*** mohan43u has quit IRC08:15
*** mohan43u has joined #buildstream08:18
*** finn has joined #buildstream08:56
gitlab-br-botjjardon opened issue #763 (Overnigth tests are failing: "Error response from daemon: Conflict. The container name "/runner-xxx" is already in use by container") on buildstream https://gitlab.com/BuildStream/buildstream/issues/76309:00
laurenceIs the meeting going ahead?09:01
laurenceah yes, had to re-join.09:02
toscalixthere is something wrong.... I had issues joining and I cannot see or hear anything09:09
toscalixlet's move to Google Meet. Let me add the link09:09
toscalixor is it me alone?09:09
*** WSalmon has joined #buildstream09:10
toscalixvalentind: laurence jjardon ^09:11
*** benschubert has joined #buildstream09:11
jjardontoscalix: Its only you09:12
laurencetoscalix, we are all on appear.in09:12
laurencegoing through the issues09:12
toscalixah, ok09:12
toscalixwill keep working on it then09:12
*** WS has joined #buildstream09:28
*** WSalmon has quit IRC09:28
*** WS is now known as WSalmon09:29
*** alatiera_ has joined #buildstream09:39
*** jonathanmaw has joined #buildstream09:41
*** tiagogomes has joined #buildstream09:49
*** tristan has joined #buildstream09:49
*** tiagogomes has quit IRC09:55
*** tiagogomes has joined #buildstream09:56
*** tpollard has joined #buildstream09:59
*** alatiera__ has joined #buildstream10:08
*** alatiera_ has quit IRC10:08
*** alatiera__ is now known as alatiera_10:14
*** raoul has quit IRC10:19
*** lachlan has joined #buildstream10:31
*** jfhbrook has joined #buildstream10:37
*** rdale has joined #buildstream10:40
*** jonathanmaw_ has joined #buildstream10:42
*** jonathanmaw has quit IRC10:43
gitlab-br-botrichardmaw-codethink approved MR !945 (bschubert/fix-silence-stopiteration-pep-0479->master: source.py: don't let StopIteration propagate to silence() contextmanager) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/94511:05
gitlab-br-botrichardmaw-codethink merged MR !945 (bschubert/fix-silence-stopiteration-pep-0479->master: source.py: don't let StopIteration propagate to silence() contextmanager) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/94511:05
Nexushey all, i'd really appreciate some reviews on:11:07
Nexushttps://gitlab.com/BuildStream/buildstream/merge_requests/92511:07
Nexushttps://gitlab.com/BuildStream/buildstream/merge_requests/92611:07
Nexusthanks!11:07
Nexus926 is an interesting one, as it's adding a --world flag to bst build, which some people dislike the name of, so i think a discussion would be useful11:08
*** lachlan has quit IRC11:11
jennishttps://wiki.codethink.co.uk/bl013/log/bl013:_Standup:_Mon_12th_November_2018/11:13
jenniswoops11:15
*** lachlan has joined #buildstream11:15
Nexus:I11:16
Nexussmh11:16
*** jonathanmaw_ is now known as jonathanmaw11:17
jonathanmawhow odd, when I run a test with "--no-cov" it passes, when I run it without, it fails because it thinks the element hasn't been built :S11:19
*** lachlan has quit IRC11:20
*** raoul has joined #buildstream11:23
*** lachlan has joined #buildstream11:28
benschubert@Nexus  here you go :)11:29
benschubertI'd also appreciate reviews on !895 and !938 if people have time11:35
gitlab-br-botMR !895: Don't cache sandbox failures https://gitlab.com/BuildStream/buildstream/merge_requests/89511:35
gitlab-br-botMR !938: Fix os.rename in git source element to correctly handle error codes https://gitlab.com/BuildStream/buildstream/merge_requests/93811:35
Nexusbenschubert: you raise a good point regarding the --world/--all flags, and i agree that we should just have one, but which? or a 3rd option? As --all already exists in some contexts, but not in the same way as this11:50
Nexusand i've heard from some people that they don't like the --world convention11:50
benschubert`--world` is at least the convention in the Gentoo world, it's easy to remember and doesn't conflict with any other --all we could have (assuming the --all all have the same meaning). I don't see any other solution that is "commonly" used in projects. And I agree that keeping the meaning the same for options accross commands should be done11:52
KinnisonI think --world also comes from Yocto11:53
Kinnisonso it's common in meta buildsystems11:53
tpollardbitbake does indeed use world11:53
KinnisonIf there's objection to 'world' then I'd go for '--all-elements'11:53
Kinnisonor '--everything'11:53
* Kinnison likes nice wordy options11:53
benschubertI would suggest against --all-elements, especially with autocompletion :)11:54
benschubertand --world has the advantage that "-w" is also unused, so we would have a convenient short option11:55
tiagogomesor bst build \*11:56
skullman* is a valid filename11:56
skullmanan alternative might be a --glob option to disambiguate it11:57
tiagogomesI think the case of having a '*' named file with build definitions is rare enough case to not be worth to consider11:58
tiagogomesAlso assuming good citizens name files with the .bst extension11:59
benschubertI'd be against *, typing a \ everytime would be a pain11:59
KinnisonI still think we should have mandated the .bst extension and removed it from element names11:59
* Kinnison runs away12:00
Nexusi agree that we shouldrequire .bst12:00
skullmanshould ≠ must12:00
tiagogomesI could turn the argument to bst build a valid glob as in (https://docs.python.org/3/library/glob.html)12:01
tiagogomesThis I think would remain backwards compatible and flexible12:02
tiagogomesSo to build everything:  bst build "**"12:02
* tiagogomes goes for lunch12:02
benschuberttiagogomes: that's something that seems safer :D12:02
gitlab-br-botvalentindavid opened MR !948 (valentindavid/integration-tests-aarch64->master: Run tests on aarch64) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/94812:08
*** lachlan has quit IRC12:10
valentindtristan, Maybe you could have a look at #144 to be sure we can close it.12:12
gitlab-br-botIssue #144: Possible race condition - inconsistent passing test https://gitlab.com/BuildStream/buildstream/issues/14412:12
*** lachlan has joined #buildstream12:13
laurencejennis, I have an email from Gitlab telling me you commented on this issue about cache clean-up... https://gitlab.com/BuildStream/buildstream/issues/737#note_11526278612:32
laurencebut i cannot see the comment on gitlab's UI - is this a gitlab bug or did you remve it?12:33
*** lachlan has quit IRC12:37
*** jonathanmaw_ has joined #buildstream12:40
*** jonathanmaw has quit IRC12:41
*** alatiera_ has quit IRC12:46
*** alatiera_ has joined #buildstream12:46
tpollardtristan: I've tried to cover your points and closed discussions that I felt were mine to close on https://gitlab.com/BuildStream/buildstream/merge_requests/786/12:48
*** lachlan has joined #buildstream12:53
*** lachlan has quit IRC12:58
NexusAny further thoughts on "bst build "**"" ?13:17
* skullman would prefer `bst build --glob "**"` or `bst build -g "**"`13:18
Nexusthat starts to become far less intuitive imo13:19
skullmanI'm just a grump about making assumptions about file path validity.13:21
Nexuswould we be introducing "--glob" as a different function then? different to the current "Just build everything" functionality ?13:23
skullmanyeah, you'd be doing the same tree walk to find things (though depending on how it's implemented you don't need to walk the whole tree) and filtering using the glob expression13:24
KinnisonOne concern I have with globbing is that if someone has READMEs or notes files, or somesuch in the tree, that we're going to hit issues.13:27
skullmanso `-g "**.bst"` rather than `--world` and assume everything under elements/ is a bst definition?13:29
KinnisonThat'd be okay for me13:29
Kinnisonthough a good shell would let you type **/*.bst and hit TAB and have it DTRT anyway13:30
NexusDTRT?13:30
Nexusand this still requires .bst to be mandatory doesn't it?13:31
benschubertI don't think you can assume everything under elements will be a bst definitions, one thing we have is ".inc" files that contain general definitions for groups of elements13:31
*** starquake has joined #buildstream13:33
NexusI don't see how it's possible to have a global "build all" without either asserting that only elements exist in the element-path or that all elements end in .bst13:34
benschubertOne thing that could be done though is use a "element-extensions:" config that would allow specifying the elements?13:34
benschubert*the elements extensions13:34
benschubertwith a default to "[.bst]" for example (or to *, if we don't want to break anyone)13:35
Nexusit might be worth making an email thread for this :/13:40
gitlab-br-botBenjaminSchubert opened MR !949 (bschubert/add-fedora-nobwrap-tests->master: Add tests for fedora with no bubblewrap available) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/94913:51
*** lachlan has joined #buildstream13:52
benschubertKinnison: this PR is close to what you requested in the issue I closed without paying attention,  would you mind having a look into this?13:52
Kinnisonbenschubert: which?13:54
Kinnison(MR number)13:54
benschubert!949 sorry13:54
benschubertand for issue #69613:55
gitlab-br-botIssue #696: Missing tests for Linux-non-bwrap-non-FUSE situations https://gitlab.com/BuildStream/buildstream/issues/69613:55
Kinnisonis there a reason it's a large number of commits?13:55
benschubertI refactored the gitlab-ci file to remove duplication and did it step by step for better clarity13:56
benschubertall commits are passing one after the other though :)13:56
benschubertI can squash some together if needed13:56
KinnisonIf they all pass then that's fine I guess14:13
Kinnison:_)14:13
benschubertthanks!14:17
*** jonathanmaw has joined #buildstream14:32
*** jonathanmaw_ has quit IRC14:33
*** lachlan has quit IRC14:33
*** Kinnison has quit IRC14:42
*** Kinnison has joined #buildstream14:42
*** lachlan has joined #buildstream14:50
*** lachlan has quit IRC15:25
gitlab-br-botjuergbi merged MR !937 (element-path_not_validated->master: Element path not validated before use) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/93715:44
jonathanmaw:-/ looks like the reason why my tests were failing when I passed "--no-cov" is because the coverage file is generated in the current directory, which changes the cache key15:57
Kinnisonoops16:00
* jonathanmaw tries replacing the "cwd" kwarg in cli.run with adding "-C" to the args.16:01
jonathanmawwell, that works!16:05
benschubertI'm not sure to grasp exactly how the mounting of directories works in the sandbox. Do we have documentation somewhere? I'm particularily interested in knowing what directories are mounted in what order and with what options (trying to replace the fuse layer just for playing)16:20
*** lachlan has joined #buildstream16:25
skullmannot really, and it varies by platform too i.e. sandboxchroot mounts the fuse layer on top of /dev, while sandboxbwrap mounts /dev on top of the fuse layer16:25
benschubertif I understand well, the FUSE layer is just here to provide a COW experience so we don't corrupt the real data on disk correct? But in the end only /buildstream and /buildstream-install are saved. Correct?16:26
skullmancorrect, though I was told at one point that buildbox continuously uploads all the filesystem changes to CAS, so everything else gets there too at some point16:27
benschubertSo I would need to save the changes made on the rest of the layer everytime, I wouldn't be able of discarding it right? Do we have somewhere a spec about the format of the data we upload?16:28
skullmanBuildStream doesn't care about the contents of anywhere but /buildstream and /buildstream-install, I think BuildBox might care since it wants to be more generic or as a side-effect of how its CAS fuse layer works, I'm not sure of the details.16:31
skullmanThe spec of the upload format is the gRPC protos.16:31
juergbiwith local execution, changes in the rootfs will not be uploaded with BuildBox, although they will be in local cache16:32
benschubertjuergbi: so they are cached locally? The context: I'm trying to add a docker sandbox, to be able to run on Windows. But I don't have access to fuse so I was thinking doing that with docker layers, but I've got trouble making sure I'm actually doing the correct thing16:33
juergbiwith remote execution all changes are needed in the remote CAS to preserve them across commands16:33
*** lachlan has quit IRC16:34
juergbibenschubert: yes, they will be cached locally but in CAS, not as regular filesystem structure16:34
juergbithat's for the Build16:35
juergbiBox case16:35
juergbiwith the current local execution, a separate rootfs temp directory will be created where COW changes are cached16:36
juergbifor Docker with overlayfs you might need two separate directories, one for the lower read-only layer and one for the changes16:36
benschubertDocker by default is COW, so saving the layer after the command run should be sufficient, I'm just not sure if the format would be correct. And for the /buildstream{,-install}, are they also COW ?16:37
skullmanbenschubert: closer to volumes AIUI16:39
juergbibenschubert: in practice the format of those COW changes should only matter for the sandbox backend itself16:39
juergbi /buildstream{,-install} are not COW, they are regular native directories, empty at startup16:39
juergbiso they should likely be volumes as skullman mentions16:40
benschubertor bind-mounts so we have direct access to them I guess, ok I think I have enough information to move, thanks a lot!16:41
skullmanjuergbi: sorry to bother you, but have you had a chance to look at the addition of the BST_GRANULAR_STAGE flag to elements in https://gitlab.com/BuildStream/buildstream/merge_requests/909 and I could ideally do with you looking at https://gitlab.com/BuildStream/buildstream/merge_requests/920 since you did the work to split up the artifact and cas cache classes and it's a new user.16:41
juergbiI think I had a brief look. let's check16:43
* skullman didn't see any comments, but GitLab is like that sometimes16:50
*** lachlan has joined #buildstream16:54
benschubertjuergbi: if you have time, i'd like a maintainer review on !895, since it has to do with caching17:04
gitlab-br-botMR !895: Don't cache sandbox failures https://gitlab.com/BuildStream/buildstream/merge_requests/89517:04
juergbiI've added it to my list17:05
benschubertThanks!17:05
*** lachlan has quit IRC17:07
gitlab-br-botvalentindavid opened (was WIP) MR !948 (valentindavid/integration-tests-aarch64->master: Run tests on aarch64) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/94817:10
*** toscalix has quit IRC17:13
*** lachlan has joined #buildstream17:15
juergbiskullman: added an initial comment17:18
juergbialso added !920 to my list17:18
gitlab-br-botMR !920: Add artifact log command https://gitlab.com/BuildStream/buildstream/merge_requests/92017:18
skullmanthanks17:18
jonathanmawIf anyone has time for review, I've fixed the CI problem I was having with https://gitlab.com/BuildStream/buildstream/merge_requests/92417:24
*** lachlan has quit IRC17:25
*** abderrahim3 has joined #buildstream17:30
*** abderrahim2 has quit IRC17:31
*** lachlan has joined #buildstream17:37
*** lachlan has quit IRC18:04
*** lachlan has joined #buildstream18:13
*** toscalix has joined #buildstream18:23
*** toscalix has quit IRC18:26
*** rdale has quit IRC18:40
*** alatiera_ has quit IRC18:42
*** raoul has quit IRC18:45
*** rdale has joined #buildstream18:50
*** lachlan has quit IRC19:31
*** lachlan has joined #buildstream19:50
*** lachlan has quit IRC19:58
*** lachlan has joined #buildstream20:09
*** tristan has quit IRC20:39
*** lachlan has quit IRC20:45
*** catonano has joined #buildstream20:46
*** jonathanmaw has quit IRC20:56
*** catonano has quit IRC23:03
*** samouy has joined #buildstream23:45

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