> > This seems like it would lead to a substantial increase in > build/test load -- one that I suspect we don't currently have the > hardware to support. This is because it would require a full > build/test run for every push, which we avoid today because many > builds and tests get merged on inbound when things are behind. (I > also don't feel like we need a full build/test run for every push, > so it feels like unnecessary use of resources to me.) > >
I would love to see a model where we only run full tests on a schedule as we do for pgo builds. For everything in between we would be able to run a much smaller set of tests that are known to be less noisy and ignoring tests which always pass. While this would be some work up front, it would allow for great scaling of our systems and much faster turnaround times. To make something like this happen we would need a method in place for us to launch builds and tests which were not run for any given changeset from a simple UI (i.e. TBPL) to hunt down a regression if one is found on the full set of tests when they are finally run. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
