tools/run-bisect-perf-regression.cfg - Issue 402433004: Test adding perf week tests as smoothness benchmark

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 402433004: Test adding perf week tests as smoothness benchmark (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src

Patch Set: g cl issue Created 6 years, 4 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:

View unified diff | Download patch | Annotate | Revision Log

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 58 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
69 'bad_revision': '4087.0.0',	69 'bad_revision': '4087.0.0',

70 'metric': 'jslib/jslib',	70 'metric': 'jslib/jslib',

71 'repeat_count': '20',	71 'repeat_count': '20',

72 'max_time_minutes': '20',	72 'max_time_minutes': '20',

73 'truncate_percent': '25',	73 'truncate_percent': '25',

74 }	74 }

75	75

76 """	76 """

77	77

78 config = {	78 config = {

79 'command': '',	79 'command': './tools/perf/run_measurement --browser=release smoothness.perf_wee k',

80 'good_revision': '',	80 'good_revision': '285470',

81 'bad_revision': '',	81 'bad_revision': '285473',

82 'metric': '',	82 'metric': 'invalid/metric',

83 'repeat_count':'',	83 'repeat_count':'1',

84 'max_time_minutes': '',	84 'max_time_minutes': '20',

85 'truncate_percent':'',	85 'truncate_percent':'0',

86 }	86 }

87	87

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

OLD	NEW

« no previous file with comments | « tools/perf/page_sets/perf_week/web-animations-staggered-triggering.html ('k') | no next file » | no next file with comments »