IRC logs for #buildstream for Tuesday, 2018-09-11

gitlab-br-botbuildstream: issue #644 ("Allow BuildStream to be installed in a remote-only mode?") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/64400:16
*** rdale has quit IRC02:05
*** tristan has joined #buildstream03:48
*** ChanServ sets mode: +o tristan03:48
gitlab-br-botbuildstream: issue #632 ("CAS server: Implement BatchReadBlobs") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/63204:23
*** leopi has joined #buildstream06:04
*** leopi has quit IRC07:06
*** leopi has joined #buildstream07:07
*** leopi has quit IRC07:11
*** leopi has joined #buildstream07:12
*** toscalix has joined #buildstream07:52
*** tristan has quit IRC08:07
*** tristan has joined #buildstream08:20
*** ChanServ sets mode: +o tristan08:21
toscalixtristan: reading your mail, are you planning to turn all those regressions into tickets or are you expecting developers to do it?08:23
*** rdale has joined #buildstream08:30
juergbijmac: is https://gitlab.com/BuildStream/buildbox/issues/2 still an issue? finn or mablanch, have you seen this or does it work for you?08:33
mablanchjuergbi: Nope, I don't remember seeing it.08:34
juergbita, closing it as needinfo for now08:46
tiagogomestristan we do it as well from the main process08:50
jmacI haven't tried a large enough build to reproduce it recently - happy to close it for now09:02
tiagogomesI wonder if before commit/pull/clean we should remove the cache_size, and rewrite it again when these operations finish, so that if something crashes there isn't a stale cache_size file09:03
*** tpollard has joined #buildstream09:04
*** bochecha has joined #buildstream09:06
gitlab-br-botbuildstream: merge request (richardmaw/element-cache-state-simplify->master: Simplify element state by removing `__cached`) #784 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/78409:07
*** abderrahim has quit IRC09:10
juergbiany opinions on what to call the repo for a buildstream project that builds buildbox? buildbox-integration?09:11
*** abderrahim has joined #buildstream09:11
KinnisonThat would follow skullman's suggestion for buildstream-integration being a buildstream project for building buildstream09:11
Kinnisonskullman: Did you stick with that in the end?09:11
skullmanI did, yes.09:11
juergbiok, let's go with that for now, ta09:12
*** jonathanmaw has joined #buildstream09:22
gitlab-br-botbuildstream: merge request (willsalmon/outOfSourecBuild->master: WIP: out of source builds) #776 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/77609:23
*** lachlan has joined #buildstream09:27
flatmushI'm looking at the patch documentation here: https://buildstream.gitlab.io/buildstream/sources/patch.html09:53
flatmushAnd it's not immediately obvious to me how I'd use that to apply a patch to a bst element.09:53
flatmushMy specific case is that I want to add the OpenSSL 1.1 patch to OpenSSH as documented here: http://www.linuxfromscratch.org/blfs/view/svn/postlfs/openssh.html09:53
flatmushCan anyone point me in the right direction?09:53
gitlab-br-botbuildstream: merge request (richardmaw/subprocess-PWD->master: WIP: Address post-merge review of Ensure PWD is set in process environment) #788 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/78809:53
*** lachlan has quit IRC09:54
gitlab-br-botbuildstream: merge request (richardmaw/subprocess-PWD->master: WIP: Address post-merge review of Ensure PWD is set in process environment) #788 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/78809:54
tpollardflatmush: freedesktop use patch with openssl here https://gitlab.com/freedesktop-sdk/freedesktop-sdk/blob/18.08/elements/base/openssl.bst09:56
flatmushtpollard: cool, thanks10:00
*** cs-shadow has joined #buildstream10:04
gitlab-br-botbuildstream: merge request (richardmaw/builddir-sockets->master: Fix: While caching build artifact: "Cannot extract [path to socket file] into staging-area. Unsupported type.") #783 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/78310:07
*** lachlan has joined #buildstream10:10
*** lachlan has quit IRC10:19
*** lachlan has joined #buildstream10:29
toscalixtiagogomes: can I add a License file in the website repo or that will impact the web?10:33
tiagogomesIt won't change anything regarding the website deployed10:34
*** lachlan has quit IRC10:34
toscalixok, thanks10:34
*** lachlan has joined #buildstream10:39
*** tristan has quit IRC10:44
*** lachlan has quit IRC11:11
*** jonathanmaw_ has joined #buildstream11:18
*** lachlan has joined #buildstream11:18
*** jonathanmaw has quit IRC11:18
*** lachlan has quit IRC11:21
*** lachlan has joined #buildstream11:25
*** lachlan has quit IRC11:29
*** alatiera_ has joined #buildstream11:37
*** alatiera_ has quit IRC11:39
*** lachlan has joined #buildstream11:41
*** leopi has quit IRC11:42
*** lachlan has quit IRC11:45
*** mohan43u has quit IRC11:47
*** mohan43u has joined #buildstream11:48
*** alatiera_ has joined #buildstream11:55
*** lachlan has joined #buildstream12:12
*** lachlan has quit IRC12:19
gitlab-br-botbuildstream: merge request (tpollard/494->master: WIP: Don't pull artifact buildtrees by default) #786 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/78612:28
WSalmonany one else getting:12:46
WSalmonPlease use node.get_closest_marker(name) or node.iter_markers(name).12:46
WSalmonDocs: https://docs.pytest.org/en/latest/mark.html#updating-code12:46
WSalmon  content = request.keywords.get('datafiles').args12:46
WSalmonPlease use node.get_closest_marker(name) or node.iter_markers(name).12:46
WSalmonDocs: https://docs.pytest.org/en/latest/mark.html#updating-code12:46
WSalmon  options.update(request.keywords.get('datafiles').kwargs)12:46
WSalmonwhen running ```python3 setup.py test --addopts --integration```12:46
WSalmonlocally12:47
WSalmonPlease use node.get_closest_marker(name) or node.iter_markers(name).12:47
WSalmonDocs: https://docs.pytest.org/en/latest/mark.html#updating-code12:47
WSalmon  content = request.keywords.get('datafiles').args12:47
WSalmonPlease use node.get_closest_marker(name) or node.iter_markers(name).12:47
WSalmonDocs: https://docs.pytest.org/en/latest/mark.html#updating-code12:47
WSalmon  options.update(request.keywords.get('datafiles').kwargs)12:47
jmacSounds familiar12:48
WSalmonirc is magling my message, i will paste bin12:48
WSalmonhttps://hastebin.com/nijiwikigu.sql12:48
jmacYep12:49
WSalmonoh, i have only just started seeing it12:49
jmac`pip3 install pytest-pylint==0.12.1` will get rid of it temporarily12:49
WSalmonlike maybe a week12:49
WSalmonta12:49
jmacThey've started appearing since pytest-pylint 0.12.2 appeared12:49
*** alatiera_ has quit IRC12:50
WSalmonits one thing to want but i get it like 1000 times12:50
WSalmonmaybe not tha much but like 90% of my terminal12:51
WSalmonscrollback12:51
WSalmon*its one thing to warn12:51
*** alatiera_ has joined #buildstream12:52
WSalmoninteresting that the ci is still using 0.12.1 i wonder if its pegged in there..12:53
gitlab-br-botbuildstream: merge request (richardmaw/subprocess-PWD->master: Address post-merge review of Ensure PWD is set in process environment) #788 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/78812:55
*** alatiera_ has quit IRC12:55
*** alatiera_ has joined #buildstream13:03
*** lachlan has joined #buildstream13:34
ikerperezI had some error when building a project with Buildstream in my Debian laptop that doesn't happen when I try it in ubuntu. When I build the project in Debian at some point it start to create directories inside ~/.cache/buildstream without never stopping and finally leads into a linking error14:31
*** lachlan has quit IRC14:31
ikerperezThe results is a directory like ~/.cache/buildstream/A/B/A/B/A/B/A/B14:32
ikerperezI haven't been the only one that had this error14:32
tlater[m]ikerperez: Most devs use debian, so I think it's unlikely to be distro specific. That said, do you have logs for this you could share, perhaps open an issue?14:33
*** lachlan has joined #buildstream14:35
flatmushThe issue I was having a week or two ago where there seemed to be a recursive variable issue was also on a standard debian install14:35
flatmushthe issue iker describes on debian is very similar14:36
ikerperezI shared them on Monday. I don't have them now but I will produce them again14:36
flatmushit's possible that there's an undocumented dependency that's not there by default on debian?14:36
toscalixif that is the case, it would be good to add it to the feature page: https://buildstream.build/feature.html14:37
* tlater[m] thinks it's unlikely, variables are resolved by buildstream itself14:38
tlater[m]But weirder things have happened14:38
toscalixtiagogomes: when you can, I hopefully addressed your concerns: https://gitlab.com/BuildStream/website/merge_requests/7714:38
gitlab-br-botbuildstream: merge request (mac_fixes->master: WIP: Implement compatibility fixes for MacOSX and WSL Blocks #411 and #412") #726 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/72614:39
gitlab-br-botbuildstream: merge request (mac_fixes->master: WIP: Implement compatibility fixes for MacOSX and WSL Blocks #411 and #412") #726 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/72614:42
*** hergertme_ has joined #buildstream14:44
*** lachlan has quit IRC14:44
*** hergertme has quit IRC14:44
*** lachlan has joined #buildstream14:45
flatmushtlater[m]: I'm not sure the issue is to do with variables14:46
tlater[m]I think it's more likely to be a regression from some CAS changes that seem to have happened recently14:47
tlater[m]Probably a slight mistake in an algorithm somewhere14:47
flatmushAll I know is that every time we've tried to run with debian, it has failed with similar looking errors. The quickest way to resolve this has been to install Ubuntu. Might be worth having some CI to test this kind of thing?14:47
tlater[m]flatmush: We do, we test on debian, ubuntu and fedora to my knowledge14:48
tlater[m]Hence I sort of believe that the distro is just a coincidence. But it's possible that some sort of dependency mess happens - in any case we'll need logs to debug, this is all conjecture :)14:50
flatmushthis is the log for my issue: https://gitlab.com/trustable/distros/minimal-distro/-/jobs/9341186114:56
flatmushthe same code worked fine when I installed Ubuntu on the CI runner14:56
tlater[m]This is definitely interesting...15:01
tlater[m]flatmush: Is there an issue for this yet? I don't have the time to debug it right now, unfortunately, and it looks like nobody else is chiming in either.15:03
flatmushI could never really characterize the issue well enough to write a detailed bug report, and I wondered if it was just an odd issue with my install15:04
flatmushthe only reason I'd add weight to this is that iker seems to be having a very similar issue15:04
tlater[m]flatmush: That log and the exact circumstances in which you trigger it is enough detail IMO. More important that we know it's out there than that it's easy to debug.15:06
ikerpereztlater[m], this are the logs https://paste.gnome.org/pqfh04sb215:07
tlater[m]Thanks ikerperez15:07
tlater[m]Interesting that it;s /lib/debug/tools15:08
tlater[m]iirc that touches a patch Sam Thursfield wrote not too long ago.15:08
*** lachlan has quit IRC15:08
* tlater[m] will write an issue and have a look at it some other day15:08
mablanchjuergbi: For BuildBox pre-fetch support, you are implementing and using BatchReadBlobs() right? Not GetTree()?15:13
gitlab-br-botbuildstream: issue #645 ("Obscure Bug when using Buildstream on Debian") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/64515:13
*** robjh has joined #buildstream15:14
flatmushikerperez: Can you attach your logs and a description to this: https://gitlab.com/BuildStream/buildstream/issues/64515:14
ikerperezsure15:16
gitlab-br-botbuildstream: issue #646 ("BuildStream attempts to create very long filenames after finisihing a build") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/64615:17
gitlab-br-botbuildstream: issue #646 ("BuildStream attempts to create very long filenames after finisihing a build") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/64615:20
robjhHi all. I'm getting this error when trying to build base.bst15:23
robjh[00:00:03][866680d4][fetch:base.bst                      ] FAILURE 403 Client Error: Forbidden for url: https://production.cloudflare.docker.com/registry-v2/docker/registry/v2/blobs/sha256/5e/5e4eaac9a3437e1b74ba3d71d11b6dbd3822a11eab91049fb185e0ce3ef28fd3/data?verify=1536681998-ChxlDoJ%2BmY9gcpGfNRXmdRaOzdc%315:23
robjhThe weird thing being, i can access that url using a browser, but curl gives me this: {"status":403,"message":"Error: invalid URL signature"}15:23
*** lachlan has joined #buildstream15:24
persiarobjh: BuildStream performs builds in a sandbox without network access, so you'll need to pre-download things and make sure that the build script can use the pre-downloaded copies.15:33
persia(unless I misunderstand, in which case someone else csn likely provide better support)15:33
juergbimablanch: yes, only BatchReadBlobs() for now. GetTree() might actually be slower in the case where most of the tree is already in the local cache. also, not sure whether BatchReadBlobs() alone is ever substantially slower than using GetTree()15:34
juergbipersia: this doesn't seem to be in the sandbox15:36
mablanchjuergbi: Make sense for BuildBox. When you've got nothing locally GetTree() is nice in that you don't have to fetch sub-Directories one by one for full recursive download.15:36
robjhpersia, i didnt write this module, but it's bst file doesnt reference that url directly15:36
juergbirobjh: I get 403 here in the browser as well. does this URL require credentials that your browser has stored?15:37
* persia is now curious what the problem ends up being15:37
juergbiit might be a redirect15:37
juergbiwhat URL is in that base.bst then?15:37
robjhjuergbi, to my knowledge, ive not logged into cloudflare.docker.com before15:37
juergbimight be regular docker.com login15:38
*** lachlan has quit IRC15:39
robjhthe git log shows that tlater[m] wrote this bst file. so he might be able to weigh in. the files contests are as follows;15:40
robjhkind: import15:40
robjhsources:15:40
robjh- kind: docker15:40
robjh  image: buildstream/image-tools15:40
robjh  track: latest15:40
robjh  ref: 2b959153ad739754b1882cfe3445fe22b3a6e72099101f30c6ea76240c92d7615:40
tlater[m]Hmm15:41
tlater[m]It's been at least a month since I last tried our docker plugin15:41
tlater[m]It's possible dockerhub changed15:41
* tlater[m] thinks cs-shadow would know best15:41
tlater[m]I have not seen that particular error myself, at any rate15:42
robjhtlater[m], when you access that url do you get a byte stream or a 403 error?15:43
tlater[m]403 on my end15:43
tlater[m]That is manually accessing it with a browser however. It's possible dockerhub refuses access if you send headers that it doesn't expect.15:44
robjhit works for me from a browser (from the codethink office) but not from curl, and not from the `bst build base` command15:45
tpollarddoes not work for me on a browser in said office15:46
tlater[m]That *does* sound like they changed the requirements for what clients can access it. robjh, tpollard  out of interest, which browser/version?15:47
robjhlol. im now getting {"status":403,"message":"TypeError: Invalid URL string."} in my browser15:48
robjhAnyway; Firefox ESR 52.8.015:48
juergbirobjh: the URL indeed looks wrong15:49
juergbiit ends with %3, i.e., incomplete escaped character15:49
juergbidon't know whether that's just cut off in the console or whether that's related to the actual issue15:50
robjhahhh... maybe i copied it wrong15:50
robjhThe last character is D15:51
tlater[m]With that I do get a byte stream15:52
robjhokay, good. and now bst has stopped complaining too15:53
gitlab-br-botbuildstream: merge request (willsalmon/outOfSourecBuild->master: WIP: out of source builds) #776 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/77615:53
robjhso something weird was happening and now it isnt. im going to go ahead and blame CDN pixies15:53
robjhsorry for the bother everyone :)15:54
tlater[m]Haha, damn gremlins15:54
robjhi'll be back if it happens again ;)15:54
*** lachlan has joined #buildstream15:57
*** lachlan has quit IRC16:28
*** lachlan has joined #buildstream16:38
*** toscalix has quit IRC16:39
cs-shadowtlater[m]: robjh: Sorry I missed your ping earlier but happy that it works now16:45
robjhcs-shadow, no worries. we're blaming CGN gremlins (but it was probably me being stupid) :)16:46
*** lachlan has quit IRC16:47
*** lachlan has joined #buildstream16:56
*** ikerperez has quit IRC16:57
*** jonathanmaw_ has quit IRC17:02
*** alatiera__ has joined #buildstream17:31
*** lachlan has quit IRC17:32
*** alatiera_ has quit IRC17:33
robjhso, these buildstream is working, how would i make it give me an image for an alternate architecture? Or would i need to run it on that architecture?17:57
gitlab-br-botbuildstream: issue #647 ("BuildStream occasionally tries to copy files in alphabetical order rather than safe linking order") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/64718:04
juergbirobjh: a buildstream project may support cross compilation, in which case there should be a project option for the target architecture18:11
cs-shadowrobjh: You can just specify the architecture and os like so: https://gitlab.com/BuildStream/bst-external/blob/master/bst_external/sources/docker.py#L4618:11
* cs-shadow will try to find a better documentation link18:12
juergbihowever, I expect most buildstream projects not to support cross compilation, which means you actually need to run bst on another architecture18:12
juergbi(with remote execution things will be more flexible)18:12
juergbics-shadow: this will select the docker image but it still requires a compatible host (or an emulator)18:14
robjhjuergbi, cs-shadow, thanks for your respective inputs18:15
cs-shadowjuergbi: That's right. My point is only valid if one wants to download the docker image for another arhictecture18:15
cs-shadowbut yeah, the build might not work after that18:15
robjhi guess the easiest thing to do would be to bring a raspberry pi into work tomorrow :)18:16
*** rdale has quit IRC19:42
*** xjuan has joined #buildstream21:54
*** bochecha has quit IRC22:16
*** mohan43u has quit IRC22:36
*** mohan43u has joined #buildstream22:39
*** alatiera__ has quit IRC23:21

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