From ace56ce368fa42b3eb496382e7387a47fff5f0a6 Mon Sep 17 00:00:00 2001 From: David Wagner Date: Wed, 15 Apr 2015 18:12:34 +0200 Subject: xmlcoverage: be able to ignore changes to unknown criteria Since a parameter-framework client may set a criterion before calling start(), the logs may show changes to criteria before the coverage script knows the list of criteria. It used to cause an unrecoverable error even with the "--force" option. This option now makes the coverage script ignore such errors. The script already takes the initial values of criteria into account when the parameter-framework starts, so there isn't any information loss. However, if this error happens for any other error than described in the first paragraph, you probably don't want to silence it. Signed-off-by: David Wagner --- tools/coverage/aplog2coverage.sh | 1 + 1 file changed, 1 insertion(+) (limited to 'tools/coverage/aplog2coverage.sh') diff --git a/tools/coverage/aplog2coverage.sh b/tools/coverage/aplog2coverage.sh index 0f0d76e..5e0e59c 100755 --- a/tools/coverage/aplog2coverage.sh +++ b/tools/coverage/aplog2coverage.sh @@ -54,6 +54,7 @@ help () { # Default values outputFile="-" coverage_report_generator_ignorable_errors="\ +--ignore-unknown-criterion \ --ignore-incoherent-criterion-state \ --ignore-ineligible-configuration-application" coverage_report_generator_options="" -- cgit v1.1