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

Issue 699295 link

Starred by 0 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Figure out how to support "waterfall-only" tests in //testing/buildbot/*.json

Project Member Reported by dpranke@chromium.org, Mar 7 2017

Issue description

See  bug 699242  for motivation ... there's probably a need from time-to-time to run tests on the continuous builders that we can't easily afford to run on the CQ.

Today, you can't just add a test to an existing CQ builder and indicate that that's what you want; if you want something to be waterfall-only you need to either set up a new builder or at least set up a new triggered tester (or add something to an existing triggered tester).

It seems like we should generally be moving away from triggered testers, and so it might be good to figure out how to support the idea of "waterfall-only" test steps in the //testing/buildbot/*.json files.

That said, this should not be the first choice for most tests, since we generally want the CQ coverage to match the waterfall.
 
Components: -Infra>Client Infra>Client>Chrome
Project Member

Comment 2 by sheriffbot@chromium.org, Apr 26 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: Available (was: Untriaged)
This is certainly a useful idea, and something we'd like to see done.

Though we have no free cycles atm, so back into our backlog this goes.

Sign in to add a comment