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

Issue 43023: Add a test case for bug 269 (Closed)

Created:
11 years, 9 months ago by Søren Thygesen Gjesse
Modified:
9 years, 7 months ago
CC:
v8-dev
Visibility:
Public.

Description

Patch Set 1 #

Total comments: 2
Unified diffs Side-by-side diffs Delta from patch set Stats (+53 lines, -0 lines) Patch
A test/mjsunit/bugs/bug-269.js View 1 chunk +49 lines, -0 lines 0 comments Download
M test/mjsunit/mjsunit.status View 2 chunks +4 lines, -0 lines 2 comments Download

Messages

Total messages: 3 (0 generated)
Søren Thygesen Gjesse
11 years, 9 months ago (2009-03-10 15:50:30 UTC) #1
Mads Ager (chromium)
LGTM http://codereview.chromium.org/43023/diff/1/3 File test/mjsunit/mjsunit.status (right): http://codereview.chromium.org/43023/diff/1/3#newcode42 Line 42: bugs/bug-269: CRASH, FAIL if $mode == debug ...
11 years, 9 months ago (2009-03-10 19:39:29 UTC) #2
Søren Thygesen Gjesse
11 years, 9 months ago (2009-03-11 08:15:09 UTC) #3
http://codereview.chromium.org/43023/diff/1/3
File test/mjsunit/mjsunit.status (right):

http://codereview.chromium.org/43023/diff/1/3#newcode42
Line 42: bugs/bug-269: CRASH, FAIL if $mode == debug
On 2009/03/10 19:39:29, Mads Ager wrote:
> Do you need this line?  All tests in the bugs directory are expected to fail. 
> Maybe they are not expected to crash?

Exactly, tests in the bugs directory are expected to fail, not crash. I find
this is the right thing to do therefore the extra line.

Powered by Google App Engine
This is Rietveld 408576698