Issue 77723008: Mark flaky debug test as failing.

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 77723008: Mark flaky debug test as failing. (Closed)

Created:
7 years, 1 month ago by Yang

Modified:
7 years, 1 month ago

Reviewers:
Michael Achenbach

CC:
v8-dev

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

Visibility:
Public.

Mark flaky debug test as failing. The issues are known. For the time being, we mark it as failing. R=machenbach@chromium.org BUG=v8:2921, v8:3005 LOG=N Committed: https://code.google.com/p/v8/source/detail?r=17938

Created: 7 years, 1 month ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+1 line, -1 line)			Patch
	M	test/mjsunit/mjsunit.status	View		1 chunk	+1 line, -1 line	0 comments	Download

Total messages: 4 (0 generated)

Yang

On 2013/11/20 15:08:40, Yang wrote: I did some investigation and found that this issue is ...

7 years, 1 month ago (2013-11-20 15:09:33 UTC) #2

Michael Achenbach

LGTM and while you're on it, you could do the same for cctest/test-alloc/CodeRange on win32.

7 years, 1 month ago (2013-11-20 16:30:09 UTC) #3

Yang

7 years, 1 month ago (2013-11-20 17:09:24 UTC) #4

Message was sent while issue was closed.

Committed patchset #1 manually as r17938 (presubmit successful).