IRC logs for #buildstream for Wednesday, 2020-04-15

*** phoenix has quit IRC00:02
*** phoenix has joined #buildstream00:10
*** phoenix has quit IRC00:57
*** phoenix has joined #buildstream01:12
*** phoenix has quit IRC01:26
*** tristan has quit IRC04:43
*** tristan has joined #buildstream04:59
*** hasebastian has joined #buildstream05:13
gitlab-br-bottristanvb approved MR !1851 (valentindavid/include-options-from-junction->master: Process options in includes files with the options of their junction) on buildstream https://gitlab.com/BuildStream/buildstream/-/merge_requests/185105:52
*** ChanServ sets mode: +o tristan05:52
tristanShall we go ahead and merge !1851 ?05:52
*** benschubert has joined #buildstream07:06
*** tristan has quit IRC07:49
*** tpollard has joined #buildstream08:18
*** hasebastian has quit IRC08:23
*** santi has joined #buildstream08:34
gitlab-br-botwillsalmon opened issue #1287 (New version of bst can not use repo that has had workspaces) on buildstream https://gitlab.com/BuildStream/buildstream/-/issues/128708:36
gitlab-br-botBenjaminSchubert closed issue #1287 (New version of bst can not use repo that has had workspaces) on buildstream https://gitlab.com/BuildStream/buildstream/-/issues/128708:39
*** rdale has joined #buildstream08:40
gitlab-br-bottraveltissues reopened issue #1287 (New version of bst can not use repo that has had workspaces) on buildstream https://gitlab.com/BuildStream/buildstream/-/issues/128708:52
WSalmonanyone else had anything like this before, ill try and get a fix for this soon, it looks simple enough, if anyone has any implimentation details or other similar things i should bear in mind please put something on the issue https://gitlab.com/BuildStream/buildstream/-/issues/128708:52
WSalmonbenschubert, you have mentioned my ticket as the duplicate08:53
benschubertyep,08:53
traveltissuesi was a bit confused08:54
benschubertah sorry08:54
benschubertmeant #126608:54
gitlab-br-botIssue #1266: Can't load a project with an older workspace to a junction https://gitlab.com/BuildStream/buildstream/-/issues/126608:54
benschubertproblem is the same08:54
benschubertthough your's actually a bit broader08:54
traveltissuesah, apologies08:55
benschubertI'd suggest closing yours WSalmon and adding that this would happen even after closing the workspace on the other ticket?08:56
*** cs-shadow has joined #buildstream09:18
*** lachlan has joined #buildstream09:25
*** phoenix has joined #buildstream09:27
*** narispo has quit IRC09:44
*** tpollard has quit IRC09:50
*** tpollard has joined #buildstream09:50
gitlab-br-botwillsalmon closed issue #1287 (New version of bst can not use repo that has had workspaces) on buildstream https://gitlab.com/BuildStream/buildstream/-/issues/128709:57
*** tristan has joined #buildstream10:14
*** lachlan has quit IRC10:38
*** lachlan has joined #buildstream10:42
*** lachlan has quit IRC11:06
*** lachlan has joined #buildstream11:06
*** lachlan has quit IRC11:15
tpollardis there a final goal for buildtrees for bst2?11:15
tpollardor is the current functionality the final cut?11:17
*** lachlan has joined #buildstream11:31
*** lachlan has quit IRC11:32
*** lachlan has joined #buildstream11:37
juergbitpollard: there isn't anything in the current plan. is there a particular aspect that you think needs work?11:54
*** ChanServ sets mode: +o tristan12:11
tristanmy memory is foggy and I've missed a great deal; but I suspect at least with buildbox and fuse that the performance of this use case is much improved since the original addition of build trees12:11
tpollardjust wondering if they were being utilised as first envisioned that's all12:16
tpollardi.e, are they being utilised with workspaces & the underlying vcs, if appropriate12:22
juergbitpollard: buildtrees are used for incremental workspace builds. however, it's not currently possible to do an incremental build using a non-workspace build as starting point12:28
juergbiwe don't capture mtimes for non-workspace buildtrees12:28
tristanI think that `bst artifact list-contents` should prefix the paths with /12:33
tpollardso, the only use for buildtrees in standard build artifacts is for bst shell?12:33
tristan... would be more consistent with split-rules settings and overlap whitelists12:33
tpollardif of course the config is enabled to cache/push/pull them12:33
*** phoenix has quit IRC12:45
*** tpollard has quit IRC12:52
*** tpollard has joined #buildstream12:52
*** persia has quit IRC12:54
*** persia has joined #buildstream12:55
juergbitpollard: for me the main use case is to debug failed builds (and incremental workspace builds) and buidltrees are enabled by default for the failure case12:58
WSalmonjuergbi, how do you inspect the buildtree in such a case without a workspace? can you use a checkout?12:59
tpollardshell12:59
juergbiyep, shell12:59
juergbithat said, allowing export/checkout would probably make sense as well13:00
tpollardCould be nice, say if you wanted to send tarball elsewhere for inspection (without using a common cache)13:05
tristanAny objections to merging !1851 now ?13:13
gitlab-br-botMR !1851: Process options in includes files with the options of their junction https://gitlab.com/BuildStream/buildstream/-/merge_requests/185113:13
* tristan now has an ever growing documentation MR to back it up13:14
*** lachlan has quit IRC13:32
juergbitristan: I haven't looked into the details with regards to correct processing order. however, I don't have any objections13:35
tristanjuergbi, yeah I believe it's well tested13:37
juergbitristan: btw: have you had a chance to take a look at !1865 ?13:37
gitlab-br-botMR !1865: element.py: Fix strong cache key calculation in non-strict mode https://gitlab.com/BuildStream/buildstream/-/merge_requests/186513:37
tristanThat's an MR now !13:38
tristanI'll rebase my branch on it for a test13:38
tristanWhat the hell...13:44
tristancoldtom, valentind ... is this something that needs to be fixed in the infra: https://gitlab.com/BuildStream/buildstream/-/jobs/512056691 ?13:44
tristanLooks like docs built successfully but failed to coordinate their artifacts with the uploader, or smth13:44
* tristan heads out for sushi...13:45
*** lachlan has joined #buildstream13:46
valentindtristan, It looks like an issue from gitlab.13:53
valentindWe do not have control on where the CI artifacts are stored I think. Only CI cache.13:53
*** lachlan has quit IRC14:06
*** lachlan has joined #buildstream14:55
tristandang15:10
* tristan hits retry with futility15:10
*** rdale_ct has joined #buildstream15:16
*** rdale has quit IRC15:19
valentindThis is configured on the gitlab instance. It is not on the runner side.15:28
valentindhttps://gitlab.com/gitlab-com/gl-infra/production/-/issues/194415:28
*** lachlan has quit IRC15:34
*** lachlan has joined #buildstream15:36
*** lachlan has quit IRC16:10
philni'm trying to debug some non-whitelisted overlaps in my SDK... is there any tips&tricks besides trial and error poking?16:14
philni'd need to know which element pulls a specific one16:15
tristanjuergbi, anyway just to say, the branch definitely fixes the side effect, I've just been waiting for gitlab to get it's story straight so I can reply with links16:15
juergbigreat, thanks for confirming16:16
tristanhttps://gitlab.com/BuildStream/buildstream/-/jobs/51225289516:20
tristanvalentind, ^^^^^^^^^^^^^ this one has been saying 3 seconds for a while longer than three seconds ...16:21
tristan:-S16:21
tristansorry for blind ping, I wish this stuff "just worked"16:21
tristanI guess that having so many parallel test jobs is a contributing factor to things being randomly broken16:22
juergbitristan: we again have the maximum amount of 100 droplets16:23
juergbiI'll drop older ones16:23
juergbiso we still have the issue of droplets not getting shut down :-/16:23
juergbitristan: new jobs should work now but automatic retry can take a very long time. manual cancel+retry stuck jobs speeds it up16:24
juergbiI'm wondering what change introduced this breakage. iirc, it was more reliable 6 months ago or so16:25
tpollardphiln: I think fdsdk might have some tooling around working through overlaps16:26
*** lachlan has joined #buildstream16:37
*** lachlan has quit IRC16:50
valentindjuergbi, I know there was a change introduce in some script that stopped removing droplets.16:54
valentindI reverted it.16:54
valentindSo I expected it would work again.16:54
valentindBut there was also an issue with gitlab runner creating way too many machines sometimes.16:56
*** lachlan has joined #buildstream16:57
*** rdale_ct has quit IRC17:01
valentindSo, there was a typo in the systemd configuration file, that was stopping the docker machine to be cleaned.17:02
valentindI fixed that.17:02
*** lachlan has quit IRC17:08
valentindThe docker-machine cache is cleaned. And made sure the script works.17:10
*** santi has quit IRC17:12
juergbita17:17
*** tpollard has quit IRC17:19
*** lachlan has joined #buildstream17:28
*** lachlan has quit IRC17:35
douglaswinshipWhen you use bst shell to test out an element, can the sandbox reach an internet connection?17:43
douglaswinshipI was told that it could, but I keep getting "could not resolve host" when I try to run curl as a test.17:43
juergbidouglaswinship: if you don't specify --isolate, bst shell does not restrict network access17:53
juergbihowever, you typically need a suitable /etc/resolv.conf in the sandbox17:53
juergbiyou can use project.conf host-files to bind-mount the host /etc/resolv.conf17:54
douglaswinshipjuergbi: thanks! I shall read up on what /etc/resolv.conf does!17:54
juergbidouglaswinship: see https://buildstream.gitlab.io/buildstream/format_project.html#host-files for an example17:54
douglaswinshipthanks!17:55
juergbiresolv.conf contains the IP address of nameservers17:55
juergbinormally managed by your DHCP client but the sandbox normally doesn't know about this, of course17:55
*** phoenix has joined #buildstream18:10
*** benschubert has quit IRC19:29
*** phoenix has quit IRC20:02
*** phoenix has joined #buildstream20:04
*** cs-shadow has quit IRC21:25

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