On 9 February 2016 at 14:51, Marco Bonardo <mbona...@mozilla.com> wrote:
> On Tue, Feb 9, 2016 at 6:54 PM, Ryan VanderMeulen <rya...@gmail.com> > wrote: > > > I'd have a much easier time accepting that argument if my experience > > didn't tell me that nearly every single "Test took longer than expected" > or > > "Test timed out" intermittent ends with a RequestLongerTimeout as the fix > > > this sounds equivalent to saying "Since we don't have enough resources (or > a plan) to investigate why some tests take so long, let's give up"... But > then maybe we should have that explicit discussion, rather than assuming > it's a truth. > Since we are focused on quality I don't think it's acceptable to say we are > fine if a test takes an unexpected amount of time to run. The fact those > bugs end up being resolved by bumping the timeout without any kind of > investigation (and it happens, I know) is worrisome. > I agree. However, this has traditionally been a very difficult area for Release Engineering and Engineering Productivity to make progress in. Who can we work with to understand these timing characteristics in more depth? _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
