| 12d9c82b31650d307e3834e435e1f5f54e3832d0 |
|
20-Apr-2015 |
David Wagner <david.wagner@intel.com> |
xml coverage: fix a copy-paste mistake
Commit ccb164c15d0f46fb233b67075f37bede8f8ad855 introduced the possibility to
ignore changes to unknown criterion through an option passed to coverage.py but
a copy-paste mistake swapped the action of this option with the option ignoring
incoherent criterion state changes.
Both flags are set by 'aplog2coverage.sh -f' so the mistake went unnoticed but
it must be fixed nevertheless.
Signed-off-by: David Wagner <david.wagner@intel.com>
/external/parameter-framework/tools/coverage/coverage.py
|
| ace56ce368fa42b3eb496382e7387a47fff5f0a6 |
|
15-Apr-2015 |
David Wagner <david.wagner@intel.com> |
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>
/external/parameter-framework/tools/coverage/coverage.py
|
| 6bd9fcf524e77a1ca7469d6d91c58afd242d388a |
|
27-Mar-2015 |
Kevin Rocard <kevin.rocard@intel.com> |
[coverage] Correct line number msg
When an error occurs during input parsing,
the line number was incorrectly displayed.
In python, enumerating an iterable will yield
an pair of index and a value.
This index starts at 0: next(enumerate([""])) == (0, "")
This index was displayed as the line number.
Add one to the index to get the line number.
Signed-off-by: Kevin Rocard <kevin.rocard@intel.com>
/external/parameter-framework/tools/coverage/coverage.py
|
| 0bb508d358ebe25d61122bde9905db6661591ba0 |
|
27-Mar-2015 |
Kevin Rocard <kevin.rocard@intel.com> |
[coverage]Quote user value in error msgs
Some pfw bug induce empty criterion value,
when log it is dificult to see the the empty
value.
Add quotes around values.
before: Error in criterion
After : Error in criterion ""
Signed-off-by: Kevin Rocard <kevin.rocard@intel.com>
/external/parameter-framework/tools/coverage/coverage.py
|
| 794fea64ed11b6c2b2604c3a0daa374c885f09d6 |
|
10-Feb-2015 |
Kevin Rocard <kevin.rocard@intel.com> |
Use minidom factory methods in xml coverage generator
The exportToXML was creating an minidom.Element using
it's constructor, which is forbidden in the documentation:
> Applications should not instantiate the classes themselves; they should use the creator functions available on the Document object.
http://docs.python.org/library/xml.dom.minidom.html
Since python 3.4 this method no longer works (private interface change)
thus the xml coverage generation was broken.
Fix by calling the recommended method Document.createElement.
See bug: http://bugs.python.org/issue15290
Signed-off-by: Kevin Rocard <kevin.rocard@intel.com>
/external/parameter-framework/tools/coverage/coverage.py
|
| b76c9d6de717a9a1cfd94e7a8eca7ee4a2035cd7 |
|
05-Feb-2014 |
David Wagner <david.wagner@intel.com> |
Change the license to 3-clause BSD
Add license header in all source files and Makefiles,
Add a "COPYING" file containing the license text.
Signed-off-by: David Wagner <david.wagner@intel.com>
/external/parameter-framework/tools/coverage/coverage.py
|
| 804e064dcd02b87e04b9a189422cc14205e8125c |
|
25-Jun-2013 |
Kevin Rocard <kevinx.rocard@intel.com> |
[coverage] Remplace tabulation indentation by spaces
BZ: 115218
The coding style request that file should be indented with spaces not
tabs.
Replaces each tab by 4 spaces.
Change-Id: I15c665bf9a4feeff5512fba9e8c883c378f106a7
Signed-off-by: Kevin Rocard <kevinx.rocard@intel.com>
Reviewed-on: http://android.intel.com:8080/115316
Reviewed-by: Denneulin, Guillaume <guillaume.denneulin@intel.com>
Reviewed-by: De Chivre, Renaud <renaud.de.chivre@intel.com>
Reviewed-by: cactus <cactus@intel.com>
Tested-by: Dixon, CharlesX <charlesx.dixon@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
/external/parameter-framework/tools/coverage/coverage.py
|
| 1dff2e64afb47af468cc211efa229627367789b7 |
|
10-Jun-2013 |
Kevin Rocard <kevinx.rocard@intel.com> |
[coverage] Move coverage generator in it's own folder
BZ: 115218
The coverage report generated script was in the tools folder.
Other files will be used for coverage reports.
Create a coverage folder in order to contain all coverage report
utilities.
Change-Id: I23ed75fb109cd4a5f6804398ef17d99e046fd49d
Signed-off-by: Kevin Rocard <kevinx.rocard@intel.com>
Reviewed-on: http://android.intel.com:8080/114667
Reviewed-by: Denneulin, Guillaume <guillaume.denneulin@intel.com>
Reviewed-by: Gonzalve, Sebastien <sebastien.gonzalve@intel.com>
Reviewed-by: cactus <cactus@intel.com>
Tested-by: Dixon, CharlesX <charlesx.dixon@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
/external/parameter-framework/tools/coverage/coverage.py
|