New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 620356 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Aug 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

Need to run webkit_tests on Windows 10 trybots.

Project Member Reported by bunge...@chromium.org, Jun 15 2016

Issue description

Currently all of the trybots which can run the webkit_tests step are on Windows 7. The divergence between layout tests for Windows 7 and later versions is about to become much greater. As a result there is a more pressing need to be able to run webkit_tests on Windows 10 trybots. While this is specifically about running webkit_tests on Windows 10 trybots, this is also more generally about being able to run webkit_tests on any Chromium trybot.

Ideally, for every bot on the waterfall there would be a corresponding 'real' trybot. This is generally considered rather expensive for commit queue bots. However, it would be beneficial to allow some means to kick off 'real' trybots manually. Somewhat less ideally, there would be some way for a patch to include a chromium/src change which would force webkit_tests to run. As a quick and dirty near term solution a Windows 10 bot could be added to the list of bots which run webkit_tests, or a property could be sent from 'git cl try' to request webkit_tests to be run.
 
Cc: qyears...@chromium.org tansell@chromium.org
Components: -Infra>Client>Chrome Blink>Infra
The easiest thing to do here would be to add one of the win10_ builders on tryserver.chromium.win to CHROMIUM_BLINK_TEST_BUILDERS.

However, we do also already have  bug 590036  to get trybots for every waterfall blink config, so we could theoretically just close this as a dup of that.
See https://codereview.chromium.org/2068793002/ for some preceding discussion of this.
I think finishing off  bug 590036  (adding trybots for all the blink bots) would be great. I have no idea what's involved in that or how long it would take though. If it's going to take a while, adding a win10_ builder on tryserver.chromium.win to CHROMIUM_BLINK_TEST_BUILDERS (especially if it's not in a CQ) would be fine for now.
It's pretty much the same work either way, and we theoretically have the machines lying around, I just need to make the time to get them set up.
Status: Fixed (was: Untriaged)
Marking as fixed, since there is now a Win10 trybot which runs layout tests.

Sign in to add a comment