Re: Improving Mac OS X 10.6 test wait times by reducing 10.7 load

2013-10-31 Thread Alexander Keybl
I think it makes a lot of sense to test the spread. +1 - Original Message - From: Armen Zambrano G. arme...@mozilla.com To: dev-platform@lists.mozilla.org Sent: Tue, 29 Oct 2013 13:31:33 -0700 (PDT) Subject: Re: Improving Mac OS X 10.6 test wait times by reducing 10.7 load Hello all, I

Re: Improving Mac OS X 10.6 test wait times by reducing 10.7 load

2013-10-31 Thread Ryan VanderMeulen
On 10/29/2013 4:31 PM, Armen Zambrano G. wrote: In order to improve our wait times, I propose that we stop testing on tbpl per-checkin [2] on OS X 10.7 and re-purpose the 10.7 machines as 10.6 to increase our capacity. Please let us know if this plan is unacceptable and needs further

Re: Improving Mac OS X 10.6 test wait times by reducing 10.7 load

2013-04-26 Thread jmaher
On Thursday, April 25, 2013 4:12:16 PM UTC-4, Ed Morley wrote: On 25 April 2013 20:14:10, Justin Lebar wrote: Is this what you're saying? * 10.6 opt tests - per-checkin (no change) * 10.6 debug tests- reduced * 10.7 opt tests - reduced * 10.7 debug tests

Re: Improving Mac OS X 10.6 test wait times by reducing 10.7 load

2013-04-26 Thread jmaher
On Friday, April 26, 2013 9:49:18 AM UTC-4, Armen Zambrano G. wrote: Maybe we can keep one of the talos jobs around? (until releng fixes the various python versions' story) IIUC this was more of an infra issue rather than a Firefox testing issue. It was infra related, but it was

Re: Improving Mac OS X 10.6 test wait times by reducing 10.7 load

2013-04-26 Thread Phil Ringnalda
On 4/25/13 1:12 PM, Ed Morley wrote: On 25 April 2013 20:14:10, Justin Lebar wrote: Is this what you're saying? * 10.6 opt tests - per-checkin (no change) * 10.6 debug tests- reduced * 10.7 opt tests - reduced * 10.7 debug tests - reduced * reduced -- m-c, m-a, m-b,

Re: Improving Mac OS X 10.6 test wait times by reducing 10.7 load

2013-04-26 Thread Justin Lebar
So what we're saying is that we are going to completely reverse our previous tree management policy? Basically, yes. Although, due to coalescing, do you always have a full run of tests on the tip of m-i before merging to m-c? A better solution would be to let you trigger a full set of tests

Re: Improving Mac OS X 10.6 test wait times by reducing 10.7 load

2013-04-26 Thread Ryan VanderMeulen
On 4/26/2013 11:11 AM, Justin Lebar wrote: So what we're saying is that we are going to completely reverse our previous tree management policy? Basically, yes. Although, due to coalescing, do you always have a full run of tests on the tip of m-i before merging to m-c? Yes. Note that we

Re: Improving Mac OS X 10.6 test wait times by reducing 10.7 load

2013-04-26 Thread Phil Ringnalda
On 4/26/13 8:11 AM, Justin Lebar wrote: So what we're saying is that we are going to completely reverse our previous tree management policy? Basically, yes. Although, due to coalescing, do you always have a full run of tests on the tip of m-i before merging to m-c? It's not just

Re: Improving Mac OS X 10.6 test wait times by reducing 10.7 load

2013-04-26 Thread Armen Zambrano G.
Would we be able to go back to where we disabled 10.7 altogether? Product (Asa in separate thread) and release drivers (Akeybl) were OK to the compromise of version specific test coverage being removed completely. Side note: adding Mac PGO would increase the build load (Besides this we have

Re: Improving Mac OS X 10.6 test wait times by reducing 10.7 load

2013-04-26 Thread Armen Zambrano G.
Just disabling debug and talos jobs for 10.7 should reduce more than 50% of the load on 10.7. That might be sufficient for now. Any objections on this plan? We can re-visit later on if we need more disabled. cheers, Armen On 2013-04-26 11:50 AM, Armen Zambrano G. wrote: Would we be able to

Re: Improving Mac OS X 10.6 test wait times by reducing 10.7 load

2013-04-26 Thread Justin Lebar
Would we be able to go back to where we disabled 10.7 altogether? On m-i and try only, or everywhere? On Fri, Apr 26, 2013 at 12:10 PM, Armen Zambrano G. arme...@mozilla.com wrote: Just disabling debug and talos jobs for 10.7 should reduce more than 50% of the load on 10.7. That might be

Re: Improving Mac OS X 10.6 test wait times by reducing 10.7 load

2013-04-26 Thread Armen Zambrano G.
On 2013-04-26 12:14 PM, Justin Lebar wrote: Would we be able to go back to where we disabled 10.7 altogether? On m-i and try only, or everywhere? The initial proposal was for disabling everywhere. We could leave 10.7 opt jobs running everywhere as a compromise and re-visit after I

Re: Improving Mac OS X 10.6 test wait times by reducing 10.7 load

2013-04-26 Thread Justin Lebar
I don't think I'm comfortable disabling this platform across the board, or even disabling debug-only runs across the board. As jmaher pointed out, there are platform differences here. If we disable this platform entirely, we lose visibility into rare but, we seem to believe, possible events. It

Re: Improving Mac OS X 10.6 test wait times by reducing 10.7 load

2013-04-26 Thread Armen Zambrano G.
On 2013-04-26 1:31 PM, Justin Lebar wrote: I don't think I'm comfortable disabling this platform across the board, or even disabling debug-only runs across the board. As jmaher pointed out, there are platform differences here. If we disable this platform entirely, we lose visibility into rare

Re: Improving Mac OS X 10.6 test wait times by reducing 10.7 load

2013-04-26 Thread Armen Zambrano G.
After re-reading, I'm happy to disable just m-i/try for now. Modifying to trigger *some* jobs on m-i through would be some decent amount of work (adding Mac pgo builders) but still different than normal operations and increase the 10.6/10.8 test load. On 2013-04-26 1:31 PM, Justin Lebar

Re: Improving Mac OS X 10.6 test wait times by reducing 10.7 load

2013-04-26 Thread Matt Brubeck
On 4/26/2013 9:10 AM, Armen Zambrano G. wrote: Just disabling debug and talos jobs for 10.7 should reduce more than 50% of the load on 10.7. That might be sufficient for now. I'd be happy for us to disable all Talos jobs on 10.7, on all trees. I've been keeping track of Talos stuff recently

Improving Mac OS X 10.6 test wait times by reducing 10.7 load

2013-04-25 Thread Armen Zambrano G.
(please follow up through mozilla.dev.planning) Hello all, I have recently been looking into our Mac OS X test wait times which have been bad for many months and progressively getting worst. Less than 80% of test jobs on OS X 10.6 and 10.7 are able to start within 15 minutes of being

Re: Improving Mac OS X 10.6 test wait times by reducing 10.7 load

2013-04-25 Thread Justin Lebar
It would be nice if we had data indicating how often tests fail on just one version of MacOS, so we didn't have guess how useful having 10.6, 10.7, and 10.8 tests are. That's bug 860870. It's currently blocked on treeherder, but maybe it should be re-prioritized, since we keep running into cases

Re: Improving Mac OS X 10.6 test wait times by reducing 10.7 load

2013-04-25 Thread Alex Keybl
We could come to the compromise of running them on m-c, m-a, m-b and m-r. Only this would help a lot since most of the load comes from m-i and try. We could make it a non-by-default platform on try. This strategy would prevent any holes in our coverage, but accomplish the goal of reducing

Re: Improving Mac OS X 10.6 test wait times by reducing 10.7 load

2013-04-25 Thread Justin Lebar
We could come to the compromise of running them on m-c, m-a, m-b and m-r. Only this would help a lot since most of the load comes from m-i and try. We could make it a non-by-default platform on try. I wonder if we should do the same for debug 10.6 tests (and maybe builds). The fact of the

Re: Improving Mac OS X 10.6 test wait times by reducing 10.7 load

2013-04-25 Thread Justin Lebar
Is this what you're saying? * 10.6 opt tests - per-checkin (no change) * 10.6 debug tests- reduced * 10.7 opt tests - reduced * 10.7 debug tests - reduced * reduced -- m-c, m-a, m-b, m-r, esr17 Yes. Now that I think about this more, maybe we should go big or go

Re: Improving Mac OS X 10.6 test wait times by reducing 10.7 load

2013-04-25 Thread Ed Morley
On 25 April 2013 20:14:10, Justin Lebar wrote: Is this what you're saying? * 10.6 opt tests - per-checkin (no change) * 10.6 debug tests- reduced * 10.7 opt tests - reduced * 10.7 debug tests - reduced * reduced -- m-c, m-a, m-b, m-r, esr17 Yes. Now that I think about