tools/findit/README - Issue 430943003: [Findit] Plain objects to represent and parse stack trace.

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/findit/README

Issue 430943003: [Findit] Plain objects to represent and parse stack trace. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

Patch Set: 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

OLD	NEW
(Empty)
	1 Usage: python findit.py key, where key is a testcase key in cluster-fuzz. In ord er to use the script, a config file containing API key from cluster-fuzz must be in the same folder as the script. A new API key can be retrieved from https://c luster-fuzz.appspot.com/#help.
	stgao 2014/07/31 01:52:23 How about leaving this file in the fourth patch? T How about leaving this file in the fourth patch? The findit.py is not in this patch yet. jeun 2014/07/31 18:41:14 Done. Show quoted text On 2014/07/31 01:52:23, Shuotao wrote: > How about leaving this file in the fourth patch? > The findit.py is not in this patch yet. Done.
	2 Currently, the script only works for job type linux_asan_chrome_mp (query = Job: linux_asan_chrome_mp). The script works by extracting file and line information from the stacktrace in failed test case, and matching it with cls regression ra nge. If either the regression range or the stacktrace information is not present in the testcase, the script will print out an error message. In a (very) near f uture, it will also look at git/svn blame for error line and possibly function n ames in the cls. Also, it would be able to parse and normalize stacktrace from a ll sources, so that the script would work for all types of job.

OLD	NEW

« no previous file with comments | « no previous file | tools/findit/component_dictionary.py » ('j') | tools/findit/component_dictionary.py » ('J')