IRC logs for #buildstream for Wednesday, 2019-09-11

*** narispo has quit IRC01:39
*** narispo has joined #buildstream01:40
*** kapip has quit IRC03:40
*** aevri has quit IRC03:41
*** aevri has joined #buildstream03:45
*** kapip has joined #buildstream03:46
gitlab-br-botjuergbi opened issue #1132 (Batch CAS writes to reduce round trips between bst and casd) on buildstream https://gitlab.com/BuildStream/buildstream/issues/113205:22
*** slaf has quit IRC07:01
*** slaf has joined #buildstream07:03
*** slaf has joined #buildstream07:03
*** slaf has joined #buildstream07:03
*** slaf has joined #buildstream07:04
*** slaf has joined #buildstream07:04
*** slaf has joined #buildstream07:04
*** slaf has joined #buildstream07:04
*** slaf has joined #buildstream07:05
*** slaf has joined #buildstream07:05
*** slaf has joined #buildstream07:05
*** slaf has joined #buildstream07:06
*** slaf has joined #buildstream07:06
*** slaf has joined #buildstream07:06
*** slaf has joined #buildstream07:06
*** slaf has joined #buildstream07:07
*** slaf has joined #buildstream07:07
*** slaf has joined #buildstream07:07
*** slaf has joined #buildstream07:07
*** slaf has joined #buildstream07:08
*** slaf has joined #buildstream07:08
*** slaf has joined #buildstream07:08
*** slaf has joined #buildstream07:08
*** lantw44 has quit IRC07:46
*** lantw44 has joined #buildstream07:46
*** lantw44 has quit IRC07:47
*** lantw44 has joined #buildstream07:47
*** rdale has joined #buildstream08:21
gitlab-br-botjuergbi opened (was WIP) MR !1469 (build-all-option->master: Add 'dependencies' option to 'build' user config) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/146908:23
*** phil has joined #buildstream09:12
*** traveltissues has joined #buildstream09:26
*** jonathanmaw has joined #buildstream09:39
*** toscalix has joined #buildstream10:11
coldtomi've just noticed that the defaults for `include-orphans` are inconsistent between `compose` and `filter` elements, which seems a bit unintuitive to me11:06
*** toscalix has quit IRC12:57
*** toscalix has joined #buildstream12:57
tlater[m]cs-shadow: regarding https://gitlab.com/BuildStream/buildstream/merge_requests/1590/#note_21486203213:00
tlater[m]Why do we have a `source checkout --deps`?13:00
* tlater[m] doesn't really see the use case for it13:00
*** narispo has quit IRC13:12
*** narispo has joined #buildstream13:13
juergbitlater[m]: isn't this a replacement for the former source bundle command?13:18
tlater[m]Hm, I suppose13:19
* tlater[m] wonders if doing the same for `artifact checkout` would result in confusio13:20
tlater[m]*confusion13:20
juergbithat already has --deps support, doesn't it?13:21
tlater[m]Not atm13:21
juergbihm, --help claims it does13:21
tlater[m]That discussion there is about adding it13:21
* tlater[m] thought removing it from `source checkout` would perhaps be better13:21
juergbiartifact checkout with deps certainly makes sense to me13:22
juergbilike bst shell without the shell ;)13:22
tlater[m]Hm, yeah, but the intention is to set up stacks to create that kind of output13:24
tlater[m]It's a nice shortcut I suppose13:24
juergbistack is essentially just a dependency list13:26
juergbiif you dropped dependencies from bst artifact checkout, checkout of a stack would be an empty directory, right?13:26
juergbicompose would work, of course13:26
jennisThe discussion was about adding --deps *all* specifically to artifact checkout13:27
jennisFor the sake of consistency. source checkout supports --deps all|none|run|build, so should we do the same for artifact checkout?13:28
jennisEven though artifact checkout --deps all may seem like quite a weird thing to do13:28
juergbiI don't think it's too weird13:28
juergbinot sure whether it will be used a lot but it's practically no effort, right?13:29
jennisIt's easy enough to support13:29
jennisyeah, I have a patch for it13:29
juergbiit would mean that you have all build dependencies in a potential chroot13:29
jennisI'll create an MR soon then13:29
juergbiso you could rebuild any component13:29
juergbiat least as long as there are no conflicts due to bootstrap elements13:29
tlater[m]Oh, master pipeline failed13:57
* tlater[m] checks if the docs still work13:57
tlater[m]Yes!13:57
coldtomtlater[m]: thanks for that docs patch, that bug was incredibly frustrating14:00
benschubertAny practical reason why we resolve the state of the cache before doing a 'source checkout' 'source track' and such?14:00
benschubertI back/forward ported updates to bst-external to the bst-plugins-experimental repo: https://gitlab.com/BuildStream/bst-plugins-experimental/merge_requests/32 is someone wants to have a look14:01
benschubertI'd like to get this in to be able to build the latest freedesktop sdk with buildstream master, which would allow me to fix our nightly tests (We can't really use the previous version, some sources have disappeared)14:03
* coldtom takes a look14:05
benschuberthttps://gitlab.com/snippets/1894045 Can someone help me make sense of this message? 'resolved key summary' is marked as failed, the rest is marked as success...14:06
tlater[m]benschubert: Have you looked at the tracking log?14:12
* tlater[m] hasn't seen this before, but can imagine that it's a bad error message for a failed cache operation.14:12
benschuberttlater[m]: my current guess is the artifact for this source was already cached and 'failed', hence shown like this14:14
tpollardit's tracked, but the state of the artifact that is cached locally is failed14:14
tlater[m]Oh, right14:14
benschubertmakes more sense, thanks :)14:14
tpollardI don't think it's a nice message though14:15
benschubertI build an artifact, it fails, it gets pushed to remote artifact server. I 'bst artifact delete' it, because it should not have happened (temporary failure) I rebuild. It gets pulled? How can I force rebuild except by --fetchers=0 ?14:30
tpollarderm14:31
tpollardyou could also --remote to a dummy url14:32
benschubertoh... also --fetchers=0 doesn't work for this14:33
benschuberttpollard: '--remote' is not available ofr builds14:33
tpollardit should be14:33
tpollardI merged it a while ago14:33
benschubertoh14:33
benschubertit's on 'build' not bst ok fair14:34
tpollardI think it could be a bst main option14:34
tlater[m]tpollard: Not in the spirit of the question, I'd say14:34
tpollardand i also started work on something along the lines of (Don't interact with any remotes option)14:34
tpollardtlater[m]?14:35
tlater[m]benschubert: We've been talking about a `bst build --force` for ages14:35
benschubertMmh my problem seems to come from a mis-downloaded tarball14:35
benschubertmy ref is correct (downloaded the zip file, sha256sum it, it matches my ref). Trying to source checkout with bst gives me a different content than the tarball I downloaded manually14:36
tlater[m]tpollard?14:37
tpollardtlater[m]: I didn't really understand what you mean by that, that's all14:38
tlater[m]bst main option makes sense, if that's what you mean. I'm constructing an email as we speak that will touch on that.14:38
* tlater[m] is worried that may cause some confusion, but leaves discussion to the ML14:39
* tpollard nods 14:39
tlater[m]Oh, you mean `build --force`? That's specifically for when you built something and a temporary failure broke the build and screwed up your artifact.14:41
tlater[m]We should be able to override remote artifacts without disabling the remote, otherwise we end up...14:42
tlater[m]Poisoning the cache I suppose?14:42
benschubert^ correct14:42
benschubertmy source cache is currently poisoned it seems...14:42
* tlater[m] didn't think he'd ever come up with that phrase to describe a build problem14:43
tpollardtainted maybe14:43
benschubertWell, my source checkout or build shell definitely doesn't contain the data from the zip file14:44
tlater[m]"Poisoning" is typically what people use to describe this vulnerability for DNS servers. It's a good fit for our case.14:45
tlater[m]benschubert: But how did you get matching keys between a broken zip and an unbroken one?14:46
tlater[m]Is this a sha collision?14:46
benschubertI would hope not14:47
tlater[m]I can see it for an artifact cache with failed builds, but not a source cache.14:47
benschubertthe sources give me 3 files, which I cant even find in the original zip file14:47
benschubertbut that do seem 'familiar'14:48
tlater[m]Can you try to manually create cache keys for the two?14:49
tlater[m]I wonder if your server delivers different zipfiles depending on the client's browser string14:50
tlater[m]Because that seems more likely than a cache collision on a network error :)14:51
benschubertOk, I've answered part of the question: it's only giving me the data from one subdirectory of my zip file14:52
benschubertthe first in alphabetical order14:52
tlater[m]... Or a deliberate attack14:52
benschubertI wish, at least I could blame it on someone else :'D14:53
benschubertthe question is, why do I only get one subdirectory of the zip file?14:53
juergbibenschubert: check 'base-dir' config14:56
juergbithe default is not ideal14:56
benschubertjuergbi: setting to '' worked14:56
benschubertbut why '*' matches only the first directory?14:56
benschubertthat seems like a bug to me, or am I missing something?14:56
juergbiI think the idea is that it works out of the box for archives that have a single directory. which is very common, at least for tarballs14:57
juergbihowever, I think we should error out if '*' is specified and there are multiple entries14:57
benschubertagreed14:58
*** cs-shadow has quit IRC15:08
gitlab-br-botjennis opened MR !1598 (jennis/add_deps_all_to_checkout->master: Support `--deps all` in `artifact checkout`) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/159815:13
benschubertjuergbi: I was thinking about cascache, should we throw an exception in `release_resources` if the process already had terminated? Or if the process doesn't terminate with 0 ?15:13
juergbibenschubert: if the process is dead before we explicitly terminate it, it's an error15:14
juergbieven if it terminates with 015:14
juergbialthough I don't expect that to happen in practice15:14
juergbi(unless someone manually sends SIGTERM or similar)15:15
benschubertunless.. segfault? :)15:15
juergbithat would be exit code -1115:15
benschubertAnd yes, I meant 1) check if already stopped -> if yes error, otherwise stop -> if not stopped correctly (0) -> error15:16
juergbiah ok15:16
juergbiyes, should probably also be an error or at least a warning15:16
juergbiwe have to be careful, though. if we send SIGKILL (after timeout), exit code will always be -9, not 015:17
juergbiso non-0 exit is only unexpected for the regular SIGTERM case, not for the SIGKILL fallback15:17
benschubertcorrect15:25
benschubertI'll add a MR for that15:25
*** narispo has quit IRC15:58
*** narispo has joined #buildstream15:58
*** toscalix has quit IRC16:04
benschubertcoldtom: is https://gitlab.com/BuildStream/bst-plugins-experimental/merge_requests/32 fine with you with an issue to tackle the fixmes? :)16:05
coldtombenschubert: looks good to me, should be fine to merge16:08
benschubertthanks a lot!16:08
*** cs-shadow has joined #buildstream16:14
*** phil has quit IRC16:51
*** phildawson_ has joined #buildstream16:51
*** jonathanmaw has quit IRC16:53
*** paulsherwood has quit IRC17:14
*** valentind has quit IRC17:21
*** jennis has quit IRC17:21
*** jward has quit IRC17:21
*** WSalmon has quit IRC17:21
*** bethw has quit IRC17:21
*** laurence has quit IRC17:21
*** laurence has joined #buildstream17:23
*** valentind has joined #buildstream17:24
*** bethw has joined #buildstream17:24
*** jennis has joined #buildstream17:25
*** jward has joined #buildstream17:25
*** WSalmon has joined #buildstream17:26
gitlab-br-botjennis opened MR !1599 (jennis/load_deps_consistently->master: Load deps in checkout like we do everywhere else) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/159917:30
*** adds68 has quit IRC17:33
*** qinusty has quit IRC17:33
*** samkirkham has quit IRC17:33
*** ikerperez has quit IRC17:33
*** Becky has quit IRC17:33
*** jennis has quit IRC17:44
*** bethw has quit IRC17:44
*** jward has quit IRC17:44
*** jward has joined #buildstream17:46
*** bethw has joined #buildstream17:48
*** jennis has joined #buildstream17:48
*** phildawson_ has quit IRC17:50
*** phildawson_ has joined #buildstream17:52
*** traveltissues has quit IRC18:07
*** phildawson_ has quit IRC18:35
gitlab-br-botjjardon opened MR !1600 (jjardon/distutils->master: Use distutils plugin from bst-plugins-experimental) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/160020:09

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