investigate why server tests do not get killed properly on shard by timeout |
||||
Issue descriptionIn issue 705633 we had server tests with timeout=3600 holding DUTs and spinning CPU cycles for days. While I don't have the feeling that client test (or run commands) are affected, we should investigate if there is a problem in general with terminating server tests. As this can easily take down the lab (and holding onto DUTs might not be noticeable if the test doesn't spin a CPU as in issue 705633) we should run a few targeted experiments to check this. Say add a server test which sleeps for 15 minutes with a timeout of 1 minute? But how to verify it gets terminated?
,
Jul 17 2017
ChromeOS Infra P1 Bugscrub. P1 Bugs in this component should be important enough to get weekly status updates. Is this already fixed? -> Fixed Is this no longer relevant? -> Archived or WontFix Is this not a P1, based on go/chromeos-infra-bug-slo rubric? -> lower priority. Is this a Feature Request rather than a bug? Type -> Feature Is this missing important information or scope needed to decide how to proceed? -> Ask question on bug, possibly reassign. Does this bug have the wrong owner? -> reassign. Bugs that remain in this state next week will be downgraded to P2.
,
Jul 24 2017
ChromeOS Infra P1 Bugscrub. Issue untouched in a week after previous message. Downgrading to P2.
,
Jan 8 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by marc...@chromium.org
, Apr 5 2017Status: Assigned (was: Untriaged)