IRC logs for #buildstream for Tuesday, 2022-12-13

*** tristan <tristan!tristan@223.62.216.189> has joined #buildstream02:45
*** ChanServ sets mode: +o tristan02:45
*** tristan <tristan!tristan@223.62.216.189> has quit IRC03:00
*** tristan <tristan!tristan@223.62.216.189> has joined #buildstream03:00
*** ChanServ sets mode: +o tristan03:00
*** tristan <tristan!tristan@223.62.216.189> has quit IRC03:47
*** tristan <tristan!tristan@223.62.216.189> has joined #buildstream03:47
*** ChanServ sets mode: +o tristan03:47
*** tristan <tristan!tristan@223.62.216.189> has quit IRC04:23
*** tristan <tristan!tristan@223.62.216.189> has joined #buildstream04:23
*** ChanServ sets mode: +o tristan04:23
*** tristan <tristan!tristan@223.62.216.189> has quit IRC04:39
*** tristan <tristan!tristan@223.62.216.189> has joined #buildstream04:39
*** ChanServ sets mode: +o tristan04:39
*** tristan <tristan!tristan@223.62.216.189> has quit IRC04:47
*** tristan <tristan!tristan@223.62.216.189> has joined #buildstream04:48
*** ChanServ sets mode: +o tristan04:48
juergbinanonyme: buildbox-fuse will deny writes (outside specified directories) for read-only root but it shouldn't affect the file/directory modes06:09
*** tristan <tristan!tristan@223.62.216.189> has quit IRC06:47
nanonymejuergbi: x86_64 build-export took about 42 minutes when I combined flatpak_repo commands manually rather than relying on nested batching07:45
nanonymeSo 40 minutes faster07:46
nanonymeI will next see if results are reproducible07:46
nanonymeI don't think nested batching works as well as people think07:48
nanonymejuergbi: if I'm right, removing sandbox.batch() here should speed builds *a lot* https://github.com/apache/buildstream/blob/master/src/buildstream/buildelement.py#L30607:49
nanonymeFor integration commands07:50
nanonymeSorry, wrong place. It was supposed to be removed from inner layer07:50
nanonymeSo here https://github.com/apache/buildstream/blob/cf88f343c13a54f0f768b9c96f0a2e58b2d9f55a/src/buildstream/element.py#L70607:51
nanonymeThat inner batch is redundant. It doesn't have a title, no flags and it is always called from within outer code which has an ongoing batch anyway07:51
juergbiif it's always called within another batch, sure, we can remove it. however, we should also fix nested batching07:52
juergbidoesn't really explain the slowness of integration of e.g. sdl2-net in CI where only a single dependency has integration commands07:53
nanonymeIndeed. It should be fine in that case07:54
nanonymeI'm anyway running another rebuild here https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/jobs/346439639507:54
nanonymeI am testing if the 42 minutes is consistent build time or a fluke07:54
nanonymeThe scenario is now basically worst possible where i686 and x86_64 are running in different Docker containers on same VM07:56
nanonymejuergbi: I'm not sure if nested batching isn't working as designed. You cannot possibly combine two batch groups when they have different labels without breaking logs07:58
juergbithe labels of the inner batches could still be shown, just not with separate timestamps07:59
juergbinot really different from different commands running in a single batch07:59
juergbithat's a downside of batching but that's expected08:00
nanonymeI'm also not altogether sure if it's intuitive calling add_commands twice with same label in scriptelement.py will actually replace rather than append08:02
nanonymescriptelement.py is happily using label as a group identifier08:02
*** tristan <tristan!tristan@223.62.173.73> has joined #buildstream09:34
*** ChanServ sets mode: +o tristan09:34
*** tristan <tristan!tristan@223.62.173.73> has quit IRC10:20
nanonymeUpdate: I ran that exact same code another time. When two instances of flatpak repo build were running on same VM in different containers, duration was more than double of original12:26

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!