Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(44)

Unified Diff: test/mjsunit/mjsunit.status

Issue 2835014: Make the apply.js unit test more resilient to differing stack positions.... (Closed) Base URL: http://v8.googlecode.com/svn/branches/bleeding_edge/
Patch Set: enable test in .status; use booleans in test Created 10 years, 6 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « test/mjsunit/apply.js ('k') | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: test/mjsunit/mjsunit.status
===================================================================
--- test/mjsunit/mjsunit.status (revision 4909)
+++ test/mjsunit/mjsunit.status (working copy)
@@ -34,9 +34,6 @@
# too long to run in debug mode on ARM.
fuzz-natives: PASS, SKIP if ($mode == release || $arch == arm)
-# Issue 494: new snapshot code breaks mjsunit/apply on mac debug snapshot.
-apply: PASS, FAIL if ($system == macos && $mode == debug)
-
zarko 2010/06/22 21:48:20 Is this sufficient to re-enable the test?
Vitaly Repeshko 2010/06/22 22:01:47 I think so, yes. After submitting you can check st
big-object-literal: PASS, SKIP if ($arch == arm)
# Issue 488: this test sometimes times out.
« no previous file with comments | « test/mjsunit/apply.js ('k') | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698