Issue 418033006: Handle bad data in analysis server integration tests.

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 418033006: Handle bad data in analysis server integration tests. (Closed)

Created:
6 years, 5 months ago by Paul Berry

Modified:
6 years, 5 months ago

Reviewers:
jwren, scheglov

CC:
reviews_dartlang.org

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

Visibility:
Public.

More Reviews

Description

Handle bad data in analysis server integration tests. If bad data is received from the analysis server (e.g. a stacktrace), switch on debugging output, let the integration test run for 1 more second (to collect the entire stacktrace), and then fail the integration test. R=scheglov@google.com Committed: https://code.google.com/p/dart/source/detail?r=38545

Patch Set 1 #

Created: 6 years, 5 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+38 lines, -3 lines)			Patch
	M	pkg/analysis_server/test/integration/integration_tests.dart	View		4 chunks	+38 lines, -3 lines	0 comments	Download

Messages

Total messages: 3 (0 generated)

Expand Messages | Collapse Messages

Paul Berry

6 years, 5 months ago (2014-07-24 17:39:30 UTC) #3

Message was sent while issue was closed.

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

Expand Messages | Collapse Messages