New issue
Advanced search Search tips

Issue 777447 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner: ----
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug



Sign in to add a comment

Widespread interactive_ui_tests timeouts on chromium.win/Win 7 Tests*

Project Member Reported by msw@chromium.org, Oct 23 2017

Issue description

interactive_ui_tests failing on chromium.win/Win 7 Tests x64 (1)

Builders failed on: 
- Win 7 Tests x64 (1): 
  https://build.chromium.org/p/chromium.win/builders/Win%207%20Tests%20x64%20%281%29

The last three cycles have failed numerous inconsistent fixtures:
 https://uberchromegw.corp.google.com/i/chromium.win/builders/Win%207%20Tests%20x64%20%281%29/builds/30235
 https://uberchromegw.corp.google.com/i/chromium.win/builders/Win%207%20Tests%20x64%20%281%29/builds/30236
 https://uberchromegw.corp.google.com/i/chromium.win/builders/Win%207%20Tests%20x64%20%281%29/builds/30237

I'm not sure if any of the CLs for build 30235 are related, possibly:
 crrev.com/c/728479 Make EndpointResolver use OnceCallback.
 crrev.com/c/732106 [headless] Add main_frame_content_updated param to BeginFrame result.

In build 30236, two separate shards failed, so I'm not even sure if it's an issue with a particular bot.
 

Comment 1 by msw@chromium.org, Oct 23 2017

To be clear, the fixtures are timing out...

Comment 2 by msw@chromium.org, Oct 23 2017

Cc: -eseckler@chromium.org -vkuzkokov@chromium.org rouslan@chromium.org
Components: Infra>Platform>Swarming
Labels: Infra-Troopers Type-Bug
Summary: Widespread interactive_ui_tests timeouts on chromium.win/Win 7 Tests* (was: interactive_ui_tests failing on chromium.win/Win 7 Tests x64 (1))
It looks like the same thing is happening flakily on Win7 Tests (1) and Win7 Tests (dbg)(1)
 https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%281%29
  https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%281%29/builds/72706 (1 shard)
  https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%281%29/builds/72708 (2 shards)

 https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%281%29
  https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%281%29/builds/64154 (1 shard)
  https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%281%29/builds/64162 (1 shard)
  https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%281%29/builds/64164 (2 shards)
  https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%281%29/builds/64165 (1 shard, just one fixture)
  https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%281%29/builds/64168 (1 shard)
  
It's usually one shard failing many various fixtures... something might bork test bots? (system dialog, etc?)
I'm going to look for commonalities between the failing fixtures and cls near the start of these timeouts.

Comment 3 by msw@chromium.org, Oct 23 2017

Mergedinto: 774959
Status: Duplicate (was: Available)
grt@ is already taking a look and has a theory.

Sign in to add a comment