IRC logs for #buildstream for Thursday, 2018-09-20

*** xjuan has quit IRC00:48
*** hergertme_ is now known as hergertme06:36
*** tristan has joined #buildstream06:47
*** mohan43u has quit IRC06:48
*** iker has joined #buildstream06:57
*** mohan43u has joined #buildstream07:02
paulsher1ood+1 for persia's last comment07:20
paulsher1oodone has to choose which upstream to track... if you're going with a distro, that's your upstream, not the upstream they are tracking07:22
*** finn has joined #buildstream07:39
*** finn has quit IRC07:40
*** finn has joined #buildstream07:41
*** bochecha has joined #buildstream07:50
bochechatristan: now that you removed blessings as a dependency, the Fedora maintainer decided to update it to a version that's recent enough for Buildstream 😏07:54
*** toscalix has joined #buildstream08:01
finnHi! So lastnight, I installed the bst-external plugins repo following the readme. I used:08:01
finn`pip show BuildStream-external`08:01
finnwhich tells me I've installed Version: 0.5.08:01
finnI then have a `test.bst` file which depends on `dock.bst`.08:02
finnInside `dock.bst` I have tried:08:02
finnkind: import08:02
finnsources:08:02
finn- kind: docker08:02
finnI get this error: No Source type registered for kind 'docker'08:02
finnany idea on what's happening here?08:02
KinnisonWhy not track the debian source via the Debian archive interfaces?08:03
Kinnisone.g. rmadison uses a CGI on qa.debian.org to learn about versions available in distributions, use that, then construct the appropriate filenames and download them from Debian infra08:03
jennisfinn, have you declared the plugin in your project.conf?08:11
jennishttps://buildstream.gitlab.io/buildstream/format_project.html#external-plugins08:12
gitlab-br-botbuildstream: merge request (Qinusty/skipped-rework-backport-1.2->bst-1.2: Backport skipped reword (!765)) #810 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/81008:30
qinustyskipped backport should pass CI now tristan08:32
gitlab-br-botbuildstream: merge request (juerg/cas-batch->master: WIP: _artifactcache/cascache.py: Use BatchReadBlobs) #813 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/81308:48
juergbitristan: !813 implements the client side of batch download support. how shall we verify that this actually fixes #554? it requires a server update as well and the server side is not merged to bst-1.2 yet (it will still work with current server, but it can't use batch download in that case)08:51
juergbiI could backport the server part first, we update at least one server and then you could test with the branch from !813. or we merge it after review but without testing it across high latency connections, backport both to 1.2 and it can be verified afterwards08:53
gitlab-br-botbuildstream: merge request (willsalmon/outOfSourecBuild->master: Out of source builds) #776 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/77609:19
*** jonathanmaw has joined #buildstream09:22
*** lachlan has joined #buildstream09:23
*** lachlan_ has joined #buildstream09:23
gitlab-br-botbuildstream: merge request (willsalmon/outOfSourecBuild->master: Out of source builds) #776 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/77609:25
*** ChanServ sets mode: +o tristan09:35
tristanjuergbi, Aha, this is great news !09:35
tristanjuergbi, Ok so... it won't make it into 1.2.1 anyway, but perhaps 1.2.1...09:37
tristanerr 1.2.209:38
tristanjuergbi, I am happy to merge both after releasing 1.2.1, and update one server and then compare performance09:39
tpollardDoes buildstream have a public artifact server ooi?09:39
lachlantristan: Did you manage to catch my question in the backlog yesterday?09:40
tristanjuergbi, I think that even bochecha has been seeing very slow downloads, and he is in France, so it doesn't require *that* high latency09:40
tristanlachlan, just catching up now... no didn't catch that09:40
lachlanOK09:40
tristanbochecha, Anyway no worries, I've been meaning to remove blessings for a long time now09:40
juergbiok. i'll just get this merged to master after review, then. and backport to 1.2 after 1.2.109:41
gitlab-br-botbuildstream: merge request (Qinusty/skipped-rework-backport-1.2->bst-1.2: Backport skipped reword (!765)) #810 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/81009:41
tristanqinusty, merged \o/09:41
tristanqinusty, I'll kick back and watch a nice build log now :)09:42
tpollardAlso with the work that's gone into buildstream-integration, would it be work that becoming part of CI?09:43
tristanOn a logging related topic, I want MessageType.LOG messages issued in cleanup and cachesize jobs; those log files are pointless, not for the lack of me opening them curiously and looking inside of them :)09:43
juergbitristan: to be clear, you also don't want the server side backported for 1.2.1? it's in master for 10 days now09:43
tristanjuergbi, I was going to ask about that actually09:44
tristanjuergbi, That could be better, I wasn't sure of how mature that part was09:44
tristanjuergbi, I say backport it, so we have servers updated earlier; and reduce fuss of testing the client side09:45
juergbiI've tested it with buildbox client and now also with buildstream client (MR)09:45
juergbithat was my thought as well09:45
tristanlachlan, I'm having a hard time finding your question in the logs... can you re-ask it please ?09:46
jjardonHi, does buildstream have any checks as part of the CI to be sure the cache key doesn't change for stable branches?09:46
juergbiyes, there are09:46
tristanjjardon, tests/cachekey/ does that... however there is *some* parts not covered well09:46
tristanWe don't have coverage for all the different build element types (but we have coverage for all different element types and source types)09:47
tristanjjardon, It's very easy to add this, if you care to throw up an MR, that would be much appreciated09:48
jjardonrigth, how is this configured in the CI? I guess it is allow to fail in master, but not in stable branches09:48
tristanNope09:48
tristanjjardon, Whenever we intentionally break cache key algorithm, we have to also update the test09:49
tristanjjardon, Lemme show you one sec09:49
jjardonah ok, so it will always fail the test, gotcha09:49
tristanhttps://gitlab.com/BuildStream/buildstream/tree/master/tests/cachekey/project/elements09:49
gitlab-br-botbuildstream: merge request (jmac/remote_exec_checkout_fix->master: Remote exec: Remove early warning and check directory is not None) #800 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/80009:50
tristanjjardon, See there, all the different elements, we add an extra element .bst file to exercise any feature / configuration which can effect cache keys in any way09:50
tristanjjardon, And we have a .expected file for the expected cache key of each element09:50
gitlab-br-botbuildstream: merge request (juerg/cas-batch-1.2->bst-1.2: _artifactcache/casserver.py: Implement BatchReadBlobs) #814 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/81409:51
tristanjjardon, When adding an element, or when the expected files need to be updated, it can be automated with the update.py script here: https://gitlab.com/BuildStream/buildstream/tree/master/tests/cachekey09:51
tristanjjardon, So it doesn't require manually updating the expected keys09:51
tristanThere is a source/ and an elements/ directory... We could use just a bare naked extra test for each element kind09:52
tristanin the elements/ directory... those have to be depended on by target.bst to be included in the test: https://gitlab.com/BuildStream/buildstream/blob/master/tests/cachekey/project/target.bst09:52
gitlab-br-botbuildstream: merge request (juerg/cas-batch->master: _artifactcache/cascache.py: Use BatchReadBlobs) #813 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/81309:53
tristanjuergbi, That would give us the added assurance that we do not change any default element configurations in the element .yaml files09:53
jjardonmmm, would be a good idea to have another test that build a real thing and check all the keys are as expected? something like https://gitlab.com/baserock/ybd/blob/master/.gitlab-ci.yml#L3009:53
tristanjjardon, I don't know what that would add09:53
*** lachlan_ has quit IRC09:54
*** lachlan has quit IRC09:54
tristanjjardon, Our test aims to capture every configuration that could possibly have any effect on cache keys, I think it's very thorough09:55
tristanjjardon, A build will only ever capture a subset of configurations, also; a build need not be run just to discover the cache keys09:55
gitlab-br-botbuildstream: issue #663 ("Missing cache key in log messages (workspace open)") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/66309:57
jjardontristan: note I said this as an additional test, not removing the current ones; you can always forget to add a check; this would be an extra. ( and you even said there is not coverage for all build types at the moment)09:59
qinustyWhere does buildstream save information relating to the currently open workspaces?09:59
qinustyI can't find a workspaces.yml in my local directory09:59
jjardontristan: is there an issue for that? maybe I have time over the weekend to add those10:00
* qinusty finds .bst/workspaces.yml10:00
tristanjjardon, technically; our test is doing the same thing as the ybd test you point out; with manufactured project data, designed specifically for exercising every possible option10:01
tristanjjardon, Also, CI is costly, we we prefer to have isolated tests which only test what they are testing for (i.e. not running huge builds)10:01
tristanjjardon, I will draw up an issue :)10:02
bochechatristan: I don't think what I had were very slow downloads… I think they were completely hung; bst still reporting it was doing something, but no download was actually happening10:03
tristanbochecha, Ah right, but I recall you were saying that long standing (1hrs ?) downloads were rather frequent, no ?10:03
tristanbochecha, I do recall that specific case was a hang, indeed10:03
bochechaah yes10:04
bochechabut then maybe they are just very big elements (e.g the flatpak images resulting from building fdo sdk)10:04
tristanOn my part, I download for a long long long long time, and my system monitor shows like 3 or 4 kbps10:04
jjardontristan: that CI job takes seconds; it's not actually building anything. It's a special ybd mode to only compute the keys I tihnk10:04
tristanjjardon, Sure, that's what we're doing, with `bst show`, using a project that is designed to exercise all the options thoroughly10:05
bochechatristan: how do you monitor download speed?10:06
tristanbochecha, gnome-system-monitor, which means... the download is taking *at most* 3 or 4 kbps10:06
tristani.e. overall system network activity monitor10:06
bochechalet me try this then :)10:07
jjardontristan: coolio, thanks for clarifications10:07
bochechaoh, gnome-system-monitor isn't in flathub :(10:07
tristanjjardon, We already have an issue: https://gitlab.com/BuildStream/buildstream/issues/318 :)10:08
qinustytristan, can you confirm that this is undesired behaviour ? https://gitlab.com/BuildStream/buildstream/issues/66310:08
tristanqinusty, Confirmed10:10
qinustyMight have time to fix it this afternoon if it doesn't go too deep down the rabbit hole10:10
tristanqinusty, It is *also* a bug that  /usr/bin/git show 72b5902157316e173de2eec5b3a2772283eec3c7:.gitmodules is being shown at all10:12
qinustynoted.10:13
tristanqinusty, The messages which pertain to resolving element state, stemming from `Source.get_consistency()` are not supposed to be shown10:13
bochechatristan: download speed is not too bad here actually: https://i.imgur.com/SUDYN3e.png10:15
bochechatristan: I had only IRC using the network at the same time10:15
bochecha(that's a `bst build flatpak-images/sdk.bst` on a revision which is in the remote cache, only download involved no actual build)10:16
*** lachlan has joined #buildstream10:18
*** lachlan_ has joined #buildstream10:18
tristanbochecha, performance will be improved with juergbi's work on batch downloads, though :)10:23
tristanjuergbi, Curiously, does CAS use pretty much the same approach we had with OSTree for push ? i.e. we were doing Tar streams and upload in a single stream10:23
juergbitristan: no, push is still non-batch, unfortunately. want to fix this as well10:24
tristanbochecha, Note that for me, it really varies, and I believe it depends mostly on the size of the files being transfered10:24
tristanjuergbi, Alright, when that is fixed, let's bring that into 1.2 as well; however pull is going to make a bigger impact on users so, very happy to have that now :)10:25
qinustyWSalmon, after having time to investigate that area of the code a little. It appears that logic was only intended to run on a success anyway.10:29
bochechatristan: possibly yes… could the server create one big file, so that the client only makes one big download at max speed, and then splits it back?10:30
qinustyIt isn't caching, just updating the workspace for the latest successful ref10:31
WSalmoni wonder why its ok for the non workspace case...10:31
WSalmoncool sounds good10:31
qinustyThe issue is purely related to workspacing, it only runs when a workspace is open.10:36
qinustyAre you able to check the patch against the issue you were seeing incase I'm fixing a separate issue?10:37
bochechatristan: fwiw it finished downloading in 23 minutes, downloaded 1700MB, which is roughly 1.2MB/s average… if juergi makes it faster, that's going to be really good! :)10:41
tristanbochecha, :)10:42
tristanbochecha, The batch downloads should help, maybe not that much on your connection, not sure, but they should help a lot I think10:43
tristanbochecha, round trips are expensive10:43
bochechawhat will the batch download actually do?10:43
tristanbochecha, FWIW, the upload with OSTree did not need to "create a huge file", we used python Tar, which allows "streaming", so on the client we add files to the stream and on the server we unpack the incomming files from the tar stream10:43
tristanbochecha, It will send multiple files over the same connection in batches, reducing round trips; from what I understand10:44
bochechanice10:44
gitlab-br-botbuildstream: issue #664 ("Current buildstream master is failing to build freedesktop-sdk") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/66410:44
bochechastreaming it all as one tar file could be nice as well10:44
KinnisonIt's worth noting that we don't really want to be adding more BuildStream specific RPCs10:45
KinnisonUntil/unless we cannot achieve reasonable performance any other way10:46
*** lachlan_ has quit IRC11:02
*** lachlan has quit IRC11:02
toscalixvalentind: I wonder what is left to be done here https://gitlab.com/BuildStream/website/merge_requests/8811:24
valentindtoscalix, just approval.11:25
toscalixassign to tiagogomes_ then, please11:26
toscalixdone11:26
*** mohan43u has quit IRC11:29
toscalixWSalmon: now the agenda section for the BuildSTream Conclave has been created, would you mind adding there your topic suggestion?11:37
toscalixWSalmon: https://wiki.gnome.org/Projects/BuildStream/Events#Proposed_topics11:38
*** lachlan has joined #buildstream11:40
persiaKinnison: Indeed.  Using madison.cgi for tracking debian-format upstream archives is far superior to watch files or anything else for derivation purposes.11:52
*** mohan43u has joined #buildstream11:54
tristanqinusty, Is https://gitlab.com/BuildStream/buildstream/issues/515 fixed ?12:14
gitlab-br-botbuildstream: issue #515 ("`bst push` will report success even if the local artifacts don't exist (and therefore aren't pushed)") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/51512:15
qinustyIndeed :)12:15
tristanqinusty, and https://gitlab.com/BuildStream/buildstream/issues/614 also ?12:15
gitlab-br-botbuildstream: issue #614 ("Follow-up from "Bschubert/backport log missed cache"") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/61412:16
qinustyThis is now much more intuitive in my opinion.12:16
qinustyYup12:16
qinustyApologies.12:16
tristanqinusty, Thanks, please close them :D12:16
tristanhttps://github.com/pallets/click/pull/782#issuecomment-42140415212:19
tristanLooks like they are now finally considering my tab completion enhancements upstream \o/12:19
tristanWith some luck, and a couple days of work... maybe we can drop all those hacks we have in our completion re-implementation12:19
*** alatiera_ has joined #buildstream12:20
tristanjuergbi, Are you ready with the backport of server side batching support ?12:21
tristanjuergbi, I could delay and release tomorrow, am writing up NEWS presently12:21
*** alatiera__ has joined #buildstream12:22
gitlab-br-botbuildstream: merge request (Qinusty/634-workspace-failed-builds->master: WIP: Do not save workspace on failed build) #812 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/81212:24
*** alatiera_ has quit IRC12:24
gitlab-br-botbuildstream: merge request (Qinusty/634-workspace-failed-builds->master: Do not save workspace on failed build) #812 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/81212:26
*** alatiera_ has joined #buildstream12:41
*** alatiera__ has quit IRC12:42
*** alatiera__ has joined #buildstream12:43
*** alatiera_ has quit IRC12:44
WSalmontoscalix, i dont seem to be able to edit the page do i need to be added to something? or am i looking in the wrong place12:51
toscalixyou need an account in the gnome wiki12:52
WSalmonjust have12:52
toscalixjjardon: might help you there12:52
toscalixthen you should be able12:52
juergbitristan: I already opened !814 for the backport12:53
WSalmonwere is the edit button?12:53
WSalmontoscalix, ^12:54
gitlab-br-botbuildstream: merge request (Qinusty/634-workspace-failed-builds->master: Do not save workspace on failed build) #812 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/81212:54
toscalixthere is on the upper right side12:54
qinustyCan I get a review on https://gitlab.com/BuildStream/buildstream/merge_requests/799?12:54
toscalixif you do not have it.... something else needs to be done12:54
toscalixI am a simple user.... jjardon knows what to do12:55
WSalmonall i can see is a little padlok that says "Immutable Page"12:55
tristantlater[m], Care to comment on this https://gitlab.com/BuildStream/buildstream/merge_requests/812#note_103112195 ?12:55
tristantlater[m], Sorry I keep getting confused around there12:55
jjardonWSalmon: what is your user in the gnome wiki? I will add you to the white list12:56
WSalmoni am WilliamSalmon12:56
tlater[m]tristan: Sure12:56
WSalmoni didnt realise that was gona be my username12:56
tlater[m]Ah, that comment again... Let's hope I still understand that.12:57
qinustytristan, I'm not familiar enough with the usage of workspaces to fully answer your queries on the desired behaviour there. Regarding https://gitlab.com/BuildStream/buildstream/merge_requests/81212:57
jjardonWSalmon: added you to https://wiki.gnome.org/TrustedEditorGroup; can you try now, please?12:57
gitlab-br-botbuildstream: merge request (juerg/cas-batch-1.2->bst-1.2: _artifactcache/casserver.py: Implement BatchReadBlobs) #814 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/81412:57
tristanjuergbi, Ah sorry didn't notice this, thanks !12:58
tristanqinusty, That's why I asked tlater[m], I have a feeling your patch is totally correct, but this is always confusing12:58
qinustyThe patch fixed a bug and corrected the behaviour to what was stated in the surrounding comments. I guess you're suggesting there is a larger problem at hand following the caching of failed builds12:58
WSalmonI can edit, but need to disapear to a meeting, will update the page when i am back12:58
tristanqinusty, It might be good to digest what tlater[m] has to say, and update the comment... not sure the rationale behind how this works is completely explained anywhere in the code12:59
qinustyagreed12:59
*** finn_ has joined #buildstream12:59
*** phildawson has quit IRC13:00
*** phildawson has joined #buildstream13:00
*** finn has quit IRC13:01
*** jonathanmaw_ has joined #buildstream13:01
*** jonathanmaw has quit IRC13:02
tristanwhoa13:07
* tristan just reproduced an old issue13:07
tristanmaybe this is new13:11
tristanAnyone recognize this crash when fetching a tarball https://bpaste.net/show/40b77c5cbefc ?13:11
tlater[m]qinusty, tristan: I'm going through all the edge cases we covered here, I'll add a write-up to that MR. It's an annoying one we keep forgetting.13:12
* tlater[m] finds it tough to think through, frankly13:12
*** alatiera_ has joined #buildstream13:14
*** alatiera__ has quit IRC13:15
tlater[m]We do have tests that confirm this is working though, so the patch itself looks to be fine.13:16
tristantlater[m], Thanks, it is indeed.13:16
tristanI will have to fix this crash, for some reason, the source has fetch() being called, without a ref13:17
tristanmirrors breakage13:18
tristanjonathanmaw_, https://gitlab.gnome.org/GNOME/gnome-build-meta/blob/master/project.conf#L64 That looks alright to me right ?13:19
tristanjonathanmaw_, Maybe we are missing tests for declared partial mirrors, where not all aliases are redefined in a mirror ?13:19
tristannice, it's perfectly reproducible = fixable13:21
*** jonathanmaw_ is now known as jonathanmaw13:23
jonathanmaw tristan: yep, that looks like the right format for mirrors. And yeah, I think the tests might be missing the case of mirrors not covering all aliases13:23
tristanjonathanmaw, interestingly `bst fetch sdk/brotli.bst` reproduces this crash from gnome-build-meta perfectly for me13:24
tristanjonathanmaw, I have to run now... would you care to take a look at this crasher ?13:24
* tristan needs to delay the release for this13:24
tristanWhat I have noticed, is in Source._fetch(), after instantiating the new source13:25
tristanI've added assert source._update_state() and assert source._get_consistency() != Consistency.INCONSISTENT, the assertion raises13:25
*** alatiera__ has joined #buildstream13:25
tristanSo, the newly instantiated source does not have it's ref set13:25
tristanAha, and there lies the problem !13:26
tristanjonathanmaw, I see... the source in fact does not have the ref set13:26
tristanjonathanmaw, And bst fetch is crashing instead of noticing that it must track13:26
tristanEven in a build, it's not noticing13:27
*** alatiera_ has quit IRC13:27
tristanWeird, ok I have something to go on if it's not magically fixed by tomorrow13:27
tristangnome-build-meta uses project.refs, but my old project.refs has core-deps/brolti.bst there, so it should have required a track (it seems to have been renamed to sdk/brolti.bst)13:29
tristanjonathanmaw, I no longer suspect that it is a source mirroring issue, by the way :)13:29
tristanOf course, I'd be delighted if I found it fixed behind my back :)13:30
*** alatiera_ has joined #buildstream13:33
*** tristan has quit IRC13:33
*** alatiera__ has quit IRC13:34
paulsher1oodplease can we change this "conclave" name? it's a clear mistake13:41
qinustytlater[m] do you know what a sources cache key is supposed to be in the log?13:41
qinustyIs it the task id (it's elements id)?13:41
qinusty+1 paulsher1ood13:41
*** finn_ has quit IRC13:43
*** phildawson has quit IRC13:43
*** phildawson has joined #buildstream13:46
tlater[m]qinusty: Sorry, not off the top of my head :|13:47
tlater[m]I did finish my little write-up: https://gitlab.com/BuildStream/buildstream/merge_requests/812#note_10312572713:47
* tlater[m] hopes that explains it well enough, and goes back to double-checking references in a report.13:47
*** finn_ has joined #buildstream13:48
jjardontlater[m]: did you have a chance to look to the CAS not emptying the cache? we got the server filled up again today :( https://gitlab.gnome.org/GNOME/gnome-build-meta/issues/4813:51
*** finn_ is now known as finn13:53
toscalixpaulsher1ood: changed https://wiki.gnome.org/Projects/BuildStream/Events#BuildStream_Gathering_201813:53
paulsher1oodtoscalix: i think conclave in spanish is a "false friend"13:53
tlater[m]jjardon: Yes, I've not managed to fill a server up and break it yet. I have suspicions, but I can't really fix anything without testing it - I hope to get a bit more done this weekend though.13:54
paulsher1oodtoscalix: tvm13:54
jjardontlater[m]: I can give you access to the GNOME server if that helps13:55
toscalixit is a latin word so it has a common meaning based on the root and then in each language might have additional meanings. But I do not think is worth arguing about the name. I added gathering13:55
*** finn_ has joined #buildstream13:55
paulsher1ood:-)13:55
*** finn has quit IRC13:56
* jjardon now wants to play magic the gathering13:56
tlater[m]jjardon: Appreciated, but I don't think it will help much - I'll want to run out of disk space every time I test, waiting to fill up a big server will take too long ;p13:56
jjardontlater[m]: we fill up it in one day yesterday. But sure I understand :)13:57
*** SotK has left #buildstream13:58
*** SotK has joined #buildstream13:58
jjardontlater[m]: btw, if you want to create a big file quickly: fallocate -l 10G 10Gigfile13:58
tlater[m]jjardon: Yeah, the problem is that that sort of "filling up" doesn't actually cause the exception14:00
tlater[m]I suspect it's lack of thinking about concurrency, so instead I'm trying mulitple pushes at the same time14:00
* tlater[m] does wonder if implementing something that allows just pushing files manually might help14:01
*** alatiera__ has joined #buildstream14:01
persiatlater[m]: Consider creating a small-ish file, and using that as a loopback mount for the cache directory.14:01
tlater[m]persia: Yep, I'm using an ext4-formatted file as a docker volume14:02
tlater[m]I've also tested with randomly-generated files in case file holes cause issues, etc.14:02
persiatlater[m]: does that permit the file to grow, or is the "server" limited to only 10MiB or so?14:02
*** alatiera_ has quit IRC14:03
tlater[m]persia: "server" is limited to 3G (because we have a minimum size of 2G)14:03
persiaHrm, yeah, filling 3G ends up taking a while, assuming you want real content.14:04
WSalmontoscalix, i have had a clash with some one when editing the wiki, i think i have fixed it but could you check you are happy, apologies if i have missed/messedup something14:07
tlater[m]persia: It will probably be helpful to modify the server a little to make testing easier, have some additional debugging output, etc., but I've only had ~10 hours of time on this so far spread accross a few days... So progress is slow.14:08
tlater[m]I also think I might need multiple BuildStream instances pushing concurrently, which I haven't tested yet.14:09
tlater[m]But anyway, I don't really have time to do much more today - I promise to shout out if I can fix it :)14:10
qinustytlater[m], before I forget. I'd also like to see the configurable warnings logic moved out of the plugin messaging API and into context14:11
qinustyWhich will allow us to produce fatal warnings from outside of plugin logic14:11
tlater[m]qinusty: Is that commented on the relevant MR?14:12
* qinusty checks14:12
tlater[m]I'll forget if it's just here ;p14:12
qinustyAdded a comment :D14:14
persiatlater[m]: Makes sense.  Good luck.14:15
qinustyApologies for dumping this onto you tlater[m], I carried the flame as far as I could14:15
tlater[m]qinusty: No problem at all, I mean, you sort of took the flame from me and ran with it.14:17
tlater[m]Hehe14:17
qinustyI guess :D14:17
qinustyI'm not sure what you want to do about those commits in the log. There is two commits from you which I didn't spend a load of time getting to work under the massive rebase. They're probably best being flattened on merge14:18
*** alatiera_ has joined #buildstream14:19
*** lachlan has quit IRC14:20
*** alatiera__ has quit IRC14:20
*** mohan43u has quit IRC14:30
*** alatiera__ has joined #buildstream14:32
*** alatiera_ has quit IRC14:34
*** lachlan has joined #buildstream14:36
*** mohan43u has joined #buildstream14:44
*** abderrahim has quit IRC14:47
*** abderrahim has joined #buildstream14:48
toscalixWSalmon: I erased the topics from the specific agenda because we ned to know first the room availability and people's availability. Your suggestions remain in the proposed topics section. Thanks for adding them14:56
*** mohan43u has quit IRC14:57
toscalixI might use the BuildSTream calendar instead of the wiki for consolidating the schedule14:57
toscalixjjardon: is still master broken?14:59
toscalixso you cannot build freedesktop-sdk?14:59
gitlab-br-botbuildstream: merge request (willsalmon/outOfSourecBuild->master: Out of source builds) #776 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/77615:01
*** mohan43u has joined #buildstream15:01
jjardontoscalix: yes15:01
jjardonhttps://gitlab.com/BuildStream/buildstream/issues/664 (note that bst-1.2 works fine)15:03
toscalixI label the bug as critical and assigned it to tristan. We need to fix it right away, if we can15:03
toscalixvalentind: around? able to help?15:03
toscalixwe should put as test to build freedesktop-sdk15:04
toscalixbeing our main source if users reports, we should take it as validation project15:04
toscalixuntil we have a better one15:04
toscalixit seems buildgrid might be another option in the near future15:04
toscalixif you commit breaks freedesktop-sdk.... it is no worth reviewing15:05
toscalixs/validation/pre-integration15:06
toscalixtiagogomes_: around? able to help?15:12
toscalixThe idea should be to revert the change that caused the problem, de-escalate the severity and then tomorrow work out what happened15:12
toscalixbut leave today freedesktop-sdk working before we go home15:13
toscalixjjardon: are you able to identify the commit that has caused the issue?15:14
*** alatiera_ has joined #buildstream15:29
*** alatiera__ has quit IRC15:31
gitlab-br-botbuildstream: merge request (Qinusty/235-manifest->master: WIP: Implement generated build manifests) #596 changed state ("closed"): https://gitlab.com/BuildStream/buildstream/merge_requests/59615:40
tpollardjjardon: do you know if gnome-build-meta is broken against bst master?15:49
gitlab-br-botbuildstream: merge request (willsalmon/outOfSourecBuild->master: Out of source builds) #776 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/77615:49
*** alatiera__ has joined #buildstream15:54
gitlab-br-botbuildstream: merge request (jmac/remote_exec_checkout_fix->master: Remote exec: Remove early warning and check directory is not None) #800 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/80015:54
tpollardugghh15:55
*** alatiera_ has quit IRC15:56
*** johanneshilling has quit IRC16:01
*** qinusty has quit IRC16:01
*** jennis has quit IRC16:01
*** coldtom has quit IRC16:01
*** adds68 has quit IRC16:01
*** tiagogomes_ has quit IRC16:01
*** qinusty has joined #buildstream16:02
*** iker has quit IRC16:02
*** johanneshilling has joined #buildstream16:05
*** jennis has joined #buildstream16:07
*** adds68 has joined #buildstream16:13
*** lachlan has quit IRC16:13
*** lachlan has joined #buildstream16:19
*** lachlan has quit IRC16:19
*** lachlan has joined #buildstream16:20
jjardontpollard: no idea16:23
jjardontpollard: well probably yes, as gnome-build-meta uses freedesktop-sdk16:23
jjardontoscalix: as I said, freedesktop-sdk is working fine; we use a stable release of buildstream to build. It's only the daily job to build with bst master the one that is failing16:24
*** alatiera_ has joined #buildstream16:46
*** alatiera__ has quit IRC16:48
*** alatiera__ has joined #buildstream16:48
*** alatiera_ has quit IRC16:50
*** alatiera_ has joined #buildstream16:50
*** lachlan has quit IRC16:51
*** alatiera__ has quit IRC16:52
*** finn_ has quit IRC16:57
juergbijjardon: do you have a last known working pipeline for a buildstream master build? it seems it was already broken yesterday (d8450166) but I can't easily find older pipelines for buildstream master16:58
*** xjuan has joined #buildstream17:03
jjardonjuergbi: no , sorry; we setup the job to build freedesktop-sdk with bst master yesterday17:03
juergbiah ok17:04
*** lachlan has joined #buildstream17:07
*** tristan has joined #buildstream17:08
gitlab-br-botbuildstream: issue #665 ("Buildstream tries to use message without a message handler if linux platform and no user namespace support") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/66517:15
*** lachlan has quit IRC17:16
*** lachlan has joined #buildstream17:23
*** jonathanmaw has quit IRC17:26
*** toscalix has quit IRC17:26
*** tristan has quit IRC17:30
*** alatiera__ has joined #buildstream17:31
*** alatiera_ has quit IRC17:33
*** alatiera_ has joined #buildstream17:34
*** lachlan has quit IRC17:35
*** alatiera__ has quit IRC17:35
*** alatiera__ has joined #buildstream17:36
*** alatiera_ has quit IRC17:37
gitlab-br-botbuildstream: merge request (jmac/vdir_import_test->master: Import test for virtual directories) #815 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/81517:39
*** alatiera_ has joined #buildstream17:39
*** alatiera__ has quit IRC17:39
*** tristan has joined #buildstream17:44
*** finn has joined #buildstream18:14
*** tristan has quit IRC18:18
*** tristan has joined #buildstream19:23
*** coldtom has joined #buildstream20:20
valentindjjardon, seems like the flatpak_image plugin does not work with buildstream master. Is that the problem?20:43
*** tristan has quit IRC21:12
*** cs-shadow has quit IRC21:32
*** mohan43u has quit IRC22:29
*** mohan43u has joined #buildstream22:30
*** mohan43u has quit IRC22:33
*** mohan43u has joined #buildstream22:36
*** mohan43u has quit IRC22:43
*** mohan43u has joined #buildstream23:01
*** mohan43u has quit IRC23:19
*** mohan43u has joined #buildstream23:25
*** hergertme_ has joined #buildstream23:33
*** hergertme has quit IRC23:35
*** hergertme_ is now known as hergertme23:56

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