Issue metadata
Sign in to add a comment
|
speedometer failures on chromium.perf Android bots at 447232:447306 |
||||||||||||||||||||||
Issue descriptionspeedometer, speedometer-turbo, and speedometer-ignition all appear to be failing on Android. cc'ing test owners bmeurer, mvstanton, hablich. Revision range first seen: 447232:447306 Link to failing step log: https://luci-milo.appspot.com/buildbot/chromium.perf/Android%20Nexus6%20Perf%20%283%29/4889 for speedometer and speedometer-turbo https://luci-milo.appspot.com/buildbot/chromium.perf/Android%20Nexus6%20Perf%20%281%29/4824 for speedometer-ignition
,
Feb 1 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/2dfbf027e6a3d4aaee892c9897c28bd18a39dabb commit 2dfbf027e6a3d4aaee892c9897c28bd18a39dabb Author: eakuefner <eakuefner@chromium.org> Date: Wed Feb 01 21:12:19 2017 [BotHealth] Disable speedometer benchmarks on Android BUG= 687681 Review-Url: https://codereview.chromium.org/2671463003 Cr-Commit-Position: refs/heads/master@{#447609} [modify] https://crrev.com/2dfbf027e6a3d4aaee892c9897c28bd18a39dabb/tools/perf/benchmarks/speedometer.py
,
Feb 6 2017
Interesting updates in that range: https://chromium.googlesource.com/v8/v8/+/a964fa290053737c492deda9ff60fadc8db80a53 (See catapult changes) And multiple TF changes: https://chromium.googlesource.com/v8/v8/+log/1cae811b..85cebb78 It is interesting that this results in a timeout with all variants though.
,
Feb 6 2017
Hmmm seems several Androids bots are having a bad time: https://chromeperf.appspot.com/report?sid=b92fe96865446761c64ae9e67746040c6147b889f15065297351b655191b8e92 Either something is broken on Arm (I couldn't find a CL in V8 that was Arm specific though) or all devices suddenly got slower. V8 range in question: https://chromium.googlesource.com/v8/v8/+log/5.8.88..5.8.90 Chromium range looks innocent. eakuefner@ is there a way to know how fast the loop in question was, maybe it was already bordering time. Although in that case it should only happen on the lower end of the spectrum (AndroindOne). This would mean that suddenly one test is not properly finishing thus the final state is never reached and a timeout is reached: https://codesearch.chromium.org/chromium/src/tools/perf/benchmarks/speedometer.py?rcl=117ffb323637f7491cc6f4f87e33ff55d4256144&l=70
,
Feb 7 2017
machenbach, any clue what the problem might be?
,
Feb 7 2017
,
Feb 7 2017
,
Feb 7 2017
It's issue 687737 . We should be able to reenable the benchmark now.
,
Feb 7 2017
,
Feb 7 2017
Thanks.
,
Feb 7 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fb4475c5d765d213d057a58276d005f32e00d7cd commit fb4475c5d765d213d057a58276d005f32e00d7cd Author: nednguyen <nednguyen@google.com> Date: Tue Feb 07 17:33:20 2017 Revert of [BotHealth] Disable speedometer benchmarks on Android (patchset #1 id:1 of https://codereview.chromium.org/2671463003/ ) Reason for revert: Should be fixed by Juan with https://codereview.chromium.org/2673483003 Original issue's description: > [BotHealth] Disable speedometer benchmarks on Android > > BUG= 687681 > > Review-Url: https://codereview.chromium.org/2671463003 > Cr-Commit-Position: refs/heads/master@{#447609} > Committed: https://chromium.googlesource.com/chromium/src/+/2dfbf027e6a3d4aaee892c9897c28bd18a39dabb TBR=simonhatch@chromium.org,charliea@chromium.org,eakuefner@chromium.org # Not skipping CQ checks because original CL landed more than 1 days ago. BUG= 687681 Review-Url: https://codereview.chromium.org/2683593003 Cr-Commit-Position: refs/heads/master@{#448655} [modify] https://crrev.com/fb4475c5d765d213d057a58276d005f32e00d7cd/tools/perf/benchmarks/speedometer.py |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by eakuefner@chromium.org
, Feb 1 2017