Conversation
Contributor
Author
|
The other test failures in the system PVA test - the configure test seems a bit flaky now, but the exports test always fails. It looks like the With the exception: |
b652e8e to
383d41a
Compare
1d0e5fb to
75b7c89
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Updating p4p to version 4 has resulted in some subtle changes to the string representation of the PV Values.
Outstanding issue related to empty strings - the counter demo block has values e.g.:
string[] required = {0}[]Whereas setting
"required": []in the expected string yields:string[] required = {?}[]I'm not sure how to replace the question mark with a zero-sized array. As this results in the failure during comparison: