This repository was archived by the owner on Aug 5, 2022. It is now read-only.
xmlcoverage: be able to ignore changes to unknown criteria #99
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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>
Contributor
Author
Contributor
|
👍 |
dawagner
added a commit
that referenced
this pull request
Apr 16, 2015
…rion-option 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.
Contributor
|
👎 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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