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

Issue 727192 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

platform_MemoryPressure test removed?

Project Member Reported by tfiga@chromium.org, May 29 2017

Issue description

Chrome Version: n/a
OS: ChromeOS

What steps will reproduce the problem?
(1) test_that <remote> platform_MemoryPressure

What is the expected result?
Test executes.

What happens instead?
Could not find matching test suite.

It looks like the control file was removed (on purpose? accidentally?) by crosreview.com/268924 as a part of  issue 483181  more than 2 years ago. However, judging by crosreview.com/191401 (and common sense), it might have been quite an important kernel regression test.

This would also nicely correlate to us getting more crashes from users related to memory pressure conditions these days.

Any insight on this?

 
Cc: grundler@chromium.org groeck@chromium.org dtor@chromium.org snanda@chromium.org

Comment 2 by grundler@google.com, May 30 2017

 issue 483181  used this as justification to remove autotest control files:
   "There is a pre-upload hook in autotest that enforces control files have at
least 1 ebuild that cares about them"

So add an ebuild for the test(s) you want to restore?

While I agree with your sentiment, kernel_per-build_regression has no owner. The entire suite was recently removed. I've been delayed from reviewing recently removed kernel tests to see which ones "really" matter:
  
  https://docs.google.com/spreadsheets/d/1t3OIHk4YFFEmptpHIWASBLNCGwFoEpZSPEZuOPnABck/edit#gid=0

(Sheriff duty was rough last week - and only minor progress the week before)

Feel free to add your thoughts in notes or even add tests that were removed longer ago.

Comment 3 by estaab@chromium.org, May 31 2017

Components: -Infra Infra>Client>ChromeOS

Comment 4 by tfiga@chromium.org, Jun 1 2017

Well, I just wanted to make sure this is something we are aware of. If that's the intended behavior, I can just have a local copy of this test just for my own purposes. Feel free to close this bug, if so.

Comment 5 by aut...@google.com, Jun 12 2017

Components: -Infra>Client>ChromeOS

Sign in to add a comment