New issue
Advanced search Search tips

Issue 676455 link

Starred by 0 users

Issue metadata

Status: Duplicate
Merged: issue 668164
Owner:
Closed: Dec 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: ----



Sign in to add a comment

blink_perf.bindings failing on 8 builders

Project Member Reported by martiniss@chromium.org, Dec 21 2016

Issue description

blink_perf.bindings failing on 8 builders

Type: build-failure

Builders failed on: 
- Win 10 High-DPI Perf: 
  https://build.chromium.org/p/chromium.perf/builders/Win%2010%20High-DPI%20Perf
- Win 10 Perf: 
  https://build.chromium.org/p/chromium.perf/builders/Win%2010%20Perf
- Win 7 ATI GPU Perf: 
  https://build.chromium.org/p/chromium.perf/builders/Win%207%20ATI%20GPU%20Perf
- Win 7 Intel GPU Perf: 
  https://build.chromium.org/p/chromium.perf/builders/Win%207%20Intel%20GPU%20Perf
- Win 7 Nvidia GPU Perf: 
  https://build.chromium.org/p/chromium.perf/builders/Win%207%20Nvidia%20GPU%20Perf
- Win 7 x64 Perf: 
  https://build.chromium.org/p/chromium.perf/builders/Win%207%20x64%20Perf
- Win 8 Perf: 
  https://build.chromium.org/p/chromium.perf/builders/Win%208%20Perf
- Win Zenbook Perf: 
  https://build.chromium.org/p/chromium.perf/builders/Win%20Zenbook%20Perf

Two tests seem to be failing: 
[  FAILED  ]  structured-clone-long-string-deserialize.html
[  FAILED  ]  structured-clone-long-string-serialize.html

I'll start a bisect and disable.

cc-ed owners.



 
Labels: -undefined Performance-Sheriff-BotHealth
Forgot to set the bug in the bisect. https://chromeperf.appspot.com/buildbucket_job_status/8992626530318082784 is the relevant bisect.
Owner: mlippautz@chromium.org
mlippautz@, I guess this is a dup of  Issue 668164  .
Could you confirm?

Status: Started (was: Available)
Interesting, this is a new one. Investigating..
Mergedinto: 668164
Status: Duplicate (was: Started)
This looks like a dup of  issue 668164 , yeah. The symptom there is an endless stream of incremental marking steps. 

The mitigation is in flight https://codereview.chromium.org/2592403002/.

A real fix involves some rethinking of how we estimate wrapper tracing marking step sizes.

Sign in to add a comment