New issue
Advanced search Search tips

Issue 859727 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
vovoy@chromium.org
cywang@chromium.org
sonnyrao@chromium.org
semenzato@chromium.org
cylee@chromium.org
conradlo@chromium.org
EstimatedDays: ----
NextAction: 2018-07-09
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

platform_MemoryPressure times out on Samus

Project Member Reported by sonnyrao@chromium.org, Jul 3 
This consistently fails on Samus due to a time out during phase 1

https://stainless.corp.google.com/search?view=matrix&row=test&col=build&first_date=2018-06-19&last_date=2018-07-02&suite=%5Epower%5C_daily%24&board=%5Esamus%24&exclude_cts=true&exclude_not_run=false&exclude_non_release=true&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=false


I think this is because these systems have either 8 or 16GB of memory, and it takes much longer to complete phase 1 than on other systems.  The simplest solution is to just make the timeout longer.

Comment 1 by sonnyrao@chromium.org, Jul 3 

I was able to get my 8GB Samus to pass with an increased timeout of 3600 seconds (vs 1800)

Amusingly, Phase 1 took exactly 1801 seconds.  I'm not sure if 3600 seconds would be enough for a 16GB system.

Comment 2 by benhenry@google.com, Jan 10

Labels: Pri-3
NextAction: 2018-07-09
Downgrading P2s that haven't been modified in more than 6 months, which also do not have a component or owner.
►

Sign in to add a comment