IRC logs for #buildstream for Monday, 2019-01-28

*** reborn has quit IRC01:17
*** nimish has joined #buildstream01:18
*** nimish has quit IRC01:40
*** nimish has joined #buildstream01:57
*** nimish has quit IRC02:22
*** nimish has joined #buildstream02:51
*** nimish has quit IRC03:01
*** toscalix has joined #buildstream08:41
*** alatiera has joined #buildstream09:04
*** benschubert has joined #buildstream09:17
*** sambishop has joined #buildstream09:19
gitlab-br-botjuergbi approved MR !1095 (valentindavid/crash_in_scheduler_857->master: Fix crash when spawned job completes very fast) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/109509:23
gitlab-br-botjuergbi approved MR !1099 (valentindavid/wrong_type_in_status_code->master: Fix type of error codes in CAS server) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/109909:23
gitlab-br-botjuergbi approved MR !1092 (valentindavid/make_cache_dir->master: Make sure testing cache directory exists) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/109209:27
gitlab-br-botjuergbi approved MR !1086 (aevri/bst_track_guidance->master: Fixup refs to 'bst track' and 'bst fetch') on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/108609:33
valentindjuergbi, I think we do not need !1092 anymore. The merge for centos fixed it in another way.09:46
valentindI will close it.09:46
gitlab-br-botvalentindavid closed MR !1092 (valentindavid/make_cache_dir->master: Make sure testing cache directory exists) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/109209:47
juergbiah, handled in .gitlab-ci.yml now09:47
juergbivalentind: couldn't this still be an issue when running integration tests locally?09:48
valentindjuergbi, maybe. I was fixing an issue with the arm builder.09:48
valentindWe can reopen it if someone has an issue locally.09:48
juergbitox doesn't seem to like Ctrl+C, really annoying09:54
juergbiit keeps running in the background09:55
juergbihave to manually killall pytest09:55
*** raoul has joined #buildstream09:56
gitlab-br-botjuergbi reopened MR !1092 (valentindavid/make_cache_dir->master: Make sure testing cache directory exists) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/109209:56
*** tpollard has joined #buildstream10:06
*** jonathanmaw has joined #buildstream10:12
*** rdale has joined #buildstream10:15
*** SotK is now known as SotK_10:45
*** SotK has joined #buildstream10:45
phildawsonHi all, I've got a couple of MRs up at the moment that could do with some review. If anyone has time to take a look at !1057 and/or !1075 I'd much appreciate it.10:52
gitlab-br-botMR !1057: plugin.py: Add API to allow plugins to raise deprecation warnings https://gitlab.com/BuildStream/buildstream/merge_requests/105710:52
gitlab-br-botMR !1075: Expose basic api for testing external plugins. https://gitlab.com/BuildStream/buildstream/merge_requests/107510:52
laurencetristan, for this issue re local cache size calculation - https://gitlab.com/BuildStream/buildstream/issues/869 - i think it may be better to ask the original issue raiser to close the ticket once the fix has landed in master11:12
laurencei'm an advocate of this workflow - i think it makes more sense than closing off the tickets directly (as can sometimes happen with gitlab's ui)11:12
laurencedo you mind if i re-open and ping benschubert on the ticket?11:13
gitlab-br-botLaurenceUrhegyi reopened issue #869 (Local cache size calculation is wrong) on buildstream https://gitlab.com/BuildStream/buildstream/issues/86911:14
gitlab-br-botaevri merged MR !1086 (aevri/bst_track_guidance->master: Fixup refs to 'bst track' and 'bst fetch') on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/108611:36
jjardonlaurence: that breaks how gitlab is meant to work: issues get closed when the MR gets merged; I think is better to reopen if the issue is seen again after testing, or even open a new issue (the root cause can be a completely different one)11:48
laurencejjardon, I thought it was only if you use the UI from within an issue and press 'create merge request' or due to our gitlab template on MRs (not sure if this template is even still there actually?)11:51
laurencei think we can still link an MR to an issue, without closing the issue, and ask the original submitter to verify (this depends on them using master branch or a dev branch)11:52
laurencenot sure if we can automate it just yet11:52
laurenceanyway, i think we'll discuss gitlab usage / governance / committer policy over the next week11:52
jjardonno; if you put in the merge request (or in the commit message in the commit of the git branch) "Fixes #12", Issue 12 will be fixed when the MR / commit gets merged. github works in the same way11:53
gitlab-br-botIssue #12: installing buildstream on fresh jessie from instructions at http://buildstream.gitlab.io/buildstream/install.html#installing https://gitlab.com/BuildStream/buildstream/issues/1211:53
jjardonThis is if you use "Fixes" or "Closes" keywords; if not the issue/Mr are linked but issue doesn't get closed11:54
jjardonlaurence: also, problem with ask to verify is that people forget and then you will have a long list of issues that are fixed but not closed because they are verify yet; I think is better to be proactive and close them and expect the reporter to reopen / open a new one if he sees the problem again11:56
laurencehmmm that's another angle, although is frustrating if someone closes an issue that doesn't fix my issue.11:59
persiaMy experience with systems that depend on reporter feedback is that most of the reporter feedback is not useful for development (sadly).  I think a lot of reporters are used to either opening new issues (with a subtly different description and referencing the issue that was incorrectly diagnosed), or to reopen the issue with something like "Thanks for fixing that other bug, but the problem I described initially still occurs (with a test case or12:00
persiaexample output, etc.).12:00
jjardonlaurence: sure, but you get a notification when it gets closed, so you can quickly check; although sometimes It doesn't get fixed, we should assume the dev knows what he is doing and the default is that it actually gets fixed12:01
laurencejjardon, if this were a community driven project, i'd be tempted to agree12:02
laurenceanyway, it's not a very important point, not one to debate for a long time :)12:03
jjardonlaurence: you have a point there, sure12:04
*** cs-shadow has joined #buildstream12:09
laurenceReading some back-scroll from this channel, I see another topic to bring for discussion this week, about disabling caches for a command12:12
laurencetpollard started some work on this a while back - https://gitlab.com/BuildStream/buildstream/merge_requests/95012:12
laurencewill raise it this week12:12
jjardonjennis: hey, seems https://gitlab.com/BuildStream/buildstream/tree/jennis/add_new_profile_topic doesn't exist anymore; Did it got merged?12:15
jennisjjardon, yeah pretty sure it did12:16
jennisone sec12:16
jennisjjardon, yes it exists in master, I think the source branch just got removed upon merge12:16
jennisDo you want me to repush?12:17
jjardonjennis: no need, thanks12:19
*** raoul has quit IRC12:29
*** sambishop has quit IRC13:01
*** bochecha has joined #buildstream13:01
gitlab-br-botjennis opened MR !1112 (jennis/filter-docs->master: Improve our filter documentation) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/111213:07
jennisjonathanmaw, would you be able to spare some time to review https://gitlab.com/BuildStream/buildstream/merge_requests/1112 ? It's an improvement (I hope...) to our filter documentation13:08
jonathanmawjennis: I'll have a look13:09
*** raoul has joined #buildstream13:14
*** bochecha has quit IRC13:16
*** sambishop has joined #buildstream13:22
abderrahim[m]   laurence : case in point, looking through the bug list, I found #179 and #706 which are fixed but are waiting for an ack13:24
gitlab-br-botIssue #179: Be smarter about querying summaries from remote caches https://gitlab.com/BuildStream/buildstream/issues/17913:24
gitlab-br-botIssue #706: Information when a circular dependency is detected is not good enough https://gitlab.com/BuildStream/buildstream/issues/70613:24
Kinnisonabderrahim[m]: Hi!  Thanks for the data sets you provided.13:24
abderrahim[m]jjardon: adds68  ^13:25
abderrahim[m]Kinnison: :)13:25
juergbilaurence: regarding disabling artifact servers, my proposal for artifact server configuration was supposed to cover this as well13:28
juergbii.e., I think we need an overall discussion on artifact server configuration13:28
abderrahim[m]speaking of artifact servers, I have a branch to fix #40113:29
gitlab-br-botIssue #401: If a project B use project A as a junction, B should not try to use the bst remote cache of A (at least by default) https://gitlab.com/BuildStream/buildstream/issues/40113:29
jonathanmawjennis: I'm finished reviewing !111213:32
gitlab-br-botabderrahimk opened MR !1113 (abderrahim/artifact-cache-junction->master: Use artifact cache specs from the parent project before those defined in junctions) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/111313:37
tpollardinteresting13:41
gitlab-br-bottpollard closed issue #829 (Download buildtrees on demand for bst shell --build) on buildstream https://gitlab.com/BuildStream/buildstream/issues/82913:44
gitlab-br-bottpollard merged MR !1050 (tpollard/829->master: Download buildtrees on demand for bst shell --use-buildtree) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/105013:44
*** nimish has joined #buildstream13:52
*** lachlan has joined #buildstream13:56
*** sambishop has quit IRC13:56
*** nimish has quit IRC13:56
*** nimish has joined #buildstream13:57
*** nimish has joined #buildstream13:57
*** raoul has quit IRC14:01
*** sambishop has joined #buildstream14:01
*** lachlan has quit IRC14:03
*** nimish_ has joined #buildstream14:03
*** nimish has quit IRC14:03
*** nimish_ is now known as nimish14:04
*** lachlan has joined #buildstream14:06
paulsherwood12:02 < laurence> jjardon, if this were a community driven project, i'd be tempted to agree14:06
paulsherwoodlaurence: what makes you think it isn't?14:06
*** nimish has quit IRC14:13
*** nimish has joined #buildstream14:13
paulsherwoodwell, in any case, i believe it is14:19
gitlab-br-botjjardon opened issue #884 (Traceback with current master (cd9b8e54aad6aa885afd28cefbbd40ea77c9353d)) on buildstream https://gitlab.com/BuildStream/buildstream/issues/88414:23
*** nimish has quit IRC14:23
*** nimish has joined #buildstream14:24
jjardonDoes anyone have the same problem as ^ with current master?14:26
abderrahim[m]jjardon: I believe you need to update grpcio14:29
jonathanmawbenschubert: would you like to have a look at https://gitlab.com/BuildStream/buildstream/merge_requests/1108 ?14:29
juergbiyes, can you try with: pip3 install --user -U --upgrade-strategy eager .14:29
juergbi(optionally also use -e)14:30
juergbipip doesn't upgrade dependencies automatically otherwise, iirc14:30
abderrahim[m]I never found the time to search for the minimum version that works, but it definitely won't work with 1.1014:30
benschubertjonathanmaw: thanks I'll have a look14:30
abderrahim[m]juergbi: well it does if the minimum requirement isn't met14:30
juergbiright14:31
juergbiso if it doesn't work right now, we may need to bump our minimum reqs14:31
abderrahim[m]jjardon: what version of grpcio do you have?14:32
jjardon1.17.114:32
*** nimish has quit IRC14:34
*** nimish has joined #buildstream14:35
jonathanmawta benschubert14:35
abderrahim[m]jjardon: works fine here with 1.16.1 and 1.17.1, maybe it's protobuf then14:43
abderrahim[m](and make sure you don't have more than one version installed, that may be also the problem)14:44
*** nimish has quit IRC14:45
*** sambishop has quit IRC14:45
*** raoul has joined #buildstream14:46
*** nimish has joined #buildstream14:48
*** nimish has joined #buildstream14:49
*** lachlan has quit IRC14:50
*** nimish has quit IRC14:50
abderrahim[m]jjardon: yeah, it's protobuf. You need at least 3.6.014:53
jennisthanks for the review jonathanmaw14:56
jjardonabderrahim[m]: mmm, I wonder how come the required version didn't got install with "pip install --user ."14:57
jjardonah, the requires is >=3.514:59
gitlab-br-botabderrahimk opened MR !1114 (abderrahim/protobuf-version->master: requirements/requirements.in: require protobuf >= 3.6) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/111414:59
jjardonwith protobuf 3.6 I got another error:15:00
jjardonhttps://www.irccloud.com/pastebin/iyWI6qJR/15:00
*** sambishop has joined #buildstream15:01
juergbijjardon: that would be too old system click15:03
tpollardyup15:05
jjardonmmm15:06
jjardonIs "pip3 install --user ." not the recommended way to install buildstream anymore?15:06
abderrahim[m]jjardon: if you have an older pip, it works15:07
abderrahim[m]with a newer version, you can use --upgrade-strategy eager15:07
abderrahim[m]but I agree that this should be fixed15:07
jjardonAre we not exercising the default installation anywhere? Maybe we can add some CI job somewhere15:08
jjardonand yeah we should update the docs15:08
abderrahim[m]jjardon: by updating the minimum version, it should work15:09
abderrahim[m]it would be nice to have a CI job to test things with the oldest supported version15:09
*** lachlan has joined #buildstream15:09
tpollardthe requirements file is pinned to 7.015:10
jjardonok, so if I use requirements/requirements.txt instead requirements/requirements.in in setup.py, everything works as expected15:10
jjardonis this expected or a bug?15:10
jennisWould appreciate a review of https://gitlab.com/BuildStream/buildstream/merge_requests/1112 if anyone has the time15:11
abderrahim[m]jjardon: requirements.txt is used for reproducibility in the CI, so it always works15:11
abderrahim[m]the requirements.in gives the versions that should work, but isn't tested by the CI15:12
jjardonrigth15:12
abderrahim[m]is Click 7.0 the required version? I seem to recall it based on a discussion on the ML15:13
jjardonabderrahim[m]: looking at requirements.txt, seems you are rigth15:13
abderrahim[m]So it works with 7.0, and doesn't with 6.715:15
tpollardyeh I think hidden got added with 7.015:15
abderrahim[m]and there is no version in between15:16
benschubertjonathanmaw: I'm not sure about https://gitlab.com/BuildStream/buildstream/merge_requests/1108/diffs?commit_id=2d7460c832f9251c7f27e1c5698759fda01b6bfa#ba11c2672dd9b17f396563914c616d753b3b69e9_59_59 . Why is the error only available with sockets and not the rest?15:16
* jjardon creates MR15:17
jennisabderrahim[m], yes Click 7.0 is required as it includes a feature to 'hide' commands, which we're using for various deprecations15:17
abderrahim[m]jjardon: I'll add it to mine15:17
jennise.g. bst fetch15:17
*** raoul_ has joined #buildstream15:18
*** raoul has quit IRC15:19
gitlab-br-botjjardon opened MR !1115 (jjardon/fix_minimum_deps->master: requirements/requirements.in: Update minimum dependencies) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/111515:19
*** lachlan has quit IRC15:21
jjardonabderrahim[m]: ah, you already created one :); please feel free to close mine15:21
*** kapil___ has joined #buildstream15:21
gitlab-br-botabderrahimk closed MR !1115 (jjardon/fix_minimum_deps->master: requirements/requirements.in: Update minimum dependencies) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/111515:23
jonathanmawbenschubert: afaict, the problem is only apparent when binding to a unix socket, where the allowed path length is surprisingly short15:24
gitlab-br-botjjardon approved MR !1114 (abderrahim/protobuf-version->master: requirements/requirements.in: update minimum versions) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/111415:25
gitlab-br-botjjardon opened issue #885 (Add CI to check current master works) on buildstream https://gitlab.com/BuildStream/buildstream/issues/88515:29
jonathanmawAIUI the unix specification is 108 characters, but linux normally permits longer paths, and WSL's implementation did not.15:29
skullmannah, it's that short on Linux too15:30
skullmanthe socket api is not good15:30
gitlab-br-botjjardon closed issue #706 (Information when a circular dependency is detected is not good enough) on buildstream https://gitlab.com/BuildStream/buildstream/issues/70615:32
benschubertjonathanmaw: ok I see, thanks!15:34
jonathanmawskullman: hmm, weird we haven't encountered it before, then. Maybe python is usually responsible for working around that and the WSL version took it down an unexpected code path15:35
jonathanmaweither that or the gitlab runner in docker mode's working directory is shorter than the runner in shell mode.15:36
*** lachlan has joined #buildstream15:37
skullmanpython doesn't work around it, I've had to stick a symlink in a tempdir as a work-around before in python15:37
gitlab-br-botjjardon closed issue #611 (Using a modern PEP8 linter detects errors/warnings) on buildstream https://gitlab.com/BuildStream/buildstream/issues/61115:42
KinnisonShould we have our workspace be something like C:\bsws then?15:47
jonathanmawI could configure my gitlab-runner to use a shorter directory15:54
jonathanmawthough the change I put in there would make the tests work for a casual user, so it offers a bit more15:54
*** raoul_ has quit IRC15:55
jonathanmawthough I'll need to change the comment because it's not actually a WSL-specific problem15:55
KinnisonThe safest thing might be to also ensure that we use a shorter path for the gitlab runner (maybe even bind a drive name to a path if you can do that)15:55
KinnisonBut yes, the generic improvements are always good15:55
* Kinnison ran into an issue of socket name lengths when ansibling things a while back15:55
*** raoul_ has joined #buildstream15:58
*** nimish has joined #buildstream16:18
jjardonKinnison: Is it possible to put those performance test in the CI somewhere?16:23
jjardonor bst have already something to detect performance regression?16:24
Kinnisonjjardon: We have a benchmarking suite which is being developed to monitor this kind of hting16:25
jjardonah cool16:25
Kinnisonthe stuff I came up with is not really suited to CI because it needs control over its environment and a human to interpret the results.16:25
* Kinnison will be going over it all in the first session tomorrow at the gathering16:25
Kinnisonif you're going to be there, you'll learn more then16:25
jjardonunfortunately I can not be there; any idea if it will be recorded?16:26
KinnisonI don't know, sorry16:26
*** nimish has quit IRC16:28
*** nimish has joined #buildstream16:28
benschubertjonathanmaw: thanks for the wsl effort :)16:29
*** nimish has quit IRC16:38
*** nimish has joined #buildstream16:39
*** sambishop has quit IRC16:45
*** nimish has quit IRC16:54
*** nimish has joined #buildstream16:54
*** nimish has joined #buildstream16:55
jennislachlan, jonathanmaw, this MR has been set for automatic merge but requires one more approval: https://gitlab.com/BuildStream/benchmarks/merge_requests/1217:08
jennisjonathanmaw, I guess you're happy to approve seeing as you set it to automatic merge17:08
jennis?17:08
* jonathanmaw just mashed the button17:08
jennisheh, thanks17:08
*** nimish has quit IRC17:10
*** nimish has joined #buildstream17:10
*** toscalix has quit IRC17:15
*** nimish has quit IRC17:15
*** nimish has joined #buildstream17:16
abderrahim[m]valentind: What's the status of #734? If you're not going to work on it, I'll try to do it17:20
gitlab-br-botIssue #734: Cleaning the internal cache is extremely slow https://gitlab.com/BuildStream/buildstream/issues/73417:20
*** nimish has quit IRC17:20
*** nimish has joined #buildstream17:21
abderrahim[m](I interrupted a cleanup after 13 hours, and it cleaned almost nothing. It didn't even clean all the artifacts from the performance testing)17:22
juergbiabderrahim[m]: I suspect the slowest part is determining what should be removed, not the actual removal17:26
juergbimore than 13 hours is horrible in any case17:27
abderrahim[m]it didn't finish cleaning up 8000+ 1~2kB artifacts, it's clear it's not the removal that takes long17:29
abderrahim[m]it may be fixable in the same way as for remote cache17:29
*** tpollard has quit IRC17:31
*** nimish has quit IRC17:31
*** nimish has joined #buildstream17:31
*** nimish has joined #buildstream17:32
*** phildawson has quit IRC17:34
*** jonathanmaw has quit IRC17:40
gitlab-br-botjennis approved MR !1113 (abderrahim/artifact-cache-junction->master: Use artifact cache specs from the parent project before those defined in junctions) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/111317:42
juergbiabderrahim[m]: yes. the issue is that BuildStream currently assumes that the whole artifact is cached locally if the artifact ref exists. cas object-based expiry breaks that assumption. we need to break that assumption anyway for 'partial cas' but that's what makes it less straight forward17:50
*** nimish has quit IRC17:52
*** nimish has joined #buildstream17:53
gitlab-br-botjjardon closed issue #884 (Traceback with current master (564cb2450a8657762e16c1d26d1373987dc4a6c5)) on buildstream https://gitlab.com/BuildStream/buildstream/issues/88417:54
gitlab-br-botjjardon merged MR !1114 (abderrahim/protobuf-version->master: requirements/requirements.in: update minimum versions) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/111417:54
*** nimish has quit IRC17:58
*** nimish has joined #buildstream17:58
*** raoul_ has quit IRC17:58
*** nimish has quit IRC18:03
*** nimish has joined #buildstream18:03
*** nimish has quit IRC18:18
*** nimish has joined #buildstream18:19
*** nimish has quit IRC18:34
*** nimish has joined #buildstream18:34
*** nimish has quit IRC18:39
*** nimish has joined #buildstream18:40
*** nimish has quit IRC18:45
*** nimish has joined #buildstream18:45
*** BILSTEIN has joined #buildstream18:46
*** BILSTEIN has left #buildstream18:48
*** nimish has quit IRC18:50
*** nimish has joined #buildstream18:51
*** alatiera has quit IRC19:07
*** nimish has quit IRC19:10
*** nimish has joined #buildstream19:11
*** nimish has joined #buildstream19:11
*** alatiera has joined #buildstream19:17
abderrahim[m]juergbi: my idea is to (1) use object-based expiry (2) go through all the refs and remove those that are missing objects (3) possibly do a last pass removing dangling objects19:19
abderrahim[m]would that work?19:19
abderrahim[m]my understanding is that now, bst removes the refs one by one, and for each ref does a (3). Is this correct?19:20
*** nimish has quit IRC19:21
*** nimish has joined #buildstream19:22
*** nimish has quit IRC19:27
*** nimish has joined #buildstream19:27
*** nimish has quit IRC19:37
*** nimish has joined #buildstream19:37
doras[m]jjardon: I'm actually modifying the freedesktop-sdk vm code, with hope to get it closer to running GNOME. So far I split systemd to libsystemd and "the rest", got systemd's default daemons to all load and run, and got dbus-daemon to host the system bus. All of this got me networking, DNS resolution and session management working (systemd-networkd, systemd-resolved and systemd-logind). I'll obviously share my changes as well once I turn19:42
doras[m]all the random hacks into actual integration code.19:42
doras[m]Since I rarely have time during weekdays, I think I'll start submitting changes incrementally. Or at least in a WIP MR.19:44
jjardondoras[m]: simply updating to systemd 240 gave us networking19:51
jjardonsee https://gitlab.com/freedesktop-sdk/freedesktop-sdk/issues/61919:52
jjardonthe first MR we were trying to add the needed users manually, but seems they are automatically added in 240 :)19:52
*** nimish has quit IRC19:52
*** nimish has joined #buildstream19:53
jjardondoras[m]: BTW, very cool project! please keep up posted (we basically do not work on that because lack of time)19:53
jjardonkeep us*19:53
jjardondoras[m]: some of us hang in #freedesktop-sdk in freenode as well19:54
jjardondoras[m]: Also, there is another MR to fix another stuff, take a look to the MR attached at https://gitlab.com/freedesktop-sdk/freedesktop-sdk/issues/61819:57
doras[m]jjardon: yeah, those are the two systemd bugs I mentioned yesterday. I saw they were fixed in 240 but postponed the update to fix a few other issues. I see you and valentind  had made similar progress.20:18
doras[m]I joined #freedesktop-sdk20:18
*** kapil___ has quit IRC20:41
*** nimish has quit IRC20:43
*** nimish has joined #buildstream20:43
gitlab-br-botjjardon opened issue #886 (Handshake timed out in the cache server) on buildstream https://gitlab.com/BuildStream/buildstream/issues/88620:47
juergbiabderrahim[m]: determining reachable objects from all refs would again be expensive/slow20:54
*** lachlan has quit IRC20:55
juergbiand there would be a big race condition between removing objects and removing the corresponding refs20:55
abderrahim[m]isn't the cleanup job supposed to have exclusive access to the cache?20:56
juergbipossibly, but ideally it's not needed20:58
juergbiwe should make sure BuildStream core can deal with partial artifacts in the local cache20:58
juergbiwe anyway want this to support reducing network bandwidth and local resources for remote execution20:59
juergbi(intermediate build results don't have to be completely downloaded with remote execution)20:59
abderrahim[m]I'm also thinking about 1.2. If the plan of dropping 1.4 proceeds, 1.2 still needs bugfixes21:00
jjardonabderrahim[m]: sorry it took so long to merge https://gitlab.com/freedesktop-sdk/infrastructure/freedesktop-sdk-docker-images/merge_requests/621:01
jjardonwrong channel21:01
juergbiyes, finding an acceptable but not too invasive solution for 1.2 might not be straight forward21:02
alatierawhat plan about 1.421:14
abderrahim[m]alatiera: not releasing 1.4, and going directly to 2.0 when it's ready21:15
alatieraoh21:16
alatieraany timeframe for 2.0? say a year?21:16
juergbisee also https://mail.gnome.org/archives/buildstream-list/2019-January/msg00010.html21:17
juergbino timeframe has been decided yet21:18
*** nimish has quit IRC21:18
*** nimish has joined #buildstream21:19
juergbiI would definitely hope that it still happens in 2019, though, but we'll likely discuss this at the gathering this week21:19
*** nimish has quit IRC21:44
*** nimish has joined #buildstream21:44
*** nimish has quit IRC21:49
*** nimish has joined #buildstream21:49
*** nimish has quit IRC21:54
*** nimish has joined #buildstream21:55
doras[m]juergbi, jennis: I've added a test for https://gitlab.com/BuildStream/buildstream/merge_requests/1110/21:59
doras[m]Nice CI setup, by the way. Writing tests is fairly easy as well.22:02
juergbigreat, thanks22:07
*** mohan43u has quit IRC22:23
*** mohan43u has joined #buildstream22:27
*** alatiera has quit IRC22:32
gitlab-br-botjuergbi closed issue #857 (test_pull_missing_blob spuriously crashes) on buildstream https://gitlab.com/BuildStream/buildstream/issues/85722:36
gitlab-br-botjuergbi merged MR !1095 (valentindavid/crash_in_scheduler_857->master: Fix crash when spawned job completes very fast) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/109522:36
doras[m]yikes, got a linting error.22:40
doras[m]Didn't expect that.22:41
doras[m]For some reason the linter lints stuff in .egg when run with "tox -e lint". That doesn't seem right.22:48
doras[m]".eggs"*22:50
*** mohan43u has quit IRC22:56
*** mohan43u has joined #buildstream23:00
gitlab-br-botdoraskayo opened MR !1116 (doraskayo/exclude-eggs-from-linting->master: setup.cfg: exclude .eggs/** from pycodestyle linting) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/111623:25
doras[m]Quite a silly MR.23:27
*** mohan43u has quit IRC23:37
*** mohan43u has joined #buildstream23:41

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