jetstream failing on chromium.perf/Android One Perf |
||
Issue descriptionjetstream failing on chromium.perf/Android One Perf Builders failed on: - Android One Perf: https://build.chromium.org/p/chromium.perf/builders/Android%20One%20Perf
,
Aug 23 2017
=== BISECT JOB RESULTS === NO Test failure found Bisect Details Configuration: android_one_perf_bisect Benchmark : jetstream Metric : benchmark_duration/benchmark_duration Revision Exit Code N chromium@494750 0 +- N/A 5 good chromium@494841 0 +- N/A 5 bad To Run This Test src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests jetstream More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8970446089571586864 For feedback, file a bug with component Speed>Bisection
,
Aug 29 2017
This is my fault. I decreased the swarming I/O timeout from a very high 1h to what nednguyen@ and I thought was more reasonable, which was 10m. However, it looks like there's a 14m period during the jetstream benchmark on Android One where no outpput is produced, triggering the I/O timeout. I'm going to add a specific exception for jetstream to increase the I/O timeout to 20m.
,
Aug 30 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/9384395001ad671cb86860e01f0fbf311ff6d0f1 commit 9384395001ad671cb86860e01f0fbf311ff6d0f1 Author: Charlie Andrews <charliea@chromium.org> Date: Wed Aug 30 00:25:56 2017 Add a swarming I/O timeout override for jetstream nednguyen@ and I thought that 10m seemed like a more reasonable I/O timeout forswarming tasks than the previous 1h. However, jetstream goes for 12m in a successful run without giving any output. This adds an exception for jetstream and a way to add future exceptions. Bug: 758309 Change-Id: If1b283ff8f4c07822652dfb22a8970a07f1fb107 Reviewed-on: https://chromium-review.googlesource.com/642346 Reviewed-by: Stephen Martinis <martiniss@chromium.org> Commit-Queue: Charlie Andrews <charliea@chromium.org> Cr-Commit-Position: refs/heads/master@{#498302} [modify] https://crrev.com/9384395001ad671cb86860e01f0fbf311ff6d0f1/testing/buildbot/chromium.perf.fyi.json [modify] https://crrev.com/9384395001ad671cb86860e01f0fbf311ff6d0f1/testing/buildbot/chromium.perf.json [modify] https://crrev.com/9384395001ad671cb86860e01f0fbf311ff6d0f1/tools/perf/core/perf_data_generator.py
,
Aug 30
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||
►
Sign in to add a comment |
||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 23 2017