On May 1, 2013 4:44 PM, "Jonathan Griffin" <[email protected]> wrote: > > On 5/1/2013 4:35 PM, Jonas Sicking wrote: >> >> On Mon, Apr 29, 2013 at 2:51 PM, Jonathan Griffin <[email protected]> wrote: >>> >>> TL;DR - The a-team and rel-eng are currently preparing to get gaia unit >>> tests running in TBPL ( https://bugzilla.mozilla.org/show_bug.cgi?id=833666), >>> on both trunk gecko branches and gaia branches (e.g., >>> https://tbpl.mozilla.org/?tree=Gaia-Master). We have a plan to integrate >>> these tests into the "main" TBPL pages for mozilla-inbound, etc, and to >>> provide try access to gaia developers. We'd like feedback to ensure that >>> this plan will satisfy developers before we begin implementation. >>> >>> == What is already in progress == >>> All the harness work has been done to get gaia unit tests into buildbot/TBPL >>> (https://bugzilla.mozilla.org/show_bug.cgi?id=833666), running on b2g >>> desktop builds. There is some additional buildbot work that is being done >>> to enable these to be turned on for the "cedar" project branch >>> (https://bugzilla.mozilla.org/show_bug.cgi?id=865379). Once we shake out >>> any remaining bugs in production there, we will turn these tests on for both >>> gecko trunk branches, like mozilla-inbound, and gaia branches, like >>> gaia-master. >> >> Does this mean that we would enable these tests to show up on >> mozilla-inbound before we have the "coupling" discussed below? That >> worries me a bit since it might further fan the bad reputation that >> gaia issues on TBPL are hard to understand. >> >> I'd almost say that I'd prefer to only surface these results on cedar >> and gaia until we have the coupling that allows us to have more >> certainty in the data. >> >> Or are you saying that we wouldn't turn this on in mozilla-inbound >> until we have the coupling? >> >> I'm even thinking that we might not want to turn things on in >> mozilla-inbound until we have try support for gaia. Otherwise we are >> putting gaia developers that got backed out in a difficult position of >> not being able to test their fixes. > > You're right; I was thinking we might want to hide these tests until this coupling was in place. We could also decide to leave them hidden until gaia-try was operational. > > But, for gaia-unit-tests, the developers can easily run them locally, so they may not need try access to debug failures there, unless we begin to see machine-specific failures.
Good point. Let's turn on the tests once we have the coupling. If the lack of try for either suite turns out to be a problem then we can turn that suite off until we have try. / Jonas _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
