tools/llvm_coverage.sh - Issue 1213063009: Add scripts for running LLVM coverage

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/llvm_coverage.sh

Issue 1213063009: Add scripts for running LLVM coverage (Closed) Base URL: https://skia.googlesource.com/skia.git@master

Patch Set: remove accidentally-include script Created 5 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
(Empty)
	1 #!/bin/sh

	2 # Copyright (c) 2015 The Chromium Authors. All rights reserved.

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

	4 # found in the LICENSE file.

	5

	6 # Run from Skia repo like this:

	7 # $ tools/llvm_coverage.sh dm

	8 # or

	9 # $ tools/llvm_coverage.sh nanobench

	10

	11 set -x

	12 set -e

	13

	14 make clean

	15 tools/llvm_coverage_build $1
	mtklein 2015/07/01 20:17:37 Any reason not to fold tools/llvm_coverage_build r Any reason not to fold tools/llvm_coverage_build right into here? Not sure it ever makes sense to have build-only coverage bots. borenet 2015/07/06 12:06:35 My plan is to run this bot as a new "coverage" fla Show quoted text On 2015/07/01 20:17:37, mtklein wrote: > Any reason not to fold tools/llvm_coverage_build right into here? Not sure it > ever makes sense to have build-only coverage bots. My plan is to run this bot as a new "coverage" flavor of the same recipe we use for all bots. That requires that we build and run separately.
	16 python tools/llvm_coverage_run.py $@

OLD	NEW