New issue
Advanced search Search tips

Issue 697952 link

Starred by 1 user
Status: Duplicate
Owner: ----
Closed: Mar 2017
Cc:
dpranke@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Running LayoutTests: content_shell took too long to startup

Project Member Reported by atotic@chromium.org, Mar 2 2017 
Chrome Version: b77998f76c35f41c8d4c590b468d893ecb00e191, Linux

- What steps will reproduce the problem?

Run layout tests:
python third_party/WebKit/Tools/Scripts/run-webkit-tests

- What is the expected result?

Tests run

- What happens instead?

All content_shells timeout on startup. After the initial timeout, tests do run. This makes running LayoutTests locally cumbersome, can't rebase, run single tests, etc.

Comment 1 by atotic@chromium.org, Mar 2 2017 

Investigation so far:

run-webkit-tests timeouts waiting for 'READY#' output from:
/usr/local/google/home/atotic/chromium/src/out/Develop/content_shell --run-layout-test --enable-crash-reporter --crash-dumps-dir=/usr/local/google/home/atotic/chromium/src/out/Develop/crash-dumps -

Running this command line in regular environment works.

Runnning this command line in test environment fails. In particular, setting 
HOME=/tmp/tmpIfxFXM
causes content_shell to hang.

Next step, figure out why is content_shell hanging.

Comment 2 by atotic@chromium.org, Mar 2 2017

Mergedinto: 697954
Status: Duplicate (was: Available)
►

Sign in to add a comment