probe: add probe targets replay artifact#197
Merged
Merged
Conversation
piotr-iohk
approved these changes
Jul 17, 2026
piotr-iohk
left a comment
piotr-iohk
left a comment
Collaborator
There was a problem hiding this comment.
LGTM.
nit: we could document the artifact + replay steps in docs/mainnet-probe.md.
pwltr
force-pushed
the
probe/order-artifact
branch
from
July 17, 2026 09:46
4788402 to
fe209cd
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
2 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.
Summary
Since order is now randomized (by default) in the nightly runs this order artifact helps replay failures locally.
artifacts/probe-targets-replay.jsonwriteProbeArtifactsvia artifact state instead of writer optionsTesting
npx eslint test/helpers/probe.ts test/specs/mainnet/probe.e2e.ts