IRC logs for #buildstream for Wednesday, 2018-08-22

*** alatiera_ has joined #buildstream03:08
*** alatiera_ has quit IRC03:19
*** alatiera_ has joined #buildstream03:35
*** dtf has quit IRC04:40
*** tristan has joined #buildstream04:53
*** ChanServ sets mode: +o tristan04:53
gitlab-br-botbuildstream: merge request (tristan/notifications->master: _frontend/linuxapp.py: Fix special casing around desktop notification escape sequence) #692 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/69204:54
gitlab-br-botbuildstream: merge request (tristan/pin-pytest-pylint->master: WIP: dev-requirements.txt: Pinning required pytest and pylint versions) #684 changed state ("closed"): https://gitlab.com/BuildStream/buildstream/merge_requests/68404:56
gitlab-br-botbuildstream: merge request (chandan/pypi-prep->master: setup.py: Add fields required for publishing on PyPi) #695 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/69505:23
gitlab-br-botbuildstream: merge request (tristan/notifications->master: _frontend/linuxapp.py: Fix special casing around desktop notification escape sequence) #692 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/69205:25
*** leopi has joined #buildstream05:29
gitlab-br-botbuildstream: merge request (willsalmon/versionTagRegrex->master: WIP: Search for tags with the *.*.* patten for version) #601 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/60105:52
gitlab-br-botbuildstream: merge request (willsalmon/versionTagRegrex->master: WIP: Search for tags with the *.*.* patten for version) #601 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/60105:52
gitlab-br-botbuildstream: merge request (jonathan/faster-except-elements-1.2->bst-1.2: Pipeline: Skip except_elements logic if no elements to except) #691 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/69105:54
tristanjuergbi, do you have an alternate take on whether we should unconditionally remove `.la` files instead of using split rules https://gitlab.com/BuildStream/buildstream/merge_requests/683 ?05:56
juergbiI'm a bit conflicted here. on one hand I'm in favor of removing .la files as they are not needed but occasionally cause trouble on Linux. however, I also don't like imposing so much policy from buildstream core05:58
juergbiI already think the current defaults do too much05:58
tristanyeah, I also don't like imposing this from BuildStream, while I have suffered .la issues for years; I don't see how they can cause build time problems with BuildStream06:04
tristanand also agree, we probably need to rethink strip commands and move them out of core06:04
tristanjuergbi, oh, and this patch from valentind looks correct to me, but I wonder is there a more efficient way than the loop employed here: https://gitlab.com/BuildStream/buildstream/merge_requests/685/diffs ?06:06
tristanit's about cleaning up CAS extracts06:06
tristan"how to find every ref which refers to this tree"06:06
juergbicould read meta/keys.yaml06:10
juergbi.la files: I don't remember the details but I think many distros remove them as well and I don't see why BuildStream would be less problematic in this regard than other distros (especially in non-strict mode)06:13
*** coldtom has joined #buildstream06:13
juergbior rather, distros using other build systems06:13
tristanjuergbi, I think it is less problematic because there is only ever one .la file for a given library installed at once06:16
tristanBut, that is just the nature of the headaches I've had with .la files, there could be others I'm not aware of06:16
juergbiis the same in my distro and I also had .la file issues, dropped .la files many years ago06:17
juergbialso, it's possible to install multiple versions of a library with buildstream as well06:18
tristanhmmm06:19
tristanjuergbi, regarding keys.yaml, I don't think that fixes the loop; the loop is to find out if there are any other artifact refs which have identical content06:19
juergbias the content SHA includes the meta directory, there shouldn't be any other refs than those in keys.yaml, or am I missing something?06:20
juergbii.e., other builds with identical content would still use deduplication for files but would use a different extract dir06:21
tristanYou are probably not missing anything, I am :)06:21
juergbiI was thinking about this myself before, though, it is indeed confusing with so many different hashes06:22
gitlab-br-botbuildstream: issue #385 ("Should notify when build fails") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/38506:24
gitlab-br-botbuildstream: merge request (tristan/notifications->master: _frontend/linuxapp.py: Fix special casing around desktop notification escape sequence) #692 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/69206:24
tristanjuergbi, ah I see what you mean; two artifacts can never be identical06:24
tristanindeed06:25
tristanas the cache keys are themselves encoded06:25
tristanjuergbi, it would be nice if you could comment on the .la files thing... personally I would like to encourage/test/improve the codepaths we explicitly layed out for the purpose of splitting and reducing output sizes06:27
juergbi(and logs are also rarely bit-for-bit identical)06:27
tristanbut it could still be a good idea to remove the .la files if we really know they dont help anyone at all06:27
juergbiImageMagick actually needs them (or at least it used to) but it's trivial to patch06:29
tristanHmmm06:30
tristaneven if we read keys.yaml in that loop...06:30
tristando we still need to discover if there is another weak key leading to this tree ?06:30
tristanOr, I wonder if we even need to read keys.yaml at all06:31
juergbireading keys.yaml would be to replace the loop06:31
tristananother weak key cannot lead to this tree06:31
juergbicorrect, the same weak key can lead to multiple artifacts06:31
juergbibut a single artifact only ever has one weak key06:31
tristanright06:32
juergbithe loop should work fine. keys.yaml would be a potential optimization to avoid iterating over all keys of an element06:32
juergbiunlikely to make a big difference in practice06:32
juergbibut depends on how many old keys stay around in the cache06:32
tristanah06:33
tristanRight, I wasn't catching on to the os.listdir() being that limited06:33
* tristan heads out to lunch06:36
*** tristan has quit IRC06:39
gitlab-br-botbuildstream: merge request (jonathan/faster-except-elements-1.2->bst-1.2: Pipeline: Skip except_elements logic if no elements to except) #691 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/69106:51
*** tristan has joined #buildstream07:18
*** tristan has quit IRC07:19
*** tristan has joined #buildstream07:19
*** ChanServ sets mode: +o tristan07:19
*** toscalix has joined #buildstream07:35
*** WSalmon has joined #buildstream07:35
*** toscalix has quit IRC07:39
WSalmonhi tristan, you have mentioned that you want https://gitlab.com/BuildStream/buildstream/merge_requests/601 merging, i had put it in wip while i work out how to test but the only code that is really "our's" is the exception, given your comment shall i just merge, i did think of some test but they all involved running git to add tags to the main code base which seems very silly to me, i was wondering about making a sample git repo like the git07:39
WSalmontests do but then getting bst to run inside that might be a faff.07:39
*** toscalix has joined #buildstream07:40
*** toscalix has quit IRC07:41
*** toscalix has joined #buildstream07:42
tristanWSalmon, agreed... lets just merge... only one thing...07:53
tristanWSalmon, let's make sure that the commit message has a link to the upstream bug report/patch for versioneer07:54
tristannow that I think of it, in case the commit message doesnt already have it07:54
WSalmoni did think of that the other day and forget, will do07:55
tristanWSalmon, thanks :)07:56
tristanOne more problem in the rear view07:56
*** rdale has joined #buildstream08:04
gitlab-br-botbuildstream: merge request (willsalmon/versionTagRegrex->master: WIP: Search for tags with the *.*.* patten for version) #601 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/60108:04
gitlab-br-botbuildstream: merge request (willsalmon/versionTagRegrex->master: WIP: Search for tags with the *.*.* patten for version) #601 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/60108:05
*** qinusty has joined #buildstream08:06
*** sstriker has quit IRC08:06
gitlab-br-botbuildstream: merge request (willsalmon/versionTagRegrex->master: Search for tags with the *.*.* patten for version) #601 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/60108:08
gitlab-br-botbuildstream: merge request (willsalmon/MR601-backport->bst-1.2: Willsalmon/mr601 backport) #696 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/69608:22
*** jennis has joined #buildstream08:37
*** solid_black has joined #buildstream08:40
tristanoh, juergbi; sorry to ping you a lot today but... any thoughts on how to fix #461 https://gitlab.com/BuildStream/buildstream/merge_requests/669#note_95498854 ?08:45
juergbioh, I forgot about that, will take a look08:48
*** WSalmon has quit IRC08:50
tristanI think it's difficult :-S08:51
*** WSalmon has joined #buildstream08:52
gitlab-br-botbuildstream: merge request (tristan/debug-symbols-location->master: Don't strip pathname from debug symbol files) #697 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/69708:54
*** jonathanmaw has joined #buildstream08:57
gitlab-br-botbuildstream: merge request (tristan/debug-symbols-location-1.2->bst-1.2: Don't strip pathname from debug symbol files) #698 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/69809:00
gitlab-br-botbuildstream: merge request (sam/debug-symbols-location->master: Don't strip pathname from debug symbol files) #529 changed state ("closed"): https://gitlab.com/BuildStream/buildstream/merge_requests/52909:02
gitlab-br-botbuildstream: merge request (valentindavid/extract-expiry->master: Remove artifact extracts when artifact expires in cache) #685 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/68509:11
tristanWSalmon, any reason why https://gitlab.com/BuildStream/buildstream/merge_requests/696 is not merged ?09:29
WSalmonoh09:29
tristanI've been waiting and watching the pipelines, ready to rebase Sam's fix for strip-commands after your two branches land09:29
WSalmonno09:29
WSalmonthe main one was merge on pipeline complete09:29
WSalmoni was gona ask if you want it to merge straight away or do a mini review09:30
tristanWSalmon, I think we did that already before, you updated the commit message right ?09:30
tristanWSalmon, please merge them :)09:31
gitlab-br-botbuildstream: merge request (willsalmon/MR601-backport->bst-1.2: Willsalmon/mr601 backport) #696 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/69609:31
gitlab-br-botbuildstream: merge request (tristan/debug-symbols-location-1.2->bst-1.2: Don't strip pathname from debug symbol files) #698 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/69809:31
gitlab-br-botbuildstream: merge request (willsalmon/versionTagRegrex->master: Search for tags with the *.*.* patten for version) #601 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/60109:33
gitlab-br-botbuildstream: merge request (tristan/debug-symbols-location->master: Don't strip pathname from debug symbol files) #697 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/69709:34
tristanWSalmon, thanks09:35
gitlab-br-botbuildstream: merge request (chandan/pypi-prep-1.2->bst-1.2: setup.py: Add fields required for publishing on PyPi) #699 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/69910:11
gitlab-br-botbuildstream: merge request (chandan/pypi-prep-1.2->bst-1.2: setup.py: Add fields required for publishing on PyPi) #699 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/69910:11
tristancs-shadow, nice, I was going to chase that down right now haha :)10:11
cs-shadow:) just in time10:12
tristancs-shadow, so what do you think our chances are of getting this all through by release ?10:12
tristanWe really need to clean up the install story (you'll notice I added the docs task to the related issue)10:13
cs-shadowtristan: this is definitely doable, we should be able to release it right now if we want to. The only thing to sort out is the automation but in the worst case, we can do publish it manually10:13
tristanI think it doesnt need to be automated by then, that's a bit more of a nice-to-have10:13
tristanyeah10:13
cs-shadowyeah, and thanks for adding the docs task. I'll pick that up next10:14
tristancs-shadow, Ok... so let's do that as soon as we land it in bst-1.2; we will need a new RC for it10:14
cs-shadowI can do a developer release on test-pypi so that people can try10:14
* cs-shadow needs to run to a meeting now but will catch up in ~30 mins10:15
tristanSo here's a game plan, we land that change in bst-1.2; and I'll try to release an RC today or tomorrow10:15
tristanAnd then we'll have a 1.1.x released on PyPI, and get the docs spinning based on that10:15
tristanso it should all come together well in advance of the release10:15
tristancs-shadow, sure :)10:15
cs-shadowSounds good10:16
gitlab-br-botbuildstream: merge request (tristan/debug-symbols-location->master: Don't strip pathname from debug symbol files) #697 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/69710:38
jennisHi all, so with the virtual directories patch, which is yet to be backported to bst-1.2, I've come across a PermissionError when trying to move files from a temporary directory to a virtual directory10:39
tristanvirtual directories10:40
jennisI assume it's because we don't have  the rights to delete these files, which happens when we call `vdirectory.import_files()`10:40
tristanAre you sure that belongs in bst-1.2 ?10:40
jennisNo its **not** in bst-1.210:40
jennishttps://paste.gnome.org/pddlrpk6l here is a stack trace of my problem10:40
tristanBut you said "yet to be backported" so... I'm wondering... I think this is related to remote execution isn't it ?10:40
jennisOh, tristan because I've been using bst-1.2 up until now, but wanted to test an element that uses the pip source plugin, so I switched to master, and found this bug10:41
tristanI see10:41
jennisWhich occurs immediately when trying to import my base image10:42
tristanDon't mind me then :)10:42
qinustyCan I get a review on https://gitlab.com/BuildStream/buildstream/merge_requests/670/ if anyone has some free time?10:43
tristanI will turn my attention to master much more in a week or two after release, I expect jmac and others working on vdirectory will be interested in your report, though :)10:43
jennisSo at some point, this import_files is calling os.unlink, which is essentially os.remove(), and this doesn't have the permission to remove files from the temp dir10:43
jennisHere is the function call: https://gitlab.com/BuildStream/buildstream/blob/master/buildstream/element.py#L137910:43
gitlab-br-botbuildstream: merge request (Qinusty/597-non-alias-url-fix->master: WIP: Qinusty/597 non alias url fix) #700 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/70010:45
jennisDoes anyone have any ideas how we could solve this?10:45
jennisOtherwise I'll write up an issue10:45
toscalixtristan: based on the BuildStream calendar, we release 1.2 RC2 tomorrow10:46
toscalixcalendar link: https://calendar.google.com/calendar/embed?src=codethink.co.uk_mpgah0uj538hnbsf4l7b4rchts%40group.calendar.google.com&ctz=Atlantic%2FCanary10:47
tristantoscalix, good timing then10:48
*** bochecha has joined #buildstream10:55
gitlab-br-botbuildstream: issue #601 ("PermissionError when calling `vdirectory.import_files()`") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/60111:00
gitlab-br-botbuildstream: merge request (chandan/pypi-prep-1.2->bst-1.2: setup.py: Add fields required for publishing on PyPi) #699 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/69911:11
gitlab-br-botbuildstream: merge request (valentindavid/faster_startup-1.2->bst-1.2: Use ArtifactCache's get_cache_size when calculating the quota) #701 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/70111:24
gitlab-br-botbuildstream: merge request (valentindavid/faster_startup-1.2->bst-1.2: Use ArtifactCache's get_cache_size when calculating the quota) #701 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/70111:25
tristanqinusty, I don't really have time to review thoroughly the logging refactor, but I've added some more comments to here: https://gitlab.com/BuildStream/buildstream/merge_requests/67011:26
tristanqinusty, in general, I worry that this branches direction favors removing LOC too much, risking legibility and coherency in favor of less LOC11:28
*** claro has joined #buildstream11:33
gitlab-br-botbuildstream: issue #578 ("--debug option leads to a traceback") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/57811:33
tristanOh crap11:35
tristan /o\11:35
valentindjuergbi, do you have an opinion on !669? How to do it differently? It is a potentially serious bug, and I think we need a fix in 1.2.11:35
tristanhttps://gitlab.com/BuildStream/buildstream/merge_requests/699 gets *merged*, while I have a pipeline that took hours to complete, which was ahead of 699 in the queue :'(11:35
gitlab-br-botbuildstream: merge request (tristan/debug-symbols-location-1.2->bst-1.2: Don't strip pathname from debug symbol files) #698 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/69811:36
cs-shadowtristan: i'm sorry, i didn't know you had other things in the queue already11:37
tristanhttps://gitlab.com/BuildStream/buildstream/merge_requests/698 ... that'll only take another one hundred and twenty three minutes and fourty one seconds11:37
juergbivalentind: I've taken a look but need to give it some more thoughs11:37
tristancs-shadow, it's just frustrating, here I am trying to close things :-/11:38
tristancs-shadow, I really didn't expect your pipeline, which was started a good twenty minutes later, to beat me heh11:38
juergbitristan: maybe we're too fast moving for semi-linear history11:38
tristanjuergbi, I don't know; it's a balance; the problem is surely compute anyway11:39
gitlab-br-botbuildstream: merge request (tristan/debug-symbols-location->master: Don't strip pathname from debug symbol files) #697 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/69711:39
cs-shadowtristan: I can definitely understand. I lost couple of races when trying to land the source transform stuff11:39
tristanjuergbi, sometimes a run takes < 30min, other times > 100min11:39
juergbiyes, if/when CI gets faster, it should be less of an issue11:39
tristanI can force this one through, in fact11:40
tristanbut meh11:40
tristandisheartening11:40
cs-shadowAnything over 30mins is really bad11:40
valentindjuergbi, OK. Thank you.11:43
tristanWe could disable the test CI on master and protected branches at least11:48
tristanAnd only do the docs build + publish part when running on master11:48
tristanThat way we have only pre-merge CI for the heavy duty stuff11:48
tristanwell, not *that* heavy duty, but still will reduce a lot of the load11:49
tristanits already redundant that the tests run pre/post merge11:49
qinustyCheers tristan, I'll have a look through the comments and leave some of my thoughts, we can come back to this next week or so if it needs more thought. It don't see it being backported so there no urgency on getting it done11:52
*** tristan has quit IRC12:05
gitlab-br-botbuildstream: merge request (BenjaminSchubert/fix-quota-tests->master: Mock storage space checks for tests.) #702 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/70212:09
gitlab-br-botbuildstream: merge request (fix-quota-tests->master: Mock storage space checks for tests.) #635 changed state ("closed"): https://gitlab.com/BuildStream/buildstream/merge_requests/63512:10
*** tristan has joined #buildstream12:18
*** ChanServ sets mode: +o tristan12:18
toscalixvalentind: who needs to approve https://gitlab.com/BuildStream/buildstream/merge_requests/701 ?12:26
valentindtoscalix, not sure.12:43
valentindjonathanmaw, I am backporting one commit from you. Can you look at !701 to say if you are fine with that?12:43
gitlab-br-botbuildstream: merge request (valentindavid/faster_startup-1.2->bst-1.2: Use ArtifactCache's get_cache_size when calculating the quota) #701 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/70112:45
jonathanmawvalentind: 👍12:47
*** noisecell has quit IRC12:49
gitlab-br-botbuildstream: merge request (tristan/debug-symbols-location-1.2->bst-1.2: Don't strip pathname from debug symbol files) #698 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/69813:04
gitlab-br-botbuildstream: merge request (Qinusty/597-non-alias-url-fix->master: Fix ValueError traceback for URL without alias or URI scheme) #700 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/70013:07
qinustyhttps://gitlab.com/BuildStream/buildstream/merge_requests/700 is ready for review if anyone fancies a quick review13:08
bochechawhen `bst build` finds everything in the remote cache and just pulls it all, why does it then pushes it all back? that seems like a big waste of time :-/13:09
qinustyIt doesnt push bochecha, *Dives into issues to find this*13:10
qinustyhttps://gitlab.com/BuildStream/buildstream/issues/55113:11
bochechaqinusty: interesting13:12
qinustyBasically, BuildStream still goes into the Push job, but the cache server will already have the artifact. Therefore skip13:12
bochechaqinusty: I do see some of those SKIPPED messages13:12
bochechabut not always13:12
qinustyOh really? buildstream version?13:12
bochechashould be on the 1.2 branch, commit hash is 970c6696f2eef0bde282f82eb95ae4708ccbf30813:13
qinustyHas it pulled an artifact generated by an earlier version of buildstream?13:13
bochechafor example, I see:13:13
bochecha[--:--:--][b7f2a886][ pull:basesdk-debug.bst             ] INFO    Downloaded artifact b7f2a88613:13
bochecha[00:13:21][b7f2a886][ pull:basesdk-debug.bst             ] SUCCESS freedesktop-sdk/basesdk-debug/b7f2a886-pull.106.log13:13
bochechafollowed further down by:13:13
bochecha[--:--:--][b7f2a886][ push:basesdk-debug.bst             ] INFO    Pushed artifact b7f2a88613:13
bochecha[00:00:06][b7f2a886][ push:basesdk-debug.bst             ] SUCCESS Pushing artifact b7f2a88613:13
gitlab-br-botbuildstream: merge request (coldtom/autotools-libtool->master: Upstream freedesktop-sdk autotools config) #683 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/68313:14
bochechaqinusty: no, we have definitely rebuilt (and thus pushed) stuff since the last time we updated bst13:14
bochechaqinusty: here's a job as an example: https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/jobs/9123166913:15
qinustyInteresting, I would have to assume it is something to do with cache keys etc. It is actually being timed as 6s which confirms that it's not skipping.13:20
bochechaall those few seconds on many elements add up :)13:21
bochecha(granted, that's certainly not the worst offender for why our CI takes so long :P)13:21
qinustyAgreed13:21
qinustyIt is definitely an issue13:22
qinustyI will happily look into it, just trying to think of how to reproduce this without triggering your build of x hours :P13:22
gitlab-br-botbuildstream: merge request (valentindavid/faster_startup-1.2->bst-1.2: Use ArtifactCache's get_cache_size when calculating the quota) #701 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/70113:22
bochechashould I reopen #551?13:22
qinustyGo ahead, it's clearly a separate issue. If you could link that CI job and reference an element which you see the issue on (b7f2a886) then it'll help13:23
bochechaby "a separate issue", you mean I should open a new one?13:24
qinustyNo, sorry. Separate from what I thought initially13:24
qinustySame issue, incorrect assumed solution :D13:25
gitlab-br-botbuildstream: issue #551 ("Artifacts are being pushed just after being pulled from the CAS cache") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/55113:25
bochechaqinusty: done, thanks for the hints :)13:28
jmacjennis: I want to try and reproduce issue #601 - is it bootstrap.bst from freedesktop-sdk? Anything unusual about your environment like unix?13:29
qinustyCould I clone freedesktop-sdk and reproduce this build locally using the testcache to see the issues?13:29
qinustybochecha ^13:29
bochechaqinusty: sure… you won't be able to push, though, I guess :-/13:29
qinustyMakes sense... But I could get to the point at which it TRIES to push13:30
qinustyOne would assume13:30
bochechaprobably13:30
qinustyDo we have any documentation surrounding the install of bst-external?13:34
*** noisecell has joined #buildstream13:36
bochechaqinusty: not that I know of, I just `pip install --user git+https://…`13:36
coldtomi clone and pip install --user .13:38
coldtombut i can't recall documentation on it13:38
bochechathere seems to be nothing at buildstream.gitlab.io at least13:39
jmactristan: This VTE fix you've pushed breaks on systems which don't define VTE_VERSION13:39
qinustyI'll raise an issue :D13:39
jennisjmac, no in my case it's a tarball of an image13:55
valentindtristan, maybe you can review a last time !685.13:55
jmacjennis: Is it private data?13:57
jennisjmac, yes13:59
jmacDrat. Well, I'll have another look through the code and see if I can figure out what's hapenning anyway14:00
jennisqinusty, I'll add a installation note the bst-external repo14:01
qinustycheers jennis14:04
jennisjmac, ok, I've given as much context as I could on the issue14:17
valentindIs the CI down?14:24
tristanjmac, it *breaks* ?14:32
*** CTtpollard has quit IRC14:32
tristanI thought accesses to os.environ['sdfsdfds'] were safe for non-existing env vars14:33
jmacIt's a KeyError here14:33
*** xjuan has joined #buildstream14:33
tristanmaybe the int(None) is not raising the expected ValueError ?14:33
tristanhmmm14:33
tristanjmac, looks like a one line fix... I'm just stopping by after gym and on my way to meet people for dinner; I can fix it tmw first thing14:34
tristansorry for breaking the world :-S14:34
jmactristan: No problems, I don't think many people have seen it14:35
tristanit's only when xterm TERM doesnt set VTE_VERSION14:35
jmacYeah, which seems to only be Ubuntu 17.10 IME. 18.04 sets it.14:35
*** tpollard has joined #buildstream14:35
jmacIt's easy to work around, obviously14:35
tristanbut, seeing as KeyError is thrown, I'd better check for KeyError when checking the TERM var also14:35
*** CTtpollard has joined #buildstream14:35
tristanTERM is almost *certainly* set, but nevertheless14:36
tristanor os.environ.get() I suppose is the right thing14:36
valentindtristan, I cannot get any build on the CI. Is someone taking care of that?14:44
qinustyjjardon knows about CI?14:45
bochechavalentind: is that digital ocean machines? we're having trouble with the fdo-sdk CI as well, and it seems they are having a downtime: https://status.digitalocean.com/14:45
gitlab-br-botbuildstream: issue #602 ("Cannot mount disk image in sandbox") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/60215:07
cs-shadowtristan: when you get a chance, can you please create an account on https://pypi.org/ and https://test.pypi.org? Also, ping me your username when you're done. Not urgent15:09
*** WSalmon has quit IRC15:11
*** tristan has quit IRC15:24
*** tristan has joined #buildstream15:24
qinustybochecha: Any chance you see a trend in the elements which are pulled and pushed? https://gitlab.com/BuildStream/buildstream/issues/551#note_9619599015:45
bochechaqinusty: I'll have a look15:58
qinusty I would also be interested to see whether it was the same elements each time? Do you have more CI builds which show this happening?16:00
toscalixtpollard: tiago will be back next wednesday16:09
qinustyHas anyone noticed how gitlab logs when viewed as raw are a little.... Screwed? https://gitlab-artifacts.s3.amazonaws.com/5c/63/5c63681383a059a6dab32deb7a44d5cf535132c0c0c35105f4ce1334be7e8bef/2018_08_22/91186759/78635410/job.log?response-content-type=text/plain%3B%20charset%3Dutf-8&response-content-disposition=inline&X-Amz-Expires=600&X-Amz-Date=216:09
qinusty0180822T160854Z&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJTOFWQ3GL4O3Q3FA/20180822/us-east-1/s3/aws4_request&X-Amz-SignedHeaders=host&X-Amz-Signature=fccb58256eb9f300b9aa588357ea5e7b3bc77f25c9795f3f7decbd8cde0ac3df16:09
qinustyI assume due to the coloured text etc16:10
qinustyhttps://gitlab.com/gitlab-org/gitlab-runner/issues/2250 ?16:12
bochechaqinusty: I have this one: https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/jobs/9129806316:13
qinustyYou only have the single remote cache right bochecha?16:28
bochechaqinusty: yes16:28
bochechaqinusty: basically, if you clone freedesktop-sdk, then you have the same config as I have :)16:29
qinustyI have :D, what're you building?16:29
qinustybst build ...16:29
coldtomall.bst it looks like16:30
*** solid_black has quit IRC16:33
qinustyI'll run a build on a modified version of 1.1.6 to check the cache keys of the element during pull and push jobs.16:34
*** noisecell has quit IRC16:48
*** leopi has quit IRC16:53
*** jonathanmaw has quit IRC17:03
*** toscalix has quit IRC17:08
bochechaqinusty: sorry, missed your messages; yes, the CI builds all.bst17:15
gitlab-br-botbuildstream: merge request (valentindavid/faster_startup-1.2->bst-1.2: Use ArtifactCache's get_cache_size when calculating the quota) #701 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/70117:28
*** leopi has joined #buildstream17:29
*** rdale has quit IRC17:51
*** alatiera_ has quit IRC17:51
*** alatiera_ has joined #buildstream17:53
*** alatiera_ has quit IRC18:25
*** alatiera_ has joined #buildstream18:25
*** leopi has quit IRC18:30
gitlab-br-botbuildstream: merge request (valentindavid/inconsistant-workspace->master: Improve error message for deleted open workspaces) #703 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/70318:34
gitlab-br-botbuildstream: merge request (chandan/fix-mainfest-dev-requirements->master: MANIFEST.in: Fix include for dev-requirements.txt) #704 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/70418:37
gitlab-br-botbuildstream: merge request (chandan/fix-mainfest-dev-requirements->master: MANIFEST.in: Fix include for dev-requirements.txt) #704 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/70418:37
gitlab-br-botbuildstream: merge request (chandan/fix-mainfest-dev-requirements->master: MANIFEST.in: Fix include for dev-requirements.txt) #704 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/70418:38
gitlab-br-botbuildstream: merge request (chandan/fix-mainfest-dev-requirements->master: MANIFEST.in: Fix include for dev-requirements.txt) #704 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/70418:38
*** alatiera_ has quit IRC19:18
gitlab-br-botbuildstream: merge request (chandan/fix-mainfest-dev-requirements-1.2->bst-1.2: MANIFEST.in: Fix include for dev-requirements.txt) #705 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/70520:13
*** TingPing has left #buildstream20:49
*** tristan has quit IRC21:18
gitlab-br-botbuildstream: merge request (chandan/fix-mainfest-dev-requirements-1.2->bst-1.2: MANIFEST.in: Fix include for dev-requirements.txt) #705 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/70523:44
gitlab-br-botbuildstream: merge request (chandan/fix-mainfest-dev-requirements->master: MANIFEST.in: Fix include for dev-requirements.txt) #704 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/70423:44

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