Clean up test lists. I cannot reproduce any of these locally. My guess
authorager@chromium.org <ager@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Mon, 17 Jan 2011 13:27:16 +0000 (13:27 +0000)
committerager@chromium.org <ager@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Mon, 17 Jan 2011 13:27:16 +0000 (13:27 +0000)
commit5cc7b5c2db6cfb0128a1a7885c42b9a44fcfb42f
treefddd4498d5f5bfc60d30942c84ef868a970f5fe1
parent3d245133a3ccc09285b975ff3d41a9c62edbe9be
Clean up test lists. I cannot reproduce any of these locally. My guess
is that the mozilla ones were caused by the safe-point table problem
and the deoptimization ones are fixed by adding support for mod and
div.

Let's see if the buildbot agrees.
Review URL: http://codereview.chromium.org/6260007

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@6351 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
test/cctest/cctest.status
test/mozilla/mozilla.status