From 3774341ff0544497e6e71f405cb222e87f98eb4c Mon Sep 17 00:00:00 2001 From: elenairina Date: Thu, 3 Aug 2017 14:46:37 +0200 Subject: Update doc of ctx.coverage_instrumented. Fixes #3434 PiperOrigin-RevId: 164113116 --- .../com/google/devtools/build/lib/rules/SkylarkRuleContext.java | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) (limited to 'src/main/java/com/google/devtools') diff --git a/src/main/java/com/google/devtools/build/lib/rules/SkylarkRuleContext.java b/src/main/java/com/google/devtools/build/lib/rules/SkylarkRuleContext.java index 51dbdf02bf..10e246e8d6 100644 --- a/src/main/java/com/google/devtools/build/lib/rules/SkylarkRuleContext.java +++ b/src/main/java/com/google/devtools/build/lib/rules/SkylarkRuleContext.java @@ -743,8 +743,11 @@ public final class SkylarkRuleContext implements SkylarkValue { @SkylarkCallable(name = "coverage_instrumented", doc = "Returns whether code coverage instrumentation should be generated when performing " + "compilation actions for this rule or, if target is provided, the rule " - + "specified by that Target. (If a non-rule Target is provided, this returns False.) This " - + "differs from coverage_enabled in the " + + "specified by that Target. (If a non-rule or a Skylark rule Target is provided, this " + + "returns False.) Checks if the sources of the current rule (if no Target is provided) or" + + "the sources of Target should be instrumented based on the --instrumentation_filter and" + + "--instrument_test_targets config settings. " + + "This differs from coverage_enabled in the " + "configuration, which notes whether coverage data collection is enabled for the " + "entire run, but not whether a specific target should be instrumented.", parameters = { -- cgit v1.2.3