do-not-merge/testing-nuts-failure-logs - #343
Open
nico-pappagianis wants to merge 1 commit into
Open
Conversation
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.
Do not merge. Throwaway PR to trigger CI and verify the new NUT failure-logging output.
Only change is a comment appended to README.md — the point is to run the
nutsandxNuts-plugin-agentjobs and confirm:[NUT-CONTEXT]appears in both jobs (every run) with orgId + pod + UTC timestamp.[NUT-FAILURE]appears for the deterministic z3 failure inxNuts-plugin-agent(and for the agentsnutscreate-agent test if the scratch org lands on an affected pod).Grep the job logs for
[NUT-CONTEXT]/[NUT-FAILURE]. Close without merging when done.