summaryrefslogtreecommitdiffstats
path: root/.travis.yml
diff options
context:
space:
mode:
authorDavid Wagner <david.wagner@intel.com>2015-04-15 18:12:34 +0200
committerEric Laurent <elaurent@google.com>2015-04-24 13:39:14 -0700
commitace56ce368fa42b3eb496382e7387a47fff5f0a6 (patch)
treee598e9c67e61f30c03d6f8a5a384253b3c56d819 /.travis.yml
parent69c025eb4b42d203b0e6859d5c350cead91d4208 (diff)
downloadexternal_parameter-framework-ace56ce368fa42b3eb496382e7387a47fff5f0a6.zip
external_parameter-framework-ace56ce368fa42b3eb496382e7387a47fff5f0a6.tar.gz
external_parameter-framework-ace56ce368fa42b3eb496382e7387a47fff5f0a6.tar.bz2
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 <david.wagner@intel.com>
Diffstat (limited to '.travis.yml')
0 files changed, 0 insertions, 0 deletions