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

Issues Search
    My Issues | Starred     Open | Closed | All

Unified Diff: test/cctest/cctest.status

Issue 321001: Fix bug that meant that dependent tests were never reported as... (Closed) Base URL: http://v8.googlecode.com/svn/branches/bleeding_edge/
Patch Set: Created 11 years, 2 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 | « no previous file | test/cctest/test-serialize.cc » ('j') | test/cctest/test-serialize.cc » ('J')
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: test/cctest/cctest.status
===================================================================
--- test/cctest/cctest.status (revision 3112)
+++ test/cctest/cctest.status (working copy)
@@ -33,7 +33,18 @@
# BUG(382): Weird test. Can't guarantee that it never times out.
test-api/ApplyInterruption: PASS || TIMEOUT
+# This is about to go away anyway.
Kasper Lund 2009/10/22 13:33:28 Maybe elaborate (a bit) on why they are going away
+test-serialize/Deserialize: PASS || FAIL
+test-serialize/DeserializeAndRunScript: PASS || FAIL
+test-serialize/DeserializeNatives: PASS || FAIL
+test-serialize/DeserializeExtensions: PASS || FAIL
+# These tests always fail. They are here to test test.py. If
+# they don't fail then test.py has failed.
+test-serialize/TestThatAlwaysFails: FAIL
+test-serialize/DependentTestThatAlwaysFails: FAIL
+
+
[ $arch == arm ]
# BUG(113): Test seems flaky on ARM.
« no previous file with comments | « no previous file | test/cctest/test-serialize.cc » ('j') | test/cctest/test-serialize.cc » ('J')

Powered by Google App Engine
This is Rietveld 408576698