IRC logs for #buildstream for Monday, 2019-05-06

*** nimish2711 has joined #buildstream02:34
gitlab-br-bottristanvb opened issue #1016 (Artifact related bugs reported as user facing errors) on buildstream https://gitlab.com/BuildStream/buildstream/issues/101605:03
*** nimish2711 has quit IRC05:48
*** nimish2711 has joined #buildstream06:01
gitlab-br-bottristanvb opened issue #1017 (Last successful workspace build can go missing) on buildstream https://gitlab.com/BuildStream/buildstream/issues/101706:47
*** tristan has joined #buildstream06:50
*** tristan has quit IRC06:50
*** tristan has joined #buildstream07:16
*** tristan has quit IRC07:41
*** tristan has joined #buildstream07:42
*** bochecha has joined #buildstream08:00
*** nimish2711 has quit IRC08:30
*** nimish2711 has joined #buildstream08:47
*** nimish2711 has quit IRC08:50
*** nimish2711 has joined #buildstream08:51
*** bochecha has quit IRC08:55
*** bochecha has joined #buildstream08:56
*** toscalix has joined #buildstream08:56
*** ChanServ sets mode: +o tristan10:38
*** nimish2711 has quit IRC10:40
gitlab-br-bottristanvb opened MR !1328 (tristan/fix-missing-workspace-artifact->master: element.py: Reset workspace state if last successful build is missing.) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/132810:41
tristanjuergbi, Care to give that one a lookover ? ^^10:41
tristanNote that I made the user feedback an INFO message, since it actually causes some state to change I think it is not a STATUS message10:42
juergbiwill take a look10:42
* tristan had quite a time figuring out #1017, partly because of #101610:43
tristanjuergbi, thanks :)10:43
*** nimish2711 has joined #buildstream10:54
tristanjuergbi, Ok to skip the obviously needed refactoring of remove_artifact_from_cache() and not block on that for the bugfix ?11:08
* tristan needs to get on with a backport, and would like to finish that today :)11:08
juergbiok with me, but we should get to that eventually11:09
tristanThen there is the regression where `bst build --track-all <elements>` is just successfully terminating without building anything11:09
gitlab-br-bottristanvb opened MR !1329 (tristan/fix-missing-workspace-artifact-1.2->bst-1.2: element.py: Reset workspace state if last successful build is missing (1.2)) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/132911:33
*** rdale has joined #buildstream11:51
tristanIs this the test that was being discussed that was hanging last week: tests/sources/zip.py::test_use_netrc[HTTP] ?12:04
* tristan has a potentially hanging fedora 29 on that test: https://gitlab.com/BuildStream/buildstream/-/jobs/20768926712:07
*** slaf has quit IRC12:09
*** nimish2711 has quit IRC12:32
gitlab-br-botmarge-bot123 closed issue #1017 (Last successful workspace build can go missing) on buildstream https://gitlab.com/BuildStream/buildstream/issues/101712:38
gitlab-br-botmarge-bot123 merged MR !1328 (tristan/fix-missing-workspace-artifact->master: element.py: Reset workspace state if last successful build is missing.) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/132812:38
gitlab-br-botmarge-bot123 merged MR !1329 (tristan/fix-missing-workspace-artifact-1.2->bst-1.2: element.py: Reset workspace state if last successful build is missing (1.2)) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/132912:39
*** slaf has joined #buildstream12:43
*** slaf has joined #buildstream12:43
*** slaf has joined #buildstream12:43
*** slaf has joined #buildstream12:43
*** slaf has joined #buildstream12:44
*** slaf has joined #buildstream12:44
*** tristan has quit IRC13:25
coldtomcan somebody take a look at https://gitlab.com/BuildStream/docs-website/merge_requests/1 when they get chance please?13:54
*** tristan has joined #buildstream14:06
*** nimish2711 has joined #buildstream15:37
*** toscalix has quit IRC15:39
*** bochecha has quit IRC15:44
abderrahim[m]Since bst2 is still quite far, I wonder whether we could backport some features to 1.2?17:09
*** ChanServ sets mode: +o tristan18:04
tristanabderrahim[m], lets talk about it in the day time... I am starting to consider whether we should roll out a 1.4 for the sake of some very simple features (like user configurable max-jobs might solve a lot of problems now)18:04
abderrahim[m]tristan: I was thinking of something along the lines of 1.4 as well, to ease transition to bst 2. (along the lines of python 2.7: if you don't have  deprecation warnings, it should be straightforward to port to py3k)18:07
abderrahim[m]I'll try to bring it up tomorrow18:07
tristanabderrahim[m], the thing about "backporting" is that it is a bit risky and intense, especially with the way 2.0 is going18:11
tristani.e. huge architectural changes are mostly in play, rather than nifty easily backportable features18:11
tristanI'm more inclined to get 2.0 semi stable and start shipping 1.91.x builds of 2.0 that are parallel installable with 1.x18:12
tristanso we can start to dare to reap the benefits of the refactoring/rearchitecturing, while accepting there will be some churn, and at the same time help the team stay on track to deliver something we know works well by the time 2.0 finally drops18:13
tristananyway, I'll stay away for now, it's past 3am and I'll try to get some sleep :)18:13
abderrahim[m]so we would be back to 1.1 time18:13
abderrahim[m]but I'm afraid it's gonna take longer18:14
abderrahim[m]tristan: good night :)18:14
tristanI expect it to take longer yes18:14
tristanit would have to be buy in, of course18:14
abderrahim[m](or what remains of it)18:14
tristanI don't know if freedesktop-sdk/gnome-build-meta would be buying in18:14
*** nimish2711 has quit IRC19:46
*** admin has quit IRC23:38
*** swick has joined #buildstream23:47

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