New issue
Advanced search Search tips

Issue 851631 link

Starred by 1 user
Status: Fixed
Owner:
jonr...@chromium.org
Closed: Aug 23
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 794961



Sign in to add a comment

Windows OOP-D Coverage on Waterfall

Project Member Reported by jonr...@chromium.org, Jun 11 2018 
In issue 829187 we had to disable viz testing coverage on Windows bots due to capacity issues.

Based on discussions there should be room on:
   Win7 Tests (dbg)(1)
   Windows 10

I will turn these back on and monitor usage graphs:

https://viceroy.corp.google.com/chrome_infra/Jobs/per_job?service_name=chromium-swarm&job_regexp=tryserver.chromium.win%3Awin10_chromium_x64_rel_ng&builder=win7_chromium_rel_ng&duration=1d&job=master.tryserver.chromium.win&refresh=-1
Project Member

Comment 1 by bugdroid1@chromium.org, Jun 15 2018 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/48c3e8e3ba6d7a204620a32fe6711f8811b1212f

commit 48c3e8e3ba6d7a204620a32fe6711f8811b1212f
Author: jonross <jonross@chromium.org>
Date: Fri Jun 15 14:28:06 2018

Re-enable viz_browser_tests on Windows

There were capacity issues when we last added viz_browser_tests to Windows.
However based on discussions in https://crbug.com/829187 there appears to be
capacity on Win7 Tests (dbg)(1). This change re-eanbles them
on that config.

TEST=viz_browser_tests

Bug:  851631 
Change-Id: Ie5f33ee667097faf0a1aadc3b5e23b85b2bd1aca
Reviewed-on: https://chromium-review.googlesource.com/1096078
Commit-Queue: Jonathan Ross <jonross@chromium.org>
Reviewed-by: Stephen Martinis <martiniss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567638}
[modify] https://crrev.com/48c3e8e3ba6d7a204620a32fe6711f8811b1212f/testing/buildbot/chromium.win.json
[modify] https://crrev.com/48c3e8e3ba6d7a204620a32fe6711f8811b1212f/testing/buildbot/test_suite_exceptions.pyl

Comment 2 by jonr...@chromium.org, Aug 23

Status: Fixed (was: Started)
We got as expanded of coverage as possible due to capacity constraints. However we are now in Field Trials, so the flag is on by default on the CQ.
►

Sign in to add a comment