Green up Win 10 Fast Ring bot |
||
Issue descriptionWe have this bot: https://ci.chromium.org/buildbot/chromium.fyi/Win%2010%20Fast%20Ring/ Will says he wants to green it up and use it to LOOK INTO THE FUTURE.
,
Jun 29 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/a8e6d828e89e396c1fc9e0e2dc78c206adbd2a06 commit a8e6d828e89e396c1fc9e0e2dc78c206adbd2a06 Author: Nico Weber <thakis@chromium.org> Date: Fri Jun 29 18:55:18 2018 Remove test exceptions for 'Win 10 Fast Ring' bot. The currently disabled set of tests on that bot is fairly arbitrary. Since the bot is currently red anyway and has been for a while (see 2nd bug), let's run all tests there, and when we get around to greening it up we can then disable suites that turn out to be unamenable to fixing. It likely won't be the suites that are currently disabled. Bug: 843511,851705 Change-Id: Ifabc504fe56ebdbdab32609055cdaf39d8d73d11 Reviewed-on: https://chromium-review.googlesource.com/1120227 Commit-Queue: Nico Weber <thakis@chromium.org> Reviewed-by: Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#571571} [modify] https://crrev.com/a8e6d828e89e396c1fc9e0e2dc78c206adbd2a06/testing/buildbot/chromium.fyi.json [modify] https://crrev.com/a8e6d828e89e396c1fc9e0e2dc78c206adbd2a06/testing/buildbot/test_suite_exceptions.pyl
,
Aug 3
This bug has an owner, thus, it's been triaged. Changing status to "assigned".
,
Oct 19
Issue 731858 has been merged into this issue. |
||
►
Sign in to add a comment |
||
Comment 1 by wfh@chromium.org
, Jun 13 2018