1079468 - [tracking][10.10] Continuous integration testing on OS X 10.10 Yosemite

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: CIDuty, task, P2)

Description

[Chris Cooper [:coop] (he/him)]

We missed the boat on 10.9 testing (bug 932431). 10.9 was meant to supplant our testing that currently happens on 10.8. After nearly a year, those 10.9 tests are still not green enough for general developer visibility. Mac OS X 10.10 Yosemite is coming out soon (within 2 weeks, by most estimates).

After discussions with product management &  A-Team, we're going to abandon support in CI for 10.9 and re-orient on 10.10. If the adoption curve for 10.10 is at all like what is was for 10.9, 10.10 will be our dominant Mac platform in the wild a few months into 2015.

We will also be more aggressive in hounding developers to fix broken tests on 10.10, and will be equally aggressive in disabling tests that are not being fixed. We can't afford to lag behind another year in Mac platform support. 

We'll have new hardware to support this platform arriving early in 2015. Once that hardware is ready, we'll be turning on whatever green tests we have, and turning *off* all testing on 10.8. 

Testing on 10.6 will remain unaffected for now.

Comment 1

[Eric Shepherd [:sheppy]]

For what it's worth, I think this is wise, especially since the system requirements for 10.10 are essentially the same as 10.9 anyway; that means most people are likely to upgrade, and probably pretty fast.

Comment 2

[Phil Ringnalda (:philor)]

Two slaves might have been too many: 10.10 is cloning mozharness to a directory which doesn't exist, which just like cloning a mozharness repo which doesn't exist causes infinite retries. With two slaves, that got up to 4K jobs, one slave that only could have done 2K jobs might have been better ;)