On Tuesday 2016-06-28 14:24 -0700, jl...@mozilla.com wrote: > My feeling is that (2) is a convenience that seems vital to opt jobs but > something that can be tolerably be missing for a few weeks in debug jobs for > the sake of migrating faster to current infra while dropping support for > legacy infra. If others feel strongly against this view point, please let me > know if you have time.
Why is it vital to opt jobs but less so for debug jobs? In general, debug jobs catch more issues since they test assertions, so it's useful in normal cases (looking for test failures) to run only debug tests on a try run. That is, there are many test failures that happen only in debug builds, but relatively few that happen only in opt builds. (Running only opt tests is mainly relevant when the performance tests are of interest.) (That said, I haven't found the triggering-new-jobs UI useful in practice yet because it requires so much clicking to trigger all the jobs for other platforms once one platform passes. Bug 1272212 would help.) -David -- 𝄞 L. David Baron http://dbaron.org/ 𝄂 𝄢 Mozilla https://www.mozilla.org/ 𝄂 Before I built a wall I'd ask to know What I was walling in or walling out, And to whom I was like to give offense. - Robert Frost, Mending Wall (1914)
signature.asc
Description: PGP signature
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
