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

Issue 908731 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Consider adding power_SuspendToIdle or similar s0ix check to CQ

Project Member Reported by kirtika@chromium.org, Nov 27

Issue description

Enabling SOF on Octopus broke s0ix. Filing this to check with power team if we can add a s0ix working check to the CQ. 
Its not clear what suites power_SuspendToIdle runs on, would it be a candidate?

 
Cc: tbroch@chromium.org
Owner: puthik@chromium.org
Status: Assigned (was: Untriaged)
Would be a good idea once we've addressed the existing failures in stainless when running power_Resume.SuspendToIdle

https://stainless.corp.google.com/search?view=matrix&row=test&col=build&first_date=2018-11-21&last_date=2018-11-27&test=%5Epower_Resume.SuspendToIdle&exclude_cts=true&exclude_not_run=false&exclude_non_release=true&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=false

as part of power_build suite.

While I failures for SKL were addressed here recently (https://issuetracker.google.com/79442787) there are failures as well on APL, KBL-U (fizz) and KBL-Y (eve) in most recent runs.

Opal would you have cycles to look at the existing failures / test flakiness?

We need https://crrev.com/c/1312213 to add power_SuspendToIdle to CQ.

Todd, can you review that?

Sign in to add a comment