The reason it was split is because there's a maximum runtime per job on appveyor and without splitting into 4 our regression tests on windows exceed the limit and were getting killed.
Currently not a way to tie the tools used to the builders run by each build. That could be useful for test runtime, and when users are trying to squeeze the last bit of performance out of scons.. Though there may be more generally useful features/bugs to spend time on. -Bill On Tue, Oct 30, 2018 at 3:53 PM Mats Wichmann <m...@wichmann.us> wrote: > On 10/30/18 2:34 PM, Mats Wichmann wrote: > > > I'm looking at the appveyor page > > https://ci.appveyor.com/project/SCons/scons/history > > this is a pretty typical display for a build: > > Failed 5 hours ago in 4 hr 44 min > > the build is divided into four chunks, but I'm not seeing the purpose of > that since they apparently still run sequentially, since it's a "free" > product, we get only one execution stream. > > slow builds don't critically hurt this project since there isn't > honestly that much change activity. still... > > > > >
_______________________________________________ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev