Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(295)

Side by Side Diff: tools/win/new_analyze_warnings/README

Issue 1061663002: Adding batch file and scripts to get new /analyze warnings. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Set executable bit on retrieve_latest_warnings.bat. Created 5 years, 8 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
OLDNEW
(Empty)
1 Use these scripts to retrieve and summarize the latest /analyze warnings
2 from buildbot. Run retrieve_latest_warnings.bat.
3
4 For best results you should have a Chromium repo that can be synced to the
5 state of the tree that produced the latest set of warnings. If you set
6 ANALYZE_REPO to point at such a repo then after the warnings are retrieved,
7 summarized, and diffed the repo will be synced appropriately. Once this
8 process has completed you can investigate the individual warnings. Typical
9 usage is like this:
10
11 > set ANALYZE_REPO=d:\src\analyze_chromium
12 > retrieve_latests_warnings.bat
13
14 For each version that is retrieved three files will be created. The _full.txt
15 file is the raw results and should usually not be looked at. The _summary.txt
16 file is a sorted, grouped, and uniqified copy of the results. The _new.txt
17 file is only created if previous results were found and it contains the diffs.
18 - analyze0067_full.txt
19 - analyze0067_summary.txt
20 - analyze0067_new.txt
OLDNEW
« no previous file with comments | « tools/win/new_analyze_warnings/OWNERS ('k') | tools/win/new_analyze_warnings/retrieve_latest_warnings.bat » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698