Skip to content
This repository was archived by the owner on Aug 5, 2022. It is now read-only.

Conversation

@dawagner
Copy link
Contributor

Commit ccb164c 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

Commit ccb164c 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>
@coveralls
Copy link

Coverage Status

Coverage remained the same at 70.13% when pulling 77f3390 on dawagner:xml-coverage-fix into ec4f597 on 01org:master.

@OznOg
Copy link
Contributor

OznOg commented Apr 20, 2015

👍

dawagner added a commit that referenced this pull request Apr 20, 2015
xml coverage: fix a copy-paste mistake

Commit ccb164c 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
@dawagner dawagner merged commit 4c11104 into intel:master Apr 20, 2015
@dawagner dawagner deleted the xml-coverage-fix branch April 20, 2015 09:06
@dawagner dawagner added the bug label May 27, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants