Issue metadata
Sign in to add a comment
|
media.tough_video_cases_extra.reference flaky on Mac 10.10 Perf (4) |
||||||||||||||||||||||||
Issue descriptionRevision range first seen: as far as the bot's history goes, oldest available failure: https://build.chromium.org/p/chromium.perf/builders/Mac%2010.10%20Perf%20%284%29/builds/3082 Link to failing step log: https://build.chromium.org/p/chromium.perf/builders/Mac%2010.10%20Perf%20%284%29/builds/3279/steps/media.tough_video_cases_extra.reference/logs/stdio The failures are due to native crashes on video.html?src=tulip2.ogv: 2016-03-18 04:30:07.403 Google Chrome[8175:19283] NSWindow warning: adding an unknown subview: <FullSizeContentView: 0x7fbc9b103ff0> 2016-03-18 04:30:07.404 Google Chrome[8175:19283] Call stack: ( 0 AppKit 0x00007fff8bf2b54d -[NSThemeFrame addSubview:] + 107 1 AppKit 0x00007fff8bf2b03f -[NSView addSubview:positioned:relativeTo:] + 208 2 Google Chrome Framework 0x0000000110674723 ChromeMain + 51699443 3 Google Chrome Framework 0x000000011067352c ChromeMain + 51694844 4 Google Chrome Framework 0x00000001106dd3c1 ChromeMain + 52128657 5 Google Chrome Framework 0x0000000110631ecc ChromeMain + 51426972 6 Google Chrome Framework 0x000000011063c5c2 ChromeMain + 51469714 7 Google Chrome Framework 0x0000000110741ebc ChromeMain + 52541068 8 Google Chrome Framework 0x000000011077a96f ChromeMain + 52773183 9 Google Chrome Framework 0x0000000110779d98 ChromeMain + 52770152 10 Google Chrome Framework 0x0000000110779870 ChromeMain + 52768832 11 Google Chrome Framework 0x0000000110778cf0 ChromeMain + 52765888 12 Google Chrome Framework 0x00000001107788ff ChromeMain + 52764879 13 Google Chrome Framework 0x00000001107767d2 ChromeMain + 52756386 14 Google Chrome Framework 0x00000001107765a7 ChromeMain + 52755831 15 Google Chrome Framework 0x00000001107759c1 ChromeMain + 52752785 16 Google Chrome Framework 0x000000010d5c41d1 ChromeMain + 645537 17 Google Chrome Framework 0x000000010d5c30ca ChromeMain + 641178 18 Google Chrome Framework 0x00000001109ce1ea ChromeMain + 55212474 19 Google Chrome Framework 0x0000000110c78d27 ChromeMain + 58008823 20 Google Chrome Framework 0x00000001109cc801 ChromeMain + 55205841 21 Google Chrome Framework 0x00000001109d09a0 ChromeMain + 55222640 22 Google Chrome Framework 0x00000001109c9df5 ChromeMain + 55195077 23 Google Chrome Framework 0x000000010da6099c ChromeMain + 5480812 24 Google Chrome Framework 0x000000010da5ff06 ChromeMain + 5478102 25 Google Chrome Framework 0x000000010d526872 ChromeMain + 66 26 Google Chrome 0x000000010d4bfd42 main + 530 27 Google Chrome 0x000000010d4bfb24 Google Chrome + 2852 ) I'm not disabling the benchmark because it's currently failing less than one in five times (https://chromium.googlesource.com/chromium/src/+/master/tools/perf/docs/perf_bot_sheriffing.md#testfailures), namely 3/20 and 15/200 most recent builds. I'm assigning it to the test owner instead. If the test is disabled, please downgrade to Pri-2.
,
Apr 12 2016
Friendly sheriff ping (According to the Perf Bot Sheriffing guide, Pri-1 build bot bugs should be pinged daily. Please close the issue if it's already been fixed or lower its priority.)
,
Apr 12 2016
These tests were disabled some time ago pending an investigation of the actual cause. The reported stack trace is from an unrelated part of code, not the test in question; there is not actually any information about the failure in the log.
,
May 5 2016
The bug that the disabling was associated with is bug 565180 ; merging this bug with that one. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by pras...@chromium.org
, Mar 21 2016