IRC logs for #buildstream for Thursday, 2018-10-25

*** Prince781 has quit IRC00:18
*** inigomartinez has joined #buildstream00:18
*** Prince781 has joined #buildstream00:21
*** Prince781 has quit IRC00:24
*** Prince781 has joined #buildstream00:26
*** Prince781 has quit IRC00:27
*** Prince781 has joined #buildstream00:28
*** xjuan has quit IRC02:29
*** mohan43u has quit IRC03:23
*** mohan43u has joined #buildstream03:23
*** catonano has joined #buildstream06:16
*** finn has joined #buildstream07:08
*** finn has quit IRC07:09
Kinnisontlater[m]: Hmm, the pipeline failed at setup because versioneer wasn't available07:56
*** Prince781 has quit IRC08:05
*** alatiera_ has joined #buildstream08:24
*** Prince781 has joined #buildstream08:25
*** catonano has quit IRC08:28
*** alatiera has quit IRC08:28
*** ssssam[m] has quit IRC08:28
*** WSalmon has quit IRC08:28
*** benschubert has quit IRC08:28
*** paulsherwood has quit IRC08:28
*** laurence has quit IRC08:28
*** mablanch has quit IRC08:28
*** milloni has quit IRC08:28
*** gitlab-br-bot has quit IRC08:28
*** Demos[m] has quit IRC08:28
*** abderrahim[m] has quit IRC08:28
*** juergbi has quit IRC08:28
*** rafaelff[m] has quit IRC08:28
*** connorshea[m] has quit IRC08:28
*** doras[m] has quit IRC08:28
*** krichter[m] has quit IRC08:28
*** pro[m] has quit IRC08:28
*** kailueke[m] has quit IRC08:28
*** asingh_[m] has quit IRC08:28
*** cgmcintyre[m] has quit IRC08:28
*** theawless[m] has quit IRC08:28
*** awacheux[m] has quit IRC08:28
*** jjardon has quit IRC08:28
*** mattiasb has quit IRC08:28
*** jjardon[m] has quit IRC08:28
*** m_22[m] has quit IRC08:28
*** tlater[m] has quit IRC08:28
*** oknf[m] has quit IRC08:28
*** hergertme has quit IRC08:28
*** lchlan has quit IRC08:28
*** Kinnison has quit IRC08:28
*** ironfoot has quit IRC08:28
*** tintou has quit IRC08:28
*** inigomartinez has quit IRC08:28
*** dineshdb[m] has quit IRC08:28
*** abderrahim3 has quit IRC08:28
*** anahuelamo has quit IRC08:28
*** slaf has quit IRC08:28
*** flatmush has quit IRC08:28
*** phildawson has quit IRC08:28
*** albfan[m] has quit IRC08:28
*** segfault3[m] has quit IRC08:28
*** waltervargas[m] has quit IRC08:28
*** tpollard has quit IRC08:28
*** persia has quit IRC08:28
*** cs-shadow has quit IRC08:28
*** valentind has quit IRC08:28
*** aiden has quit IRC08:28
*** thinkl33t has quit IRC08:28
*** Prince781 has quit IRC08:28
*** catonano has joined #buildstream08:28
*** inigomartinez has joined #buildstream08:28
*** dineshdb[m] has joined #buildstream08:28
*** alatiera has joined #buildstream08:28
*** ssssam[m] has joined #buildstream08:28
*** abderrahim3 has joined #buildstream08:28
*** WSalmon has joined #buildstream08:28
*** benschubert has joined #buildstream08:28
*** anahuelamo has joined #buildstream08:28
*** paulsherwood has joined #buildstream08:28
*** laurence has joined #buildstream08:28
*** valentind has joined #buildstream08:28
*** mablanch has joined #buildstream08:28
*** milloni has joined #buildstream08:28
*** aiden has joined #buildstream08:28
*** slaf has joined #buildstream08:28
*** tintou has joined #buildstream08:28
*** ironfoot has joined #buildstream08:28
*** Kinnison has joined #buildstream08:28
*** lchlan has joined #buildstream08:28
*** hergertme has joined #buildstream08:28
*** oknf[m] has joined #buildstream08:28
*** tlater[m] has joined #buildstream08:28
*** m_22[m] has joined #buildstream08:28
*** jjardon[m] has joined #buildstream08:28
*** mattiasb has joined #buildstream08:28
*** jjardon has joined #buildstream08:28
*** awacheux[m] has joined #buildstream08:28
*** theawless[m] has joined #buildstream08:28
*** cgmcintyre[m] has joined #buildstream08:28
*** asingh_[m] has joined #buildstream08:28
*** kailueke[m] has joined #buildstream08:28
*** pro[m] has joined #buildstream08:28
*** krichter[m] has joined #buildstream08:28
*** doras[m] has joined #buildstream08:28
*** connorshea[m] has joined #buildstream08:28
*** rafaelff[m] has joined #buildstream08:28
*** juergbi has joined #buildstream08:28
*** abderrahim[m] has joined #buildstream08:28
*** Demos[m] has joined #buildstream08:28
*** gitlab-br-bot has joined #buildstream08:28
*** flatmush has joined #buildstream08:28
*** thinkl33t has joined #buildstream08:28
*** phildawson has joined #buildstream08:28
*** albfan[m] has joined #buildstream08:28
*** segfault3[m] has joined #buildstream08:28
*** irc.eagle.y.se sets mode: +oo ironfoot jjardon08:28
*** waltervargas[m] has joined #buildstream08:28
*** tpollard has joined #buildstream08:28
*** cs-shadow has joined #buildstream08:28
*** persia has joined #buildstream08:28
*** finn has joined #buildstream08:28
*** jonathanmaw has joined #buildstream08:34
*** Prince781 has joined #buildstream08:34
adds68What do i need to pass to the Element class in order to receive and Element object back in Python?08:37
adds68i just want to look at what is inside an Element object, but it seems passing a yaml file to Element.configure() does not work08:38
valentindadds68, You cannot construct an element. They are constructed by buildstream.08:38
skullmanadds68: mostly you load them via the pipeline, they're normally instantiated from MetaElements, but you'll want to avoid having to do that yourself08:39
skullmanyou need to run something like: app.stream.load_selection(elements, selection=PipelineSelection.NONE)08:39
*** bochecha has joined #buildstream08:43
adds68skullman oh ok thanks, so i need to import app from BuildStream?08:43
skullmanyou're writing an external tool?08:44
adds68skullman a bst plugin, but i want to mess around with an element object to understand the data structure a bit more08:45
skullmanhm, I've not done a plugin, can't say I know where the entry point is or what gets passed along08:46
adds68skullman, i shall keep looking around, but thanks anyway :)08:47
skullmanIIRC it's a layering violation for plugins to have access to the app, and maybe even to the stream, so I'm not sure there is an answer08:47
adds68skullman, yea i'd assume this isn't a normal thing to do, but i just wondering if i could do that in iPython for example08:48
adds68i was*08:48
laurencefollowing the talk at the gathering last week, is there actually a WIP doc of buildstream's architecture available to look over ?08:50
*** raoul has joined #buildstream08:51
*** catonano has quit IRC08:53
phildawsonlaurence, it's not an mr yet, but theres a branch along the lines of tristan/architecture-docs08:54
phildawsonor at least it wasn't when I looked a couple of days ago08:54
laurencephildawson, cheers08:55
valentindadds68, the element is different depending on the plugin used. They all inherit on Element which inherit from Plugin. So Element and Plugin class are the two places to look at for API.08:55
*** catonano has joined #buildstream08:56
valentindtiagogomes, jjardon, What was the reason for having separate builder for overnight builds? More memory? Bigger CPUs? Pricing of DO?08:57
tiagogomesvalentind, main reason was, we had those two virtual machines provided by Codethink, so why not use them for something08:58
valentindtiagogomes, can you forward me the last email from/to operations about those virtual machines.09:00
adds68valentind, ok i shall take a look at Plugin, seems annoying though that you can't just get an object to play around/debug with09:00
tiagogomesvalentind sure09:01
tiagogomesdone09:01
valentindadds68, in a plugin you are already in an element, so you can look at self.09:02
valentindtiagogomes, thank you.09:02
adds68valentind, ahhh ok, i was confused as for the Manifest plugin, Element is passed, so i assumed you needed an Element object09:03
valentindadds68, if you want to look at a specific Element, you can create a plugin that gets Element object through dependencies with self.dependencies(), and then in your .bst of your element just add a dependency to the element you want to look at.09:03
tiagogomesIs there any way of removing some files from an artifact other than using a script element. The files that I need to remove are not in any domain09:04
valentindadds68, I do not see where an element is passed.09:04
valentindadds68, CollectManifestElement is a class not a function.09:05
adds68valentind, class CollectManifestElement(Element), i would have expected to see "self"09:05
valentindadds68, this is class inheritance.09:05
adds68valentind, i should have read the Plugin guidelines before though! :P09:05
valentindIt means CollectManifestElement is  a subclass of Element.09:06
adds68valentind, ahhh yes! 0_009:06
valentindadds68, I recommend reading the Python documentation it is nicely written: https://docs.python.org/3/tutorial/classes.html09:07
benschuberttiagogomes: there is the "compose" element  that has an exclude parameter https://docs.buildstream.build/elements/compose.html09:13
tiagogomesyup, but you exclude domains there. I want to filter at file level, not domain level09:14
benschubertoups sorry didn't read you well enough, I think there isn't anything else sadly, since both filter and compose are doing the same :/09:16
adds68valentind thanks :) I've spent to long looking at YAML :P09:17
benschuberthttps://gitlab.com/BuildStream/buildstream/merge_requests/886 ready for review: removing pytest-runner to simplify the lifes of people behind vpns/using other pypi servers :)09:20
gitlab-br-botwillsalmon opened MR !897 (willsalmon/defaultWorkspaces->master: WIP: Updated Workspace CLI) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/89709:28
*** lachlan has joined #buildstream09:30
gitlab-br-botBenjaminSchubert approved MR !891 (aevri/include-error->master: More user-friendly reporting on include errors) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/89109:38
gitlab-br-botBenjaminSchubert approved MR !889 (valentindavid/ruamel_warnings->master: Fix some ruamel warnings during tests) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/88909:41
* Kinnison wonders if anyone here is able to think about the docker CI systems? https://gitlab.com/BuildStream/buildstream/merge_requests/892 is currently failing to merge because tlater[m]'s updated docker images seem to lack Versioneer, but I have no idea what to do to diagnose/resolve this09:48
tpollardhmm09:51
cs-shadowKinnison: versioneer is not part of the Docker image, it is included in the buildstream repo09:52
Kinnisoncs-shadow: then might you be able to shed any light on https://gitlab.com/BuildStream/buildstream/-/jobs/112255926 and why it might have failed?09:52
* Kinnison is a smidge out of his depth with this stuff09:52
cs-shadowWhat I suspect has happened is that we have got newer versions of setuptools and we don't explicitly include versioneer (and some other necessary things) in our MANIFEST.in and we should do that09:52
jmacbenschubert: I'm taking a look at !886 now. I think jonathanmaw will need to check his previous questions are addressed.09:53
cs-shadowI think we need add "include versioneer.py" to the end of09:54
cs-shadowhttps://gitlab.com/BuildStream/buildstream/blob/master/MANIFEST.in#L2609:54
Kinnisoncs-shadow: I'll give that a go, ta09:54
benschubertjmac: thanks!09:55
adds68valentind, is there anyway to get a "node" without calling buildstream?09:56
Kinnisoncs-shadow: that got it through source_dist.  Thanks!09:56
valentindadds68, You mean to parse a file?09:57
cs-shadowKinnison: glad to hear that09:57
Kinnisoncs-shadow: I'd have been wandering in the reeds assuming it was a docker issue for hours otherwise09:57
adds68valentind, from the docs it says "Parameters:node (dict) – The loaded configuration dictionary"09:57
cs-shadowI am secretly rather happy that we hit this issue in the CI as I always had this issue with sdist locally and was procrastinating to create an issue :)09:58
adds68valentind, which the CollectManifestElement expects to receive?09:58
Kinnisoncs-shadow: hah10:00
Kinnisoncs-shadow: I tagged you in the MR, as thanks :-D10:00
valentindadds68, yes, configure expects a dict as parameter. Are you trying to test the plugin without running buildstream?10:01
adds68valentind, yea correct10:02
phildawsonCan anyone tell me what the fetch_subproject parameter in Stream._load does? I've followed it about 10 methods down so far and haven't got to the bottom yet. My assumption is that if true, the buildstream project files for any junctioned projects will be fetched, but that is just an assumption.10:02
*** catonano has quit IRC10:02
valentindphildawson, I think you are correct.10:03
Kinnisoncs-shadow: I fear even more fallout - I'm now seeing issues with "--integration" being an unknown argument.  URGH10:04
valentindphildawson, I think it fetches junctions during loading.10:04
* Kinnison thinks tlater[m] needs to weigh in on this10:04
valentindSo that means before the pipeline is scheduled.10:04
cs-shadowKinnison: I think that's because we are also missing conftest.py from the MANIFEST.in10:07
Kinnisoncs-shadow: I think MANIFEST.in is seriously underpopulated10:07
Kinnisonthe docs build is failing because none of the documentation is copied in either10:08
phildawsonthanks valentind10:08
valentindadds68, I do not think it is easy. But if you plan to make some unit testing tools for plugins, that can be interesting, but it is some work. Otherwise I would recommend just to test with .bst files that instantiate your plugin.10:08
cs-shadowKinnison: I agree. Essentially, at some point setuptools included a lot of stuff from the top-level without them being in the MANIFEST.in, which I think was a bug. And I guess it's been fixed now and we are seeing the fallout from that10:08
* Kinnison sets about sorting MANIFEST.in out10:08
adds68valentind, yea it seems extremely abstract, so i guess the pain is not worth it10:09
valentindadds68, there are already .bst files using the collect-manifest plugin in the fd.o sdk branch, have you seen them?10:10
adds68valentind, yea but this method of working is a bit verbose, i usually like to load stuff into iPython and play around with the objects10:11
tlater[m]Kinnison: That's pretty odd, the branch is essentially just master with that one commit on top.10:12
Kinnisontlater[m]: yay for non-strictly-constrained versioning10:12
* Kinnison can replicate the sdist issues so is updating MANIFEST.in to try and fix10:13
valentindadds68, real hackers debug with printf!10:13
adds68valentind, hahaha why was python chosen, we may as well of used C! :P10:13
skullmanargp *is* a better command-line parser than click10:16
skullmanbut no, I wouldn't suggest BuildStream even in jest10:17
skullmans/BuildStream/& be written in C/10:17
valentindadds68, Be happy it is not written in Pascal.10:17
* skullman locates more caffeine to reduce future typoing10:17
gitlab-br-botaevri closed issue #452 (Mistyped urls can cause a stack trace) on buildstream https://gitlab.com/BuildStream/buildstream/issues/45210:17
gitlab-br-botaevri merged MR !893 (aevri/unknown-uri-452->master: _downloadablefilesource: handle ValueError-s) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/89310:17
gitlab-br-botjmacarthur approved MR !886 (bschubert/remove-pytest-runner->master: Remove dependency on pytest-runner) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/88610:17
*** lachlan has quit IRC10:18
* tlater[m] picks up a new bit of `sed` magic10:18
*** lachlan has joined #buildstream10:19
skullmantlater[m]: if you want a bit of bash magic to go with it, {filedescriptor}<$filepath opens a file and puts the file descriptor number in $filedescriptor, instead of having to guess at which file descriptor number may be available10:21
skullmanhandy for if you're using flock10:21
* tlater[m] revels in newly acquired knowledge10:24
*** Prince781 has quit IRC10:34
tiagogomesWhat "Conflicting junction bootstrap-junction.bst in subprojects, define junction in xpad" exactly means?10:41
adds68do plugins only get called at build time?10:45
tiagogomesvalentind if project B junctions from project A, and project C junctions from project B, that's not allowed?10:49
*** phildawson has quit IRC10:49
adds68tiagogomes i think at the moment nested junctions are not supported?10:49
valentindtiagogomes, this is allowed.10:50
valentindBut you need to make sure that junctions of the same name are the same.10:50
valentindSo if A has B as junction and B as C as junction. If A also has a C as junction, it should be the same as the one in B. If you want to access to C from A directly, you should also have it in A.10:51
valentindtiagogomes, and the name is actually the name in project.conf I think.10:53
valentindOr no, I think you need to have matching names in project.conf for matching .bst filename for junctions.10:54
valentindThe error message however is not very good.10:56
WSalmoni think i have upset my system and am having this issue when i try to build the doc's https://hastebin.com/yupapaqeja.bash which is funny cos i was building them fine a few weeks ago, any one seen this one before and can tell me the issue before i spend time fixing it?11:00
gitlab-br-botBenjaminSchubert opened MR !898 (bschubert/fix-command-sandbox->master: Check is command is a str and replace by list before checking existence) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/89811:00
valentindtiagogomes, I think I know. You have 2 subprojects using a junction of the same name (the name of the .bst file). But this junction is not found in the top project. This seems to not be allowed.11:01
jmacWSalmon: Not seen that one, sorry. element_enums was changed a few weeks ago, but I've not seen that error, I'm afraid11:01
valentindAnd the matching project.conf name, I was wrong. It does not matter, we use only the .bst file name of the junction as identifier.11:02
WSalmonjmac, thanks11:02
tiagogomesvalentind actually I renamed the bst file on C to have the same filename as in B, and I think it worked11:02
tiagogomesWhich is odd, because the filename shouldn't matter, but rather the URL11:02
WSalmoni tried reinstalling to see if there was a problem, i suspect something is caching a old thing but i cant workout what i need to do to rebuild just that11:02
WSalmonyep a git clean -fxd fixed it11:04
jjardonhow can I force buildstream to rebuild a element?11:19
jjardonalso, is there any way to show all the configure / make logs when building?11:19
tiagogomesjjardon delete the ref from rm -rf ~/.cache/buildstream/artifacts/cas/refs11:20
*** Prince781 has joined #buildstream11:21
jjardontiagogomes: thanks, any idea about the second?11:21
tiagogomes--verbose or --debug?11:22
jjardontiagogomes: those options doesnt seem to exist11:23
tiagogomesjjardon bst --verbose --debug build …11:23
tiagogomesThey need to be placed before the subcommand11:23
jjardonah rigth11:23
jjardontiagogomes: still, no configure and make output after passing those11:24
jjardononly debug output of bst itself11:25
tpollardyou'll want bst show11:26
tpollardI believe11:26
tpollardit won't give logs but can show you what it's going to do11:27
jjardontpollard: I need to see the output of running configure and make over a element; not sure that would help11:28
coldtomjjardon: you can find the logs in the cache, but it's a bit of a pain11:30
jjardonindeed11:30
jjardontiagogomes: tiagogomes coldtom thanks, found it11:35
tiagogomeshow did you do it11:36
jjardonsearching on the ~/.cache/buildstream/logs/freedesktop-sdk/desktop-fftw/ folder11:36
jjardonsee which one is the newest as there are several files there11:37
jjardonso yeah not the best UX  :)11:37
gitlab-br-botjennis opened MR !899 (jennis/patch_remote_cache_docs->master: Improve our documentation for configuring an artifact server) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/89911:55
jennisKinnison, regarding yesterday, are you able to review this small docs patch?11:58
jennishttps://gitlab.com/BuildStream/buildstream/merge_requests/899/11:58
* Kinnison takes a peek11:58
jennisThe line lengths may need changing11:59
Kinnisonreviewed12:01
jennisKinnison: regarding the unrelated fix, I did add this to the commit message?12:02
jennisor should we still have this separate12:03
KinnisonSeparate commits please12:03
Kinnisonsame MR is fine12:03
Kinnisoncs-shadow: this MANIFEST.in problem is making me very sad.  I'm half tempted to replace the entire thing with "include-recursive . *"12:06
*** catonano has joined #buildstream12:07
jennisKinnison, changes made12:07
* Kinnison dislikes the whitespace cleanup being in a link correction commit12:08
Kinnisonthink about it, git annotate now says that the whitspace cleanup is related to a link correction12:08
KinnisonI'd avoid the whitespace cleanup unless changing the text around it12:09
Kinnisonjennis: also you don't appear to have taken on board my comment about rewording the explanation of /CN12:09
*** lachlan has quit IRC12:20
*** phildawson has joined #buildstream12:28
tiagogomesWhen stating multiple artifacts, if a path in one artifact is a symbolic link, and it is something else in another artifact; what happens?12:28
tiagogomes*staging12:29
laurencedo people get an email notification when someone gives the 'thumbs up' to a gitlab comment?>12:33
laurencehave been giving a few recently and am hoping i'm not creating spam mail12:33
cs-shadowlaurence: I don't think that it generates email notifications, at least I don't see them in my inbox12:41
cs-shadowKinnison: It's rather sad but once it is fixed, it should be relatively easier to keep it up to date12:42
Kinnisoncs-shadow: yeah except to avoid a screenful of crud, I ended up with things like "recursive-include tests *" which is a bit sadmaking12:43
valentindtiagogomes, That depends.12:45
valentindtiagogomes, Is it a directory in the other artifact?12:45
valentindtiagogomes, And does it contain something?12:46
valentindIf it is not a directory it will be an overlap. If it is a directory and the symlink is staged first, then no problem will happen. If it is a directory containing files and those files are staged before the symlink, then you will get an error message.12:48
laurencecs-shadow, cool, thanks12:51
Kinnisoncs-shadow: I think I've finally bottomed the MANIFEST.in stuff, I've pushed what I hope will be the last time I need to frob it12:51
Kinnisoncs-shadow: If you're okay with the changes, I'd appreciate a final OK on https://gitlab.com/BuildStream/buildstream/merge_requests/892 (obv. it needs to finish the tests successfully too)13:01
cs-shadowKinnison: was just looking at it :)13:01
Kinnison\o/13:01
jennisKinnison, !899 now includes your comments13:02
* Kinnison goes to re-review13:02
jennisThanks13:02
Kinnisonjennis: You can have a thumbsup13:03
jenniswhy thanks13:03
* Kinnison is impressed that laurence understood the SSL implications well enough to review too :-D13:03
jmactiagogomes, valentind: I've tried to capture the rules for this at https://wiki.gnome.org/Projects/BuildStream/ImportRules13:03
tiagogomesthanks jmac and valentind13:04
jennisI can see laurence as a participant but can't see his participation13:05
jennisoh, a thumbs up13:05
*** lachlan has joined #buildstream13:10
KinnisonOh for pity's sake13:15
Kinnisonthe coverage isn't working13:15
* Kinnison sobs13:15
Kinnisontlater[m], cs-shadow: If either of you have any idea how to resolve the newly exposed coverage issue (https://gitlab.com/BuildStream/buildstream/-/jobs/112652068) I'd appreciate pointers.  I am entirely beyond my comfort zone here :(13:20
* cs-shadow is taking a look but not sure what's going wrong13:26
tlater[m]Kin13:27
tlater[m]whoops13:27
tlater[m]Heh13:27
tlater[m]Kinnison: I won't have time today, but I'll try to merge it over the weekend if nobody else comes up with a solution by then.13:28
jennisHas anyone seen an error like this before: OPENSSL_internal:WRONG_VERSION_NUMBER when trying to pull from a remote cache13:28
Kinnisontlater[m]: Okay, thanks.  Hopefully someone will spot it before then :/13:28
jennis Handshake failed with fatal error SSL_ERROR_SSL: error:100000f7:SSL routines:OPENSSL_internal:WRONG_VERSION_NUMBER13:29
Kinnisonjennis: That sounds like the python ssl library you have is built against a different libssl to the one found at runtime13:29
jennisuhh ok13:29
tlater[m]jennis: That can only happen if you're not using distro packages for either of the two - I'd say that is more likely to be an issue on your server.13:30
jennistlater[m], distro packages of BuildStream?13:31
tlater[m]jennis: Distro packages for openssl/python13:32
jennisoh13:32
jennis(:13:32
gitlab-br-botjennis merged MR !899 (jennis/patch_remote_cache_docs->master: Improve our documentation for configuring an artifact server) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/89913:35
jennismhmm tlater server has it13:35
tlater[m]jennis: By "it" you mean the error?13:36
jennistlater[m], no, `apt install python-openssl` -> nothing needed to be done13:37
cs-shadowKinnison: I suspect we should be copying ".coverage" instead of/in addition to ".coverage.*" but I am trying to understand how it was working before.13:39
tlater[m]jennis: The issue is that `python-openssl` uses openssl libraries, and therefore needs to be compiled against something on your machine. Distro packages are downloaded pre-compiled, and it is assumed that you only use other distro packages. If you use a non-distro package, for example for openssl, then suddenly `python-openssl` will try to talk to something it doesn't know how to talk to.13:39
tlater[m]And that's what is probably causing your error.13:39
tlater[m]My other guess is mismatching protocols (i.e. one side uses an ancient version of a library involved), but I think that would be a different error - also I trust Kinnison knows enough about these errors to make an accurate guess ;)13:40
jennisconsidering the client I'm using, I wouldn't be surprised if it's the latter13:41
jennisthanks tlater[m]13:41
tlater[m]jennis: To figure out if they mismatch, write a small python script that does some openssl thing and see if it breaks13:41
cs-shadowKinnison: can you please try changing "cp .coverage.* ..." to "cp .coverage ..." here: https://gitlab.com/BuildStream/buildstream/blob/4247cef3985b4fa0a15ed02b7beae1dc1a9cd8f1/.gitlab-ci.yml#L8113:44
Kinnisoncs-shadow: I just rebooted, let me get my VM back up13:45
cs-shadowsure13:45
KinnisonOkay I've pushed that, let's cross fingers :-D13:47
* Kinnison nips to a brief meeting while CI runs13:47
* cs-shadow will keep an eye on the CI13:48
gitlab-br-botBenjaminSchubert opened issue #728 (SandboxBwrap incorrectly checks its arguments type for command) on buildstream https://gitlab.com/BuildStream/buildstream/issues/72813:51
*** lachlan has quit IRC14:02
raoulThink I've got remote job cancellation working, but it probably needs an integration test. Would having an integration test that runs if buildgrid is installed be alright?14:03
*** toscalix has joined #buildstream14:04
mablanchraoul: At the moment, the REAPI client is not tested, here is the opened issue tracking that: https://gitlab.com/BuildStream/buildstream/issues/62914:06
*** brlogger has joined #buildstream15:08
*** gitlab-br-bot has joined #buildstream15:16
*** lachlan has joined #buildstream15:16
KinnisonNice15:17
* Kinnison hi5s cs-shadow15:17
* cs-shadow hi5s Kinnison15:17
KinnisonAs a word of warning to anyone with open MRs, when you rebase for merge, be aware you may get new lint warnings \o/15:18
gitlab-br-botraoul.hidalgocharman opened MR !900 (725-job-cancellation-on-remote-builds->master: WIP: _sandboxremote.py: Add sigterm handler that sends CancelOperation) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/90015:19
*** anahuelamo- has joined #buildstream15:23
*** anahuelamo has quit IRC15:23
WSalmonthis looks quite interesting anyone else have any feed back for ben? https://gitlab.com/BuildStream/buildstream/issues/728 tlater[m] skullman tiagogomes15:29
*** lachlan has quit IRC15:32
bochechaI have a question which isn't directly related to buildstream, but I hope nobody will mind, it's about how builstream uses bwrap in its CI :)15:34
bochechawhenever i try using bwrap in docker, I get "bwrap: No permissions to creating new namespace, likely because the kernel does not allow non-privileged user namespaces. On e.g. debian this can be enabled with 'sysctl kernel.unprivileged_userns_clone=1'."15:34
bochechadoes the Buildstream CI do anything special to make this work?15:34
skullmanI think it may run as root, since we use the same kind of container to run the UNIX tests, and they *do* have to run as root.15:41
jjardonbochecha: the docker image runs with privileged permissions15:54
jjardonbochecha: this is the config of the runners:15:56
jjardonhttps://www.irccloud.com/pastebin/MqOwaTa0/15:56
*** lachlan has joined #buildstream15:58
*** lachlan has quit IRC16:11
*** abderrahim4 has joined #buildstream16:15
*** abderrahim3 has quit IRC16:16
*** lachlan has joined #buildstream16:17
*** xjuan has joined #buildstream16:31
benschubertWould people be against using pytest-timeout (https://pypi.org/project/pytest-timeout/) to set a per-test timeout? Some tests do block indefinitely for some reasons and that's quite hard to debug :/16:33
benschubertI'll open an issue if no strong opposition from here :)16:33
tpollardlooks interesting for debugging16:35
bochechajjardon: ok, that explains it then… unfortunately I don't control those runners, so I guess I just won't be able to do what I needed :(16:37
bochechajjardon: thanks for confirming16:37
*** bochecha has quit IRC16:41
gitlab-br-bottacgomes approved MR !898 (bschubert/fix-command-sandbox->master: WIP: Check is command is a str and replace by list before checking existence) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/89816:42
raoulI'm trying to add messages to a SIGTERM handler in _sandboxremote when it's called, via the context and then the message function, but they don't seem to get to output. Anyone got any idea why and how to get around it?16:44
*** tpollard has quit IRC16:46
*** raoul has quit IRC16:50
*** toscalix has quit IRC16:54
*** Prince781 has joined #buildstream16:57
gitlab-br-botcs-shadow closed issue #713 (Don't redundently document directory configuration in plugins) on buildstream https://gitlab.com/BuildStream/buildstream/issues/71316:59
gitlab-br-botcs-shadow merged MR !896 (chandan/source-doc-directory->master: plugins: Don't redundantly document common configurations) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/89616:59
*** jonathanmaw has quit IRC17:03
*** phildawson_ has joined #buildstream17:04
*** phildawson has quit IRC17:05
*** anahuelamo- has quit IRC17:05
*** anahuelamo has joined #buildstream17:06
*** anahuelamo has quit IRC17:07
*** anahuelamo has joined #buildstream17:07
*** Prince781 has quit IRC17:10
*** catonano has quit IRC17:12
*** loganlee has joined #buildstream17:13
*** Prince781 has joined #buildstream17:15
*** catonano has joined #buildstream17:19
*** Prince781 has quit IRC17:33
*** Prince781 has joined #buildstream17:40
gitlab-br-botBenjaminSchubert opened issue #730 (Show each warning only once when running tests) on buildstream https://gitlab.com/BuildStream/buildstream/issues/73017:56
*** Prince781 has quit IRC18:02
*** tuxcanfly has joined #buildstream18:06
*** Prince781 has joined #buildstream18:10
*** Prince781 has quit IRC18:18
*** alatiera_ has quit IRC19:01
*** catonano has quit IRC19:01
*** catonano has joined #buildstream19:17
*** Prince781 has joined #buildstream20:34
*** cs-shadow has quit IRC20:40
*** bochecha has joined #buildstream21:26
*** xjuan has quit IRC21:44
*** Prince781 has quit IRC21:46
*** Prince781 has joined #buildstream22:39
*** Prince781 has quit IRC23:14
*** catonano has quit IRC23:35
*** Caerus has joined #buildstream23:44
*** bochecha has quit IRC23:53

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