On Wed, Dec 23, 2015 at 6:58 AM, James Graham <ja...@hoppipolla.co.uk> wrote: > On 23/12/15 01:15, Ben Kelly wrote: [...] >> 10) https://bugzilla.mozilla.org/show_bug.cgi?id=1231798 > > > This is a web-platform-tests test which is an interesting case. De-facto I > am on point for all problems in these tests, which is fine, but in practice > there's a limited amount I can do. If the test is broken in some obvious way > I can fix it, or I can disable it. In some cases I know the feature under > test well enough to do something a bit more clever. But, in order to get the > right fix, it would be better to loop in the people in the team responsible > for the feature under test rather than just considering all wpt failures to > ateam's responsibility.
I would certainly not expect the ateam or yourself to be responsible for fixing all wpt failures. You should feel empowered to reach out to engineering leads for areas where you've identified the underlying implementation most likely being the cause of the failure as opposed to the test itself or the harness! And thanks for helping shepherd all these tests, highly valuable work! - jst _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
