Issue 149282: Another attempt at correctly marking a debug test that fails in debug...

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Issue 149282: Another attempt at correctly marking a debug test that fails in debug... (Closed)

Created:
11 years, 5 months ago by Mads Ager (chromium)

Modified:
9 years, 7 months ago

Reviewers:
yurys

CC:
v8-dev

Base URL:
http://v8.googlecode.com/svn/branches/bleeding_edge/

Visibility:
Public.

Another attempt at correctly marking a debug test that fails in debug mode on arm. Let's see if we can make the builder green. TBR=yurys@chromium.org Committed: http://code.google.com/p/v8/source/detail?r=2383

Created: 11 years, 5 months ago

		Unified diffs	Side-by-side diffs	Stats (+1 line, -0 lines)
	M	test/mjsunit/mjsunit.status	View	1 chunk	+1 line, -0 lines	0 comments

Total messages: 2 (0 generated)

On 2009/07/07 21:08:00, Mads Ager wrote:
> 

LGTM