Issue 7329016: Updated status file for test262 to latest revision.

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 7329016: Updated status file for test262 to latest revision. (Closed)

Created:
9 years, 5 months ago by Michael Starzinger (Google)

Modified:
9 years, 5 months ago

Reviewers:
Rico

CC:
v8-dev

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

Visibility:
Public.

Description

Updated status file for test262 to latest revision. R=ricow@chromium.org BUG= TEST=

Patch Set 1 #

Created: 9 years, 5 months ago

Download [raw] [tar.bz2]

	Unified diffs	Side-by-side diffs	Stats (+141 lines, -151 lines)			Patch
M	test/test262/README	View	1 chunk	+2 lines, -2 lines	0 comments	Download
M	test/test262/harness-adapt.js	View	1 chunk	+1 line, -1 line	0 comments	Download
M	test/test262/test262.status	View	22 chunks	+138 lines, -148 lines	0 comments	Download

Messages

Total messages: 2 (0 generated)

Expand Messages | Collapse Messages

Rico

9 years, 5 months ago (2011-07-08 09:25:11 UTC) #2

LGTM
I am fine with committing this as is, but we should probably try to update the
status file with V8 issue numbers for all the failures in cases where it is
actually real failures (e.g. I see a lot of Object.defineProperty bug, we should
put bug numbers in the status files and file new ones where existing ones do not
cover them)

Expand Messages | Collapse Messages