IRC logs for #buildstream for Tuesday, 2019-09-10

*** jjardon has quit IRC01:08
*** skullone[m] has quit IRC01:08
*** dineshdb[m] has quit IRC01:08
*** tchaik[m] has quit IRC01:08
*** mrmcq2u[m] has quit IRC01:08
*** lchlan has quit IRC01:08
*** waltervargas[m] has quit IRC01:08
*** ssssam[m] has quit IRC01:08
*** lchlan has joined #buildstream01:08
*** abderrahim[m] has quit IRC01:08
*** benschubert has quit IRC01:08
*** pro[m] has quit IRC01:08
*** benschubert has joined #buildstream01:08
*** Trevinho[m] has quit IRC01:08
*** m_22[m] has quit IRC01:08
*** Demos[m] has quit IRC01:09
*** awacheux[m] has quit IRC01:09
*** jjardon[m] has quit IRC01:09
*** mattiasb has quit IRC01:09
*** doras has quit IRC01:09
*** cgmcintyre[m] has quit IRC01:09
*** nielsdg has quit IRC01:09
*** tlater[m] has quit IRC01:09
*** theawless[m] has quit IRC01:09
*** reuben640[m] has quit IRC01:09
*** albfan[m] has quit IRC01:09
*** kailueke[m] has quit IRC01:09
*** krichter[m] has quit IRC01:09
*** connorshea[m] has quit IRC01:09
*** jjardon has joined #buildstream01:10
*** ChanServ sets mode: +o jjardon01:10
*** skullone[m] has joined #buildstream01:11
*** dineshdb[m] has joined #buildstream01:23
*** tchaik[m] has joined #buildstream02:21
*** mrmcq2u[m] has joined #buildstream02:46
*** waltervargas[m] has joined #buildstream03:02
*** ssssam[m] has joined #buildstream03:11
*** pro[m] has joined #buildstream03:37
*** abderrahim[m] has joined #buildstream03:47
juergbibenschubert: that was useful: https://gitlab.com/BuildGrid/buildbox/buildbox-common/merge_requests/11804:26
juergbiI haven't verified yet that this indeed fixes the issue, but I'd expect it to04:27
*** m_22[m] has joined #buildstream04:39
*** Trevinho[m] has joined #buildstream04:55
*** jjardon[m] has joined #buildstream05:12
*** awacheux[m] has joined #buildstream05:17
*** Demos[m] has joined #buildstream05:18
*** mattiasb has joined #buildstream05:39
*** doras has joined #buildstream06:07
*** nielsdg has joined #buildstream06:08
*** cgmcintyre[m] has joined #buildstream06:09
*** tlater[m] has joined #buildstream06:17
benschubertjuergbi: cheers I'll try as soon as I'm the office!06:24
*** theawless[m] has joined #buildstream07:43
*** reuben640[m] has joined #buildstream07:54
*** albfan[m] has joined #buildstream08:09
*** kailueke[m] has joined #buildstream08:09
*** krichter[m] has joined #buildstream08:10
*** connorshea[m] has joined #buildstream08:12
*** rdale has joined #buildstream08:25
*** traveltissues has joined #buildstream08:25
*** phildawson_ has joined #buildstream09:04
gitlab-br-botjuergbi opened MR !1591 (juerg/casd->master: casremote.py: Limit request size for batch download and upload) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/159109:14
juergbibenschubert: I've verified that the buildbox-common MR fixes the issue here with a test case09:15
benschubertjuergbi: oh awesome!09:15
juergbiand !1591 should fix #112909:15
gitlab-br-botIssue #1129: Error when src-push to a remote: Message larger than max https://gitlab.com/BuildStream/buildstream/issues/112909:15
benschubertlet me try this right now :)09:15
juergbialso, with !1591 the buildbox-common bug can't ever be triggered because buildbox won't have to split the gRPC messages as now the buildstream client will already split requests to casd09:16
juergbii.e., with !1591 none of the two issues should occur anymore even with the old buildbox-common09:17
gitlab-br-bottraveltissues approved MR !1591 (juerg/casd->master: casremote.py: Limit request size for batch download and upload) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/159109:19
benschubertjuergbi: awesome, that means we don't need to make a new release for the other?09:23
juergbicorrect09:23
benschubertSo what was happening is one client would fail with a request too big, and all subsequent ones would fail because it was using the same client context?09:23
juergbithe buildbox-common issue was triggered if the request from bst to casd was bigger than buildbox's message size limit (1 MB) but smaller than the default gRPC core limit of 4 MB09:25
juergbii.e., this case triggers message splitting in casd, however, the message splitting had a bug in that it reused the same ClientContext and thus, the second message failed with the assertion failure you saw09:26
benschubertI see09:26
juergbiI think the assertion failure aborted casd, although I haven't verified that09:27
benschubertI'll retry the build see if everything succeeds then :)09:27
benschubertI can confirm it was killing it09:27
juergbiI haven't verified this via fdo-sdk build yet, should probably do this as well09:27
*** jonathanmaw has joined #buildstream09:33
benschubertjjardon: is the flathub remote very flacky usually? https://gitlab.com/BuildStream/buildstream/-/jobs/291588211 I tried a dozen times...09:55
tpollardbenschubert: it's not too uncommon https://gitlab.com/BuildStream/buildstream/issues/109809:56
gitlab-br-bottraveltissues approved MR !1550 (tpollard/notificationhandler->master: Stream - Scheduler notification handler) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/155009:57
tpollardalthough it looks like we're correctly handing the error messages now :)09:59
tpollardas in, we're actually getting the error out, not just a BUG about it being out of sync10:00
benschubertYep, but we don't get the 3 retries I've seen with other sources, that seems weird10:00
jjardonbenschubert: we had same issue with bst-1 branch. 100% reproducible, while the bst-1.2 was 100% of the times fine10:00
jjardonIn the end the "fix" was to use Debian9 instead fedora30 for the ci job10:01
benschubertjjardon: thanks I'll try that fix :)10:01
benschubertit should be the last thing before we can have the nightly tests pass again10:02
jjardonNice!! :)10:02
juergbiDebian 9 ostree uses libsoup as HTTP backend (HTTP 1.x) while Fedora ostree uses curl as HTTP backend (HTTP/2), afaict10:02
benschubertjuergbi: oh that would explain the 'http2 message out of sync"10:03
gitlab-br-bottpollard opened MR !1592 (tpollard/sandboxmessage->master: _message.py: Use bool for sandbox Message() parameter) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/159210:06
*** cs-shadow has joined #buildstream10:07
benschubertjuergbi: one "cheap" test for the pushing to remote caches would be to add a local remote artifactserver on the nightly tests, would slow them down a bit, but would allow us to check a  more real scenario, what do you think?10:07
tpollardwe still have a spare cache server hosted on digitalocean currently10:09
tpollardbut that wouldn't be local obviously :)10:09
juergbibenschubert: could make sense. I did add a test to my MR, though, so at least basic build and push for an element with many files is now tested10:09
benschubertjuergbi: great, yeah, we'll see, let's get the tests fixed first :D10:10
benschubertjuergbi: also, I *think* the issue is fixed with the update to BUildStream, I have seem to have gone further10:10
benschuberttpollard: I would just like to make sure we have to push ewverything every time :)10:11
gitlab-br-botBenjaminSchubert approved MR !1591 (juerg/casd->master: casremote.py: Limit request size for batch download and upload) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/159110:11
juergbibenschubert: ok, I wanted to try it here locally as well but I'm still hitting the ostree background thread issue10:11
tpollardbenschubert: yep, definitely worth the slight overhead imo10:11
juergbiwondering why noone else sees this10:11
juergbimaybe I need to recreate my venv10:11
benschubertjuergbi: are you running on fedora?10:11
juergbino10:11
juergbibut I tried with both ostree/libsoup and ostree/curl10:12
benschubertthen I have no idea, I'm using ubuntu 19.04 and it seems to work :)10:12
juergbiI tried with ostree 2019.1 and 2019.3 (latest)10:12
juergbiUubntu 19.04 also has ostree 2019.110:12
benschubertjuergbi: https://gitlab.com/snippets/1893654 this is roughly my setup10:13
juergbita10:14
gitlab-br-botcoldtom opened MR !1593 (coldtom/filter-element-improvements->master: plugins/elements/filter.py: Allow passing integration commands through, fail if dep is a stack element) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/159310:22
gitlab-br-botmarge-bot123 closed issue #1129 (Error when src-push to a remote: Message larger than max) on buildstream https://gitlab.com/BuildStream/buildstream/issues/112910:29
gitlab-br-botmarge-bot123 merged MR !1591 (juerg/casd->master: casremote.py: Limit request size for batch download and upload) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/159110:29
jjardonbochecha: Is buildstream 1.4.1  already in F30? I wonder if there is some kind of bug at https://repology.org/project/buildstream/versions11:00
*** phil has joined #buildstream11:01
*** phildawson_ has quit IRC11:02
gitlab-br-botmarge-bot123 merged MR !1550 (tpollard/notificationhandler->master: Stream - Scheduler notification handler) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/155011:17
jenniscs-shadow, I've opened !1590 which makes source checkout a lot more like artifact checkout. This was in response to a UI thread that you wrote last November (:O), would you be able to review?11:18
gitlab-br-botMR !1590: Ensure `source checkout` is symmetric to `artifact checkout` https://gitlab.com/BuildStream/buildstream/merge_requests/159011:18
cs-shadowjennis: thanks! will have a look now11:19
bochechajjardon: only in updates-testing for now11:22
bochechajjardon: I'll be able to push it to stable in 5 days11:23
jjardonAh, then makes sense, thanks!11:23
bochecha(packages need to stay a week in testing by policy)11:23
bochechaunless people test it and give it a +111:23
bochechathen it can go to stable right away11:23
*** phil has quit IRC11:42
gitlab-br-bottraveltissues opened MR !1594 (traveltissues/typo->master: Fix typo in pipeline msg detail) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/159411:54
gitlab-br-bottpollard approved MR !1594 (traveltissues/typo->master: Fix typo in pipeline msg detail) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/159411:56
gitlab-br-bottraveltissues opened MR !1595 (traveltissues/none-childdata->master: Return early from tracking queue if no result) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/159512:02
traveltissuesty tpollard12:06
gitlab-br-botmarge-bot123 merged MR !1594 (traveltissues/typo->master: Fix typo in pipeline msg detail) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/159412:35
* tlater[m] really wants to make the master pipeline fail to test if his docs fixes work12:40
tlater[m]I think that may be a bad desire.12:40
*** phil has joined #buildstream12:49
gitlab-br-botmarge-bot123 merged MR !1592 (tpollard/sandboxmessage->master: _message.py: Use bool for sandbox Message() parameter) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/159213:14
*** phildawson_ has joined #buildstream13:20
*** phil has quit IRC13:21
jenniscs-shadow, tlater[m], tpollard, I've taken your review comments on !1584 on board and the MR has now changed significantly13:29
gitlab-br-botMR !1584: WIP: Add UI section in CONTRIBUTING https://gitlab.com/BuildStream/buildstream/merge_requests/158413:29
tpollardwill give it a gander13:35
benschubertjuergbi: https://gitlab.com/snippets/1893722 that happened 3 times then went away :'D14:23
juergbibenschubert: hm, that happens if casd isn't ready within 15s. either startup failed or it's _really_ slow14:33
benschubertOuch, ok, I'll open a ML thread about logging for casd, I think it's becoming useful :D14:34
juergbiwe should probably also add a is_alive() check to provide a better error message in case casd terminates unexpectedly14:43
benschubertagreed, I 'll add this now :)14:44
traveltissuesany strong feelings about !1595?14:45
cs-shadowjennis: just to verify that I'm not looking at the wrong thing, you haven14:52
cs-shadowyou haven't already added the design principles from the ML threads, right?14:52
*** bochecha has quit IRC14:58
gitlab-br-botBenjaminSchubert opened MR !1596 (bschubert/casd-better-reporting->master: [cascache] Check whether local casd is dead when grpc returns UNAVAILABLE) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/159615:09
benschubertjuergbi: ^15:11
jennisno cs-shadow, I think we're going to do the design principles after a "this is what the frontend should look like" email from tlater[m]15:15
jenniswell, it'd probably make sense to15:15
gitlab-br-botjuergbi opened MR !1597 (juerg/cache-usage->master: cascache.py: Fix cache usage monitor on Python older than 3.7) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/159715:16
juergbibenschubert: commented15:17
juergbitraveltissues: !1597 should fix #113115:17
gitlab-br-botIssue #1131: Error loading elements for freedesktop-sdk https://gitlab.com/BuildStream/buildstream/issues/113115:17
benschubertjuergbi: thanks a lot! I haven't tested it manually, I wonder if it might be worth adding a test starting the cascache, killing the process and then trying to connect?15:18
juergbiexercising the error path would definitely be nice :)15:19
juergbibut if it's not as it simple as it sounds for some reason, I wouldn't block the MR on it15:19
juergbiat least a quick manual test would be good, though15:19
cs-shadowjennis: thanks, that makes sense. Just wanted to confirm15:20
benschubertjuergbi: sure!15:22
gitlab-br-botBenjaminSchubert approved MR !1597 (juerg/cache-usage->master: cascache.py: Fix cache usage monitor on Python older than 3.7) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/159715:22
juergbita15:23
gitlab-br-botBenjaminSchubert approved MR !1595 (traveltissues/none-childdata->master: Check result is not None in tracking queue done()) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/159515:23
traveltissuesty benschubert juergbi15:23
gitlab-br-bottraveltissues approved MR !1597 (juerg/cache-usage->master: cascache.py: Fix cache usage monitor on Python older than 3.7) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/159715:31
traveltissuesjuergbi, i've tested this locally now, thanks15:32
juergbita15:32
juergbiit's now also covered by CI15:33
jennisbenschubert, https://gitlab.com/BuildStream/buildstream/merge_requests/1590#note_214866002, are you suggesting that we `seek()` after we've added all of the files?15:55
jennisNot sure what this gains over `close()`15:55
benschubertjennis: not sure why we are closing the file there, but if that is something we would rather not do, seek() would work15:56
jennisWithout closing the file I was getting EOF errors when trying to extract the tarball15:58
jennisEnsuring we close the tarfile after we've added all of the files prevented this15:59
benschubertand seek() on the tarfile should have the same effect :)15:59
jennisBut is there any advantage to using seek() over close()?15:59
benschubertwe avoid closing/reopening? If we are reopening anyways then no16:00
gitlab-br-botmarge-bot123 merged MR !1595 (traveltissues/none-childdata->master: Check result is not None in tracking queue done()) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/159516:08
*** phil has joined #buildstream16:09
*** phildawson_ has quit IRC16:10
juergbibenschubert: hm, thinking about it, I'm actually surprised that it mostly works (except for returncode 0 despite SIGKILL) even though this is typically running in a job child process and waitpid() doesn't allow waiting for sibling processes (buildbox-casd is a child of the main process)16:18
juergbilooking at the full job log, there are definitely still cases where we get the gRPC UNAVAILABLE error16:19
juergbiso I think it works only if SIGCHLD was already processed by the main process at the point the job child process was forked16:20
juergbialthough I would expect even more gRPC UNAVAILABLE errors in that case. maybe I'm still missing something16:21
benschubertmmh good point, I'll put this MR back to WIP then16:30
benschubertany idea where to start debugging?16:30
benschubertor what the bugfix should be?16:42
juergbibenschubert: not sure. it seems to work at least sometimes and is just an error message improvement, so it might still be better to merge it than not to16:45
juergbidon't know how much time makes sense to invest to make it work in all cases16:45
benschubertthat's a fair point. I'm happy to merge it as is if you are happy with it, I'm not entirely comfortable with that part of the code :)16:46
*** traveltissues has quit IRC17:00
gitlab-br-botmarge-bot123 closed issue #1131 (Error loading elements for freedesktop-sdk) on buildstream https://gitlab.com/BuildStream/buildstream/issues/113117:08
gitlab-br-botmarge-bot123 merged MR !1597 (juerg/cache-usage->master: cascache.py: Fix cache usage monitor on Python older than 3.7) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/159717:08
*** jonathanmaw has quit IRC17:10
*** narispo has joined #buildstream18:06
*** phil has quit IRC18:07
benschubertArtifact servers don't push data from junctions anymore correct?19:30
benschubertah, found the doc, sorry :)19:31
*** rdale has quit IRC20:03
*** narispo has quit IRC21:26
*** narispo has joined #buildstream21:26

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