tools/run-bisect-perf-regression.cfg - Issue 18997002: Perf bisect: tentative workaround newline bug.

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

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

Side by Side Diff: tools/run-bisect-perf-regression.cfg

Issue 18997002: Perf bisect: tentative workaround newline bug. (Closed) Base URL: http://git.chromium.org/chromium/src.git@master

Patch Set: Created 7 years, 5 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

OLD	NEW
1 # Copyright (c) 2013 The Chromium Authors. All rights reserved.	1 # Copyright (c) 2013 The Chromium Authors. All rights reserved.

2 # Use of this source code is governed by a BSD-style license that can be	2 # Use of this source code is governed by a BSD-style license that can be

3 # found in the LICENSE file.	3 # found in the LICENSE file.

4	4

5 """Config file for Run Performance Test Bisect Tool	5 """Config file for Run Performance Test Bisect Tool

6	6

7 This script is intended for use by anyone that wants to run a remote bisection	7 This script is intended for use by anyone that wants to run a remote bisection

8 on a range of revisions to look for a performance regression. Modify the config	8 on a range of revisions to look for a performance regression. Modify the config

9 below and add the revision range, performance command, and metric. You can then	9 below and add the revision range, performance command, and metric. You can then

10 run a git try <bot>.	10 run a git try <bot>.

(...skipping 67 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
78	78

79 config = {	79 config = {

80 'command': '',	80 'command': '',

81 'good_revision': '',	81 'good_revision': '',

82 'bad_revision': '',	82 'bad_revision': '',

83 'metric': '',	83 'metric': '',

84 'repeat_count':'',	84 'repeat_count':'',

85 'max_time_minutes': '',	85 'max_time_minutes': '',

86 'truncate_percent':'',	86 'truncate_percent':'',

87 }	87 }

	88

	89 # Workaround git try issue, see crbug.com/257689

OLD	NEW

« no previous file with comments | « no previous file | no next file » | no next file with comments »