IRC logs for #buildstream for Monday, 2019-02-18

*** nimish has quit IRC02:43
*** bochecha has joined #buildstream03:37
*** mohan43u has joined #buildstream06:44
*** cs-shadow has joined #buildstream06:45
juergbihi jmac, I've updated !991 now that symlinks should no longer be an issue. can you please take a look? I've described the changes in an MR comment07:56
gitlab-br-botMR !991: Cache artifacts with virtual directories instead of filesystem. https://gitlab.com/BuildStream/buildstream/merge_requests/99107:56
*** tristan has joined #buildstream08:15
*** tristan has quit IRC08:20
*** tristan has joined #buildstream08:23
juergbihi tristan, any thoughts on !968, especially with regards to the point I raised?08:26
gitlab-br-botMR !968: Allow absolute paths in whitelist https://gitlab.com/BuildStream/buildstream/merge_requests/96808:26
*** ChanServ sets mode: +o tristan08:34
jmacjuergbi: Having a look now08:34
juergbita08:34
gitlab-br-botjmacarthur opened issue #917 (Maximum recursion error while using tar source (upstream Python issue)) on buildstream https://gitlab.com/BuildStream/buildstream/issues/91708:55
*** alatiera has joined #buildstream09:06
*** tristan has quit IRC09:06
*** tristan has joined #buildstream09:07
*** cs-shadow has quit IRC09:27
*** tpollard has joined #buildstream09:32
*** raoul has joined #buildstream09:33
jmacjuergbi: I don't recognise any of this code anymore, sorry. I can still review it, but it's going to be a multi-hour job, and I don't think I'll have enough time for it anytime soon.09:37
laurencejmac, i'm struggling to find your write up of the RE testing on the wiki - is it still there?09:39
juergbijmac: ok, then just let's leave it as is. it shouldn't have anything controversial. it's actually simpler now due to the symlink handling change in master09:40
laurencejmac, ah found it09:41
laurencehttps://wiki.gnome.org/Projects/BuildStream/RemoteExecutionTesting09:41
*** jonathanmaw has joined #buildstream09:42
gitlab-br-bottristanvb merged MR !1155 (tristan/document-release-process->master: CONTRIBUTING.rst: Documenting the release process) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/115509:43
juergbitristan: I've replied to your comment09:48
*** tristan has quit IRC09:52
*** tristan has joined #buildstream09:54
*** ChanServ sets mode: +o tristan09:54
tristanjuergbi, network seems to keep slipping... replied again09:58
juergbitristan: it seems like we're still misunderstanding each other. a couple lines below the highlighted regex change, that's actually what the patch does (prepending a slash)09:59
juergbii.e., there are essentially two changes in the branch09:59
juergbione to prepend the slash to make proper comparison, matching the documentation09:59
juergbiand another one to keep backward compatibility with whitelists that don't expect absolute paths10:00
tristanjuergbi, Yeah I noticed that after making the initial comment10:00
juergbithe first one I think we can all agree on10:00
juergbithe second one is my question10:00
juergbii.e., do we really want that for master10:00
tristanAnd I think I included my agreement with you in the last comment :)10:00
tristanSecond sentence10:00
juergbiah ok, your 'this' was a bit ambiguous to me10:01
tristanAhhh10:01
tristanSorry :)10:01
juergbino problem10:01
juergbivalentind: can you please confirm that the highlighted change in !968 is just for backward compatibility?10:01
gitlab-br-botMR !968: Allow absolute paths in whitelist https://gitlab.com/BuildStream/buildstream/merge_requests/96810:02
gitlab-br-bottristanvb opened issue #918 (requirements makefile adds pkg-resources 0.0.0) on buildstream https://gitlab.com/BuildStream/buildstream/issues/91810:19
*** lachlan has joined #buildstream10:32
*** lachlan has quit IRC10:40
*** lachlan has joined #buildstream10:41
laurenceadds68, where does your marge-bot forward email to?10:55
laurencejust a handful of core contributors? is the mail useful?10:55
adds68laurence, its just the standard gitlab emails for a specific MR10:56
laurenceok cheers11:00
laurencejuergbi, want to receive emails from marge-bot? tristan, do you ?11:00
juergbiI don't think I normally want these mails as I'll already get notified by merges via my normal GitLab account11:01
juergbihowever, if needed for admin or so, I can be a receiver and just automatically filter them out11:01
laurenceok11:02
laurenceI'll not do so for now11:02
tristanlaurence, What I understand from adds68 is that the merge bot just comments on the merge request; and gitlab as a result sends an email, am I misunderstanding ?11:05
tristanadds68, ^^ ?11:07
adds68tristan, yea correct11:07
adds68laurence, tristan  see the bottom of this issue as an example: https://gitlab.com/freedesktop-sdk/freedesktop-sdk/merge_requests/68111:08
adds68MR* sorry11:08
juergbitristan: I think laurence's question is about whether you want the emails that are sent to marge-bot's email address11:09
tristanyeah11:09
juergbiand you probably don't (normally)11:09
tristanErr right, we only want to know if something is broken, if it absolutely must have an email address, it would be fine if it were an archive that a buildstream developer could inspect when finding that the merge bot is having trouble11:10
gitlab-br-botraoul.hidalgocharman approved MR !991 (jmac/cache_artifacts_with_vdir->master: Cache artifacts with virtual directories instead of filesystem.) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/99111:15
gitlab-br-botjuergbi closed issue #787 (Alter Element._cache_artifact so it uses the virtual directory system) on buildstream https://gitlab.com/BuildStream/buildstream/issues/78711:18
gitlab-br-botjuergbi merged MR !991 (jmac/cache_artifacts_with_vdir->master: Cache artifacts with virtual directories instead of filesystem.) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/99111:18
tpollardhttps://2019.fossasia.org/event/schedule.html#5216 tristan 's talk is on the schedule :D11:22
tristanAlready !11:31
laurencetristan, juergbi, adds68, ok thanks - I'll have the emails sent to myself, I don't mind deleting them / setting up a filter11:33
adds68tpollard, get some stickers printed11:36
*** lachlan has quit IRC11:44
jmacIf I checkout an element which has a build-depends in it, should I expect to see the contents of the dependency artifact in the dependent element's checkout?11:49
Kinnisonjmac: The defaults are runtime dependencies, try --deps build11:58
Kinnisonjmac: if you want that11:58
jmacOK, that looks like it's doing something, thanks12:00
KinnisonNo probs, confused me a few times too12:00
juergbiKinnison: you expect build dependencies to be included in a checkout by default, or was it simply confusing but you agree that they shouldn't be included by default?12:09
Kinnisonjuergbi: I expected only the single element's content12:10
Kinnisonjuergbi: i.e. 'none'12:10
juergbiah ok, that I can understand12:10
*** nimish has joined #buildstream12:13
*** lachlan has joined #buildstream12:13
*** lachlan has quit IRC12:23
*** lachlan has joined #buildstream12:31
*** lachlan has quit IRC12:37
tristanso I zapped the gitlab caches on the weekend and they have been rebuilt since then12:38
tristanBut pipelines are still taking somewhere from 40min to 60min, instead of ~25/30min12:38
juergbitristan: might be buildtree-related. for one, multiple buildtree tests are among the 20 slowest, and also other integration tests might take a bit longer with buildtrees12:41
juergbialthough, not sure about the latter, given that I don't expect the buildtrees of our tests to be very large12:41
gitlab-br-botcs-shadow opened MR !1156 (chandan/remove-pkg-resources->master: requirements/Makefile: exclude pkg-resources) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/115612:45
tristanjuergbi, Except I recall that pipelines were in good health at the time we introduced tox12:46
tristanThat is the confusing part :-S12:46
tristanMaybe I should try running a pipeline from around then and see if it takes around the same time12:46
*** cs-shadow has joined #buildstream12:49
juergbitristan: might it be this? conftest.py: Use different artifact directory for integration tests12:57
gitlab-br-bottristanvb opened MR !1157 (tristan/collect-missing-coverage->master: .gitlab-ci.yml: Some new test environments were added, but not collecting coverage.) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/115712:58
tristanjuergbi, it's not supposed to, I mean; that just makes the directories unique per run, so that there are no races when running parallel tests with detox12:59
juergbibut did we clean the artifact caches before?12:59
tristanAll I can imagine is that might causing artifact caches to land in the cache13:00
tristanYes13:00
gitlab-br-botcs-shadow approved MR !1157 (tristan/collect-missing-coverage->master: .gitlab-ci.yml: Some new test environments were added, but not collecting coverage.) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/115713:00
tristanjuergbi, The artifact cache is never supposed to persist in the gitlab cache, only the sources are stored/shared/reused13:00
juergbiI don't mean across CI jobs, I meant across integration tests in a single job13:00
tristanNope, that they should not13:01
tristanIt is one artifact cache for the session13:01
juergbiok, but with your commit not anymore13:01
juergbihence possible slowdown13:01
juergbi(but better isolation)13:01
tristanI cannot believe that to be true13:01
juergbiwhich part exactly?13:02
tristanSo what did I miss ?13:02
tristanhehe13:02
tristanjuergbi, it is a session wide value, I don't know what black magic caused `scope="session"` to work before, but it should work equally now13:03
tristan6286d8209a3db7fcf2b490a55044fa4c2be0c00713:03
tristani.e. if you check that commit, you will see that we only change the directory name, it is still removed at the end of the session wide fixture13:03
juergbiah, the fixture is per session, I missed that13:03
tristanyeah I was totally confused at that when writing that commit13:04
tristanbut it seems to work the same way as it did before13:04
tristanthat should really make the integration tests a *lot* slower if I screwed that up :)13:04
juergbinot sure it would be that drastic, as long as sources are still cached13:06
juergbiindependent of why the slowdown happened, maybe we should start running tests in parallel to speed things up, at least when the CI runners are not overbooked13:07
juergbithere is still one integration test (cachedfail) that often fails when running tests in parallel, though13:07
juergbiwould be good to fix that in any case, of course13:07
juergbilocally I can run all tests in about 5 min13:07
tpollardwoah13:07
tristanyeah I'm impressed13:08
tristanjuergbi, each integration test would have to do the import - one optimization I made before is that we had the alpine image named/cached differently in different tests13:08
tristanplus the flatpak runtime13:09
tristanI think that for the integration tests, the slowest ones are the autotools build one because it is the first to create the base runtime artifact13:09
tristan(as I understand, CPU is never a problem, it is I/O on gitlab which is to be feared)13:10
juergbiafter the WIP CAS optimizations (incl. source cache), we could probably have that _a lot_ faster13:10
juergbialthough, initial import into CAS still needs to happen, of course. should still be faster, though13:11
gitlab-br-bottristanvb closed issue #918 (requirements makefile adds pkg-resources 0.0.0) on buildstream https://gitlab.com/BuildStream/buildstream/issues/91813:43
gitlab-br-bottristanvb merged MR !1156 (chandan/remove-pkg-resources->master: requirements/Makefile: exclude pkg-resources) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/115613:43
Kinnisoncs-shadow: Thanks for a comprehensive update on the dockers13:52
cs-shadowKinnison: you're welcome :)13:52
gitlab-br-botmatthew-yates opened issue #919 ('bst build <elem>' does not assemble all requried elements in some circumstances) on buildstream https://gitlab.com/BuildStream/buildstream/issues/91913:57
*** tristan has quit IRC14:00
*** phildawson has quit IRC14:01
*** phildawson has joined #buildstream14:01
*** raoul has quit IRC14:02
*** tristan has joined #buildstream14:15
*** ChanServ sets mode: +o tristan14:15
gitlab-br-bottristanvb merged MR !1157 (tristan/collect-missing-coverage->master: .gitlab-ci.yml: Some new test environments were added, but not collecting coverage.) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/115714:27
*** bochecha has quit IRC14:42
*** raoul has joined #buildstream15:03
gitlab-br-botjennis closed issue #234 (Allow viewing build logs from artifacts) on buildstream https://gitlab.com/BuildStream/buildstream/issues/23415:05
raouljuergbi, after you've looked at the cache dir MR, if you could it'd be good if you had a quick look over the WIP source cache MR (!1124) to check I'm going in the right direction. There's still few bits left like the source refs (how they're named and where the refs should be kept), which need to be done, though could possibly be done in separate MR.15:13
juergbiok, will do15:14
raoulcheer :)15:14
*** nimish has quit IRC15:26
*** nimish has joined #buildstream15:36
jonathanmawjjardon: I'm looking into adding the details of the new runner to https://wiki.gnome.org/action/login/Projects/BuildStream/Infrastructure, and it seems to be an Immutable Page to me15:51
*** lachlan has joined #buildstream15:53
*** lachlan has quit IRC16:06
gitlab-br-botjuergbi opened issue #920 (Use virtual directories for staging dependencies) on buildstream https://gitlab.com/BuildStream/buildstream/issues/92016:26
gitlab-br-botjuergbi opened issue #921 (Drop extract directories) on buildstream https://gitlab.com/BuildStream/buildstream/issues/92116:29
gitlab-br-botphildawson opened issue #922 (Make it easy to test BuildStream against external plugins) on buildstream https://gitlab.com/BuildStream/buildstream/issues/92216:39
*** lachlan has joined #buildstream16:59
laurencejmac, iirc you also had a page on the wiki about symlinks (i think??? or absolute relative paths..?? can't quite remember)17:01
laurenceanyway i think it may be obsolete now due to the recent changes17:01
jmacYes, hang on...17:04
jmachttps://wiki.gnome.org/Projects/BuildStream/ImportRules, but yes, as you say, I think the new rules make most of that obsolute17:05
jmacobsolete17:05
juergbijmac: I think we can also close #817 or was any of that not symlink-related?17:06
gitlab-br-botIssue #817: We need examples showing the importance of file import ordering https://gitlab.com/BuildStream/buildstream/issues/81717:06
gitlab-br-botjmacarthur closed issue #817 (We need examples showing the importance of file import ordering) on buildstream https://gitlab.com/BuildStream/buildstream/issues/81717:07
jmacYep, good point17:07
juergbita17:07
juergbiregarding ImportRules, we should still document what overwrites/replacements are allowed / what fails, but yes, it should be quite a bit simpler now17:07
*** lachlan has quit IRC17:23
*** mlalkaka has joined #buildstream17:33
gitlab-br-botjonathanmaw opened MR !1159 (jonathan/wsl-tests-allow-fail->master: Allow WSL tests to run, but they don't block the CI) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/115917:36
*** lachlan has joined #buildstream17:50
*** lachlan has quit IRC17:55
*** mohan43u has quit IRC18:01
*** lachlan has joined #buildstream18:02
gitlab-br-botcs-shadow approved MR !1159 (jonathan/wsl-tests-allow-fail->master: Allow WSL tests to run, but they don't block the CI) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/115918:03
*** lachlan has quit IRC18:06
*** raoul has quit IRC18:19
juergbivalentind: do you mind if I quickly update !968 to remove the backward compatibility bit for master or will you do that?18:27
gitlab-br-botMR !968: Allow absolute paths in whitelist https://gitlab.com/BuildStream/buildstream/merge_requests/96818:27
*** tristan has quit IRC18:28
gitlab-br-botcs-shadow opened MR !1160 (chandan/fix-badge-subprocess-error->master: doc/badges.py: Fix catching of CalledProcessError) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/116018:46
*** jonathanmaw has quit IRC18:54
gitlab-br-botjonathanmaw merged MR !1159 (jonathan/wsl-tests-allow-fail->master: Allow WSL tests to run, but they don't block the CI) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/115918:57
*** juanalday has joined #buildstream18:58
*** mlalkaka has quit IRC19:28
*** mlalkaka has joined #buildstream19:30
*** juanalday has quit IRC19:47
gitlab-br-botcs-shadow opened MR !1161 (chandan/fix-mapping-import->master: buildstream/_yaml.py: Import Mapping from collections.abc) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/116119:47
*** tristan has joined #buildstream19:49
*** nimish has quit IRC19:49
*** juanalday has joined #buildstream20:00
valentindjuergbi, I do not mind.20:10
*** lachlan has joined #buildstream20:24
gitlab-br-botcs-shadow merged MR !1160 (chandan/fix-badge-subprocess-error->master: doc/badges.py: Fix catching of CalledProcessError) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/116020:31
*** lachlan has quit IRC20:40
*** mohan43u has joined #buildstream20:59
*** mohan43u has quit IRC21:25
*** mohan43u has joined #buildstream21:34
*** mlalkaka_ has joined #buildstream21:36
*** mlalkaka has quit IRC21:37
*** juanalday has quit IRC21:41
*** tristan has quit IRC22:25
*** mlalkaka_ has quit IRC22:25
*** juanalday has joined #buildstream22:52
*** cs-shadow has quit IRC23:40

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