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

Issue 842978 link

Starred by 1 user
Status: Duplicate
Merged: issue 843199
Owner: ----
Closed: May 2018
Cc:
perezju@chromium.org
█ kereliuk@chromium.org
█ nednguyen@chromium.org
johnchen@chromium.org
jbudorick@chromium.org
st...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug



Sign in to add a comment

chromedriver_py_tests, telemetry_perf_unittests, telemetry_unittests flaky on win7_chromium_rel_ng

Project Member Reported by ynovikov@chromium.org, May 15 2018 
In https://chromium-review.googlesource.com/c/chromium/src/+/1058172 these tests failed during
https://ci.chromium.org/buildbot/tryserver.chromium.win/win7_chromium_rel_ng/166991
but passed during
https://ci.chromium.org/buildbot/tryserver.chromium.win/win7_chromium_rel_ng/167159

chromedriver_py_tests, telemetry_perf_unittests, telemetry_unittests were flaky due to timeouted or expired Swarming tasks.
All shards timed out, the common theme seems to be not being able to restart browser.

Seeing similar failures in 30 out of last 200 jobs.

Comment 1 by ynovikov@chromium.org, May 15 2018

Cc: nednguyen@chromium.org

Comment 2 by ynovikov@chromium.org, May 15 2018

Cc: perezju@chromium.org kereliuk@chromium.org johnchen@chromium.org jbudorick@chromium.org st...@chromium.org
Just happened to me in both tries on my CL.
https://ci.chromium.org/buildbot/tryserver.chromium.win/win7_chromium_rel_ng/167863
https://ci.chromium.org/buildbot/tryserver.chromium.win/win7_chromium_rel_ng/168036

Very annoying.

Comment 3 by st...@chromium.org, May 15 2018

Summary: INVALID_TEST_RESULTS (was: chromedriver_py_tests, telemetry_perf_unittests, telemetry_unittests flaky on win7_chromium_rel_ng)
hromedriver_py_tests, telemetry_perf_unittests, telemetry_unittests flaky on win7_chromium_rel_ng due to timeouted or expired Swarming tasks.


This belongs to the category INVALID_TEST_RESULTS I mentioned in the tech talk this morning.
This category covers ~20% of failed builds that are retried and succeeded in CQ.

Comment 4 by st...@chromium.org, May 15 2018

Summary: INVALID_TEST_RESULTS covers ~20% of failed builds that are retried and succeeded in CQ. (was: INVALID_TEST_RESULTS)

Comment 5 by st...@chromium.org, May 15 2018

Description: Show this description

Comment 6 by st...@chromium.org, May 15 2018

Components: Infra>Client>Chrome

Comment 7 by ynovikov@chromium.org, May 15 2018 

stgao@, I don't understand why did you change the description.
INVALID_TEST_RESULTS is not the problem, the problem is that browser fails to start.

Comment 8 by ynovikov@chromium.org, May 15 2018 

Also, looks like because of all the retries, win7_chromium_rel_ng is out of capacity right now. Perhaps it needs to be throttled.

Comment 9 by st...@chromium.org, May 15 2018

Summary: chromedriver_py_tests, telemetry_perf_unittests, telemetry_unittests flaky on win7_chromium_rel_ng (was: INVALID_TEST_RESULTS covers ~20% of failed builds that are retried and succeeded in CQ.)
(I thought this is a general issue besides those tests. I will file a separate bug.)
Reverted the summary description.

Comment 10 by ynovikov@chromium.org, May 15 2018 

To emphasize, these 3 test suits always fail together.
Sometimes there are other failures in the build, but often it is just these 3.

Comment 11 by ynovikov@chromium.org, May 15 2018 

This could possibly be related to  issue 843199 , which is also Win7 specific and browser fails to start.

Comment 12 by ynovikov@chromium.org, May 15 2018

Mergedinto: 843199
Status: Duplicate (was: Untriaged)
►

Sign in to add a comment