New issue
Advanced search Search tips

Issue 828882 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Reorganize testing priorities

Project Member Reported by ihf@chromium.org, Apr 4 2018

Issue description

Right now autotest priorities are not chosen not well:

Priority = enum.Enum('Weekly', 'Daily', 'PostBuild', 'Default', 'Build',
                     'PFQ', 'CQ', 'Super',  start_value=10, step=10)

Proposal:
1) Weekly should be higher than Daily, to encourage people have an incentive to use less resources.
2) Same for PostBuild (perbuild), it should be lowest in this list.
3) We need a new priority for test_that :lab:, right now it is 'Default'. I think it should be either lowest or below Daily, as otherwise people starve pools.

In other words we should end up with something like:

Priority = enum.Enum('PostBuild', 'TestThat', 'Daily', 'Weekly', 'Default', 'Build',
                     'PFQ', 'CQ', 'Super')
 

Comment 1 by pwang@chromium.org, Apr 4 2018

I'm wondering why we can't just use the numerical priority as the lab is supporting it rather than the ill defined enum. The priority enum might become inconsistent in some sense for the suite_scheduler and buildbot.

Comment 2 by ihf@chromium.org, Apr 4 2018

Well, as in many cases it is good to have a human readable layer of indirection. The divergence between chromite and autotest is unfortunate and a separate problem.
Cc: ayatane@chromium.org
Owner: pprabhu@chromium.org
Status: Assigned (was: Untriaged)
Autotest is going away.

With that said, we do want to figure out task priorities for Swarming/Skylab.
Components: -Infra>Client>ChromeOS>Test Infra>Client>ChromeOS>Test>Platform

Sign in to add a comment