Re: To bump mochitest's timeout from 45 seconds to 90 seconds

I concur with Ryan here, and I'd add that IME 90% if not more of these timeouts (where they are really timeouts because the test is long, rather than just brokenness in the test that leaves it hanging until the timeout) happen on debug/asan builds, where "perf regressions" isn't really a

Re: To bump mochitest's timeout from 45 seconds to 90 seconds

On Tue, Feb 9, 2016 at 8:09 PM, Gijs Kruitbosch wrote: > I concur with Ryan here, and I'd add that IME 90% if not more of these > timeouts (where they are really timeouts because the test is long, rather > than just brokenness in the test that leaves it hanging until

Re: Gecko/Firefox stats and diagrams wanted

On Tue, Feb 9, 2016 at 12:31 PM, Nicholas Alexander wrote: > I also wanted to try to find some diagrams to show how Firefox and Gecko >> work/their architecture, from a high level perspective (not too insane a >> level of detail, but reasonable). >> > > Nathan Froyd

Re: To bump mochitest's timeout from 45 seconds to 90 seconds

On Tue, Feb 9, 2016 at 6:54 PM, Ryan VanderMeulen 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

Re: To bump mochitest's timeout from 45 seconds to 90 seconds

90 seconds for a simple test sounds like a lot of time and a huge bump from the current situation (45). The risk is people will start writing much bigger tests instead of splitting them into smaller an more manageable tests. Plus when a test depends on a long timeout in the product, developers are

Re: To bump mochitest's timeout from 45 seconds to 90 seconds

I will try 60 seconds and see how it goes. On 16-02-09 05:47 AM, Marco Bonardo wrote: > 90 seconds for a simple test sounds like a lot of time and a huge bump from > the current situation (45). > The risk is people will start writing much bigger tests instead of > splitting them into smaller an

Re: Reftests moving to structured logging

This is now live on central. On 04/02/16 01:28 PM, Andrew Halberstadt wrote: Reftest is the last major test harness still not using structured logs, but that should change by the end of the week. See bug 1034290 [1] for more details. I've tried my best to make sure things like

Re: MozReview/Autoland in degraded state

Try integration is now restored. Autoland to inbound will be available pending some further testing. On Fri, Feb 5, 2016 at 5:34 PM, Gregory Szorc wrote: > r+ carry forward/"status" column is now working again. > > Autoland / Try integration is still offline. > > On Fri, Feb

Gecko/Firefox stats and diagrams wanted

Hi all, I’m writing a presentation about browsers, standards implementation, and cross-browser coding to give at some universities. As a part of it, I wanted to present some stats about Firefox/Gecko to show how many people on average commit to it (say, every month, every year?), how many

Memory Usage on Perfherder & Memory Reduction

Hi All, Recently Geoff Brown landed an AWSY-like system [1] for tracking memory usage on Perfherder. This is awesome. It's one of my pinned tabs. I was happy to see two recent "drops" in memory usage: 1. A ~3% drop in "Resident Memory Tabs closed [+30s]", likely due to Bug 990916 which expires

TCW Soft Close: Tree Closing Maintenance Window, Sat February 13 2016, 06:00-10:00a PST

FYI. We do not expect any significant impact to platform operations. "Soft Close" means we'll leave the trees open, but devs who push: - can expect issues - are personally responsible for managing their job (retries, etc.) -- Forwarded message -- From: Date:

Re: To bump mochitest's timeout from 45 seconds to 90 seconds

On 9 February 2016 at 14:51, Marco Bonardo wrote: > On Tue, Feb 9, 2016 at 6:54 PM, Ryan VanderMeulen > 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

Re: To bump mochitest's timeout from 45 seconds to 90 seconds

On Tue, Feb 9, 2016 at 2:47 AM, Marco Bonardo wrote: > Based on that, bumping the timeout may have 2 downsides, long term: > - slower tests for everyone > - sooner or later 90 seconds won't be enough again. Are we going to bump to > 180 then? > Essentially restating

Re: Gecko/Firefox stats and diagrams wanted

+Kyle, +Nathan On Tue, Feb 9, 2016 at 9:00 AM, Chris Mills wrote: > Hi all, > > I’m writing a presentation about browsers, standards implementation, and > cross-browser coding to give at some universities. As a part of it, I > wanted to present some stats about Firefox/Gecko

Re: To bump mochitest's timeout from 45 seconds to 90 seconds

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. -Ryan On 2/9/2016 12:50 PM, Haik Aftandilian wrote: On Tue, Feb 9, 2016