Issue 788403005: Mark test with issue number in co19 status file

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 788403005: Mark test with issue number in co19 status file (Closed)

Created:
6 years ago by sigurdm

Modified:
6 years ago

Reviewers:
karlklose, floitsch

CC:
reviews_dartlang.org, floitsch

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

Target Ref:
refs/remotes/git-svn

Visibility:
Public.

Mark test with issue number in co19 status file I think that this bug is the right one, though it seems there is disagreement as to whether you can trust identity of errors/stack traces after rethrow. See: https://codereview.chromium.org/78343002 (Ivans comment) and dartbug.com/18394 that suggests the test is wrong. R=floitsch@google.com Committed: https://code.google.com/p/dart/source/detail?r=42423

Created: 6 years ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+1 line, -1 line)			Patch
	M	tests/co19/co19-dart2js.status	View		2 chunks	+1 line, -1 line	0 comments	Download

Total messages: 6 (2 generated)

sigurdm

6 years ago (2014-12-17 08:32:58 UTC) #6

Message was sent while issue was closed.

Committed patchset #1 (id:1) manually as 42423 (presubmit successful).