Issue 479703002: Remove reliability test data.

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 479703002: Remove reliability test data. (Closed)

Created:
6 years, 4 months ago by Lei Zhang

Modified:
6 years, 4 months ago

Reviewers:
Avi (use Gerrit)

CC:
chromium-reviews

Base URL:
svn://svn.chromium.org/chrome/trunk/src

Project:
chromium

Visibility:
Public.

Remove reliability test data. Reliability tests have been dead for a while. Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=291312

Created: 6 years, 4 months ago

Download [raw] [tar.bz2]

	Unified diffs	Side-by-side diffs	Stats (+0 lines, -232 lines)			Patch
D	chrome/test/data/reliability/known_crashes.txt	View	1 chunk	+0 lines, -212 lines	0 comments	Download
D	chrome/test/data/reliability/sample_pages/page1.html	View	1 chunk	+0 lines, -10 lines	0 comments	Download
D	chrome/test/data/reliability/sample_pages/page2.html	View	1 chunk	+0 lines, -10 lines	0 comments	Download

Total messages: 6 (0 generated)

commit-bot: I haz the power

CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/thestig@chromium.org/479703002/1

6 years, 4 months ago (2014-08-21 23:21:41 UTC) #4

commit-bot: I haz the power

FYI, CQ is re-trying this CL (attempt #1). The failing builders are: win_chromium_x64_rel_swarming on tryserver.chromium.win ...

6 years, 4 months ago (2014-08-22 00:33:00 UTC) #5

Message was sent while issue was closed.

Committed patchset #1 (1) as 291312