Repository navigation
Conversation
- `--junit-out PATH` writes JUnit XML from the shared redacted result. Each target is a test case, and run diagnostics get a separate case. Allowed differences pass, policy-disallowed differences fail, and compilation or operational failures are errors. Exit codes are unchanged. - `--suppress-source-content-warnings` silences expected `verify_content` warnings for source-backed files whose byte evidence is unavailable. It applies to all report formats. Errors, non-source warnings, and mismatched digest algorithms stay visible. - The JUnit path is validated against the other output destinations, and the acceptance harness now produces and scans the JUnit artifact for disclosure and determinism. - Document the new options in the README, CI guide, and development guide. Add the 0.6.0 and 0.5.0 changelog entries, and ignore `*.report.xml` and `COMMAND_HISTORY.md`.
- Cover the `--suppress-source-content-warnings` flag end to end: with it, `verify_content` warnings disappear from every output format, while the node diff, aggregate, outcome and exit code stay identical. - Check that the File source-reference change is still reported when its warning is suppressed. - Check that retrieval failures still produce errors and a non-zero exit, so suppression cannot hide real problems. - Unit-test `ResolveFileContentEvidence` and `ResolveMembershipEvidence` across historical, changed, list, recursive and local sources: evidence and retrievals are unchanged, only the warning goes away. - Verify unrelated diagnostics (invalid checksum, unsafe source, no source, mismatched algorithms) are not altered by the option.
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
1 participant
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.
No description provided.