Make CQ trybots test patches for committing in the order that they will land |
||||||
Issue descriptionSometimes the tree fails to compile because two patches land at the same time that break the compile when applied together. Ideally the CQ would pick an ordering for in flight patches to land in and require trybot runs to include all preceding patches as well. I understand this would remove the time saved by doing dry-runs. It would be interesting to see the numbers on the amount of time saved with dry-runs vs time lost due to the tree not compiling.
,
Jan 18 2017
Unfortunately that's something that is expected to happen from time to time since we can not test all patches sequentially. There were proposals in the past suggesting to test CLs applied in batches with other CLs to be landed in order... this idea was referred as Evergreen or Unibrow, but it was decided that things were running mostly smooth and added complexity was hard to justify [1]. As for the dry-runs, we only re-use jobs if they are less than 24 hours old. [1]: https://groups.google.com/a/google.com/d/msg/chrome-infrastructure-team/VB8-kO861cI/Om6z7bJK9O0J
,
Jan 18 2017
I'll mark this as Available and P3 in case we ever decide to do it.
,
Jan 23 2017
,
Aug 31 2017
,
Aug 31 2017
,
Jul 2
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by phajdan.jr@chromium.org
, Jan 16 2017