Loading Webpages Timeouts in Test for Mash |
|||||
Issue descriptionWhen running mash_browser_tests there are often timeouts of the entire suite. This can be seen with test cases, such as BrowserTest.*, hitting the output timeouts of base/test/launcher/test_launcher.cc. This is a hard cap of 15s, and local testing showed these sometimes block for 25s. While the tests do eventually pass successfully, on trybots they take so long that the test suite times out. In the case of BrowserTest.* they eventually call ui_test_utils::NavigateToURLBlockUntilNavigationsComplete which then blocks for far too long
,
Aug 30 2017
+chiniforooshan@ I'm not sure what the current status of tracing is, and if a variant can be ran locally which could let us generate a trace to track down where page loading is slow. Thoughts?
,
Aug 30 2017
Can you please try to first cherry pick https://chromium-review.googlesource.com/c/chromium/src/+/575716 and then cherry pick https://chromium-review.googlesource.com/c/chromium/src/+/643747 and then capture a trace? Thanks!
,
Aug 30 2017
A startup trace of 30s with --mash: https://drive.google.com/a/google.com/file/d/0Bz3HKuYDrDnyTDRvaG9EYk9nVEU/view?usp=sharing A startup trace of 30s without --mash: https://drive.google.com/a/google.com/file/d/0Bz3HKuYDrDnyN2ZnajEwU2FQYmM/view?usp=sharing
,
Feb 26 2018
,
Jun 20 2018
Hey James, I just noticed this issue in my backlog, I'm not sure if it's even valid anymore. Have you been seeing timeout issues with mash_browser_tests at all lately?
,
Jun 20 2018
I haven't seen timeouts recently. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by jonr...@chromium.org
, Aug 3 20172.9 MB
2.9 MB Download