New issue
Advanced search Search tips

Issue 857236 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature

Blocked on:
issue 846951



Sign in to add a comment

Flaky test timeouts due to Gaia authentication failures

Project Member Reported by ynovikov@chromium.org, Jun 27 2018

Issue description

I saw several cases of different tests on different bots in last 2 days, so I eventually decided to report this.

Last case that prompted me to report is
https://ci.chromium.org/p/chromium/builders/luci.chromium.try/mac_chromium_rel_ng/81777
[17672:775:0626/193333.236108:WARNING:gaia_auth_fetcher.cc(902)] Could not reach Google Accounts servers: errno -120
[17672:775:0626/193335.792704:WARNING:gaia_auth_fetcher.cc(902)] Could not reach Google Accounts servers: errno -120
[17672:775:0626/193344.722976:WARNING:gaia_auth_fetcher.cc(902)] Could not reach Google Accounts servers: errno -120
[17672:775:0626/193407.696003:WARNING:gaia_auth_fetcher.cc(902)] Could not reach Google Accounts servers: errno -120

Traceback (most recent call last):
  _RunGpuTest at content/test/gpu/gpu_tests/gpu_integration_test.py:132
    self.RunActualGpuTest(url, *args)
  RunActualGpuTest at content/test/gpu/gpu_tests/maps_integration_test.py:97
    action_runner.WaitForJavaScriptCondition('window.startTest != undefined')
  traced_function at third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py:52
    return func(*args, **kwargs)
  WaitForJavaScriptCondition at third_party/catapult/telemetry/telemetry/internal/actions/action_runner.py:261
    return self._tab.WaitForJavaScriptCondition(*args, **kwargs)
  traced_function at third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py:52
    return func(*args, **kwargs)
  WaitForJavaScriptCondition at third_party/catapult/telemetry/telemetry/internal/browser/web_contents.py:239
    return self._inspector_backend.WaitForJavaScriptCondition(*args, **kwargs)
  traced_function at third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py:52
    return func(*args, **kwargs)
  WaitForJavaScriptCondition at third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend.py:302
    e.message + '\n' + debug_message)
TimeoutException: Timed out while waiting 60s for IsJavaScriptExpressionTrue.
Console output:

Locals:
  IsJavaScriptExpressionTrue : <function IsJavaScriptExpressionTrue at 0x11136a410>
  condition                  : 'window.startTest != undefined'
  context_id                 : None
  debug_message              : 'Console output:\n'
  e                          : TimeoutException('Timed out while waiting 60s for IsJavaScriptExpressionTrue.',)
  kwargs                     : {}
  timeout                    : 60

I'm not sure what role authentication plays in running the tests. Ideally, I would want to avoid it if it isn't necessary.
If we have to authenticate during the tests, I would like these failures to be reported as infra failures and not test failures.
 

Comment 1 by kbr@chromium.org, Jun 27 2018

Blockedon: 846951
I don't think the warning from gaia_auth_fetcher.cc is related to any test timeouts. See for example this successful run:

https://ci.chromium.org/p/chromium/builders/luci.chromium.try/mac_chromium_rel_ng/82664

and this passing shard from maps_pixel_test:

https://chromium-swarm.appspot.com/task?id=3e5c456351d21410&refresh=10&show_raw=1

It contains the same warning, but the test passed.

A recent bug fix in  Issue 846951  corrected a source of potential timeouts. We should try to hypothesize why these other random timeouts might be happening, maybe by adding more detailed logging to the test.

Status: WontFix (was: Unconfirmed)
Well, if it's not because of authentication failures, the logs don't have anything else to accuse.
Going to close this bug.

Sign in to add a comment