Issue 18328002: Test fix - array-feedback.js has a test that only make sense when

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 18328002: Test fix - array-feedback.js has a test that only make sense when (Closed)

Created:
7 years, 5 months ago by mvstanton

Modified:
7 years, 5 months ago

Reviewers:
Hannes Payer (out of office)

CC:
v8-dev

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

Visibility:
Public.

Test fix - array-feedback.js has a test that only make sense when running crankshaft. Allow the test to tolerate --nocrankshaft. BUG= R=hpayer@chromium.org Committed: https://code.google.com/p/v8/source/detail?r=15403

Created: 7 years, 5 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+10 lines, -7 lines)			Patch
	M	test/mjsunit/array-feedback.js	View		1 chunk	+10 lines, -7 lines	0 comments	Download

Total messages: 3 (0 generated)

mvstanton

Hi Hannes, here is the fix for the gcstress issue you saw. thanks! --Michael

7 years, 5 months ago (2013-07-01 07:23:31 UTC) #1

mvstanton

7 years, 5 months ago (2013-07-01 09:00:23 UTC) #3

Message was sent while issue was closed.

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