Issue metadata
Sign in to add a comment
|
cc_perftests failing on multiple builders |
||||||||||||||||||||||
Issue descriptionFiled by sheriff-o-matic@appspot.gserviceaccount.com on behalf of ashleymarie@google.com cc_perftests failing on multiple builders Builders failed on: - Android Nexus5 Perf: https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5%20Perf - Android Nexus6 Perf: https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus6%20Perf - Android Nexus7v2 Perf: https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus7v2%20Perf
,
Jan 19 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14ca89b8840000
,
Jan 20 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/d88ff313cff497b7769ecd1a4c8e5e263ed3fd90 commit d88ff313cff497b7769ecd1a4c8e5e263ed3fd90 Author: Ashley Enstad <ashleymarie@chromium.org> Date: Sat Jan 20 02:15:21 2018 Disabling failing cc_perftests Disabling the following tests until a revert can be made to fix them: RasterBufferProviderCommonPerfTest.BuildTileTaskGraph RasterBufferProviderPerfTests/RasterBufferProviderPerfTest.ScheduleAlternateTasks/0 RasterBufferProviderPerfTests/RasterBufferProviderPerfTest.ScheduleAlternateTasks/1 RasterBufferProviderPerfTests/RasterBufferProviderPerfTest.ScheduleAlternateTasks/2 RasterBufferProviderPerfTests/RasterBufferProviderPerfTest.ScheduleAlternateTasks/3 Bug: 803874 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel Change-Id: Id660d765cf3f69f511cb91c291c273e4a4d3787e Reviewed-on: https://chromium-review.googlesource.com/876506 Reviewed-by: Ned Nguyen <nednguyen@google.com> Reviewed-by: enne <enne@chromium.org> Commit-Queue: Ashley Enstad <ashleymarie@chromium.org> Cr-Commit-Position: refs/heads/master@{#530733} [modify] https://crrev.com/d88ff313cff497b7769ecd1a4c8e5e263ed3fd90/cc/raster/raster_buffer_provider_perftest.cc
,
Jan 20 2018
📍 Found significant differences after each of 2 commits. https://pinpoint-dot-chromeperf.appspot.com/job/14ca89b8840000 [Downloads] Animate checkmark on OfflineGroupHeaderView By huayinz@chromium.org · Thu Jan 18 20:04:36 2018 chromium @ 863a492713b741ae185dbf14bea36cc270cd4b04 Add histograms for total number of quads By ccameron@chromium.org · Thu Jan 18 22:37:04 2018 chromium @ df9acf92e059174204619b3a9828ec3317ef2d15 Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Jan 22 2018
I suspect this is a misattribution. I also don't understand the pinpoint here: This: https://pinpoint-dot-chromeperf.appspot.com/job/14ca89b8840000 doesn't seem to bisect to my change -- it just finds that my change was the one where the build was no longer broken. Am I reading that right? And what exactly is the failure? Is it a crash -- do we have a stack? I 567.452s run_tests_on_device(0a38ca3e) ../../base/test/test_suite.cc:73: Failure I 567.452s run_tests_on_device(0a38ca3e) Value of: TestSuite::IsMarkedMaybe(test_info) I 567.452s run_tests_on_device(0a38ca3e) Actual: true I 567.452s run_tests_on_device(0a38ca3e) Expected: false I 567.452s run_tests_on_device(0a38ca3e) Probably the OS #ifdefs don't include all of the necessary platforms. I 567.452s run_tests_on_device(0a38ca3e) Please ensure that no tests have the MAYBE_ prefix after the code is preprocessed.
,
Jan 23 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ashleymarie@chromium.org
, Jan 19 2018