Issue 498163002: Make benchmark runner understand chromium perf output.

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 498163002: Make benchmark runner understand chromium perf output. (Closed)

Created:
6 years, 4 months ago by Michael Achenbach

Modified:
6 years, 2 months ago

Reviewers:
Benedikt Meurer

CC:
v8-dev

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

Project:
v8

Visibility:
Public.

Make benchmark runner understand chromium perf output. BUG=406405 LOG=n TEST=python -m unittest run_benchmarks_test R=bmeurer@chromium.org Committed: https://code.google.com/p/v8/source/detail?r=24509

Created: 6 years, 2 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+41 lines, -15 lines)			Patch
	M	tools/run_perf.py	View	1	3 chunks	+24 lines, -9 lines	0 comments	Download
	M	tools/unittests/run_perf_test.py	View	1	1 chunk	+17 lines, -6 lines	0 comments	Download

Total messages: 4 (0 generated)

Michael Achenbach

Ping. How about this change now? Or should it be more generic then a graph/trace ...

6 years, 2 months ago (2014-10-09 13:23:51 UTC) #2

Michael Achenbach

6 years, 2 months ago (2014-10-10 07:12:47 UTC) #4

Message was sent while issue was closed.

Committed patchset #2 (id:20001) manually as 24509 (presubmit successful).