Issue 229453002: Support returning a Future from a setUp or test body in scheduled_test.

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 229453002: Support returning a Future from a setUp or test body in scheduled_test. (Closed)

Created:
6 years, 8 months ago by nweiz

Modified:
6 years, 8 months ago

Reviewers:
Bob Nystrom, kasperl

CC:
reviews_dartlang.org

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

Visibility:
Public.

Support returning a Future from a setUp or test body in scheduled_test. R=rnystrom@google.com BUG=18088 Committed: https://code.google.com/p/dart/source/detail?r=34849

Created: 6 years, 8 months ago

Download [raw] [tar.bz2]

	Unified diffs	Side-by-side diffs	Stats (+73 lines, -9 lines)			Patch
M	pkg/scheduled_test/CHANGELOG.md	View	1 chunk	+4 lines, -0 lines	0 comments	Download
M	pkg/scheduled_test/lib/scheduled_test.dart	View	3 chunks	+22 lines, -9 lines	0 comments	Download
M	pkg/scheduled_test/test/scheduled_test/set_up_test.dart	View	1 chunk	+27 lines, -0 lines	0 comments	Download
M	pkg/scheduled_test/test/scheduled_test/wrap_future_test.dart	View	1 chunk	+20 lines, -0 lines	0 comments	Download

Total messages: 4 (0 generated)

nweiz

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

6 years, 8 months ago (2014-04-08 22:45:50 UTC) #3

kasperl

6 years, 8 months ago (2014-04-09 05:25:43 UTC) #4

Message was sent while issue was closed.

Looks like this is causing redness on the analyzer build bot.