fast/js/regress/to-int32-boolean.html is timing out |
||||
Issue descriptionPlease refer to: https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Linux%20Trusty/builds/13374 https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Mac10.11%20%28retina%29/builds/3576 https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Mac10.11/builds/5260 It seems to be related to this v8 roll: https://codereview.chromium.org/2050663002 ccing to v8 sheriffs.
,
Jun 8 2016
Assigning to one of the v8 sheriffs so that it has an owner and doesn't get forgotten.
,
Jun 9 2016
Should be fixed by https://chromium.googlesource.com/v8/v8/+/7f7918d3732515193fa417fb71da09e777a5983e Toon, can you please remove the timeout mark again when the fix has rolled?
,
Jun 21 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/bfa362418c015768ba8314038760c79cf46d6fd5 commit bfa362418c015768ba8314038760c79cf46d6fd5 Author: verwaest <verwaest@chromium.org> Date: Tue Jun 21 13:55:12 2016 Revert of Mark fast/js/regress/to-int32-boolean.html as timeout (patchset #2 id:20001 of https://codereview.chromium.org/2054493002/ ) Reason for revert: This was fixed soon after. Original issue's description: > Mark fast/js/regress/to-int32-boolean.html as timeout > > This test seems to be timed out in multiple bots > > BUG= 618399 > NOTRY=true > TBR=machenbach@chromium.org, vogelheim@chromium.org > > Committed: https://crrev.com/57055bee86b5bbfbe138ac592eed0e9d7d9a423c > Cr-Commit-Position: refs/heads/master@{#398647} TBR=machenbach@chromium.org,vogelheim@chromium.org,xidachen@chromium.org # Not skipping CQ checks because original CL landed more than 1 days ago. BUG= 618399 Review-Url: https://codereview.chromium.org/2084003002 Cr-Commit-Position: refs/heads/master@{#400981} [modify] https://crrev.com/bfa362418c015768ba8314038760c79cf46d6fd5/third_party/WebKit/LayoutTests/TestExpectations
,
Jun 22 2016
|
||||
►
Sign in to add a comment |
||||
Comment 1 by bugdroid1@chromium.org
, Jun 8 2016