On 5/11/18 11:28 PM, Gregory Szorc wrote:
You could trigger dozens of builds on Taskcluster and they would all come back in the time it takes a single build to run.
This is doable, and basically corresponds to doing N-ary search for N>2. With some tooling support so you don't have to pick the revisions by hand, could work.
Or you codify the thing you are testing for, submit it to bisect-in-the-cloud, and it does everything for you and reports on the results. It still might take dozens of minutes to a few hours. But at least you wouldn't be burdened with the overhead of doing everything manually.
Yeah, the typical thing that needs testing during a bisect is some random website, that's a bit hard to fully automate... I agree that for cases we can turn into an automated test we should be able to do way better. The latency is not that big a deal usually if it's truly zero-attention.
-Boris _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
