IRC logs for #buildstream for Tuesday, 2020-02-04

*** narispo has quit IRC06:23
*** narispo has joined #buildstream06:25
*** narispo has quit IRC06:34
*** narispo has joined #buildstream06:35
*** mohan43u has quit IRC06:37
*** mohan43u has joined #buildstream06:39
*** narispo has quit IRC06:54
*** narispo has joined #buildstream06:54
*** traveltissues has joined #buildstream08:47
*** coldtom4 is now known as coldtom09:06
*** santi has joined #buildstream09:54
*** tpollard has joined #buildstream09:59
*** jonathanmaw has joined #buildstream10:16
coldtomanyone against merging https://gitlab.com/BuildStream/buildstream-docker-images/-/merge_requests/157 ?10:24
benschubertcoldtom: I actually had one comment still, just noticed it today10:26
*** phildawson-ct has joined #buildstream10:45
*** phildawson has quit IRC10:47
*** cs-shadow has joined #buildstream10:53
benschubertWSalmon: one amendment to what I said at FOSDEM about breaking changes on plugins, there will be at least one, for adapting for the RemoteAssetAPI (Formerly FetchAPI)11:07
WSalmonah, thanks for the heads up benschubert11:13
benschubertWSalmon: that would probably only affect source plugins and should not be a huge hard change11:14
WSalmonack benschubert11:14
benschubertcoldtom: thanks :) Do you have merge rights or want me to merge?11:16
WSalmoni had assumed that remote things could be don so as to not impinge on the plug-ins them selves only how they are invoked, but i can see that the subtleties of how they work especially around sources could lead to breaks11:16
coldtomi have merge rights for that repo, thanks benschubert!11:17
WSalmonok, it seems no one moved coldtom in to the merge rights group once his first commits landed could juergbi or some one add him to the list?11:18
WSalmoni assume we still work like that11:18
*** traveltissues has quit IRC11:18
*** traveltissues has joined #buildstream11:19
juergbiWSalmon: buildstream or docker-images merge rights are missing?11:20
WSalmoni think he has docker but should have buildstream11:20
coldtom^ that is correct11:20
WSalmon*should have both11:20
juergbicoldtom: fixed11:25
coldtomta juergbi11:25
WSalmonthanks juergbi11:30
*** narispo has quit IRC11:31
*** narispo has joined #buildstream11:41
*** traveltissues has quit IRC12:18
*** narispo has quit IRC12:20
*** narispo has joined #buildstream12:20
*** narispo has quit IRC12:59
*** narispo has joined #buildstream13:01
*** lachlan has joined #buildstream13:02
*** lachlan has quit IRC13:04
*** lachlan has joined #buildstream13:04
*** traveltissues has joined #buildstream13:12
*** lachlan has quit IRC13:15
*** lachlan has joined #buildstream13:16
*** lachlan has quit IRC13:19
*** narispo has quit IRC13:26
*** narispo has joined #buildstream13:27
*** phildawson-ct has quit IRC13:44
*** lachlan has joined #buildstream13:47
*** phildawson-ct has joined #buildstream13:48
*** lachlan has quit IRC13:56
*** phildawson-ct has quit IRC14:15
*** phildawson-ct has joined #buildstream14:15
*** phildawson-ct has quit IRC14:26
*** phildawson-ct has joined #buildstream14:27
juergbioh, we have duplicate but outdated tar plugin in bst-plugins-experimental :-/14:31
juergbithat was very confusing14:31
*** phildawson-ct has quit IRC14:32
*** phildawson-ct has joined #buildstream14:32
juergbibenschubert: I assume ^^^ is temporary but apparently it was incorrect for more than two months14:34
juergbiis there something we can improve to avoid this happening again?14:35
coldtomthe problem is that the tar plugin is massively wrapped up with the rest of the test suite i believe, so the MR to migrate it out of the main repo never landed14:38
coldtomfor example, the docs also depend on it14:38
juergbiok but duplicate code for months is not exactly a solution either14:40
juergbihttps://gitlab.com/BuildStream/bst-plugins-experimental/-/merge_requests/8114:40
coldtomagreed, i think there was talk of a decorator to allow external plugin deps for some tests to allow this14:41
juergbicoldtom: I'm a bit out of the loop with the external plugin work. do I need to bump a version in buildstream git (tox.ini?) to get the fixed plugins after my MR is merged?14:42
juergbior does it use plugins-experimental master in buildstream master CI?14:43
cs-shadowIMHO  we shouldn't merge either MR until both MRs are ready (i.e. the MR on plugins repo and the buildstream MR).14:43
cs-shadowI think we've been too eager with the plugin move lately14:43
juergbiI agree14:43
coldtom+114:43
juergbishall we rip tar out in that case?14:43
cs-shadowjuergbi: both buildstream and plugins run against a  fixed tag  of each other . For buildstream, it's captured here: https://gitlab.com/BuildStream/buildstream/-/blob/master/tox.ini#L1114:44
juergbior will that cause any problems?14:44
juergbics-shadow: ok, I guessed correctly, then. thanks14:44
cs-shadowI'd personally be fine with removing tar  from plugins-experimental since it's not solving anything at this  stage14:45
cs-shadowthe only  downside I can think of is  if someone started depending on that version of it14:45
cs-shadowbut  I don't know if  that has happened already or not14:45
juergbipip is also duplicated14:45
coldtomcs-shadow: i can say that none of the projects i've done with bst master have depended on it, not sure about others though14:46
juergbiok, and otherwise it should be trivial to change those projects back to the core plugin14:46
juergbisame holds true for the pip plugins, I suppose14:47
cs-shadowyeah, I vote  for  removing tar then, since it's more hairy14:47
juergbithat was merged very recently, though. maybe pip removal on buildstream is almost ready14:47
cs-shadowpip I think is close to being ready in https://gitlab.com/BuildStream/buildstream/-/merge_requests/1810 so maybe we juts  need to do that14:47
juergbiok, will just remove tar14:48
*** narispo has quit IRC15:06
tpollardpip just needs the pytest support for the cache key test, unless anyone thinks otherwise15:09
juergbics-shadow: oh, the deb plugin depends on the tar plugin15:15
cs-shadowah! I hadn't realized that  until now15:16
*** rdale has quit IRC15:16
*** rdale has joined #buildstream15:16
cs-shadowthat's probably also wrong on its own though15:17
cs-shadowso, we manually update tar for now?15:17
juergbiI guess that's the simplest approach15:18
juergbihopefully not necessary for too long15:18
*** bochecha_ has joined #buildstream15:23
*** bochecha has quit IRC15:23
*** bochecha_ is now known as bochecha15:23
*** bochecha_ has joined #buildstream15:24
*** bochecha has quit IRC15:26
*** bochecha_ is now known as bochecha15:26
*** traveltissues has joined #buildstream15:31
*** bochecha has quit IRC15:32
*** jonathanmaw has quit IRC15:33
*** jonathanmaw has joined #buildstream15:34
*** phildawson-ct has quit IRC15:38
*** phildawson-ct has joined #buildstream15:41
*** phildawson-ct has quit IRC15:47
juergbics-shadow: are you aware of the issue with the tests-plugins-master test in buildstream?15:58
juergbi INTERNALERROR> pkg_resources.VersionConflict: (BuildStream 1.93.0+44.gb57dbff9 (/builds/BuildStream/buildstream/src), Requirement.parse('buildstream>=1.93.0.dev0<2.0.0'))15:58
juergbi(or anyone else)15:58
cs-shadowjuergbi: I wasn't aware of this. Seems like setuptools doesn't think that 1.93.0.gitsha is >= 1.93.0.dev016:00
cs-shadowif one of them is considered  strictly less than the other we can probably fix this nicely, otherwise maybe just do a > 1.92.10 or something. I need to run to a meeting but I'll have a look at fixing this later this evening unless you fix it already16:02
juergbiok, ta. I might take a closer look, will let you know if I do16:04
*** traveltissues has quit IRC16:05
*** xjuan has joined #buildstream16:19
*** phildawson-ct has joined #buildstream16:20
juergbics-shadow: hm, odd, this returns True: version.parse("1.93.0+44.gb57dbff9") >= version.parse("1.93.0.dev0")16:35
juergbiwondering whether it's somehow using a version check function that is not compliant with PEP44016:36
juergbino, I don't think so16:40
juergbithe issue could be that it considers the git URL for buildstream specified in plugins-experimental tox.ini to be a better match than the buildstream branch16:43
*** lachlan has joined #buildstream17:06
gitlab-br-botcs-shadow opened issue #1260 (Tests are failing against bst-plugins-experimental master) on buildstream https://gitlab.com/BuildStream/buildstream/issues/126017:13
cs-shadowjuergbi: that's odd - created ^ for record. Seems like `pip` is happy to install it, but setuptools/pkg_resources fails to find it17:15
*** lachlan has quit IRC17:31
benschubertjuergbi: 1) I will send an email to the ML tomorrow for a proposal on handling more involved tests when we extract plugin so we can correctly excise tar from BuildStream17:36
benschubert2) We have a problem with bst-plugins-experimental specifying buildstream as a dependency. I want to remove it, but I think some people were against it? And that is the reason for your second problem I think17:36
juergbiok, thanks for the info17:38
juergbibenschubert: if 2) is also an issue if we tag a new plugins-experimental release, then this is a blocker for !176117:38
gitlab-br-botMR !1761: mtime support https://gitlab.com/BuildStream/buildstream/-/merge_requests/176117:38
benschubertjuergbi: Is it? tests do pass17:39
benschubertor am I missing something?17:39
juergbibenschubert: the broken/outdated tar plugin from bst-plugins-experimental 0.15.0 is the cause of the userchroot test failure in the mtime MR17:40
juergbithe tar plugin update is merged now to bst-plugins-experimental master17:41
juergbibut if upgrading buildstream CI to latest bst-plugins-experimental is blocked by (2) above, it's hence also a blocker for !176117:41
juergbiI can get the test to pass by dropping the bst version check in bst-plugins-experimental install-requirements.txt17:43
benschubertLet's do that17:43
*** jonathanmaw has quit IRC18:01
juergbibenschubert: https://gitlab.com/BuildStream/bst-plugins-experimental/-/merge_requests/8218:03
juergbibenschubert: ah, I just saw your https://gitlab.com/BuildStream/bst-plugins-experimental/-/merge_requests/7618:04
juergbiwondering whether that might fix the issue as well18:04
*** santi has quit IRC18:04
benschubertjuergbi: it would not I think18:04
benschubertbut we can definitely merge it :)18:04
benschubertah no, I need a rebase18:05
benschubertlet me do that18:05
juergbiok, let's merge that after rebase and then let's do a quick test in buildstream CI just in case18:05
benschubertdone18:07
benschubertgood to merge?18:07
juergbibenschubert: yes, approved18:12
benschubertset to merge18:13
juergbiI actually misread the diff before. you're right, that won't fix the other issue18:13
benschubertI'm not even sure why we want the plugin to depend on buildstream :/18:13
juergbibenschubert: my guess was that it's needed to test bst-plugins-experimental via tox, i.e., to have it automatically install a suitable version of buildstream in the venv18:15
juergbibut that might be completely wrong18:15
benschubertI think we pin the version in tox itself, I'm not sure anymore18:17
benschubertif removing version pinning doesn't break, that means it's not handled by this part18:17
cs-shadowno, I think this is more of a philosophical question - should plugins depend on the thing they are plugins for?18:17
cs-shadowone side of the argument goes that since they `import` something, they should. Whereas the other side goes that it's implicit that the plugins need what they are plugins for and should only list additional stuff18:18
juergbiright. strictly to indicate a requirement/dependency, the latter does seem logical18:19
juergbihowever, with pip auto-installing dependencies, it gets a bit odd18:19
benschubertand we don't want to have to do pip install --no-deps because it gets weird :)18:20
juergbiyep, so unless we can disable auto-install somehow for the dependency on 'buildstream', I'd rather not have the dependency listed at all18:20
juergbi(assuming this doesn't break tox in plugins-experimental)18:21
benschubertwe have our ways of adding that to tox, it's definitely not a problem18:21
juergbithat said, I don't have a very strong opinion on it. I mainly want to avoid breakage in buildstream core18:21
benschubert+2 on that18:22
juergbibenschubert: I think the version number in install-requirements.txt also had the effect that test-master-fedora-31 wasn't actually testing buildstream master: https://gitlab.com/BuildStream/bst-plugins-experimental/-/jobs/42579747718:31
juergbiotherwise that error message would also appear in other branches18:31
benschubert-_- right18:31
*** xjuan has quit IRC20:40
*** xjuan has joined #buildstream22:11
*** ikerperez has quit IRC22:12
*** xjuan has quit IRC22:14
*** xjuan has joined #buildstream22:14
*** xjuan has quit IRC22:33

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