Replace 10.7 testers with 10.9 in master.chromium.mac

Replace 10.7 testers with 10.9 in master.chromium.mac


Revert "Replace 10.7 testers with 10.9 in master.chromium.mac"

This reverts commit 68247d4b91bdec2a94a5a054993bc00ce408b41f.

Replace 10.7 testers with 10.9 in master.chromium.mac

BUG=412374, 412376
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=292832

[pschmidt1, 2014-11-03 22:20:35]

pschmidt@chromium.org changed reviewers:
+ rsesek@chromium.org

[pschmidt1, 2014-11-03 22:22:44]

The two slaves are now on 10.9

[Robert Sesek, 2014-11-03 22:25:41]

Awesome! I didn't know these were upgraded.

There are some additional renames needed since Mac10.6 (dbg)(1) was upgraded to
10.8, per https://crbug.com/412376. Do you want to roll up the renames for that
into this CL, or in another? I was waiting on putting together a CL for that
rename until the 10.7->10.9 switch happened, just to reduce the cognitive load
of multiple master restarts.

https://codereview.chromium.org/701623002/diff/1/masters/master.chromium.mac/...
File masters/master.chromium.mac/master_mac_cfg.py (right):

https://codereview.chromium.org/701623002/diff/1/masters/master.chromium.mac/...
masters/master.chromium.mac/master_mac_cfg.py:23: 'Mac10.9 Tests (1)',
Since these are on swarming now, do we want the (1) in the name?

[pschmidt1, 2014-11-03 22:48:25]

On 2014/11/03 at 22:25:41, rsesek wrote:
> Awesome! I didn't know these were upgraded.
> 
> There are some additional renames needed since Mac10.6 (dbg)(1) was upgraded
to 10.8, per https://crbug.com/412376. Do you want to roll up the renames for
that into this CL, or in another? I was waiting on putting together a CL for
that rename until the 10.7->10.9 switch happened, just to reduce the cognitive
load of multiple master restarts.
> 
>
https://codereview.chromium.org/701623002/diff/1/masters/master.chromium.mac/...
> File masters/master.chromium.mac/master_mac_cfg.py (right):
> 
>
https://codereview.chromium.org/701623002/diff/1/masters/master.chromium.mac/...
> masters/master.chromium.mac/master_mac_cfg.py:23: 'Mac10.9 Tests (1)',
> Since these are on swarming now, do we want the (1) in the name?

Mac10.6 (dbg)(1) is at 10.8 but not Mac10.6 Tests (1)?  Do you want that one at
10.8 as well?

[Robert Sesek, 2014-11-03 22:49:57]

On 2014/11/03 22:48:25, pschmidt1 wrote:
> On 2014/11/03 at 22:25:41, rsesek wrote:
> > Awesome! I didn't know these were upgraded.
> > 
> > There are some additional renames needed since Mac10.6 (dbg)(1) was upgraded
> to 10.8, per https://crbug.com/412376. Do you want to roll up the renames for
> that into this CL, or in another? I was waiting on putting together a CL for
> that rename until the 10.7->10.9 switch happened, just to reduce the cognitive
> load of multiple master restarts.
> > 
> >
>
https://codereview.chromium.org/701623002/diff/1/masters/master.chromium.mac/...
> > File masters/master.chromium.mac/master_mac_cfg.py (right):
> > 
> >
>
https://codereview.chromium.org/701623002/diff/1/masters/master.chromium.mac/...
> > masters/master.chromium.mac/master_mac_cfg.py:23: 'Mac10.9 Tests (1)',
> > Since these are on swarming now, do we want the (1) in the name?
> 
> Mac10.6 (dbg)(1) is at 10.8 but not Mac10.6 Tests (1)?  Do you want that one
at
> 10.8 as well?

No, we want to keep a Mac 10.6 release tester. The end-goal config is:

10.6 release tests
10.8 release tests
10.9 debug+release tests

I think we're set on the main waterfall after this!

[pschmidt1, 2014-11-03 23:19:40]

On 2014/11/03 at 22:49:57, rsesek wrote:
> On 2014/11/03 22:48:25, pschmidt1 wrote:
> > On 2014/11/03 at 22:25:41, rsesek wrote:
> > > Awesome! I didn't know these were upgraded.
> > > 
> > > There are some additional renames needed since Mac10.6 (dbg)(1) was
upgraded
> > to 10.8, per https://crbug.com/412376. Do you want to roll up the renames
for
> > that into this CL, or in another? I was waiting on putting together a CL for
> > that rename until the 10.7->10.9 switch happened, just to reduce the
cognitive
> > load of multiple master restarts.
> > > 
> > >
> >
https://codereview.chromium.org/701623002/diff/1/masters/master.chromium.mac/...
> > > File masters/master.chromium.mac/master_mac_cfg.py (right):
> > > 
> > >
> >
https://codereview.chromium.org/701623002/diff/1/masters/master.chromium.mac/...
> > > masters/master.chromium.mac/master_mac_cfg.py:23: 'Mac10.9 Tests (1)',
> > > Since these are on swarming now, do we want the (1) in the name?
> > 
> > Mac10.6 (dbg)(1) is at 10.8 but not Mac10.6 Tests (1)?  Do you want that one
at
> > 10.8 as well?
> 
> No, we want to keep a Mac 10.6 release tester. The end-goal config is:
> 
> 10.6 release tests
> 10.8 release tests
> 10.9 debug+release tests
> 
> I think we're set on the main waterfall after this!

How about now?

[Robert Sesek, 2014-11-03 23:23:16]

LGTM. Thanks!

[hinoka, 2014-11-04 19:22:26]

The CQ bit was checked by hinoka@chromium.org

[commit-bot: I haz the power, 2014-11-04 19:22:50]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/701623002/20001

[commit-bot: I haz the power, 2014-11-04 19:24:17]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-11-04 19:24:18]

Presubmit check for 701623002-20001 failed and returned exit status 1.

Running presubmit commit checks ...

** Presubmit ERRORS **
tests/masters_test.py (26.51s) failed
1 masters failed:
master.client.polymer
62 masters succeeded, 1 failed, 0 skipped in 26.0s.

=== Error running master.client.polymer === 
2014-11-04 11:23:25-0800 [-] gitpoller: using workdir
'/b/infra_internal/commit_queue/workdir/tools/build/masters/master.client.polymer/gitpoller/polymer-gestures'
2014-11-04 11:23:25-0800 [-] gitpoller: initializing working dir from
https://github.com/Polymer/polymer-gestures
2014-11-04 11:23:25-0800 [-] gitpoller: using workdir
'/b/infra_internal/commit_queue/workdir/tools/build/masters/master.client.polymer/gitpoller/PointerEvents'
2014-11-04 11:23:25-0800 [-] gitpoller: initializing working dir from
https://github.com/Polymer/PointerEvents
2014-11-04 11:23:25-0800 [-] configuration update complete
2014-11-04 11:23:25-0800 [-] while initializing GitPoller repository
	Traceback (most recent call last):
	  File
"/b/infra_internal/commit_queue/workdir/tools/build/third_party/twisted_10_2/twisted/internet/_baseprocess.py",
line 60, in maybeCallProcessEnded
	    proto.processEnded(Failure(reason))
	  File
"/b/infra_internal/commit_queue/workdir/tools/build/third_party/twisted_10_2/twisted/internet/utils.py",
line 159, in processEnded
	    self.deferred.callback((out, err, code))
	  File
"/b/infra_internal/commit_queue/workdir/tools/build/third_party/twisted_10_2/twisted/internet/defer.py",
line 361, in callback
	    self._startRunCallbacks(result)
	  File
"/b/infra_internal/commit_queue/workdir/tools/build/third_party/twisted_10_2/twisted/internet/defer.py",
line 455, in _startRunCallbacks
	    self._runCallbacks()
	--- <exception caught here> ---
	  File
"/b/infra_internal/commit_queue/workdir/tools/build/third_party/twisted_10_2/twisted/internet/defer.py",
line 542, in _runCallbacks
	    current.result = callback(current.result, *args, **kw)
	  File
"/b/infra_internal/commit_queue/workdir/tools/build/third_party/buildbot_8_4p1/buildbot/changes/gitpoller.py",
line 336, in _convert_nonzero_to_failure
	    raise EnvironmentError('command failed with exit code %d: %s' % (code,
stderr))
	exceptions.EnvironmentError: command failed with exit code 128: fatal:
https://github.com/Polymer/polymer-dev/info/refs?service=git-upload-pack not
found: did you run git update-server-info on the server?



Presubmit checks took 75.2s to calculate.

[hinoka, 2014-11-04 19:43:47]

The CQ bit was checked by hinoka@chromium.org

[commit-bot: I haz the power, 2014-11-04 19:43:59]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/701623002/20001

[commit-bot: I haz the power, 2014-11-04 19:45:24]

Committed patchset #2 (id:20001) as 292832