|
|
DescriptionDisable blink_perf.canvas on linux.
This has been red going on a week now.
BUG=488059
CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:linux_perf_bisect;tryserver.chromium.perf:mac_perf_bisect;tryserver.chromium.perf:win_perf_bisect;tryserver.chromium.perf:android_nexus5_perf_bisect
Committed: https://crrev.com/2e2d7141b8f141bfb194427afde9fb2bf1ed5486
Cr-Commit-Position: refs/heads/master@{#330085}
Patch Set 1 #
Messages
Total messages: 18 (6 generated)
simonhatch@chromium.org changed reviewers: + sullivan@chromium.org
lgtm
The CQ bit was checked by simonhatch@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1129383007/1
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: mac_perf_bisect on tryserver.chromium.perf (JOB_TIMED_OUT, no build URL) win_perf_bisect on tryserver.chromium.perf (JOB_TIMED_OUT, no build URL)
The CQ bit was checked by simonhatch@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1129383007/1
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: win_perf_bisect on tryserver.chromium.perf (JOB_TIMED_OUT, http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/...)
The CQ bit was checked by simonhatch@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1129383007/1
Message was sent while issue was closed.
Committed patchset #1 (id:1)
Message was sent while issue was closed.
Patchset 1 (id:??) landed as https://crrev.com/2e2d7141b8f141bfb194427afde9fb2bf1ed5486 Cr-Commit-Position: refs/heads/master@{#330085}
Message was sent while issue was closed.
On 2015/05/15 12:56:47, I haz the power (commit-bot) wrote: > Patchset 1 (id:??) landed as > https://crrev.com/2e2d7141b8f141bfb194427afde9fb2bf1ed5486 > Cr-Commit-Position: refs/heads/master@{#330085} I believe https://codereview.chromium.org/1142603002 fixed this issue and the perf bot didn't test the CL yet. http://build.chromium.org/p/chromium.perf/builders/Linux%20Perf%20%284%29?num... I think we should check if the CL fix this issue before landing this CL.
Message was sent while issue was closed.
On 2015/05/15 13:35:16, dshwang wrote: > On 2015/05/15 12:56:47, I haz the power (commit-bot) wrote: > > Patchset 1 (id:??) landed as > > https://crrev.com/2e2d7141b8f141bfb194427afde9fb2bf1ed5486 > > Cr-Commit-Position: refs/heads/master@{#330085} > > I believe https://codereview.chromium.org/1142603002 fixed this issue and the > perf bot didn't test the CL yet. > http://build.chromium.org/p/chromium.perf/builders/Linux%20Perf%20%284%29?num... > > I think we should check if the CL fix this issue before landing this CL. Ah I didn't realize you already had a fix in flight! I'll back this out for now, see if your CL fixes things.
Message was sent while issue was closed.
A revert of this CL (patchset #1 id:1) has been created in https://codereview.chromium.org/1142643002/ by simonhatch@chromium.org. The reason for reverting is: Possible fix has landed, reverting to see if bot goes green.. |