Issue 619673003: Shard Win 7 Tests x64 (1) to 6 instead of 3 machines.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Issue 619673003: Shard Win 7 Tests x64 (1) to 6 instead of 3 machines. (Closed)

Created:
6 years, 2 months ago by jam

Modified:
6 years, 2 months ago

Reviewers:
M-A Ruel

CC:
chromium-reviews

Base URL:
https://chromium.googlesource.com/chromium/src.git@master

Project:
chromium

Visibility:
Public.

Shard Win 7 Tests x64 (1) to 6 instead of 3 machines. The Win 7 x64 testers had twice as many cores as the 32 bit ones, and I didn't notice that when picking the sharding level earlier. Now that they're all going to the same swarming slaves, which are almost all 4-core, increase the sharding level. BUG=414808 R=maruel@chromium.org Committed: https://chromium.googlesource.com/chromium/src/+/fc00a30c8afb53fdc97b1746b8a6ba918c4e3987

Created: 6 years, 2 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+1 line, -1 line)			Patch
	M	testing/buildbot/chromium.win.json	View		1 chunk	+1 line, -1 line	0 comments	Download

Total messages: 5 (1 generated)

commit-bot: I haz the power

Patchset 1 (id:??) landed as https://crrev.com/fc00a30c8afb53fdc97b1746b8a6ba918c4e3987 Cr-Commit-Position: refs/heads/master@{#297437}

6 years, 2 months ago (2014-09-30 16:51:45 UTC) #4

jam

6 years, 2 months ago (2014-09-30 16:51:47 UTC) #5

Message was sent while issue was closed.

Committed patchset #1 (id:1) manually as
fc00a30c8afb53fdc97b1746b8a6ba918c4e3987 (presubmit successful).