testBlinkPerfTracingMetricsForMeasureTime failing on Android Nexus 5 but not 5X (CQ) |
||
Issue descriptiontestBlinkPerfTracingMetricsForMeasureTime failing on Android Nexus 5 (linux_android_rel_ng) but not 5X (android_n5x_swarming_rel) linux_android_rel_ng log: https://chromium-swarm.appspot.com/task?id=35c420b37bd3cf10&refresh=10&show_raw=1 android_n5x_swarming_rel log: https://chromium-swarm.appspot.com/task?id=35c37418936e7c10&refresh=10&show_raw=1 This is super weird, as I don't expect there is much different between the two devices :-/ wangxianzhu@: could it be that the painting code in the test can only run 5x?
,
Apr 26 2017
Maybe just because Nexus 5 is slow and needs a bigger timeout?
,
May 1 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/37edd8a0d254bfecf082744086abe31ffb8cc321 commit 37edd8a0d254bfecf082744086abe31ffb8cc321 Author: nednguyen <nednguyen@google.com> Date: Mon May 01 15:23:45 2017 Simplify test file used by testBlinkPerfTracingMetricsForMeasureFrameTime & enable it on Android This test was failing on Android Nexus 5 device due to the loading taking too long. Simplifying its test case seems to fix the problem. BUG= 715685 TBR=wangxianzhu@chromium.org Review-Url: https://codereview.chromium.org/2849153002 Cr-Commit-Position: refs/heads/master@{#468314} [modify] https://crrev.com/37edd8a0d254bfecf082744086abe31ffb8cc321/third_party/WebKit/PerformanceTests/TestData/color-changes-measure-frame-time.html [modify] https://crrev.com/37edd8a0d254bfecf082744086abe31ffb8cc321/tools/perf/benchmarks/blink_perf_unittest.py
,
May 1 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by sullivan@chromium.org
, Apr 26 2017