Skip to content

Define global error merge guidance #90

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Ma11hewThomas wants to merge 2 commits into from
Open

Define global error merge guidance #90

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
594c557
Define global error merge guidance
Ma11hewThomas Nov 1, 2026
ee9761d
Keep error merge guidance focused on preservation
Ma11hewThomas Nov 1, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

### Changed

- Defined global error merge guidance: concatenate entries from all input reports without deduplication.

- Formalized the extension model for `extra`, including ownership categories, location-specific definitions, independently versioned official contracts and separate CTRF and extension validation and conformance.

- Clarified output-line arrays and valid omission or empty arrays when no stdout or stderr was captured, on final results and previous attempts.
Expand Down
2 changes: 2 additions & 0 deletions spec/ctrf.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -830,6 +830,8 @@ Global errors MUST NOT be counted as test results.
Consumers MUST account for reported global errors when interpreting the run; passing test results alone do not establish an error-free run.
Omission means no global errors were reported; it does not establish run completeness.

When merging reports, producers SHOULD concatenate `errors` from all input reports without deduplicating entries.

---

### 6.6. `extra`
Expand Down
Loading