x/build: shard and scale the
I missed a Windows test failure in CL 220645 because I forgot to run it against the
I'm not in the habit of running that SlowBot because it is currently much too slow. To pick some relevant runs:
Since there is nothing particularly special about the hardware needed to run the
The text was updated successfully, but these errors were encountered:
The longtest builders are currently primarily post-submit builders, where it's okay for them to be as slow as they need to be in order to provide additional test coverage. In this context, whether they take 40 minutes or 50 makes little difference. The longtest builders are also sometimes requested via SlowBots for changes that are riskier than usual, or otherwise desire additional coverage beyond the normal TryBots. They're also always enabled for CLs to release branches. In such contexts, speeding up SlowBot runs from 40 minutes to 20 or less would be appreciated and in turn help people use longtest SlowBots more frequently. Longtest builders are already configured to use sharded tests. Configure them to use additional helpers to speed up test execution. Try out 3, 5, and 9 helpers to see how much it helps before settling. For golang/go#37439. Change-Id: I425bc0257b7a54bb32c0eb1719fea7ba3f4fd461 Reviewed-on: https://go-review.googlesource.com/c/build/+/268037 Trust: Dmitri Shuralyov <firstname.lastname@example.org> Run-TryBot: Dmitri Shuralyov <email@example.com> TryBot-Result: Go Bot <firstname.lastname@example.org> Reviewed-by: Alexander Rakoczy <email@example.com> Reviewed-by: Carlos Amedee <firstname.lastname@example.org>
I sent https://golang.org/cl/268037 for this.
I had a chance to try out all 3 values for additional TryBot helpers (3, 5, and 9) in at least one CL and the times so far were:
It seems even just 3 additional helpers goes a long way to speed up the longtest SlowBot. I'll collect some more timing data next up.
(It's not a completely fair comparison since the builders are different, but it's enough to get some idea.)