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

Issue 642156 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Aug 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

several failures on Mac HDD Perf (5)

Project Member Reported by martiniss@chromium.org, Aug 29 2016

Issue description

Builder: https://uberchromegw.corp.google.com/i/chromium.perf/builders/Mac%20HDD%20Perf%20%285%29?numbuilds=50
Tests: blink_style.top_25, page_cycler_v2.intl_hi_ru, v8.top_25_smooth

Looks like a bot misconfiguration; several log lines like

(INFO) 2016-08-26 22:03:03,225 browser.DumpStateUponFailure:346  *************** BROWSER STANDARD OUTPUT ***************
(INFO) 2016-08-26 22:03:03,226 browser.DumpStateUponFailure:348  2016-08-26 21:55:31.487 Google Chrome[5639:24960] NSWindow warning: adding an unknown subview: <FullSizeContentView: 0x7ffb78693ed0>
2016-08-26 21:55:31.488 Google Chrome[5639:24960] Call stack:
(
    "+callStackSymbols disabled for performance reasons"
)
<<<< VTVideoEncoderSelection >>>> VTSelectAndCreateVideoEncoderInstanceInternal: no video encoder found for 'avc1'

[04:55:32.023] VTSelectAndCreateVideoEncoderInstanceInternal signalled err=-12908 (err) (Video encoder not available) at /SourceCache/CoreMedia_frameworks/CoreMedia-1562.240/Sources/VideoToolbox/VTVideoEncoderSelection.c line 1245
[04:55:32.023] VTCompressionSessionCreate signalled err=-12908 (err) (Could not select and open encoder instance) at /SourceCache/CoreMedia_frameworks/CoreMedia-1562.240/Sources/VideoToolbox/VTCompressionSession.c line 946


It's also failing v8.top_25_smooth.reference and blink_style.top_25.reference, although with different errors. 
 

Comment 1 by d...@chromium.org, Aug 29 2016

Cc: d...@chromium.org
Owner: jo...@chromium.org
Status: Assigned (was: Available)
John redeployed this as part of https://crbug.com/641637. Are there manual steps being done on these after they get deployed?

Comment 2 by jo...@google.com, Aug 29 2016

I think I missed the telemetry keychain (not sure if that's the root cause, but giving it a try).

Comment 3 by jo...@google.com, Aug 30 2016

Status: Fixed (was: Assigned)

Sign in to add a comment