Skip to content

Add optional threadId to attempt history entries - #86

Open
alexshamrai wants to merge 1 commit into
ctrf-io:mainfrom
alexshamrai:feature/attempt-thread-id
Open

alexshamrai wants to merge 1 commit into
ctrf-io:mainfrom
alexshamrai:feature/attempt-thread-id

Conversation

@alexshamrai

@alexshamrai alexshamrai commented Oct 26, 2026 •

Copy link
Copy Markdown
Contributor

Adds optional threadId to attempt history entries, so each previous attempt can record the thread or worker that executed it (new section 11.12.1). Section 9.25 now says the Test-level threadId describes the final attempt represented by the test object.

Following the review in #74, the two fields share one contract, as Test and history attemptId do: an optional string at both levels, plus a SHOULD to qualify the value with the process or host when test cases run in more than one process or on more than one host. The change adds no rule for an attempt without threadId, and no serial-execution guarantee.

Adds threadId to the retry history of the standalone and inline comprehensive examples, a valid document whose previous and final attempts ran on different workers, and type cases rejecting non-string attempt values. Adds the changelog entries under Unreleased. Closes #74.

Version metadata is unchanged; the new fixtures use the current 0.2.0, leaving the 0.3.0 alignment to the release preparation in #75. The 0.3.0 stack also edits the 9.25 wording, the Test threadId schema description and the Unreleased changelog, and appends to the same normative test files, so bringing this into the stack will need small conflict resolutions. I'm happy to resolve them, or to rebase onto the stack instead.

Attempt history entries can record the thread or worker that executed
them, using the same contract as the Test threadId. The Test threadId
now explicitly describes the final attempt, and producers that run test
cases in more than one process or on more than one host are asked to
qualify threadId values.

No omission rule and no serial-execution guarantee are added.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Proposal: Add optional threadId to retryAttempts entries

1 participant